Skip to main content
Glama

Report Inspect

report_inspect
Read-only

Inspect a Google Data Studio report to retrieve its identity, navigation, pages, versions, and page fingerprints for accurate editing and conflict checks.

Instructions

Get report identity, navigation, pages, versions and page fingerprints.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "report_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description is consistent with a safe read. It adds useful detail by naming the categories of metadata returned, but it omits behavior an agent would want: what a null report_id does, whether fingerprints are hashes, and how paging or version history is bounded.

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?

One front-loaded sentence with zero filler; every listed noun conveys distinct return content. Nothing is repeated from the title or annotations.

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?

An output schema exists, so the return shape need not be spelled out, and the annotations cover the safety profile. The remaining gap is the single optional parameter whose null default is left entirely unexplained, which is enough ambiguity to matter for a one-parameter lookup tool.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions report_id at all. Its default of null strongly suggests a context-dependent behavior (perhaps a currently open report), but nothing in the description resolves that ambiguity, so it fails to compensate for the undocumented parameter.

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?

The description uses a specific verb ("Get") and enumerates the exact resources returned: identity, navigation, pages, versions and page fingerprints. That makes the scope far clearer than a generic "inspect report", though it never explicitly contrasts itself with siblings like report_content_get or report_audit, which an agent would have to disambiguate on its own.

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?

There is no guidance on when to choose this tool over report_content_get, report_audit, report_links or report_open. The description only says what is returned, so the agent must infer the selection rule from sibling names rather than from any stated condition.

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