Meta MCP Server

Create Saved Audience

meta_create_saved_audience

Create a reusable targeting preset for your ad account by specifying audience name and targeting criteria.

Instructions

Creates a saved audience (reusable targeting preset) for an ad account.

Args:

ad_account_id (string): Ad account ID
name (string): Audience name
targeting (object): Targeting spec object

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": "<name>",
      "targeting": "<targeting>"
    },
    "name": "meta_create_saved_audience"
  }
}

Input Schema

Name	Required	Description	Default
`ad_account_id`	Yes
`name`	Yes
`targeting`	Yes	Targeting specification
`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.6/5.0

Behavior2/5

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

Annotations already indicate a mutating, non-idempotent action. The description only restates 'Creates' without adding details about required permissions, potential errors, response shape, or consequences of repeated calls. It provides no behavioral context beyond what is already implied by the annotations.

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 concise and front-loads the action, but it includes a redundant 'Args:' listing that duplicates the schema's parameter definitions. This structure is functional but could be clearer; it is not overly verbose but also not optimally streamlined.

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?

For a create operation with a nested targeting object and no output schema, this description is incomplete. It doesn't explain what a saved audience is used for, the expected fields of the targeting object, the return value (e.g., created audience ID), or any constraints. An agent would need to consult additional resources or infer from naming to call this tool correctly.

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

Parameters2/5

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

The description lists parameters with generic labels like 'Ad account ID' and 'Audience name', which add little over the schema. The 'targeting' parameter is described only as 'Targeting spec object', leaving the complex structure undocumented. With schema coverage at 50%, the description should compensate but does not, leaving the agent without necessary details for correct invocation.

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 action (creates) and the resource (saved audience), and even clarifies 'reusable targeting preset'. It distinguishes the tool from siblings like meta_create_custom_audience by naming the specific resource type, though it doesn't explicitly contrast it with alternative audience types.

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 versus alternatives such as meta_create_custom_audience or meta_create_lookalike_audience is provided. The description doesn't mention any conditions, prerequisites, or when not to use it, leaving the agent to infer the appropriate context.

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

Deploy Server