MCP Atlassian

Upload Multiple Attachments

confluence_upload_attachments

Destructive

Upload multiple attachments to Confluence pages or blog posts in one operation, automatically versioning existing files. Ideal for bulk uploading documentation assets.

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

Input Schema

TableJSON Schema

Name	Required	Description
`comment`	No	(Optional) Comment for all uploaded attachments. Visible in version history. Example: 'Q4 2024 batch upload'
`content_id`	Yes	The 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_paths`	Yes	Comma-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.
`minor_edit`	No	(Optional) Whether this is a minor edit. If true, watchers are not notified. Default is false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations include destructiveHint=true, but the description adds valuable behavior beyond that by disclosing that same-named files automatically create new versions. It also clarifies that all files share the same comment and minor_edit settings, which is useful 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 reasonably concise and front-loaded with the primary purpose, followed by the efficiency comparison and key behavioral note. The bulleted use cases add a little length but are relevant and easy to scan.

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 presence of a full input schema, an output schema, and annotations, the description covers the essential behavioral and usage context. It doesn't discuss permission requirements or limits, but those are not necessary for a tool of this complexity.

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%, so the schema already documents all parameters thoroughly. The description doesn't need to add much; it adds only general batch behavior, not parameter-level detail beyond the schema.

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?

States a specific verb and resource: upload multiple attachments to Confluence content in one operation. It explicitly contrasts itself with the sibling tool upload_attachment, making its scope clear.

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?

Provides clear context for when to use it: bulk uploading, adding multiple related files, and batch updating attachments. It also names the alternative upload_attachment, though it doesn't explicitly state 'use upload_attachment for a single file'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server