Skip to main content
Glama

Page Duplicate

page_duplicate
Destructive

Duplicate a loaded page in View to preserve fields, styles, and shared sources, returning a component ID map for the copied page.

Instructions

Duplicate a loaded page, retaining fields/styles and sharing its existing sources.

Open the source page in View first. Native duplicateConfig generates component IDs and control aliases; only its delta is applied to full saved JSON, preserving opaque properties. Copies page visibility/icon. Returns a component ID map. Conditions with owners absent from the source page are omitted from the copy as in native duplication; omitted_condition_owner_ids reports them explicitly. This creates a page inside the bound report, never a report/datasource asset.

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>",
      "name": "<name>",
      "expected_structure_fingerprint": "<expected_structure_fingerprint>"
    },
    "name": "page_duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
indexNo
dry_runNo
page_idYes
report_idNo
expected_structure_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?

Goes well beyond the readOnlyHint=false/destructiveHint=true annotations: shares existing sources rather than copying them, applies only a native duplicateConfig delta to full saved JSON to preserve opaque properties, copies visibility/icon, and explicitly reports omitted conditions with owner-less entries via omitted_condition_owner_ids. The major omission is that the schema's default dry_run=true means no page is actually created unless the caller opts out, which the description never discloses for a destructive-flagged mutation.

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-loaded with the core action and kept to a handful of dense sentences with no filler; the middle sentences about delta application are technical but earn their place. Slightly jargon-heavy phrasing costs it the top mark.

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?

Return-value explanation is unnecessary given the output schema, and the duplication semantics are unusually well documented. However, for a destructive, six-parameter mutation with zero schema coverage, missing dry-run default behavior and the meaning of the mandatory fingerprint leave the definition short of what an agent needs to invoke it safely.

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 six parameters, and the description names none of them. Critically, the required expected_structure_fingerprint concurrency guard, the nullable report_id (vs. the "bound report"), index, and dry_run are all left entirely to the caller's inference; only the component ID map output is hinted at, and an output schema already covers that.

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 and resource ("Duplicate a loaded page") and pins down its scope with "This creates a page inside the bound report, never a report/datasource asset," which is exactly the distinction an agent needs against component-level duplication siblings. Retention behavior (fields/styles, existing sources) is stated up front.

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?

Provides one real prerequisite ("Open the source page in View first") and scopes the tool to pages rather than whole reports, but gives no explicit when-to-use vs. when-not guidance relative to the duplication siblings, and never mentions that a preview/dry-run mode exists.

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