Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_saved_audience

Retrieve details of a saved audience using its ID. Specify fields to filter the response.

Instructions

Get details of a specific saved audience by 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": {
      "audience_id": "<audience_id>"
    },
    "name": "get_saved_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields to return
audience_idYesSaved audience ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. 'Get' clearly signals a read-only operation, but it does not disclose other aspects such as return format, pagination, or error handling. The description is minimal and does not enrich the safety profile beyond the obvious read nature.

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?

The description is a single, front-loaded sentence that directly states the action and resource. No wasted words, ideal for a simple getter.

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 low-complexity get-by-ID tool, the description is mostly adequate, but without an output schema or any description of what 'details' includes, the agent may not know what fields are returned by default. The 'fields' parameter hints at configurability, but the description does not clarify the default return structure.

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?

The input schema has 100% coverage with descriptions for both parameters (audience_id and fields), so the tool description adds no additional parameter context. Baseline of 3 applies as the schema does the heavy lifting and the description does not conflict.

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 action (Get details), the resource (saved audience), and the qualifier (specific by ID). This distinguishes it from list_saved_audiences (which lists multiple) and other audience-related tools.

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 usage when a single saved audience ID is known, but it does not explicitly state when to use this tool over alternatives like list_saved_audiences or get_audience. No explicit when-not-to-use guidance is provided, but the purpose is clear enough to infer the primary use case.

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