Skip to main content
Glama
Sign In
confluence-wiki-mcp-server

confluence-wiki-mcp-server

by blantian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_wiki_references

Get linked pages from a Confluence Wiki page. Optionally fetch their titles and summaries.

Instructions

获取 Wiki 页面引用的其他页面链接，可选抓取被引用页面的标题和摘要。

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": {
      "pageId": "<pageId>"
    },
    "name": "get_wiki_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
fetchNo
pageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It does not explicitly state that this is a read-only operation or describe any side effects, rate limits, or other 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.

Conciseness4/5

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

The description is a single sentence that efficiently conveys the core function. It is front-loaded with the verb and resource. Minor improvement could be made by separating the optional fetch 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 no output schema and no annotations, the description should provide more details about return format, data volume, or limitations. The current description is too minimal for an agent to fully understand the tool's behavior.

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 description only hints at the 'fetch' parameter by mentioning optional retrieval of titles and summaries. It does not explain 'pageId' or 'depth' (especially the range and default). With 0% schema description coverage, this is insufficient.

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 retrieves references from a wiki page and optionally fetches details of referenced pages. It distinguishes from sibling tools like fetch_wiki_page or get_wiki_attachments.

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 guidance on when to use this tool versus alternatives like search_wiki or get_wiki_page_context. The description only states the basic function without usage context.

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