Skip to main content
Glama

add_internal_link

Append an internal hyperlink to a paragraph that points to a named bookmark, using the paragraph's ID, display text, and bookmark name.

Instructions

Append an internal anchor hyperlink (w:anchor) at the end of a paragraph.

Internal links reference bookmarks by name and do NOT add a relationship.

Args: para_id: w14:paraId of the target paragraph. text: Display text for the hyperlink. bookmark: Name of the bookmark to link to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
para_idYes
textYes
bookmarkYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the burden. It reveals appending behavior, bookmark reference, and absence of relationship addition. It does not mention error handling but provides key behavioral traits.

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 sentence followed by a clear parameter list. Every word is necessary, and the structure is front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool, the description covers purpose, behavior, and parameters. An output schema exists, so return value explanation is unnecessary. It is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully explains each parameter: para_id as w14:paraId, text as display text, bookmark as bookmark name. This adds significant meaning beyond the schema's basic type.

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 clearly states the tool appends an internal anchor hyperlink to a paragraph, specifying it uses bookmarks and does not add a relationship. This differentiates it from siblings like add_hyperlink (external) and add_bookmark.

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

Usage Guidelines4/5

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

The description explains that internal links reference bookmarks, implying a prerequisite, and contrasts with external links. However, it does not explicitly state when not to use it or mention alternative tools.

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/SecurityRonin/docx-mcp'

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