Skip to main content
Glama
theloniuser

InDesign UXP MCP Server

by theloniuser

apply_object_style

Apply a named object style to a page item in an InDesign document, specifying item type and index for precise styling.

Instructions

Apply an object style to a page item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNameYesObject style name
itemTypeNorectangle
itemIndexNoItem index
Behavior2/5

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

No annotations exist, so the description must convey behavioral traits. It only states the action without any details on side effects (e.g., overriding styles), error handling (e.g., missing style), or return values (no output schema). This is insufficient 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.

Conciseness4/5

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

The description is a single sentence that is front-loaded and concise, with no wasted words. It efficiently conveys the core purpose, though it could benefit from additional detail.

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 too minimal. It fails to explain how the tool interacts with page items (e.g., selection vs. explicit index) or what happens when input is invalid, leaving critical gaps for an AI agent.

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 covers 67% with descriptions for styleName and itemIndex, but itemType lacks a description and the tool's description adds no extra meaning. For example, 'itemIndex' is vague (index in what context?) and itemType's enum values are self-explanatory but not documented further.

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 clearly states the action ('Apply an object style') and the target resource ('a page item'), which distinguishes it from sibling tools like apply_paragraph_style or apply_color. However, it does not explain what an object style is, which could be ambiguous for an AI agent unfamiliar with InDesign.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives (e.g., set_page_item_properties) or mention prerequisites like object style existence or page item selection.

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