Meta MCP Server

List Saved Audiences

meta_list_saved_audiences

Read-only

Retrieve saved audiences targeting presets for a specific ad account to view or manage predefined audience segments.

Instructions

Lists saved audiences (targeting presets) for an ad account.

Args:

ad_account_id (string): Ad account ID

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": {
      "ad_account_id": "<ad_account_id>"
    },
    "name": "meta_list_saved_audiences"
  }
}

Input Schema

Name	Required	Description	Default
`ad_account_id`	Yes
`limit`	No
`after`	No
`response_format`	No	Output format: 'markdown' for human-readable or 'json' for machine-readable	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.2Jun 15, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe. The description adds no behavioral context such as pagination, permissions, or response format. It doesn't contradict annotations, but it adds nothing beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief with one sentence and an Args section, but the Args section duplicates schema information and is unnecessary. It's concise but not well-structured as it repeats parameters. It's acceptable but not optimal.

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

Completeness2/5

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

The tool has 4 parameters, 1 required, no output schema. The description provides minimal info: it lists saved audiences for an ad account, but doesn't explain pagination parameters, result format, or any notes on return structure. Given the read-only nature and lack of output schema, more detail on what is returned would be helpful. It's incomplete.

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

Parameters1/5

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

Schema coverage is only 25% (only response_format has description). The description only mentions ad_account_id, which is obvious from the name. It doesn't explain 'after' (pagination cursor), 'limit' (page size), or 'response_format' as the schema does for the latter. The description fails to compensate for low schema coverage.

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?

The description clearly states the verb 'Lists' and the resource 'saved audiences (targeting presets)' for an ad account, distinguishing it from create/delete saved audience tools. However, it doesn't explicitly differentiate from other list tools like meta_list_custom_audiences, but 'saved audiences' is specific enough.

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 guidance on when to use this tool vs alternatives. It doesn't mention other audience tools or provide context like 'use this for read-only retrieval' or 'if you need custom audiences, use meta_list_custom_audiences'. The description only states purpose, not usage context.

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

Deploy Server