Skip to main content
Glama

Report Rename

report_rename

Rename a Google Data Studio report title in the header, with optional dry-run preview and read-back verification.

Instructions

Rename the report (the title in the header). Verified by read-back. The report description is a settings_set key (reportDescription) on {"kind":"report"}.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
dry_runNo
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already covered; the description adds that the change is verified by read-back, which is real behavioral value. But it omits two significant behaviors visible only in the schema: dry_run defaults to true (so a call may be a no-op), and how a null report_id resolves to a target report. For a mutation tool, those omissions are meaningful.

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 first two sentences are tight and front-load the action plus the verification behavior. The third sentence is cryptic and notation-heavy ("a settings_set key (reportDescription) on {"kind":"report"}") and reads like a fragment rather than guidance.

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

Completeness2/5

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

An output schema exists, so return values needn't be described, but the definition still leaves critical gaps for a 3-parameter mutation: the dry-run default, target resolution via report_id, and what happens when the name already exists. Given zero schema coverage, the description does not do enough to make the tool safely callable.

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%, so the description must carry parameter meaning, and it only explains `name` (the header title). Neither `dry_run` (default true) nor the nullable `report_id` target selector is explained anywhere, leaving an agent to guess whether a call actually mutates.

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 ("Rename the report") and disambiguates what gets renamed ("the title in the header"), which is genuinely clarifying since 'name' is the only documented parameter. It doesn't distinguish itself from the sibling *_rename tools or report_patch, but the verb+resource pairing is unambiguous 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 Guidelines3/5

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

There is an implicit boundary line: the trailing sentence routes report-description edits to settings_set, which implies this tool is only for the header title. However, there is no explicit when-to-use guidance, no mention of report_patch as an alternative, and no statement of prerequisites or when not to call it.

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