Retrieve all Meta ad accounts accessible with the current token. Get account ID, name, currency, timezone, and status to identify which accounts to use.
List all Meta ad accounts accessible with the current token. Returns account ID, name, currency, timezone, and status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It clearly indicates a read/list operation and qualifies access scope with 'current token', but it does not explicitly state that it is read-only or disclose rate limits, pagination, or permission requirements beyond token access.
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?
Two concise sentences, with the primary action and scope front-loaded and the second sentence listing useful return fields. There is no filler or redundant content.
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 list endpoint with no output schema, the description is complete enough: it states what is listed, under what auth scope, and what fields will be returned. No critical missing context is apparent.
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 covers 100% of them. With no parameters to document, the baseline is 4; the description appropriately includes no parameter information and focuses on the operation.
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 uses the specific verb 'List' with a clear resource ('all Meta ad accounts') and an explicit scope ('accessible with the current token'). It also names the returned fields, which distinguishes it from sibling account-detail tools like meta_get_account_details.
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 implies when to use this tool: when an agent needs to enumerate the ad accounts available to the current token. However, it does not explicitly mention alternatives or when not to use it, such as when needing a single account's details versus a full list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.