meta-ads-mcp

get_campaign_ads

Retrieve all ads for a specific campaign by providing its ID. Optionally specify fields, limit, and pagination cursor.

Instructions

Get all ads belonging to a specific campaign.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_campaign_ads"
  }
}

Input Schema

Name	Required	Description
`after`	No	Pagination cursor for next page
`limit`	No	Number of results (default 25)
`fields`	No	Comma-separated fields to return
`campaign_id`	Yes	Campaign ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Mar 19, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description bears the full burden of behavioral disclosure. It only states the basic purpose and does not mention pagination, response format, rate limits, or any side effects. Since the tool likely returns paginated results (given 'after' and 'limit' parameters), this omission is significant.

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 a single, front-loaded sentence of eight words. It wastes zero words and immediately conveys the action and target, making it highly concise and well-structured.

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

Completeness3/5

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

For a simple listing tool with fully documented parameters and no output schema, the description is minimally adequate. However, it fails to mention that results are paginated or how to retrieve all ads across pages, which is important contextual information for a user expecting 'all ads' in a single response.

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?

The input schema has 100% parameter coverage, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides, but it doesn't need to because all four parameters (campaign_id, after, limit, fields) are already described in the schema.

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?

The description 'Get all ads belonging to a specific campaign' uses a specific verb ('Get'), clearly identifies the resource ('ads'), and scopes it by campaign. This distinguishes it from sibling tools like list_ads (all ads) and get_adset_ads (ads by adset).

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

Usage Guidelines3/5

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

The description implies the tool is used when you need ads for a specific campaign, but it does not explicitly state when to use it over alternatives or provide exclusion criteria. There is no mention of related tools like get_campaign_leads or get_adset_ads, leaving guidance implicit.

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

Deploy Server