Accounts, IDs, and units
Loading server catalog…. Download catalog
Advarde MCPAvailable subject to your connection’s permissions.
Description: Identify the correct workspace connection before requesting account data or preparing changes.
Documentation: Getting started
Output: See the protocol description and workflow notes below.
Access: Workspace-scoped MCP authentication.
Start with ads_list_accounts
account_id is the Advarde connection UUID returned by ads_list_accounts. It is not the upstream ad-account ID. Campaign, ad-group, and ad IDs come from the relevant resource listings.
Currency and time
Use the account currency and timezone. Money values ending in _micros are integer micros. Use ads_plan_money and ads_plan_schedule for explicit conversions; do not infer currency exchange rates.
Reporting
Follow pagination and use explicit date windows. Missing metrics are unknown, not zero. Recalculate aggregate rates from totals rather than averaging row rates.
Authentication
Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.
For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.
Responses
200Successful protocol response
Inspect result.isError for tool-level failures, even when the HTTP status is 200.
202Notification accepted
MCP notifications return no JSON-RPC response body.
400Invalid request
Check the JSON-RPC envelope, parameters, and protocol version.
406Not acceptable
Accept must include application/json and text/event-stream.
429Rate limited
Wait for the Retry-After interval before making another request.
401Unauthorized
A valid, unexpired MCP bearer token is required.
403Access denied
Your connection needs access to this workspace and the requested operation.