Skip to main content
Glama
Sign In
indesign-nutria-mcp

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

interactive_addHyperlink

Add a hyperlink to selected text or a page item in Adobe InDesign by providing the link name, URL, page index, and item index.

Instructions

Add a hyperlink to a text selection or page item

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": {
      "name": "<name>",
      "url": "<url>",
      "pageIndex": "<pageIndex>",
      "itemIndex": "<itemIndex>"
    },
    "name": "interactive_addHyperlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
itemIndexYes
pageIndexYes
document_idNoWhich open document to act on: a name (see document_listOpen) or a 0-based index. Defaults to the front document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies mutation through the verb 'Add'. It does not state permission requirements, whether an existing hyperlink on the target is replaced, whether the document must be saved, or any side effects.

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?

It is a single, front-loaded sentence with no wasted words, which is good structure. However, the brevity reflects under-specification rather than tightness, given what the tool actually requires.

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?

For a 5-parameter mutation tool with no annotations, no output schema, and only 20% schema coverage, the description is too thin. It omits parameter meaning, targeting rules for text selection vs. page item, and any state or permission context.

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?

Schema description coverage is only 20% (only document_id is documented). The description never mentions url, name, pageIndex, or itemIndex, so four required parameters—including what 'name' represents for a hyperlink and how page/item indices resolve—remain unexplained in both places.

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 states a specific verb and resource ('Add a hyperlink') plus its target ('a text selection or page item'), so an agent can distinguish it from interactive_listHyperlinks and interactive_deleteHyperlink. It stops short of explicitly contrasting with those siblings, so it is clear but not perfectly differentiated.

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?

There is no when-to-use guidance and no alternatives named. The agent must infer the intended context from the sibling names (e.g., that list/delete counterparts exist) rather than from the description.

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

Deploy Server

Other Tools