Skip to main content
Glama

confluence_get_attachments

Retrieve all attachments from a specified Confluence page by providing its page ID.

Instructions

Get list of attachments for a Confluence page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesThe ID of the page

Implementation Reference

  • The handler function `getAttachments(pageId)` that fetches attachments from Confluence API.
    async function getAttachments(pageId) {
      try {
        const response = await client.get(
          `${CONFLUENCE_API_BASE}/content/${pageId}/child/attachment`,
          { params: { expand: 'version' } }
        );
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get attachments: ${error.message}`);
      }
    }
  • index.js:382-395 (registration)
    Registration of the tool `confluence_get_attachments` with its name, description, and inputSchema (requires pageId).
    {
      name: 'confluence_get_attachments',
      description: 'Get list of attachments for a Confluence page',
      inputSchema: {
        type: 'object',
        properties: {
          pageId: {
            type: 'string',
            description: 'The ID of the page',
          },
        },
        required: ['pageId'],
      },
    },
  • The call handler case that delegates to `getAttachments(args.pageId)` when the tool is invoked.
    case 'confluence_get_attachments': {
      const result = await getAttachments(args.pageId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • The input schema for the tool, defining pageId as a required string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        pageId: {
          type: 'string',
          description: 'The ID of the page',
        },
      },
      required: ['pageId'],
    },
Behavior2/5

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

No annotations provided; description is minimal and does not disclose behavioral traits like pagination, limits, or authentication requirements.

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?

Single sentence with no waste, but could include more detail without harming conciseness.

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?

No output schema, no annotations; description does not explain return value structure or pagination, leaving gaps for a list operation.

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 coverage is 100% with pageId described; tool description adds no extra meaning beyond the schema, meeting baseline.

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 verb 'Get list' and resource 'attachments for a Confluence page', distinguishing it from siblings like confluence_add_labels or confluence_create_page.

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; lacks context about prerequisites or constraints.

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/gkrauchunas-arlo/confluence-mcp'

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