Skip to main content
Glama

Components Duplicate

components_duplicate
Destructive

Duplicate ungrouped top-level components on one static-canvas page in a single write, preserving fields, styles, and conditional formatting while regenerating IDs.

Instructions

Copy ungrouped top-level components on the same static-canvas page in one write.

Load the page using report_refresh first. Preserves fields/styles, regenerates IDs/control aliases and copies owned conditional formatting. New objects are appended to the component list, offset in pixels. Preview IDs are provisional. Grouped/responsive/component-child operations require separate support.

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_duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
page_idYes
offset_xNo
offset_yNo
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

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true but say nothing about mechanics; the description adds real value by stating what is preserved (fields/styles, owned conditional formatting), what is regenerated (IDs/control aliases), where new objects land (appended, pixel offset), and the caveat that preview IDs are provisional. It does not explain the dry_run default of true or how expected_fingerprint guards concurrent edits, which leaves gaps 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?

The core action and scope are front-loaded in the first sentence, and each following sentence adds distinct information (prerequisite, preservation behavior, output placement, limitations). Slight density with fragments like 'Preview IDs are provisional' keeps it just under maximum clarity.

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 no prose, and the description covers preservation, ID regeneration, and placement well. For a destructive mutation with a concurrency token and a dry-run default, the absence of any explanation of expected_fingerprint or dry_run leaves the definition incomplete for safe invocation.

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 7 parameters, so the description must carry the load; it does clarify the page context, component selection, and pixel offset semantics. However, the required expected_fingerprint parameter is never explained, and dry_run/report_id behavior is left entirely to the bare schema.

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?

The description names a specific verb (copy), resource (ungrouped top-level components), and scope constraint (same static-canvas page, single write). The 'same page' qualifier implicitly separates it from the cross-page copy sibling without needing the sibling name.

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?

It gives an explicit prerequisite ('Load the page using report_refresh first') and an explicit exclusion ('Grouped/responsive/component-child operations require separate support'). It stops short of naming the alternative tool for cross-page copies, but the same-page constraint makes the boundary inferable.

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