Skip to main content
Glama

Upload Multiple Attachments

confluence_upload_attachments
Destructive

Upload multiple files to Confluence pages or blog posts in a single operation, automatically versioning existing attachments.

Instructions

Upload multiple attachments to Confluence content in a single operation.

More efficient than calling upload_attachment multiple times. If files with the same names exist, new versions are created automatically.

Useful for:

  • Bulk uploading documentation assets (diagrams, screenshots, etc.)

  • Adding multiple related files to a page at once

  • Batch updating existing attachments with new versions

Args: ctx: The FastMCP context. content_id: The ID of the content to attach to. file_paths: List of file paths to upload. comment: Optional comment for the attachments. minor_edit: Whether this is a minor edit.

Returns: JSON string with upload results for each file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_idYesThe ID of the Confluence content (page or blog post) to attach files to. Example: '123456789'. If uploading multiple files with the same names, new versions will be created automatically.
file_pathsYesComma-separated list of file paths to upload. Can be absolute or relative paths. Examples: './file1.pdf,./file2.png' or 'C:\docs\report.docx,D:\image.jpg'. All files uploaded with same comment/minor_edit settings.
commentNo(Optional) Comment for all uploaded attachments. Visible in version history. Example: 'Q4 2024 batch upload'
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?

Beyond the destructiveHint annotation, the description discloses automatic version creation for existing files and that comment/minor_edit apply to all files. This adds valuable behavioral context.

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 well-structured: purpose, efficiency, versioning, use cases, then Args/Returns. It is concise and front-loaded. Minor redundancy with schema descriptions does not detract.

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

Completeness5/5

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

Given the presence of annotations, output schema, and comprehensive schema descriptions, the description provides complete context for the tool's behavior, parameters, and usage scenarios.

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

Parameters3/5

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

Schema description coverage is 100%, with detailed parameter descriptions. The tool description adds minimal extra parameter info beyond the schema, so baseline score of 3 is appropriate.

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 uploads multiple attachments in a single operation. It differentiates from the sibling 'confluence_upload_attachment' by highlighting efficiency and batch capability.

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?

The description lists specific use cases (bulk upload, batch update) and implies not using it for single uploads. It does not explicitly mention when to use alternative singular tool, but the sibling name is available.

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