Skip to main content
Glama
zhanglongxiao111

indesign-cli MCP Server

resize_page_item

Resize a page item on a specific page by its index, providing new width and height, with an optional anchor point to control the resize origin.

Instructions

Resize a page item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYesNew width
heightYesNew height
itemIndexYesIndex of the page item to resize
pageIndexYesIndex of the page containing the item
anchorPointNoAnchor point for resizingCENTER_ANCHOR
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as side effects, prerequisites, or constraints. The one-sentence description offers no transparency.

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

Conciseness2/5

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

The description is very short but at the expense of missing critical information. It is under-specified rather than concise.

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

Completeness1/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 including an enum, and no output schema, the description is woefully inadequate. It provides no context on how resizing works, the role of anchor points, or expected behavior.

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?

Schema coverage is 100% with parameter descriptions, so the baseline is 3. The description adds no extra value beyond the schema, but it does not contradict it.

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

Purpose2/5

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

The description 'Resize a page item' is essentially a tautology of the tool name. It does not provide any additional context or differentiation from sibling tools like 'resize_page' or 'move_page_item'.

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 on when to use this tool versus alternatives such as 'resize_page' or 'move_page_item'. The description lacks any context for appropriate usage.

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