Skip to main content
Glama
Sign In
Paperboy CMS

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

move_content

Idempotent

Move a page in the page tree: parentId re-parents it (its URL path follows its new position, and the old URL gets a 301 automatically), beforeId/afterId place it among its siblings. Its whole subtree moves with it.

Instructions

Move a page in the page tree: parentId re-parents it (its URL path follows its new position, and the old URL gets a 301 automatically), beforeId/afterId place it among its siblings. Its whole subtree moves with it. Refused when the new parent is the page itself, is not a page, or lies outside your sections. Sibling order only sticks under a parent with a manual child sort; a computed sort (name, date…) re-orders it. Returns {ok:true}. To change only the URL's last segment, set a new slug with update_content instead; blocks and globals are not in the tree. Requires the content.update permission (Admin, Editor, Author — an Author only within their own sections).

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": {
      "documentId": "<documentId>"
    },
    "name": "move_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite slug or id to act in (multisite). Omit to use this server's default site. Call list_sites to see what exists — an empty tree or search usually means the wrong site, not missing content.
afterIdNoPlace it directly after this sibling (documentId).
beforeIdNoPlace it directly before this sibling (documentId).
parentIdNodocumentId of the new parent page; null moves it to the top level. Omit to keep the current parent.
documentIdYesThe item's documentId (stable across locales and versions), e.g. from list_tree, list_content or get_content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • changedInput schema / properties / documentId / description
      Previous value: -"The item's documentId (stable across locales and versions), e.g. from tree, list_pages or get_content."New value: +"The item's documentId (stable across locales and versions), e.g. from list_tree, list_content or get_content."
  2. Changed4 schema fields changedv0.1.3
    • addedInput schema / properties / afterId / description
      Added value: +"Place it directly after this sibling (documentId)."
    • addedInput schema / properties / beforeId / description
      Added value: +"Place it directly before this sibling (documentId)."
    • changedInput schema / properties / documentId / description
      Previous value: -"Content documentId"New value: +"The item's documentId (stable across locales and versions), e.g. from tree, list_pages or get_content."
    • addedInput schema / properties / parentId / description
      Added value: +"documentId of the new parent page; null moves it to the top level. Omit to keep the current parent."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare it non-destructive and idempotent, but the description goes well beyond them: it discloses the automatic 301 redirect, that the whole subtree moves, the exact refusal conditions, the sibling-order caveat under computed sorts, and the required content.update permission with role-level nuance. This is rich behavioral context not derivable from the annotations.

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 densely packed, with nearly every clause carrying distinct information (redirects, refusals, permissions). The parenthetical-heavy style makes it slightly harder to scan than an ideally structured description, but there is little waste.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers the return value ('Returns {ok:true}'), refusal cases, permission requirements, and side effects like the 301 redirect and subtree move. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: parentId 're-parents' it and the URL path follows, beforeId/afterId place it among siblings, and sibling order only sticks under manual sort. That last constraint is not in the schema and materially affects how an agent sets these params.

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 ('Move a page in the page tree') and immediately distinguishes itself from siblings by scoping to tree repositioning rather than content editing. An agent can tell it apart from update_content, duplicate_content, and trash_content without opening any schema.

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?

Explicitly routes the agent: 'To change only the URL's last segment, set a new slug with update_content instead' and 'blocks and globals are not in the tree.' It also names the permission and role conditions under which the tool is available, giving clear when-to-use and when-not-to-use guidance.

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