Skip to main content
Glama
megamaced

collectives-mcp

by megamaced
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

move_page_to_collective

Destructive

Move or copy a page and its subpages/attachments into another Collective. Specify source and destination Collective IDs to reorganize content across teams.

Instructions

Move or copy a page (with its subpages and attachments) into a different Collective. Set copy: true to duplicate instead of moving. The page id changes on arrival, so use the returned page for follow-up calls. For reorganising within one Collective use move_page or copy_page instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copyNoCopy instead of moving. Defaults to false (move).
indexNoPosition among the target parent children (0 = first).
pageIdYesPage to move or copy.
parentIdNoTarget parent page in the destination Collective. Omit to place it at the root.
collectiveIdYesSource Collective id.
newCollectiveIdYesDestination Collective id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructive/non-read-only behavior. Description adds useful behavioral details: subpages and attachments are included, page id changes, and the returned page should be used for follow-ups.

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?

Two concise sentences. The main action and key distinction are front-loaded, with copy behavior and alternatives stated efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers the key side effects, copy/move behavior, and guidance on using the return value. It could mention permissions or error cases, but given the annotations and schema, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% description coverage and each parameter already has a clear description. The tool description does not add much beyond the schema, so baseline 3 is appropriate.

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 ('Move or copy') and resource ('page ... into a different Collective'). Explicitly distinguishes it from move_page/copy_page, which are for reorganising within one Collective.

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

Usage Guidelines5/5

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

Explains when to use this tool vs alternatives: 'For reorganising within one Collective use move_page or copy_page instead.' Also clarifies copy behavior with 'copy: true'.

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