Skip to main content
Glama

Community Viz Register

community_viz_register
Destructive

Register a community visualization manifest in a report before creating components that use its type, or remove it when no components depend on it.

Instructions

Add (or with register=false remove) a community visualization to the report (needed before components_create can use its type). viz_id: manifest path (gs://bucket/path or google://...) plus U+00A0 and the component ID, e.g. "google://devrel/googlecharts gauge", "gs://datastudio_visualizations/funnel/v4/prod pmaMetricFunnel". Then components_create with type=viz_id (no explicit fields: the editor binds its defaults; adjust data slots with components_patch). Removal is refused while components use it. Journalled, verified, 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": {
      "viz_id": "<viz_id>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "community_viz_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
viz_idYes
dry_runNo
registerNo
report_idNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds real context beyond them: removal is blocked while components reference the viz, and operations are 'journalled, verified, restorable'. However it never mentions that dry_run defaults to true, which materially changes what a call does — a meaningful omission for a destructive tool.

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?

Front-loads the mutation semantics, then the id format, then the follow-on call — a sensible order with no filler. The U+00A0 notation is dense but justified by the unusual separator requirement; the example strings are long but earn their space.

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?

With an output schema present and annotations covering the destructive profile, the description needn't explain return values, and it covers the orchestration well. But for a destructive mutation tool it leaves a required parameter (expected_fingerprint) and the dry_run default unexplained, so an agent could call it without understanding the confirmation or preview mechanics.

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%, so the description must carry the load. It does so excellently for viz_id (manifest path plus U+00A0 plus component ID, with two concrete examples) and explains register=false, but expected_fingerprint (a required parameter), dry_run, and report_id get no explanation at all.

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

Purpose5/5

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

States a specific verb+resource ('Add (or with register=false remove) a community visualization to the report') and even names the downstream dependency (components_create). An agent can distinguish this from community_viz_list or components_create purely from the description.

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 an explicit ordered workflow: register first, then components_create with type=viz_id, then adjust data slots with components_patch, and notes that removal is refused while components use it. It stops short of naming an alternative tool (e.g. a listing tool) for the read/inspect case, so 5 is not warranted.

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