x_ads_list_accountsList X ad accounts accessible with your connected token to retrieve account IDs, names, and approval status. Use this first to identify which ad accounts you can manage.
List X ad accounts the connected token can manage. Returns id, name, approval status. Call this first.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already communicate that this is a safe, non-destructive read. The description adds value by stating the token-management scope and the returned fields, but it does not discuss pagination, rate limits, or error behavior. With annotations covering the safety profile, a mid-range score is appropriate.
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 a single, dense sentence that states the action, scope, returned data, and usage order. There is no redundant or filler text.
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, read-only listing tool, the description covers what the tool returns and how it fits into the workflow. The absence of an output schema is mitigated by explicitly naming the returned fields, and the annotations cover safety and openness.
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 zero parameters and the schema coverage is 100%, so there is no parameter information missing. The description appropriately does not invent parameter details, and the no-parameter baseline applies.
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 a specific verb ('List'), the resource ('X ad accounts'), and the scope ('the connected token can manage'). It also names the returned fields, which separates it from other list-oriented sibling tools like x_ads_list_creatives or x_ads_list_pixels.
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 instruction 'Call this first' explicitly positions the tool as the entry point before other X Ads operations. It gives clear contextual guidance, though it does not explicitly name alternatives or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.