Skip to main content
Glama

Upload Attachment

confluence_upload_attachment
Destructive

Upload a file to Confluence pages or blog posts, with versioning support for existing attachments.

Instructions

Upload an attachment to Confluence content (page or blog post).

If the attachment already exists (same filename), a new version is created. This is useful for:

  • Attaching documents, images, or files to a page

  • Updating existing attachments with new versions

  • Adding supporting materials to documentation

Args: ctx: The FastMCP context. content_id: The ID of the content to attach to. file_path: Path to the file to upload. comment: Optional comment for the attachment. minor_edit: Whether this is a minor edit (no notifications).

Returns: JSON string with upload confirmation and attachment metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_idYesThe ID of the Confluence content (page or blog post) to attach the file to. Page IDs can be found in the page URL or by using the search/get_page tools. Example: '123456789'
file_pathYesFull path to the file to upload. Can be absolute (e.g., '/home/user/document.pdf' or 'C:\Users\name\file.docx') or relative to the current working directory (e.g., './uploads/document.pdf'). If a file with the same name already exists, a new version will be created.
commentNo(Optional) A comment describing this attachment or version. Visible in the attachment history. Example: 'Updated Q4 2024 figures'
minor_editNo(Optional) Whether this is a minor edit. If true, watchers are not notified. Default is false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations include destructiveHint=true; description confirms modification via new versions. Adds context on versioning, comment visibility, and minor edit suppression of notifications. No contradiction with annotations.

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?

Well-structured with bullet points for use cases. Some redundancy in Args section given schema, but not overly verbose. Could be slightly more concise.

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?

Covers all parameters and required info. Output return value described. Sibling tools include plural variant, so a note on batch upload would improve completeness, but overall sufficient for single upload.

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

Parameters4/5

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

Schema coverage is 100%; description adds real-world examples and clarifications beyond schema (e.g., file path formats, comment visibility). Provides marginal but useful added meaning.

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 the action (upload), resource (attachment to Confluence content), and differentiates from siblings like delete/download. It also mentions versioning behavior, providing a specific verb and resource scope.

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

Usage Guidelines3/5

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

Lists use cases but does not explicitly distinguish from sibling 'confluence_upload_attachments' (plural) for batch uploads. No guidance on when to use alternative tools or prerequisites. Adequate but lacks exclusions.

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/GeiserX/atlassian-browser-mcp'

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