Skip to main content
Glama
theloniuser

InDesign UXP MCP Server

by theloniuser

resize_page_item

Resize a page item on a specific page in an InDesign document by specifying new width, height, and an anchor point.

Instructions

Resize a page item

Input Schema

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

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

No annotations provided, and the description only says 'Resize a page item' without disclosing side effects, permissions, or constraints (e.g., whether items can be resized beyond page bounds).

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?

Extremely concise (4 words) but lacks structure and substantive information. Not informative enough to earn a higher score.

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?

No output schema, no annotations, and description omits return values, error conditions, or typical use cases. Incomplete for a mutation tool.

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 covers 100% of parameters with descriptions, so baseline is 3. Description adds no additional meaning beyond what the schema already provides.

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

Purpose3/5

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

Description states verb 'Resize' and resource 'page item', which is clear but identical to the tool name, offering no differentiation from siblings like 'resize_page' or 'set_page_item_properties'.

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 vs alternatives such as 'move_page_item' or 'set_page_item_properties'. Missing prerequisites or context.

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/theloniuser/indesign-uxp-server'

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