Skip to main content
Glama

Reporting overview

reporting_overview
Read-onlyIdempotent

Spend, attributed revenue and named conversion events for the workspace's connected ad accounts on Meta, Google Ads and TikTok. Without dates it returns each account's latest synchronized window with entity settings and status; with entityIds, those exact campaigns, ad groups or ads with their platform and ids, and for a campaign its last seven days against the seven before. lastDays=N covers the last N complete calendar days (today excluded), and from with to covers explicit calendar periods: measured totals for accounts and campaigns, explicit gaps and complete=false when coverage is missing, 93 days at most; exact ad set and ad periods are not available here. An ad set, ad group, ad or keyword over dates is read by performance_period. compare=true returns the period and the one just before it in one read. Other non-overlapping periods are separate reads, and rolling-window totals are not independent periods. Meta results can be visits, leads or clicks rather than purchases, so an acquisition CPA needs the conversion definition. Store orders come from store_revenue. Meta figures count each ad set's own attribution setting, as Ads Manager does; a userStatement naming a window ("7-day click only", "1-day click", "without views", "1-day view", "engaged view") counts Meta's purchases and revenue in it, and one asking click versus view ("view-through") adds both windows beside Ads Manager's figure; the result names the window. When the call's userStatement asks what moved on the ads ("what moved this week", "which ads are dying"), it returns the report of what moved instead, at ad level from each Meta account's latest sync: the ads spending more, less, stopped, dying slowly or at a low ROAS, against the period before.

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": {
      "input": "<input>"
    },
    "name": "reporting_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / input / properties / chart / description
      Previous value: -"Dated reads: draw ad spend and attributed revenue day by day, every account in one currency (per currency only when the person asks per account or currency), each metric against its period before when compare is set. Set it when the person asks for a chart, a trend, an evolution or the days of a period (day by day), not for a figure or a ranking. The screen then shows the days: write the period totals."New value: +"Dated reads: draw spend and attributed revenue day by day in one currency (per currency only if asked per account or currency), against the period before when compare is set. For a chart, a trend or the days of a period, not a figure or a ranking."
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behaviour on top: coverage gaps surface as explicit gaps and complete=false, 93 days maximum, campaign reads default to last seven days versus the prior seven, compare=true returns both periods in one read, and Meta attribution windows can shift what purchases and revenue mean. The alternate 'what moved' mode driven by userStatement is disclosed rather than hidden.

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

Conciseness3/5

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

The purpose is front-loaded, but the body is a dense run-on paragraph where date semantics, attribution caveats, routing rules and the 'what moved' mode all run together. Almost every sentence carries information, yet the lack of structure makes it harder to scan than its length alone would justify.

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 and nested inputs, the description carries most of the burden and largely meets it: it explains what comes back for the no-date case, for entity reads, and that a result names the attribution window used. It does not describe the shape of the 'what moved' report in comparable detail, which is the main residual gap.

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 75%, and the description still adds real meaning: entityIds changes the grain and default date window, lastDays versus from/to are mutually exclusive with UTC-based exclusion of today, and compare changes the shape of every row. It adds less for actionType and currency beyond what the schema already says, leaving a small gap.

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?

States a specific verb-and-resource combination: spend, attributed revenue and named conversion events for the workspace's connected Meta, Google Ads and TikTok accounts. It also names the boundaries against siblings (ad set/ad group/ad/keyword over dates goes to performance_period, store orders go to store_revenue), so an agent can separate it from neighbours without opening another schema.

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?

Explicit routing conditions are given: omit dates for the latest synchronized window, use entityIds for exact campaigns/ad groups/ads, use lastDays for N complete days, use from/to for explicit periods, and use performance_period for ad set/ad/keyword over dates. It also says other non-overlapping periods are separate reads and that rolling-window totals are not independent periods, which pre-empts a common misuse.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.