Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

move_content

Idempotent

Move a page and its subtree to a new parent or sibling position. Re-parenting changes the URL path and automatically applies a 301 redirect to the old URL.

Instructions

Move a page in the tree: give parentId to re-parent it (its URL path changes with its new position, and the old URL gets a 301 automatically), and/or beforeId/afterId to place it among its siblings. The page's whole subtree moves with it. Sibling order only sticks under a parent whose child sort is manual; a computed sort (name, date…) re-orders it. Returns {ok:true}.

Input Schema

TableJSON 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 tree, list_pages or get_content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=true) but say nothing about side effects; the description adds substantial unannotated behavior: URL path changes, automatic 301 on the old URL, whole-subtree movement, and the sort-mode dependency. These are exactly the traits an agent needs before mutating content.

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?

Front-loads the core action and parameter roles, then layers behavior and edge cases in dense, waste-free sentences. Nothing is redundant and the return claim is tacked on efficiently.

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?

No output schema exists, and the description supplies the return shape ({ok:true}) as well as the side-effect and sort-mode caveats. An agent has everything needed to invoke this mutation correctly and predict its effects.

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 interaction semantics the schema does not: it explains how parentId and beforeId/afterId combine ('and/or') and that the subtree follows. This goes beyond the per-field descriptions, justifying a 4.

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) and resource (a page in the tree) and immediately distinguishes the two operation modes: re-parenting via parentId vs. sibling placement via beforeId/afterId. An agent can tell this apart from update_content without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context for when each parameter applies (give parentId to re-parent, and/or beforeId/afterId to place among siblings) and warns about the manual-vs-computed sort caveat. It does not explicitly rule out alternative siblings (e.g. update_content) or state prerequisites, so it stays short of a 5.

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