Skip to main content
Glama

reframe_page

Resize an InDesign page by defining new bounding box coordinates in millimeters. Specify page index and top-left to bottom-right corners to reframe the page.

Instructions

Reframe (resize) a page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIndexYesPage index
x1YesTop-left X coordinate in mm
y1YesTop-left Y coordinate in mm
x2YesBottom-right X coordinate in mm
y2YesBottom-right Y coordinate in mm
coordinateSpaceNoPAGE_COORDINATES
Behavior2/5

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

No annotations are present, so the description carries full responsibility. It only states the action without detailing behavioral traits such as whether content is clipped, scaled, or moved, or any side effects on page content.

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?

The description is a single, front-loaded sentence with no wasted words. Its brevity is efficient, though it could include more detail without significant overhead.

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 complexity of a coordinate-based resizing tool, the description is too sparse. It omits details on coordinate system, impact on page content, and prerequisites, leaving the agent with insufficient context to invoke the tool correctly, especially without an output schema or annotations.

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?

The schema covers 5 of 6 parameters with descriptions, but the coordinateSpace parameter lacks a description. The tool description adds minimal meaning beyond 'resize by coordinates'. With 83% schema coverage, the baseline is 3, and the description does not compensate for the missing parameter documentation.

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?

The description 'Reframe (resize) a page' indicates the action and resource but is vague. It does not differentiate from the sibling 'resize_page' tool, leaving ambiguity about whether reframing uses explicit coordinate bounds versus scaling.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives like 'resize_page' or 'move_page', nor does it specify 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/zachshallbetter/indesign-mcp-server'

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