Skip to main content
Glama

Components Copy To Page

components_copy_to_page
Destructive

Copies selected top-level components to another page with matching geometry, settings, and fields but new IDs, enabling safe page duplication without conditional formatting.

Instructions

Copy components to another page (copy + paste): same geometry, settings and fields, new IDs. Ungrouped top-level components; conditional formatting rules are not copied. One journalled, verified, restorable write of the target page.

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": {
      "source_page_id": "<source_page_id>",
      "component_ids": "<component_ids>",
      "target_page_id": "<target_page_id>"
    },
    "name": "components_copy_to_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
component_idsYes
source_page_idYes
target_page_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses that the write is single, journalled, verified and restorable, and that it only affects the target page -- meaningful safety context for a destructive operation. It omits what happens to components already present on the target page, which is the main behavioral question an agent would have.

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?

Three dense sentences, front-loaded with the action and its fidelity guarantees, then narrowed to eligibility constraints, then the write-safety claim. Every clause carries information; the semicolon-chained scope sentence is compact but slightly harder to parse than separate sentences would be.

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?

An output schema exists, so return values need no prose, but for a destructive cross-page write the description leaves essential facts unstated: the default dry_run behavior, whether existing target components are overwritten, and what report_id does. An agent could follow this definition and still invoke the tool incorrectly.

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 5 parameters, so the description must compensate and largely does not. Most critically, it never mentions dry_run, whose default of true means a default invocation performs no actual copy -- an agent reading only this description would misjudge the call's effect; report_id is likewise unexplained.

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 states a specific verb and resource pair ('Copy components to another page') plus the copy+paste semantic ('same geometry, settings and fields, new IDs'), which an agent can distinguish from in-page duplication. It does not name the closest sibling (components_duplicate) either way, so differentiation is by implication rather than explicit routing.

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?

Applicability is implied through scope constraints: only 'ungrouped top-level components' are eligible and 'conditional formatting rules are not copied', which tells an agent when this tool will silently not do what it expects. There is no explicit when-to-use vs. when-not, no mention of prerequisites or of the alternative in-page duplication path.

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