Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ads_get_adset

Retrieve complete details for a single ad set, including targeting configuration and dayparting schedule.

Instructions

Get full details of a single ad set, including targeting and dayparting (adset_schedule).

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": {
      "adset_id": "<adset_id>"
    },
    "name": "ads_get_adset"
  }
}

Input Schema

NameRequiredDescriptionDefault
adset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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 is the only source of behavioral disclosure. It explicitly mentions included details (targeting, dayparting) which adds context about the response, and the verb 'Get' implies a read-only operation. However, it does not explicitly state that it is non-destructive or mention any side effects or permissions.

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 concise sentence that front-loads the action and resource, and then adds valuable specificity about targeting and dayparting. No wasted words.

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 one-parameter get tool with no output schema, the description adequately indicates the return value ('full details') and highlights key fields. It could mention alternative tools or edge cases, but given the simplicity, it is mostly complete.

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 input schema has no description coverage (0%), and the description does not compensate by explaining the adset_id parameter beyond the obvious 'single ad set'. For example, it doesn't specify where the ID comes from or any formatting requirements.

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 uses the specific verb 'Get' and clearly specifies the resource as 'full details of a single ad set'. It differentiates from sibling tools like ads_list_adsets (which lists many) and ads_get_adset_schedule (which focuses only on schedule).

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 ('Get full details of a single ad set') but does not explicitly state when to use it versus alternatives like ads_list_adsets or ads_get_adset_schedule. No exclusions or alternative tool names are given.

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