distribution.techdistribution.tech

MCP tool

Resolve an audience

resolve_audience

The audience fit for one of your campaigns (intent_id) or for a profile you describe (product, audience, geography): the audience segments it matches and.

Overview

The audience fit for one of your campaigns (intent_id) or for a profile you describe (product, audience, geography): the audience segments it matches and the coverage per channel. The same check a campaign gets when it starts.

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

Arguments

Arguments of resolve_audience
NameTypeRequiredDescription
intent_idstring (uuid)NoOne of your campaigns. Leave out to describe a profile instead.
productstringNoWhat is being promoted.
audiencestringNoWho it is for, in your words.
geographystringNoWhere the audience is, or worldwide.

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 audience: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": "resolve_audience",
    "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 resolve_audience
NameTypeRequiredDescription
version1Yes
computed_atstring (date-time)Yes
coverage_as_ofstring (date-time) or nullYes
segmentsarray of objectYes
regionsarray of stringYes
unresolvedbooleanYes
channelsarray of objectYes
thinbooleanYes
summarystringYes
structuredContent, every field with its type
{
  "version": 1,
  "computed_at": "<date-time>",
  "coverage_as_of": "<date-time>",
  "segments": [
    {
      "id": "<string>",
      "label": "<string>"
    }
  ],
  "regions": [
    "<string>"
  ],
  "unresolved": false,
  "channels": [
    {
      "channel": "x_creators",
      "label": "<string>",
      "sale": "live",
      "level": "strong",
      "verified_nodes": 0,
      "priced_units": 0,
      "note": "<string>"
    }
  ],
  "thin": false,
  "summary": "<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.