Skip to main content
Glama

Ads Uploader: Meta Ads MCP

List Insight Fields

ads_list_insight_fields
Read-onlyIdempotent

Discover Ads Insights fields by search, group or ids. Without filters, returns a compact group index and recommended fields. accountId adds the custom conversions of that account. Breakdown IDs belong in ads_query_insights.breakdowns, not fields. A 429 carries Retry-After. ROW_QUOTA_EXCEEDED carries the time the quota resets (meta.quota.resetsAt).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_list_insight_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoExact field IDs whose full entries to return.
kindNoOptional catalog kind. Use breakdown to discover values for query.breakdowns, not query.fields.
groupNoOptional exact catalog group such as delivery, conversions, video, identity, breakdown, or date.
limitNoMaximum catalog entries to return in this offset-based page.
offsetNoZero-based catalog offset for the next field-catalog page.
searchNoOptional text matched against supported field IDs, labels, kinds, and groups.
accountIdNoOptional account for custom conversion definitions. Omit for static discovery without account access.
recommendedNoWhen true, return only catalog entries recommended for common reporting queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, and the description adds behavior the annotations cannot: the default no-filter response shape, the account-scoped side effect of accountId, and error semantics (429 carries Retry-After, ROW_QUOTA_EXCEEDED carries meta.quota.resetsAt). Rate-limit and quota-reset disclosure is exactly the kind of operational context that prevents blind retries.

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?

Five short sentences, each carrying a distinct fact: discovery modes, default behavior, account scoping, breakdown routing, and error payloads. No filler and the most important routing detail appears early.

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

Completeness5/5

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

With 8 optional parameters, no output schema, and pagination handled in the schema, the description still explains what a bare call returns, how account scoping changes results, and how failures surface. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns one step above it by describing the emergent behavior of the empty-parameter case and clarifying that breakdown-kind entries are not query field values. Much of the rest (accountId's meaning) duplicates the schema rather than extending it.

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

Purpose5/5

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

States a specific verb and resource ('Discover Ads Insights fields') and names the three access modes (search, group, ids). It also distinguishes this catalog-discovery tool from the actual query tool by noting that breakdown IDs belong in ads_query_insights.breakdowns, not fields.

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?

Gives concrete calling contexts: no filters yields a compact group index plus recommended fields, and accountId is the switch that pulls in account custom conversions. It also routes breakdown discovery away from query.fields. It stops short of an explicit 'call this before composing a query' statement, but the guidance is otherwise actionable.

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.