Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Page Images

confluence_get_page_images
Read-onlyIdempotent

Retrieve all image attachments from a Confluence page and return them as base64-encoded inline content that clients can render directly, excluding non-image files.

Instructions

Get all images attached to a Confluence page as inline image content.

Filters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP) and returns them as base64-encoded ImageContent that clients can render directly. Non-image attachments are excluded.

Files with ambiguous MIME types (application/octet-stream) are detected by filename extension as a fallback. Images larger than 50 MB are skipped with an error entry in the summary.

Input Schema

NameRequiredDescriptionDefault
content_idYesThe ID of the Confluence page or blog post to retrieve images from. Example: '123456789'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv1.0.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive behavior beyond them: image-only filtering, base64 ImageContent encoding for direct rendering, MIME-type fallback by filename extension, and a 50 MB skip that surfaces an error entry in the summary. That last detail materially affects how an agent interprets partial results.

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?

Four tight, front-loaded sentences: purpose first, then filtering, then encoding, then edge cases. No sentence is redundant, and each adds a distinct operational fact.

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?

With no output schema, the description still explains the return shape (base64 ImageContent plus error entries in a summary) and the size-limit behavior. An agent has everything needed to call it and interpret the result.

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% and the single parameter is documented with an example in the schema, so the description adds no parameter-specific semantics. Baseline 3 applies since the schema carries the full burden here.

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 ('Get all images attached to a Confluence page') plus the output form ('inline image content'), which lets an agent distinguish it from the attachment-listing and download siblings without opening the schema. The scope is precise and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool returns renderable images, so an agent can infer it should prefer this over confluence_get_attachments when it wants visuals. However, no sibling tool (confluence_get_attachments, confluence_download_attachment, confluence_download_content_attachments) is named, and there are no explicit when-not conditions.

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