meta-ads-mcp

update_audience

Update an existing custom audience's name or description by providing the audience ID. Only specified fields are modified.

Instructions

Update an existing custom audience. Only provided fields will be modified.

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": {
      "audience_id": "<audience_id>"
    },
    "name": "update_audience"
  }
}

Input Schema

Name	Required	Description
`name`	No	New audience name
`audience_id`	Yes	Audience ID to update
`description`	No	New audience description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Mar 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses partial update behavior ('only provided fields will be modified'), which is useful, but omits permissions, error handling, and response format, leaving some behavioral ambiguity.

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 sentences, front-loaded with purpose, with no wasted words. Efficiently conveys the core function and update semantics.

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?

The tool is simple with 3 params and no output schema. The description covers purpose and partial update behavior, but lacks usage guidance, validation, or error context. Adequate for the low complexity, but not thorough.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaning by clarifying that only provided fields are updated, which is not evident from the schema alone and helps the agent understand optional parameter behavior.

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 clearly states the verb 'Update' and the resource 'existing custom audience', distinguishing it from create/delete/get audience tools. It is specific and unambiguous.

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 when to use the tool (to update an existing audience) but provides no explicit guidance on when not to use it or when to prefer alternatives. The context is clear but no exclusions are stated.

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

Deploy Server