distribution.techdistribution.tech

MCP tool

Network coverage

inventory

How well the network reaches your own audience today, per channel: approved creators and posts on sale at a current price, and whether coverage is strong or.

Overview

How well the network reaches your own audience today, per channel: approved creators and posts on sale at a current price, and whether coverage is strong or thin. Counts only, never a creator's identity.

Server
https://app.distribution.tech/api/mcp
Scope
inventory:read
Changes data
No, a read
REST endpoint
GET /inventory

Arguments

This tool takes no arguments.

Call with curl

The server speaks streamable HTTP, so one JSON-RPC tools/call request runs the tool. Set DISTRIBUTION_API_KEY to a key from Developers with the inventory:read scope; the arguments shown are the required ones.

curl
curl -X POST "https://app.distribution.tech/api/mcp" \
  -H "Authorization: Bearer $DISTRIBUTION_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "inventory",
    "arguments": {}
  }
}'

Result

The answer's structuredContent follows the tool's output schema (the same JSON is in its text content). It has these fields:

Result fields of inventory
NameTypeRequiredDescription
segmentsarray of objectYes
unresolvedbooleanYes
coverage_as_ofstring (date-time) or nullYes
channelsarray of objectYes
structuredContent, every field with its type
{
  "segments": [
    {
      "id": "<string>",
      "label": "<string>"
    }
  ],
  "unresolved": false,
  "coverage_as_of": "<date-time>",
  "channels": [
    {
      "channel": "x_creators",
      "label": "<string>",
      "sale": "live",
      "level": "strong",
      "verified_nodes": 0,
      "priced_units": 0,
      "note": "<string>"
    }
  ]
}

Get access

Keys are created in Developers once your brand is approved. Connect an agent to ask for access, then read the agent guide for the full flow.