list_conversion_event_settingsRetrieve all conversion event definitions in your ad account to audit tracking setup and identify gaps. Use this to verify configured conversions before optimizing campaigns.
List all conversion definitions configured for the current ad account.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | ||
| limit | No |
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 full behavioral burden. It communicates a read-only list operation and the account scope, but it does not disclose pagination, result format, or that 'after' and 'limit' mean the response may not actually contain all definitions at once; the word 'all' may therefore mislead.
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 sentence starting with the verb, front-loading the core purpose with no filler or redundancy. It is appropriately concise for a simple list operation.
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?
A basic invocation is possible since there are no required parameters and the description names the resource and scope. However, with no output schema and no parameter documentation, the agent cannot reliably know the response shape or how to paginate through results, so the definition is only minimally complete.
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?
Schema description coverage is 0%, and the description adds no meaning for the two parameters 'after' and 'limit'. The schema only provides names and types, leaving 'after' completely ambiguous and giving no guidance on how pagination works.
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 states a specific verb ('List'), a clear resource ('conversion definitions'), and a clear scope ('current ad account'). It clearly differentiates this from sibling tools like create_conversion_event_setting or audit_conversion_tracking by indicating enumeration rather than creation or auditing.
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 the tool: when you need to see all conversion definitions for the current ad account. However, it does not explicitly mention alternatives, exclusions, or when another tool such as audit_conversion_tracking or create_conversion_event_setting would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.