meta-ads-mcp

list_saved_audiences

Retrieve reusable targeting presets stored in a Meta ad account, with pagination, field selection, and account ID fallback. Use it to review existing presets for campaign targeting.

Instructions

List saved audiences in the ad account. Saved audiences are reusable targeting presets.

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

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
`account_id`	No	Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.1Oct 21, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}

First observedv1.2.0Mar 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only operation, whether results are paginated (the schema implies it but the description is silent), what the response shape is, or what auth is needed. The semantic definition of 'saved audience' is the only added value.

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 short sentences, front-loaded with the action, and the second sentence earns its place by defining the resource. No filler.

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 4-parameter list tool with no annotations and no output schema, the description is only minimally adequate. It omits pagination behavior and return shape, though the parameter documentation softens the impact since cursoring is described in the schema.

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%, so all four parameters (after, limit, fields, account_id) are fully documented including the env-var fallback. The description adds nothing parameter-level, which is acceptable given the schema does the work – baseline 3.

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?

States a specific verb (List) and resource (saved audiences) scoped to the ad account, and the second sentence clarifies what a saved audience actually is. It does not, however, differentiate from the nearby list_custom_audiences sibling, leaving the agent to infer the distinction.

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

Usage Guidelines2/5

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

No statement of when to use this versus list_custom_audiences or get_saved_audience, no prerequisites, no exclusions. The agent gets a purpose but zero routing guidance despite several plausible alternatives in the sibling set.

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

Deploy Server