Skip to main content
Glama
Sign In
voog-mcp

voog-mcp

by runnel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

page_duplicate

Duplicate a page including its full content to reuse or edit without affecting the original. The new page is hidden by default.

Instructions

POST /pages/{id}/duplicate — create a copy of the page (including its content). The new page is hidden by default per Voog convention.

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": {
      "site": "<site>",
      "page_id": "<page_id>"
    },
    "name": "page_duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds that the new page is hidden by default, which is not captured by annotations. Annotations indicate it is non-read-only, non-destructive, and non-idempotent, which is consistent. The description is clear about behavior beyond annotations.

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?

The description is extremely concise, with two sentences that each provide useful information: the action and endpoint, and a specific behavioral note. No unnecessary words.

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?

While the core purpose is clear, the description lacks details about return values (no output schema), parameter explanations, prerequisites, or limitations. It is complete enough for a simple duplicate action but leaves gaps for an agent.

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%, but the description does not explain the meaning or usage of the 'site' or 'page_id' parameters. It only references page_id in the URL pattern. The description fails to add value beyond 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 clearly states it creates a copy of the page including its content, and distinguishes from siblings like page_create by noting the new page is hidden by default. It provides a specific verb-resource pair and endpoint pattern.

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?

The description implies usage for duplicating a page but does not explicitly state when to use this tool versus alternatives such as page_create. No guidance on prerequisites or when not to use is provided.

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