CrunchJunkie

get_report_data

Read-only

Assemble a report's live data (KPIs, charts, tables) for a period, pulled from the connected sources exactly as the app does. datePreset and comparePreset default to the report's saved config; widgetIds (from get_report) limits the result to chosen widgets, which matters for large tables (a 500-row table alone can run to about 90,000 characters); brandFilter reads query-based widgets as branded or non-branded only. A widget that could not be read for the period is null, with the reason in _meta.unavailable. Third-party text (URLs, domains, page titles, search queries) is named in untrustedContent. Notes on donuts, sparklines, margins of error, memory-sourced answers, Peec AI counts and report filters arrive in howToRead.

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": {
      "reportId": "<reportId>"
    },
    "name": "get_report_data"
  }
}

Input Schema

Name	Required	Description
`reportId`	Yes	The report id.
`widgetIds`	No	Only these widgets (ids from get_report). Omit for the whole report.
`datePreset`	No	Date range, e.g. "last_month", "last_7_days", "last_30_days", "quarter_to_date", "last_quarter", "year_to_date", "custom_YYYY-MM-DD_YYYY-MM-DD".
`brandFilter`	No	Branded or non-branded only, for the widgets that count search queries or keywords, as if each had that filter. Omit for the widgets as saved.
`comparePreset`	No	Comparison, e.g. "none", "previous_period", "previous_year".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / brandFilter / description

Previous value: -"Read the report's widgets that count search queries or keywords (Search Console and the other sources that can split them) for branded (naming the client's brand terms) or non-branded ones only, as if each widget had that filter; each such widget's aiNote states the terms, and Google's anonymized queries are in neither group. A widget whose figures cannot be split by query comes back null with its code in _meta.unavailable. Omit for the widgets as saved."New value: +"Branded or non-branded only, for the widgets that count search queries or keywords, as if each had that filter. Omit for the widgets as saved."

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: failed widgets are null with the reason in `_meta.unavailable`, third-party text is flagged in `untrustedContent`, and interpretive notes land in `howToRead`. The output-size warning is exactly the kind of non-obvious trait an agent needs.

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?

Front-loaded with purpose, then parameter-by-parameter guidance and finally return-shape notes; nearly every clause carries information. It is a dense single paragraph, and the closing enumeration (donuts, sparklines, margins of error, Peec AI counts) is listy, but it is not padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the burden of explaining the return payload — null widgets, `_meta.unavailable`, `untrustedContent`, `howToRead` — and does so. An agent has enough to call it correctly and interpret the response without guessing.

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 100%, so the baseline is 3, but the description adds real semantics the schema lacks: datePreset and comparePreset fall back to the report's saved config, and brandFilter applies only to query-based widgets. The maxItems of 50 on widgetIds is left to 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?

States a specific verb ('Assemble') and resource ('a report's live data (KPIs, charts, tables) for a period'), with the scope qualifier 'pulled from the connected sources exactly as the app does'. The references to widgetIds '(from get_report)' clarify the relationship to the sibling that returns report structure.

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?

Gives clear conditional guidance: omit widgetIds for the whole report but use it for large tables (with a 90,000-character justification), and omit brandFilter for widgets as saved. It never states an explicit exclusion or names a competing tool for retrieving data, so it stops short of the top band.

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

All CrunchJunkie tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?