InDesign MCP Server

by Tlechanteur

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

edit_text_frame

Change text content, font size, font family, color, or alignment of an existing text frame in Adobe InDesign.

Instructions

Edit properties of an existing text frame

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": {
      "frameIndex": "<frameIndex>"
    },
    "name": "edit_text_frame"
  }
}

Input Schema

Name	Required	Description
`content`	No	New text content
`fontSize`	No	Font size in points
`alignment`	No
`pageIndex`	No	Page index
`textColor`	No	Text color
`fontFamily`	No	Font family name
`frameIndex`	Yes	Text frame index on page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'edit properties' without mentioning side effects, prerequisites, error behavior, or what happens to the document. This is a significant gap for a mutation tool.

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, front-loaded sentence with no wasted words. It is concise and immediately understood.

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 tool's complexity (7 parameters, mutation, no output schema, no annotations), the description is minimal and incomplete. It lacks prerequisites, side effects, and usage context beyond the basic operation.

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 description coverage is high (86%), and the description adds no extra parameter meaning beyond the schema. Baseline of 3 is appropriate since the schema handles the parameter documentation.

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 'Edit properties of an existing text frame' clearly states the verb (edit), resource (text frame), and scope (existing, not create). It distinguishes well from sibling tools like create_text_frame.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for modifying existing text frames, but it does not explicitly state when to use it versus alternatives or provide exclusions. Usage context is present but not elaborated.

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