Skip to main content
Glama
theloniuser

InDesign UXP MCP Server

by theloniuser

apply_color

Apply a named color swatch to an object's fill or stroke in an InDesign document. Specify the object index, color swatch name, and choose between fill or stroke.

Instructions

Apply color to an object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectIndexYesObject index
colorNameYesColor swatch name
colorTypeNoFILL
Behavior2/5

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

No annotations are provided, and the description only states 'Apply color' without disclosing behavioral traits such as whether previous colors are overwritten, which object types are supported, or side effects like reflow. The description fails to compensate for the lack of annotations.

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?

The description is a single sentence, which is concise but overly terse. It lacks front-loading of critical information and could be structured to convey more value without increasing length significantly.

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 has three parameters, no output schema, and no annotations, the description is insufficient. It does not explain what 'color' means (e.g., swatch vs. direct color), the impact of colorType, or the expected result. The agent lacks enough context to invoke the tool correctly.

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 input schema describes objectIndex and colorName, but colorType lacks a description. The tool description adds no additional meaning beyond what the schema provides. With 67% schema description coverage, the description should have elaborated on parameter usage, but it does not.

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 'Apply color to an object' clearly indicates the action (apply color) and the resource (object). It distinguishes from sibling tools like apply_object_style or apply_master_spread which have different purposes. However, it could be more specific by clarifying the type of object or scope of color application.

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 such as apply_object_style or set_page_item_properties. There is no mention of prerequisites, limitations, or context in which this tool is preferred.

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/theloniuser/indesign-uxp-server'

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