Skip to main content
Glama
Sign In
MCP Atlassian Server

MCP Atlassian Server

by dunz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_attachments_uploaded_by_user

List attachments uploaded by a specific user in Confluence, optionally filtered by space.

Instructions

List all attachments uploaded by a specific user, with optional filtering by space.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_attachments_uploaded_by_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of attachments to return. Default is 25, maximum is 100.
startNoThe starting index for pagination. Default is 0.
spaceKeyNoOptional space key to filter results to a specific space.
usernameNoThe username of the user (alternative to accountId).
accountIdNoThe Atlassian account ID of the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It claims to list 'all attachments,' yet the schema reveals pagination with limit defaulting to 25 and maximum 100, so the tool returns a page, not necessarily all. It also omits behavior when neither username nor accountId is supplied, ordering, and error cases.

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?

A single, front-loaded sentence with no filler. Every word contributes to the core purpose and the space-filtering option.

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?

This is a paginated list tool with no output schema and no annotations, yet the description does not mention pagination behavior, the need to supply either username or accountId, or what the response contains. Given the five parameters and the dual user-identifier ambiguity, the description is insufficient for safe invocation.

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 documents all parameters. The description adds little beyond the schema, merely restating that space filtering is optional. No additional semantics are provided for pagination or the username/accountId relationship.

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: list attachments uploaded by a specific user, with an optional space filter. This clearly distinguishes it from siblings like list_attachments_on_page (attachments on a page) and list_pages_created_by_user (pages, not 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 such as list_attachments_on_page or download_confluence_attachment. The description implies a use case but provides no explicit context, 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