Skip to main content
Glama
Sign In
@growi/mcp-server

@growi/mcp-server

Official
by growilabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

duplicatePage

Idempotent

Create a copy of a wiki page. Optionally duplicate all descendant pages recursively and control user-related resources.

Instructions

Duplicate a page. Can recursively duplicate the page with its descendants.

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": {
      "pageId": "<pageId>"
    },
    "name": "duplicatePage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYes
appNameNoGROWI app name to operate on (optional, uses default if not specified)
isRecursivelyNo
pageNameInputNo
onlyDuplicateUserRelatedResourcesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.3/5.0
Behavior3/5

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

Description adds recursion behavior beyond annotations. However, annotations claim idempotentHint=true while duplication is typically non-idempotent, creating a contradiction not addressed in description. No disclosure of effects on source page or permissions.

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?

Extremely concise with two succinct sentences. Front-loaded with main action, then recursion detail. No wasted words.

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?

Despite having 5 parameters and a mutation operation, description is minimal. No output schema, no explanation of return value, permissions, or side effects. Incomplete for correct agent usage.

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 coverage is low (20%), and description provides no parameter explanations. Critical params like pageNameInput, isRecursively, onlyDuplicateUserRelatedResources are left undocumented, leaving the agent to infer meaning.

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 'Duplicate a page' with recursion option, providing a specific verb and resource. It distinguishes from siblings like createPage (creates new empty page) and renamePage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. Does not mention when not to use, e.g., for simple copying or moving, or exclusions like permission requirements.

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