Skip to main content
Glama
mikusnuz

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_account_insights

Retrieve ad account performance metrics such as impressions, clicks, spend, and reach, aggregated by campaign, ad set, or ad to analyze results.

Instructions

Get performance insights for the ad account. Returns metrics like impressions, clicks, spend, reach, etc.

Input Schema

NameRequiredDescriptionDefault
levelNoAggregation level: campaign, adset, ad
fieldsNoComma-separated insight fieldsimpressions,clicks,spend,reach,frequency,cpc,cpm,ctr,actions,cost_per_action_type
filteringNoJSON string for filtering
account_idNoAd account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
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. Changed3 schema fields changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
    • 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden. It discloses the returned metrics, which is mildly useful, but says nothing about whether this is a read-only operation, required permissions, pagination/row limits, or the caveat that empty results may not mean zero performance (that caveat lives only in the schema).

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?

Two short, front-loaded sentences with no padding; the purpose is stated first. The 'etc.' trailing example list is slightly loose but harmless.

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?

With 8 optional parameters, no output schema, and no annotations, the description is thin: it hints at return content but omits pagination behavior, the interaction between date_preset/time_range/time_increment, and any dependency on account-level defaults. The rich schema compensates for most parameter detail, but the behavioral picture remains incomplete.

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% across all 8 parameters, so the schema already documents levels, fields, filtering, breakdowns, date ranges, and time increment. The description's metric list loosely maps to the `fields` default but adds no syntax, defaults, or constraints beyond what the schema provides; baseline 3 applies.

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 for the ad account') and gives examples of returned metrics. However, it does not differentiate itself from the sibling insight tools (get_campaign_insights, get_adset_insights, get_ad_insights), and 'for the ad account' is misleading given the `level` param allows campaign/adset/ad aggregation, so an agent could confuse it with those siblings.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no exclusions, and never names the alternative insight tools. An agent must infer from the name alone that this is the account-scoped variant rather than the campaign/adset/ad ones.

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