Skip to main content
Glama

confluence_add_link

Insert a hyperlink into a Confluence page after a specified text or as a new paragraph.

Instructions

Add a hyperlink to a Confluence page.

If after_text is provided, the link is inserted right after the first occurrence
of that text in a paragraph. Otherwise it's appended as a new paragraph at the
end of the page.

Args:
    page_id: A numeric page ID or a Confluence URL (including short /wiki/x/ links).
    link_text: The display text for the link.
    url: The URL to link to.
    after_text: Optional text to insert the link after (inline within a paragraph).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
page_idYes
link_textYes
after_textNo
Behavior3/5

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

No annotations exist; description explains insertion behavior but does not disclose side effects, permissions, error handling, or idempotency. It covers the placement logic but lacks full behavioral insight.

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?

Description is relatively concise with a clear front-loaded purpose. The 'Args:' listing is slightly verbose but still efficient. Every sentence contributes to understanding.

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

Completeness3/5

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

Lacks output schema and does not describe return values. Also does not cover error cases (e.g., page not found) or duplicate detection. Adequate for basic usage but incomplete for a robust agent.

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 has 0% description coverage, but the 'Args:' section in the description fully details each parameter: page_id accepts numeric or URL formats, link_text for display text, url for target, after_text as optional inline insertion point. This adds significant meaning beyond parameter names.

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?

Description clearly states 'Add a hyperlink to a Confluence page' with specific placement behavior (inline after text or appended). This distinguishes it from siblings like edit_page or create_page.

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?

Provides clear context for when to use: adding a link, with explanation of two insertion modes. No explicit when-not-to-use or comparison to alternatives, but siblings like edit_page imply different purposes.

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/karbassi/confluence-adf-mcp'

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