Tools
Every MCP tool, with its inputs, limits and errors.
The server exposes 12 tools. All of them read data. None of them write.
A client only sees the tools its scopes allow. All data belongs to the workspace you approved.
Account
| Tool | Inputs | Returns | Scope |
|---|---|---|---|
me | none | The team's id and name, and the scopes granted to this connection. | none |
Publications and offers
| Tool | Inputs | Returns | Scope |
|---|---|---|---|
list_publications | limit | Your publications, newest first. | offers:read |
get_publication | publication_id | One publication. | offers:read |
list_offers | publication_id, limit | The offers a publication sponsors: status, payout, budgets and spend. | offers:read |
get_offer | publication_id, offer_id | One offer. | offers:read |
get_offer_stats | publication_id, offer_id | Total spend, spend this month and the number of active agreements. | offers:read |
get_conversion_summary | offer_id, start, end | Verified, paid and reversed subscriber counts and spend for a date range. | offers:read |
get_conversion_summary covers the last 30 days by default. Pass start and end as ISO 8601 date-times to change the range, up to 366 days.
Agreements
| Tool | Inputs | Returns | Scope |
|---|---|---|---|
list_agreements | publication_id, limit | The offers a publication promotes, with status and accepted terms. | agreements:read |
get_agreement | publication_id, agreement_id | One agreement. | agreements:read |
Payouts and balance
| Tool | Inputs | Returns | Scope |
|---|---|---|---|
list_payouts | limit | Your payouts, latest period first. | payouts:read |
get_payout | payout_id | One payout with a line per offer. | payouts:read |
get_balance | none | Balance, reserved and available amounts. | balance:read |
Conventions
- IDs are UUIDs.
- Money is an integer number of cents, with a
currencyfield. - Dates are ISO 8601 in UTC.
limitdefaults to 50. The maximum is 100. List tools are not paginated.- Text written by other users, such as offer names and descriptions, is wrapped in
<untrusted-content>tags. Assistants are told to treat it as data, not as instructions.
Limits
| Limit | Value |
|---|---|
| Tool calls | 30 per minute for each connection (one user, one workspace, one client) |
| Requests before sign-in | 120 per minute for each IP address |
| Calls in one batch | 20 |
| Request body | 256 KB |
Errors
Errors follow JSON-RPC 2.0. Each one carries data.request_id; quote it when you contact support.
| Code | Message | Meaning |
|---|---|---|
-32700 | parse_error | The body is not valid JSON. |
-32600 | invalid_request, batch_too_large | Bad request shape, an empty batch, or more than 20 calls in a batch. |
-32601 | method_not_found | Unknown method or tool, or a tool the connection has no scope for. |
-32602 | invalid_params | A tool argument is missing or invalid. |
-32603 | internal_error | Something failed on our side. |
-32001 | missing_token, invalid_token | Not signed in, or access expired or was revoked. HTTP 401. |
-32004 | not_found | The item does not exist or belongs to another team. |
-32005 | rate_limited | Too many calls. Wait and retry. |
-32006 | payload_too_large | The request body is over 256 KB. HTTP 413. |
Most errors arrive with HTTP 200 and the error in the JSON-RPC body. The per-IP limit is the exception: it returns HTTP 429 with a Retry-After header.