Skip to main content
Glama

Revision Name Current

revision_name_current

Rename the current version of a Google Data Studio report in its version history, giving the active revision a clear label for tracking changes.

Instructions

File > Version history > Name current version.

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": "revision_name_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

D1.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral detail beyond them: it does not say whether an existing named version is overwritten, what name assignment does to subsequent versions, whether permissions are required, or what the response contains. For a mutation tool the description is essentially silent.

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?

It is a single short sentence with no filler and is front-loaded, but the brevity stems from under-specification rather than disciplined editing. There is nothing to trim, yet nothing substantive is conveyed.

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

Completeness1/5

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

A write operation with zero schema description coverage and an output schema present still needs its effect, preconditions, and parameter meanings explained. The description supplies none of these, leaving an agent unable to predict outcomes or pass 'name' correctly.

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

Parameters1/5

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

Schema description coverage is 0% for 2 parameters. The description does not explain whether 'name' is the new label for the current version or an identifier of an existing version, and never mentions 'report_id' at all, so it adds zero meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a UI navigation path ("File > Version history > Name current version") rather than a statement of what the tool does. It restates the title ('Revision Name Current') without saying what 'naming' the current version means operationally or how it differs from the sibling revision_restore.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as revision_restore even though it is the closest sibling. The menu path at best implies where in the product the action lives, which is only weak implied usage context.

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