Retrieve all items on a specific InDesign page by providing its index, returning details for each item such as type and bounds.
List all page items on a specific page
| Name | Required | Description | Default |
|---|---|---|---|
| pageIndex | Yes | Index of the page to list items from |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states the action without disclosing what is returned (e.g., item IDs, types), behavior for empty pages, or any side effects. The description lacks behavioral details beyond the basic listing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that directly states the tool's purpose with no extraneous words. It is front-loaded and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and a simple parameter, the description is adequate for a basic list tool but lacks details about return values, pagination, or constraints. It is minimally complete but could be improved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (one parameter, 'pageIndex', with description). The description adds no additional meaning beyond the schema. However, it does not specify if the index is 0-based or 1-based, which would be helpful context. Baseline 3 is appropriate given high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'List all page items on a specific page'. It uses a specific verb ('list') and resource ('page items') with a clear scope, distinguishing it from siblings like 'get_page_item_info' or 'get_page_content_summary'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. With many sibling tools related to page items (e.g., get_page_item_info, delete_page_item), the description does not specify scenarios for listing vs other operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.