indesign-mcp-server

Overview Schema Source Related Servers Discussions Admin

export_epub

Export an InDesign document as an EPUB file. Specify the output path, select EPUB version (2 or 3), and control image format and inclusion.

Instructions

Export document as EPUB

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": {
      "filePath": "<filePath>"
    },
    "name": "export_epub"
  }
}

Input Schema

Name	Required	Description	Default
`version`	No		EPUB3
`filePath`	Yes	Output EPUB file path
`imageFormat`	No		PNG
`includeImages`	No	Include images

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says the document is exported as EPUB, without mentioning side effects like file creation, overwriting, or whether existing files are replaced. It also doesn't clarify any dependencies or limitations, providing minimal transparency beyond the basic operation.

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 extremely concise, using only four words without wasted verbiage. It is front-loaded with the core action. However, it may be too terse for a tool with four parameters, though the conciseness dimension rewards brevity, so this is still effective.

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?

This export tool has four parameters, no output schema, and no annotations. The description only states the basic export action, omitting essential context such as output file behavior, version selection, or image handling. It is completely inadequate for an agent to invoke the tool correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents filePath and includeImages, but version and imageFormat are only defined by enums/defaults with no descriptions. The description adds no parameter information whatsoever, failing to compensate for the 50% schema coverage gap. The agent lacks guidance on choosing EPUB2 vs EPUB3 or image formats.

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

Purpose4/5

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

The description 'Export document as EPUB' clearly states the action (export) and the target format (EPUB), distinguishing it from sibling tools like export_pdf and export_images. However, it doesn't elaborate on the scope or specifics, so it lacks some differentiation beyond the format name.

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 is provided on when to use this tool versus alternatives such as export_pdf or package_document. There is no mention of prerequisites, contexts, or exclusions, leaving the agent to infer usage from the tool name alone.

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