Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

confluence_attachment_list

List attachments on a Confluence page, one page per call. Use the returned next_cursor to fetch subsequent pages and set limit to control page size.

Instructions

List attachments on a Confluence page (one page per call). Pass the returned next_cursor back as cursor to fetch the next page. limit defaults to 25. Mirrors omni-dev atlassian confluence attachment list.

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>"
    },
    "name": "confluence_attachment_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of attachments per page. Defaults to 25.
cursorNoPagination cursor (use `next_cursor` from a previous call).
page_idYesConfluence page ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `confluence_attachment_list` tool."
    • removedInput schema / title
      Removed value: -"ConfluenceAttachmentListParams"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry full transparency burden. It explains pagination behavior but does not explicitly state that this tool is read-only or has no side effects. The default limit and cursor usage are disclosed, but additional behavioral traits (e.g., authentication needs, rate limits) are absent.

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?

Three sentences, each with a distinct purpose: purpose, pagination usage, default and mirror. No wasted words, front-loaded with core functionality.

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

Completeness3/5

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

The description covers pagination and defaults but lacks details on return format (e.g., what fields are in each attachment). Given no output schema, mentioning that it returns attachment metadata would improve completeness. For a simple list tool, it is adequate but has a gap.

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 baseline is 3. The description reinforces parameter usage (limit defaults to 25, cursor pagination) but does not add new meaning beyond the schema. The mirroring note is not param-related.

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 it lists attachments on a Confluence page, with the specificity 'one page per call'. The verb 'List' and resource 'attachments on a Confluence page' are precise. Among siblings, there is no other attachment listing tool, so it is well-differentiated.

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 explicitly explains how to use pagination ('Pass the returned next_cursor back as cursor') and notes the default limit. However, it does not specify when to use this tool versus alternatives (e.g., for non-attachment content, use other reading tools). The guidance for pagination is clear.

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