Skip to main content
Glama

Components Delete

components_delete
Destructive

Delete ungrouped top-level components and their owned formatting from a Datastudio page in one guarded write while preserving grouped components, datasource assets, fields, and report resources.

Instructions

Delete ungrouped top-level components and their owned formatting in one page write.

Does not delete datasource assets, fields or report resources. Group membership is guarded. operation_restore can recreate deleted components from the journal.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNo
page_idYes
report_idNo
component_idsYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description had a lower bar and still adds real substance: atomicity ('in one page write'), cascade behavior ('their owned formatting'), protected resources, a guard on grouped components, and journal-based recoverability. The one notable omission is that dry_run defaults to true, meaning the call is safe-by-default unless overridden — a behavioral trait the description never mentions.

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?

Three tight sentences, each carrying distinct information: what is deleted, what is protected, and how to recover. The destructive scope is front-loaded in the first sentence, and there is no filler or restatement of the name.

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?

A destructive, multi-parameter write whose return values are covered by an output schema, so the description need not explain results. However, for a call requiring a fingerprint token and defaulting to a non-destructive dry run, the absence of any parameter explanation leaves genuine invocation risk. Adequate on intent, materially incomplete on operands.

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 five parameters, and the description compensates for none of them. The required expected_fingerprint is completely opaque — an agent cannot infer it is an optimistic-concurrency token or how to obtain it — and dry_run, report_id, and component_ids are also unaddressed. The only implicit mapping is 'page' to page_id and 'components' to component_ids.

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 plus a scope qualifier: 'Delete ungrouped top-level components and their owned formatting.' The second sentence carves out what is explicitly NOT touched (datasource assets, fields, report resources), which sharpens the boundary. It stops short of naming the sibling to use for grouped components or for editing rather than deleting, so it is clear but not fully sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives usable negative guidance ('does not delete datasource assets, fields or report resources') and a guard condition ('group membership is guarded'), which tells an agent when this call will refuse or is inappropriate. It also names the recovery route (operation_restore). There is no positive statement of when to prefer this over components_patch or pages_delete, which keeps it from a 5.

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