TrueClicks

Execute Meta Ads report

meta_ads_execute_report

Read-only

Execute a Meta (Facebook) Marketing API query for one account and return the result rows as TSV (tab-separated, header row + one row per line). The query is Graph API syntax, an edge name plus parameters such as fields=, date_preset=, time_range=. The act_ prefix and access token are added automatically; do not include them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Graph API edge plus parameters. Do not include the act_<accountId> prefix or access_token; they are added automatically. Examples: 'campaigns?fields=name,status,daily_budget'; 'ads?fields=name,adset_id,campaign_id'; 'insights?fields=impressions,clicks,spend&date_preset=last_7d'; 'insights?fields=impressions,clicks,spend&time_range={"since":"2025-01-01","until":"2025-01-31"}'. Account-level queries start with 'me/' (e.g. 'me/adaccounts?fields=name,currency').
`accountId`	Yes	TrueClicks account id (the numeric Id field from the account listing, not the Meta customer id / ClientCustomerId). Must be a Meta account accessible by the connector.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / accountId / description

Previous value: -"Ad platform account ID to query (must be a Meta account accessible by the connector)."New value: +"TrueClicks account id (the numeric Id field from the account listing, not the Meta customer id / ClientCustomerId). Must be a Meta account accessible by the connector."

changedInput schema / properties / query / description

Previous value: -"Graph API edge plus parameters. Do not include the act_<accountId> prefix or access_token — they are added automatically. Examples: 'campaigns?fields=name,status,daily_budget'; 'ads?fields=name,adset_id,campaign_id'; 'insights?fields=impressions,clicks,spend&date_preset=last_7d'; 'insights?fields=impressions,clicks,spend&time_range={\"since\":\"2025-01-01\",\"until\":\"2025-01-31\"}'. Account-level queries start with 'me/' (e.g. 'me/adaccounts?fields=name,currency')."New value: +"Graph API edge plus parameters. Do not include the act_<accountId> prefix or access_token; they are added automatically. Examples: 'campaigns?fields=name,status,daily_budget'; 'ads?fields=name,adset_id,campaign_id'; 'insights?fields=impressions,clicks,spend&date_preset=last_7d'; 'insights?fields=impressions,clicks,spend&time_range={\"since\":\"2025-01-01\",\"until\":\"2025-01-31\"}'. Account-level queries start with 'me/' (e.g. 'me/adaccounts?fields=name,currency')."

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description is transparent that this performs a read-only query (no destructive action) and returns TSV rows. The annotations already mark readOnlyHint and destructiveHint, and the description adds clarity about output format and automatically injected prefixes, covering behavior beyond the annotations without contradiction.

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?

The description is compact and information-dense, with a clear first sentence and practical examples. It is slightly longer than strictly necessary because of the extensive query examples, but those examples directly aid correct usage and do not waste space.

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?

The description covers the essential context: what the tool does, what output format to expect, key parameter disambiguation, and query syntax. Since no output schema is provided, the description compensates by specifying TSV with a header row, which is sufficient for this dynamic report tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are explained in detail: accountId is clearly distinguished from Meta's customer id and provided with context, and query is fully described with syntax rules, examples, and the note that the act_<accountId> prefix and access_token are auto-added. This is strong, concrete parameter guidance that goes beyond the schema.

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 the tool executes a Meta (Facebook) Marketing API query and returns results as TSV. It explicitly differentiates from Google Ads and Microsoft Ads report tools via the Meta-specific naming and API references, so an agent can distinguish it from sibling tools.

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?

The description implicitly signals usage for Meta Ads reports by stating 'Meta (Facebook) Marketing API query' and contrasts with Google/Microsoft siblings in the sibling list. It gives concrete examples but does not explicitly state 'use this when you need Meta Ads data' or compare with other Meta report tools, leaving slightly to inference.

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

All TrueClicks tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but the audit and report tools (e.g., audit_rule_output_table vs audit_rule_output_table_historical vs audit_rule_result vs audit_rule_result_campaign) are closely related and rely on detailed descriptions to differentiate.

Naming Consistency4/5

Naming is generally consistent with snake_case and domain-prefixed groups (google_ads_*, ms_ads_*, perfmon_*), though a few tools are bare nouns (account, task, user) rather than verb-led, which slightly deviates from the dominant pattern.

Tool Count4/5

23 tools is on the higher end but justified for a platform covering multiple ad platforms, audit reports, alerts, and user management; it remains navigable with clear groupings.

Completeness4/5

The tool set comprehensively covers account enumeration, audit results, report execution for major ad platforms, perfmon alerts, pacing targets, tasks, and users. Minor gaps exist (e.g., no create/update/modify operations), but the core analytics and monitoring surface is well covered.

Resources

Need Help?