Skip to main content
Glama

Revisions List

revisions_list
Read-only

List version history for a Google Data Studio report or datasource to review changes and track edits over time.

Instructions

Version history of the report (default) or of a datasource (entity_id).

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

Input Schema

NameRequiredDescriptionDefault
entityNoreport
entity_idNo
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds that it returns version history and defaults to reports, but does not disclose ordering, pagination, or what revision metadata is included. With annotations covering the safety profile, this is moderate added value.

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?

The definition is a single front-loaded sentence with no unnecessary wording. The default scope and datasource override are stated immediately.

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?

For a three-parameter list tool with zero schema descriptions, the definition leaves report_id undocumented and does not clarify how entity, entity_id, and report_id interact. The output schema and readOnlyHint cover return values and safety, but invocation semantics remain incomplete.

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. It loosely covers entity and entity_id, but never mentions report_id, leaving one of three parameters unexplained and giving no format or relationship details between the identifiers.

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 clearly states the resource is version history and identifies two scopes: report by default or datasource via entity_id. It does not name a sibling tool or use an explicit verb like 'list', but the purpose is specific enough to distinguish it from most sibling list operations.

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?

It explains how to target a datasource using entity_id and notes that report is the default, which is useful selection guidance. However, it gives no when-to-use/when-not guidance or alternatives among the many sibling list tools.

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