Skip to main content
Glama
Sign In
confluence-mcp

confluence-mcp

by 1vecera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_attachment

Retrieve a file attached to a Confluence page by providing the page ID and filename. Choose to receive the content as base64 or save it directly to a specified output file.

Instructions

Download an attachment from a page by filename.

Args: page_id: The page ID. filename: The attachment filename. output_file: If provided, save the attachment to this file path instead of returning base64 in the response.

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": {
      "page_id": "<page_id>",
      "filename": "<filename>"
    },
    "name": "download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
filenameYes
output_fileNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral transparency burden. It discloses the key output behavior (base64 by default, file save with output_file) but omits other aspects like error handling, file not found behavior, or size limits.

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 concise: a one-line purpose statement followed by a tight Args section. No wasted words, and the most critical information (purpose and options) is front-loaded.

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

Completeness4/5

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

Given the tool has only 3 parameters and an output schema, the description covers the essentials: what it does and the two output modes. It doesn't detail error cases or security, but those are less critical for a simple download utility.

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 description coverage is 0%, so the description must explain parameters. It does so effectively: page_id, filename, and output_file are all described clearly, including the effect of leaving output_file null.

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 opens with a specific verb and resource: 'Download an attachment from a page by filename.' This clearly distinguishes it from siblings like list_attachments and upload_attachment by focusing on retrieval of a single known attachment.

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 explicit guidance on when to use this tool versus alternatives. It does imply the need to know the filename, but it doesn't mention list_attachments for discovery or provide any exclusions or prerequisites.

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