Skip to main content
Glama
zhanglongxiao111

indesign-cli MCP Server

create_text_frame

Creates a text frame on the active page with specified size, position, and text content. Supports custom fonts, colors, and alignment.

Instructions

Create a text frame on the active page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position in mm
yNoY position in mm
widthNoWidth in mm
heightNoHeight in mm
contentYesText content for the frame
fontNameNoFont name (use format: FontName\tStyle)Arial\tRegular
fontSizeNoFont size in points
alignmentNoLEFT
textColorNoText color (RGB hex or name)Black
characterStyleNoCharacter style name to apply during creation
paragraphStyleNoParagraph style name to apply during creation
Behavior2/5

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

No annotations provided, so description carries full burden. Only mentions 'on the active page', but lacks details on behavior like layer selection, return value, or error conditions.

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

Conciseness3/5

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

Very concise, one sentence, but too brief for an 11-parameter tool. Lacks structure or grouping of parameters.

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?

Incomplete for the complexity. No output schema, no annotations, and the description lacks details about behavior, return value, and edge cases.

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 (91%), so the description adds minimal value. It doesn't elaborate on parameters beyond what the schema already provides.

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?

Clearly states it creates a text frame on the active page. Verb 'create' and resource 'text frame' are specific. Distinguishes from siblings like create_rectangle and create_master_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 Guidelines2/5

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

No guidance on when to use this tool vs alternatives like edit_text_frame or place_file_on_page. No mention of 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/zhanglongxiao111/indesign-cli'

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