Skip to main content
Glama

Meta ads: List ads

meta_list_ads
Read-onlyIdempotent

List the ads in a Meta ad set, campaign or whole ad account with what each says: format, primary text, headline, button, link and status. Give one of adset_id, campaign_id or ad_account_id.

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": "meta_list_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
adset_idNoOne ad set's ads (ids from meta_list_ad_sets)
campaign_idNoOne campaign's ads (ids from meta_list_campaigns)
ad_account_idNoInstead: every ad in the account, e.g. act_123 (from meta_list_accounts or the client's linked Meta account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / ad_account_id
      Added value: +{
      +  "description": "Instead: every ad in the account, e.g. act_123 (from meta_list_accounts or the client's linked Meta account)",
      +  "type": "string"
      +}
    • addedInput schema / properties / adset_id / description
      Added value: +"One ad set's ads (ids from meta_list_ad_sets)"
    • addedInput schema / properties / campaign_id / description
      Added value: +"One campaign's ads (ids from meta_list_campaigns)"
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered by structured data. The description adds value by naming the fields returned, which matters since there is no output schema. It says nothing about pagination, result limits, or behavior when multiple ids are supplied.

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?

Two sentences, zero filler: the first covers scope and return content, the second covers the invocation rule. Front-loaded and appropriately sized for a simple list tool.

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 list tool with full schema coverage and no output schema, the description supplies the scope options and the returned fields, which is sufficient to call it correctly. Minor gaps remain around result volume/pagination and whether an account-wide listing is truncated, but nothing essential 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 per-parameter descriptions (including id provenance from meta_list_ad_sets/meta_list_campaigns/meta_list_accounts) do the heavy lifting, giving a baseline of 3. The description adds a one-of constraint between the three selectors that the schema itself does not express (zero required parameters), which is genuine extra meaning.

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 ("List the ads") plus all three supported scopes: ad set, campaign, or whole ad account. The added clause enumerating returned fields (format, primary text, headline, button, link, status) makes the tool's output purpose unambiguous and separates it from status-mutation siblings like meta_set_ad_status.

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?

"Give one of adset_id, campaign_id or ad_account_id" is an explicit usage rule that tells the agent how to invoke it and implicitly that exactly one scope selector is expected. It does not name alternatives or say when not to use it (e.g., use a set/account listing tool first), so it stops short of full routing 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.