Skip to main content
Glama

meta_ads_ad_sets_get

Retrieve complete targeting spec, budget, and configuration for a Meta Ads ad set. Use before updating to merge targeting changes and avoid overwrites.

Instructions

Fetches the full detail record for a single ad set, including the complete targeting spec and budget/bidding configuration. Returns id, name, campaign_id, status, effective_status, daily_budget, lifetime_budget, optimization_goal, billing_event, targeting (full spec), start_time, end_time, and delivery_estimate (if available). Read-only. Call this before meta_ads_ad_sets_update when you plan to modify targeting, so you can merge instead of overwrite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
ad_set_idYesAd set ID to inspect.
Behavior4/5

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

Declares read-only nature and lists returned fields, but does not elaborate on rate limits, error handling, or permission needs. With no annotations, this is sufficient but not exhaustive.

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?

Three sentences: purpose with fields, read-only note, and usage guideline. No wasted words, information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a get tool: lists all returned fields, notes read-only, and provides integration guidance. No output schema needed.

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?

Schema coverage is 100% with parameter descriptions, and the description adds no extra clarification for parameters. Baseline 3 is appropriate.

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 a specific verb 'Fetches' and resource 'ad set', lists returned fields, and distinguishes from sibling tools like meta_ads_ad_sets_list and meta_ads_ad_sets_update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to call this tool (before update to merge targeting) and implies not to call for listing or creation. Provides clear context and alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server