Skip to main content
Glama

Ads Uploader: Meta Ads MCP

List Conversion Definitions

ads_list_conversions
Read-onlyIdempotent

Read pixels, custom conversion definitions and standard event names. This describes available events, not measured conversion totals. Pixels and custom conversions share one bounded cursor page. A 429 carries Retry-After. ROW_QUOTA_EXCEEDED carries the time the quota resets (meta.quota.resetsAt).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>"
    },
    "name": "ads_list_conversions"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOpaque paging.after cursor. Keep filters unchanged.
freshNoBypass the read cache.
limitNo
accountIdYesAd account ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only and idempotent annotations, the description adds useful operational behavior: pixels and custom conversions share a bounded cursor page, a 429 carries Retry-After, and ROW_QUOTA_EXCEEDED includes meta.quota.resetsAt. It does not discuss authorization or the response envelope, but it provides substantial behavior beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is five short, front-loaded sentences with no filler. It moves efficiently from purpose to scope disambiguation to pagination and error behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with no output schema, the description covers the returned resource categories, pagination behavior, and important error cases. It could be slightly more complete by describing the response envelope or cursor field, but the core information an agent needs is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75%, which sets a baseline of 3. The description adds pagination context by explaining that pixels and custom conversions share one bounded cursor page, but it does not add per-parameter meaning for accountId, fresh, or limit; those are largely left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with a specific verb, 'Read', and names concrete resources: pixels, custom conversion definitions, and standard event names. The sentence 'This describes available events, not measured conversion totals' usefully disambiguates the tool's scope, though it does not explicitly name a sibling tool it differs from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage boundary by saying this describes available events rather than measured conversion totals, which helps an agent avoid using it for reporting totals. It does not explicitly name an alternative tool to use for measured conversion totals, so it falls short of full when/when-not/alternatives guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.