Skip to main content
Glama

meta_ads_insights_breakdown

Retrieve ad delivery metrics (impressions, clicks, spend, conversions) for a campaign, segmented by audience dimensions like age, gender, country, or device platform. Ideal for ad-hoc performance analysis across specific breakdowns.

Instructions

Pulls delivery metrics for a campaign broken down along one dimension (age, gender, device_platform, placement, country, region, etc.). Returns rows with the breakdown key plus impressions, clicks, spend, cpc, ctr, conversions, and cost_per_conversion. Read-only. Use this for ad-hoc slicing; for pre-packaged splits use the dedicated meta_ads_analysis_audience (age/gender) or meta_ads_analysis_placements tools, which add interpretation.

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.
campaign_idYesCampaign to break down.
breakdownNoDimension to split by. Meta accepts a single breakdown or a small set joined by commas (e.g. 'age,gender'). Some combinations are rejected by Meta — stick to one breakdown per call when unsure.
periodNoAnalysis window. Accepts Meta predefined ranges ('today', 'yesterday', 'last_7d', 'last_14d', 'last_30d' (default), 'last_90d') or explicit 'YYYY-MM-DD..YYYY-MM-DD'. Longer windows cost more Graph API quota.
Behavior4/5

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

No annotations provided, so description carries full burden. It declares read-only nature and lists output metrics, but could add more on error handling or quota implications.

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 action and output, followed by usage guidance. No redundant information; every sentence earns its place.

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?

With no output schema or annotations, description covers purpose, output metrics, and alternatives. Missing details on pagination or error cases but sufficient for basic use.

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%, baseline 3. Description adds value by explaining breakdown usage (single vs comma-separated) and warning about rejected combinations, enhancing parameter understanding.

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 it pulls delivery metrics for a campaign broken down along one dimension, lists possible breakdown dimensions and returned metrics, and distinguishes from sibling tools by naming alternatives.

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 use (ad-hoc slicing) and when not to use (pre-packaged splits), and names specific alternative tools with their purposes.

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