distribution.techdistribution.tech
Get a plan

MCP tool

Set the creator guidelines

set_creator_guidelines

Set what every booked creator of one campaign reads: pitch (what the post should get across, up to 800 characters), key_messages, references (https links).

Overview

Set what every booked creator of one campaign reads: pitch (what the post should get across, up to 800 characters), key_messages, references (https links), voice (up to 300 characters), dos and donts (each list up to 8 items of up to 200 characters). Replaces the campaign's guidelines as a whole; a field left out is cleared. An archived campaign is refused (conflict, archived). Creators read the pitch, dos and donts with their proposal and everything once they accept; they never see a price, a budget or an email. campaign_status returns them. Needs an idempotency_key.

Server
https://app.distribution.tech/api/mcp
Scope
campaigns:write
Changes data
Yes, pass an idempotency_key
REST endpoint
POST /campaigns/{id}/creator-guidelines

Arguments

Arguments of set_creator_guidelines
NameTypeRequiredDescription
idempotency_keystringYesYour unique id for this request. Retry with the same id and the same arguments to get the same answer; it never runs twice.
campaign_idstring (uuid)YesThe campaign id from campaign_status or create_campaign.
pitchstringNoWhat the post should get across, a short paragraph.
key_messagesarray of stringNoThe points every post should make, up to 8.
referencesarray of string (uri)NoUp to 8 https links: the product, a launch post, a demo.
voicestringNoThe tone, in a sentence.
dosarray of stringNoWhat the creators should do, up to 8.
dontsarray of stringNoWhat the creators must not do, up to 8.

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 campaigns:write 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": "set_creator_guidelines",
    "arguments": {
      "idempotency_key": "<string>",
      "campaign_id": "<uuid>"
    }
  }
}'

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 set_creator_guidelines
NameTypeRequiredDescription
campaign_idstring (uuid)Yes
creator_guidelinesobjectYes
structuredContent, every field with its type
{
  "campaign_id": "<uuid>",
  "creator_guidelines": {
    "pitch": "<string>",
    "key_messages": [
      "<string>"
    ],
    "references": [
      "<uri>"
    ],
    "voice": "<string>",
    "dos": [
      "<string>"
    ],
    "donts": [
      "<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.