Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

audiences_get_saved

Retrieve full details, including targeting JSON, for any saved audience by its ID.

Instructions

Get full detail of a single saved audience (including targeting JSON).

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": {
      "saved_audience_id": "<saved_audience_id>"
    },
    "name": "audiences_get_saved"
  }
}

Input Schema

NameRequiredDescriptionDefault
saved_audience_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of indicating behavior. It clarifies the return content (full detail, including targeting JSON), implying a read operation, but does not disclose error handling, auth requirements, or behavior for nonexistent IDs.

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?

A single, front-loaded sentence with no unnecessary words. Every element earns its place by conveying the operation, the resource, and the key detail (targeting JSON).

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?

For a simple read-by-ID tool with one parameter and no output schema, the description sufficiently covers the main behavior and the notable return detail. It lacks edge-case and permission context, but the low complexity reduces the need for more.

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?

Schema description coverage is 0%, and the description does not elaborate on the saved_audience_id parameter format, source, or how it relates to other audience IDs. The parameter name is self-explanatory, but the description adds no parameter-specific guidance beyond what the schema already shows.

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 a specific verb ('Get'), resource ('a single saved audience'), and scope ('full detail ... including targeting JSON'), which distinguishes it from list-level audience tools and other get-by-ID sibling tools.

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 wording implies this is for retrieving one saved audience by ID, and the 'single' qualifier provides context for when to use it rather than a list tool. However, it does not explicitly name alternatives or 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

Other Tools