Skip to main content
Glama
zhanglongxiao111

indesign-cli MCP Server

move_page

Move a page to a specified position, such as at the beginning, end, before, or after a reference page. Adjust page order in InDesign documents by providing the page index and desired location.

Instructions

Move a page to a different position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bindingNoDEFAULT_VALUE
positionNoAT_END
pageIndexYesPage index to move
newPositionNoLocationOptions value used by the current handler
referencePageIndexNoReference page index (for BEFORE/AFTER positioning)
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the action and target, omitting details like whether the operation is destructive/undoable, how invalid indices are handled, or if there are side effects on other pages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but underspecified. It front-loads the core action, but the lack of additional sentences for clarity makes it barely adequate.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is too minimal. It does not explain how to specify the new position (position vs newPosition), the role of referencePageIndex, or what the result looks like. This is insufficient for an agent to use the tool correctly.

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 description adds no meaning beyond the input schema. Schema coverage is 60%, but the description does not clarify the missing 40% (e.g., binding, position) or explain how parameters interrelate. The schema's own descriptions for some parameters are still present but not enhanced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it moves a page to a different position, which is specific to the page resource. However, it does not differentiate from similar sibling tools like move_page_item or move_spread, though the noun 'page' offers some distinction.

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 is provided on when to use this tool versus alternatives (e.g., move_page_item, duplicate_page). There are no prerequisites, exclusions, or context about typical usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhanglongxiao111/indesign-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server