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

confluence-wiki-mcp-server

by blantian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_wiki_assets

Retrieve embedded images and attachments from a Confluence Wiki page, returning their URLs, media types, and file sizes.

Instructions

列出 Wiki 页面的内嵌图片和附件，返回 URL、媒体类型和文件大小。

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_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYes
includeAttachmentsNo
includeInlineImagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.3/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose important behavioral traits such as read-only nature, authentication requirements, error handling, or pagination.

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?

The description is a single concise sentence, but it lacks essential details, making it under-specified.

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 is incomplete. It does not cover return behavior, error cases, or authentication context.

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

Parameters1/5

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

Schema has 3 parameters with 0% schema description coverage. The description does not explain the meaning or effect of 'pageId', 'includeAttachments', or 'includeInlineImages'.

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 tool lists inline images and attachments of a Wiki page and returns URL, media type, file size. However, it does not differentiate from the similarly named sibling tool '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 download_wiki_asset or get_wiki_attachments. No context on prerequisites or exclusions.

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