Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_async_report

Generate an async insight report for large Meta Ads data queries. Returns a report_run_id to poll with get_async_report.

Instructions

Create an async insight report for large data queries. Returns a report_run_id to poll with get_async_report.

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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: the operation is asynchronous and yields a report_run_id that must be polled via get_async_report. It omits secondary operational context such as whether the report expires, expected latency, permission requirements, or that all 8 parameters are optional (notably no default time window is stated).

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 short sentences with zero filler; the purpose and scope lead, and the essential follow-up action (polling) is stated second. Nothing is redundant with the schema.

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?

There is no output schema, and the description compensates by naming the returned handle (report_run_id) and the tool that consumes it, which is the one piece an agent must know to use this correctly. Remaining gaps — report lifetime, latency, and error behavior — are minor against a 100%-documented input schema.

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% and all 8 parameters are self-documented (including the env-var fallback for account_id and the breakdown opt-in caveat). The description adds no parameter-level meaning at all, so the baseline 3 for a fully-documented schema 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 and resource ('Create an async insight report') plus a scope qualifier ('for large data queries'), which differentiates it from the many synchronous insight siblings like get_account_insights. It names get_async_report but as the polling follow-up rather than as the alternative it replaces, so the differentiation from sync insight tools is implied rather than stated.

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

Usage Guidelines4/5

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

'for large data queries' gives a clear selection condition and the second sentence tells the agent exactly what to do next (poll with get_async_report). However, it never states when NOT to use this tool — e.g. that smaller queries should use get_account_insights/get_campaign_insights instead — so the alternative routing is left to inference.

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