Skip to main content
Glama

Datasource Settings Set

datasource_settings_set
Destructive

Updates Google Data Studio datasource editor settings, including cache freshness, report field editing, community visualization access, and native functions, using fingerprint checks to prevent conflicts.

Instructions

Datasource editor settings: data freshness (cache_hours 0 = every 15 minutes, 1, 4, 12 = default), field editing in reports, community visualizations access, native functions. datasource_get fingerprint; publishes and reads back; restorable.

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>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "datasource_settings_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
cache_hoursNo
datasource_idYes
native_functionsNo
allow_shared_sourceNo
community_viz_accessNo
expected_fingerprintYes
field_editing_in_reportsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety bar is lower. The description adds real value beyond them: 'publishes and reads back; restorable' discloses reversibility, and the fingerprint reference signals an optimistic-concurrency guard. It omits the most consequential behavior though—that dry_run defaults to true and no writes occur unless explicitly disabled.

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?

Very compact—two telegraphic sentences with no filler—and the settings list is front-loaded. The compression goes too far in places: '1, 4, 12 = default' and 'publishes and reads back' are dense enough to be ambiguous rather than merely brief.

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?

This is a destructive mutation with 9 undocumented parameters, and the description leaves out dry_run's default-true semantics and allow_shared_source entirely—both of which change what the tool actually does. An output schema exists, so return values need not be explained, but the write/restore lifecycle and the parameter mapping are too thin for a tool this consequential.

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

Parameters3/5

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

Schema description coverage is 0% across 9 parameters, so the description must compensate and it only partially does. It clarifies cache_hours values (though the phrase '1, 4, 12 = default' is garbled and does not clearly map codes to meanings) and names four boolean settings, but leaves dry_run, report_id, allow_shared_source, and datasource_id with no explanation in either schema or description.

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

Purpose3/5

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

The description enumerates the settings being changed (data freshness, field editing in reports, community viz access, native functions), which tells an agent the resource. But it never states the verb explicitly ('set' is only in the name) and the phrasing 'Datasource editor settings:' is a noun fragment rather than 'Updates X settings'. The scope is inferable but not crisply asserted.

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?

'datasource_get fingerprint' implies a read-before-write workflow, which is genuine usage context. However, there is no when-to-use vs. when-not guidance relative to siblings such as settings_set or datasource_sharing_set, and no mention that dry_run defaults to true (a precondition the agent must consciously override to actually apply changes).

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