Skip to main content
Glama

Datasource Rename

datasource_rename

Renames a Google Data Studio datasource title in its editor and in Add data/home lists, using a fingerprint check and read-back to verify the update.

Instructions

Rename a datasource (the title in its editor and in Add data / home lists). datasource_get fingerprint; journalled; read back on draft and published.

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": {
      "datasource_id": "<datasource_id>",
      "name": "<name>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "datasource_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
dry_runNo
report_idNo
datasource_idYes
allow_shared_sourceNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely new behavior: the operation is journalled and the result is read back on both draft and published, telling the agent the rename propagates to published state. It still does not explain what the fingerprint guards against (staleness/conflict) or what happens on mismatch.

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?

Two short sentences, front-loaded with the purpose and effect before the workflow note. The second sentence is telegraphic to the point of being fragmentary, but every clause carries information.

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 return values need not be described, and the draft/published behavior is covered. However, for a six-parameter mutation with 0% schema coverage, the absence of any explanation of dry_run, allow_shared_source, or report_id leaves an agent unable to call it confidently.

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% across six parameters, so the description must carry the load and largely does not. It only gestures at expected_fingerprint (via datasource_get); name, dry_run (defaulting to true), allow_shared_source, and report_id get no explanation at all, and the distinction between preview and commit is left ambiguous.

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 a datasource") plus a scope clarification that the name is the title shown in the editor and in Add data / home lists, which distinguishes it from datasource_fields_rename. It does not explicitly name that sibling, so differentiation is by implication rather than direct routing.

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?

The fragment "datasource_get fingerprint" signals a prerequisite workflow: fetch the current fingerprint with datasource_get before calling. There is no explicit when-not guidance, and no mention of when to prefer a dry run versus committing the change.

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