Skip to main content
Glama

get_adset_insights

Retrieve performance insights for a specific ad set, including impressions, clicks, spend, CTR, and custom breakdowns, to analyze and optimize Meta ad set results.

Instructions

Get performance insights for a specific ad set.

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": "get_adset_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoAggregation level: campaign, adset, ad
fieldsNoComma-separated insight fieldsimpressions,clicks,spend,reach,frequency,cpc,cpm,ctr,actions,cost_per_action_type
adset_idYesAd Set ID
filteringNoJSON string for filtering
breakdownsNoBreakdown dimensions: age,gender,country,region,publisher_platform,platform_position,device_platform,comscore_market (replaces dma). Some accounts must opt in in Ads Manager for impression_device, hourly_stats_aggregated_by_audience_time_zone, and frequency_value; empty results do not necessarily mean zero performance.
time_rangeNoJSON string {since,until} in YYYY-MM-DD format
date_presetNoLowercase date preset, for example: today, yesterday, last_7d, last_14d, last_30d, this_month, last_month, this_quarter, last_quarter, this_year, last_year
time_incrementNoTime granularity: all_days, 1, 7, monthly

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.1
    • changedInput schema / properties / breakdowns / description
      Previous value: -"Breakdown dimensions: age,gender,country,region,placement,device_platform"New value: +"Breakdown dimensions: age,gender,country,region,publisher_platform,platform_position,device_platform,comscore_market (replaces dma). Some accounts must opt in in Ads Manager for impression_device, hourly_stats_aggregated_by_audience_time_zone, and frequency_value; empty results do not necessarily mean zero performance."
    • changedInput schema / properties / date_preset / description
      Previous value: -"Date preset: TODAY,YESTERDAY,LAST_7D,LAST_14D,LAST_30D,THIS_MONTH,LAST_MONTH,THIS_QUARTER,LAST_QUARTER,THIS_YEAR,LAST_YEAR"New value: +"Lowercase date preset, for example: today, yesterday, last_7d, last_14d, last_30d, this_month, last_month, this_quarter, last_quarter, this_year, last_year"
  2. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the core action. It does not state that this is a read-only operation, whether results are paginated, how the 8 optional parameters (time_range, breakdowns, filtering) affect the response, or any rate/credit constraints — a significant gap for a data-retrieval tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no wasted words. It is efficient, though arguably under-specified rather than optimally concise.

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?

The schema is fully documented and there is no output schema to explain, so return values need not be described. However, with zero annotations and a large optional-parameter surface, the description leaves behavioral and usage context incomplete for an agent deciding between the several insight tools.

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 description coverage is 100%, so the schema already documents all 8 parameters including their formats (JSON strings, date presets, comma-separated fields). The description adds no syntax or semantic detail beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('performance insights') scoped to 'a specific ad set'. The ad-set scoping implicitly distinguishes it from the sibling insight tools get_account_insights, get_campaign_insights, and get_ad_insights, though it never names them.

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 'specific ad set' phrasing implies the usage context (single-adset performance reporting) but gives no explicit when-to-use guidance, no prerequisites, and does not route the agent to alternatives like get_campaign_insights or get_ad_insights for other levels.

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