Skip to main content
Glama
megamaced

collectives-mcp

by megamaced
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

copy_page

Duplicate a page within the same parent folder, optionally specifying a new title. Supports both leaf and folder pages.

Instructions

Duplicate a page under the same parent. If newTitle is provided, the copy gets that title. Works for both leaf and folder pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexNoPosition among the target parent's children (0 = first). Omit to use the server default.
pageIdYes
newTitleNoTitle for the copy. If omitted, server assigns a default.
collectiveIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / index
      Added value: +{
+  "description": "Position among the target parent's children (0 = first). Omit to use the server default.",
+  "type": "integer"
+}
  2. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate a write operation (readOnlyHint false, openWorldHint true, idempotentHint false). The description adds that duplication stays under the same parent and allows a new title, which is useful. However, it does not disclose whether folder page duplication is recursive (copying children) or describe permissions/side effects, which are important given openWorldHint.

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 three concise sentences with the core action first, followed by title handling and applicability. No fluff or redundancy.

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?

As a mutation tool with openWorldHint and no output schema, the description should clarify return values and side effects. It does not explain how folder pages are duplicated (whether subpages are copied) or any constraints. This ambiguity leaves an agent without critical information for correct invocation.

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?

The schema provides descriptions for index and newTitle, but not for required collectiveId and pageId. The tool description repeats newTitle behavior but does not explain collectiveId or pageId, nor does it clarify index semantics. With 50% schema coverage, the description fails to compensate for missing parameter documentation.

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 a specific action (duplicate) on a specific resource (page) under the same parent, and notes title handling. It distinguishes from siblings like create_page, move_page, and rename_page by emphasizing duplication. The scope (leaf and folder pages) adds clarity.

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 when to use it (when duplicating a page) but provides no explicit guidance on alternatives or exclusions. It does not mention when not to use it or how it differs from create_page or move_page. The context is clear but lacks explicit routing.

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