Skip to main content
Glama

Components Scope

components_scope
Destructive

Moves top-level components between report-level and page-level scope in Google Data Studio reports. Set target scope and page ID to arrange components that display on every page or a single page.

Instructions

Arrange > Make report-level (to="report": the components show on every page) or Make page-level (to="page": report-level components move onto page_id). Ungrouped top-level components without conditional formatting. Two journalled writes (target first, then source); a failure between them is returned as partial, never lost.

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": {
      "page_id": "<page_id>",
      "component_ids": "<component_ids>",
      "to": "<to>"
    },
    "name": "components_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
dry_runNo
page_idYes
report_idNo
component_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds substantial value beyond that: it discloses the two-write journalled sequence (target first, then source) and that a mid-sequence failure is returned as 'partial, never lost'. That partial-failure semantics is exactly the kind of behavior an agent needs before committing to a destructive reorganize. It stops short of stating permission requirements or whether the operation is reversible.

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?

Dense but front-loaded: the operation is stated first, then the mode semantics, then the precondition, then the failure behavior. Some phrasing is jargon-heavy ('journalled writes') and the parenthetical 'to="report"' style reads like UI/help text, but no sentence is wasted.

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 annotations cover the destructive profile. However, for a destructive five-parameter mutation the omission of dry_run's role and report_id's purpose leaves a meaningful gap an agent must resolve from the schema alone.

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 five parameters, so the description must compensate. It does explain the 'to' enum values and ties page_id to the to="page" case, but dry_run (which defaults to true and gates whether anything actually happens), report_id, and component_ids are never mentioned.

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 names a concrete verb pair ('Make report-level' / 'Make page-level') and the resource (components, via the Arrange menu), and explains what each mode does to the components. It is specific enough to act on, though it never names the sibling components_arrange or another tool it might be confused with.

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 states a real precondition ('Ungrouped top-level components without conditional formatting') and clarifies the two mode outcomes, but gives no explicit when-to-use/when-not guidance relative to alternatives such as components_arrange or components_copy_to_page. Usage is implied by the mode descriptions rather than directed.

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