Meta Ads by Get MCP Ads

meta get ads

meta_get_ads

Read-onlyIdempotent

List ads from a Meta ad account, optionally filtered by ad set, to retrieve ad ID, name, status, and creative reference for campaign oversight.

Instructions

List ads for a Meta ad account, optionally filtered by ad set. Returns ad ID, name, status, and creative reference.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`cursor`	No	Pagination cursor from previous response
`adSetId`	No	Alias for adsetId. If both are supplied, they must match.
`adsetId`	No	Filter by ad set ID; adSetId is also accepted.
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`statusFilter`	No	Filter by native effective_status, not configured status. PAUSED excludes IN_PROCESS, CAMPAIGN_PAUSED and ADSET_PAUSED. Omit for post-creation verification and inspect both returned status fields.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Sep 23, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare a read-only, idempotent, non-destructive operation, so the description does not need to restate safety. It adds some useful return-field context, but it does not disclose pagination behavior or the effective-vs-configured status nuance, which remain in the parameter schema rather than the description.

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 concise sentences with the core action front-loaded and no filler. The return summary is compact and complements, rather than duplicates, the schema and output schema.

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?

Given rich annotations, a full schema with 100% parameter coverage, an output schema, and a clear description, the tool is largely complete for an agent to invoke effectively. It is only slightly incomplete in not providing explicit alternative routing or behavioral caveats beyond what structured fields already handle.

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 100% and parameters like adSetId/adSetId aliasing plus statusFilter semantics are already documented. The description adds only the high-level notion of an optional ad-set filter, matching baseline value over the schema without going further.

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 names a specific verb ('List'), a clear resource ('ads'), a scope ('Meta ad account'), and an optional ad-set filter, making the tool's purpose immediately distinguishable from sibling tools like meta_get_campaigns and meta_get_adsets.

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?

The phrase 'List ads for a Meta ad account, optionally filtered by ad set' gives clear context for when the tool applies. It does not explicitly contrast alternatives such as meta_get_adsets or meta_get_ad_activity, nor does it state when not to use this tool.

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

Deploy Server