Check current billing status including whether billing is set up, credit balance, Stripe customer ID, and payment method status. Use this to determine if billing setup is needed before making paid API calls.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of conveying behavior. It clearly indicates a read-only status check by using 'Check' and lists the specific data points returned. It does not mention side effects (none expected) or auth requirements, but for a simple status query the transparency is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core function and followed by usage guidance. Every word earns its place; no filler or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description is adequately complete. It states what the tool does, what information it provides, and when to use it. No critical gaps are apparent for an agent to correctly select and invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, so the schema provides no parameter info. The description goes beyond the schema by detailing what the tool returns (billing setup, credit balance, Stripe customer ID, payment method status), giving the agent meaningful context about the output despite no input parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Check current billing status including whether billing is set up, credit balance, Stripe customer ID, and payment method status.' It uses a specific verb ('Check') and resource ('billing status'), and distinguishes itself from sibling tools like setup_billing and purchase_credits by focusing on querying status rather than modifying it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use guidance: 'Use this to determine if billing setup is needed before making paid API calls.' It implies the context and purpose, though it does not explicitly name alternatives (e.g., setup_billing). This is clear but falls short of fully explicit alternative specification.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
There are exact duplicates (get_task_status/tasks_get, list_tasks/tasks_list) and several overlapping analytics, attribution, and semantic search clusters (get_attention_metrics vs get_creative_attention vs get_social_attention; find_similar_moments vs semantic_search_observations; get_campaign_attribution vs get_multi_touch_attribution vs get_roas). Detailed descriptions help, but with 83 tools an agent will frequently struggle to pick the right one.
Most tools follow a snake_case verb_noun pattern (list_devices, create_campaign, delete_webhook), but there are notable inconsistencies: list_* and get_* are used interchangeably for list operations, attention tools mix conventions (get_attention_metrics vs get_creative_attention vs get_social_attention), and the legacy tasks_get/tasks_list names break the established get_task_status/list_tasks pattern.
83 tools is an extreme count for a single MCP server, spanning device management, sensing, campaigns, media buys, attribution, webhooks, billing, API discovery, and AdCP protocol concerns. This is a broad API surface dump rather than a focused tool set, and it would be far better split into several coherent servers.
Despite the enormous surface, core campaign lifecycle is incomplete: create_campaign explicitly tells the agent to use update_campaign to activate a campaign, but no update_campaign tool exists, and there are no list/delete campaign tools. Significant capabilities exist for analytics, attribution, and webhooks, but the primary advertising workflow has a dead end.