InDesign MCP Server

by Tlechanteur

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

delete_page

Remove a specific page from an InDesign document by specifying its page index.

Instructions

Delete a page from the document

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pageIndex": "<pageIndex>"
    },
    "name": "delete_page"
  }
}

Input Schema

Name	Required	Description	Default
`pageIndex`	Yes	Page index to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 8, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the delete action but does not warn about irreversibility, impact on document structure or references, or potential error conditions. This is a significant gap for a destructive operation.

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

Conciseness5/5

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

The description is a single sentence, nine words long, and delivers the essential function without any unnecessary words. It is highly concise and well-structured.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema, so a minimal description could suffice. However, important context is missing: the destructive nature of the operation is not disclosed, and whether pageIndex is zero-based is not clarified. This leaves the description adequate but not fully complete.

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 pageIndex described as 'Page index to delete'. The description adds no additional parameter semantics, but since the schema already covers it, the baseline of 3 is appropriate.

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

Purpose5/5

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

The description uses a specific verb 'delete' with a clear resource 'page from the document', which distinguishes it from sibling tools like add_page, duplicate_page, and navigate_to_page. It unambiguously states what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, exclusions, or related tools. It simply states the function without contextual usage information.

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