Send feedback

Overview

Tell the distribution team about a problem or an idea, with any valid key, without asking the user first. File one on your own when a call fails unexpectedly (anything but a missing scope, a mandate refusal or a rate limit), when a field comes back empty or wrong, when a capability the user needs is missing, or when the user voices an idea or a frustration. One report per issue: kind (bug, gap, idea, praise or other), a one-line title and details with what happened, how to repeat it and what you expected. Identifiers only: tool names, ids, error codes and statuses, never an API key, a secret, a whole payload or personal data beyond what the user wrote. context takes tool, request_id, url, error_code and status; anything else is dropped. Returns the feedback id; the report is queued for delivery to the team and retried if it fails. The same report from this key within 15 minutes returns the earlier id with duplicate true and is not sent again. 20 a brand an hour.

Server

https://app.distribution.tech/api/mcp

Scope

any valid key

Changes data

No, a read

REST endpoint

POST /feedback

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 any valid key scope; the arguments shown are the required ones.

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": "feedback_send",
    "arguments": {
      "kind": "bug",
      "title": "<string>",
      "details": "<string>"
    }
  }
}'

Result

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

{
  "id": "<uuid>",
  "notified": "pending",
  "duplicate": false
}

Other tools

• inventory: Network coverage
• resolve_audience: Resolve an audience
• campaign_status: Campaign status
• evidence: Proof of delivery
• results: Results
• brain_get: Company context
• creators_search: Find creators
• creator_get: One creator
• creator_ask_price: Ask for a price
• plan_quote: Quote a plan
• create_campaign: Start a campaign
• plan_add_creator: Add a creator
• plan_remove_creator: Remove a creator
• plan_move_dates: Move a plan's dates
• plan_swap_creator: Swap a creator
• set_creator_guidelines: Set the creator guidelines
• approve_plan: Approve and get the pay link
• archive_campaign: Archive a campaign
• rename_campaign: Rename a campaign
• delete_campaign: Delete a draft campaign
• feedback_list: Your feedback

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.