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

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Space Permissions

confluence_get_space_permissions
Read-onlyIdempotent

List all permission assignments for a Confluence space.

Instructions

List all permission assignments for a Confluence space.

Wraps GET /wiki/api/v2/spaces/{id}/permissions.

Note: This tool is only available for Confluence Cloud. Server/Data Center instances use different permission APIs.

Returns a JSON object with a 'results' list of permission assignment objects. Each entry contains the principal (user or group), the operation permitted, and the target. Use this to audit who has access to a space.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of permission entries to return. Defaults to 25.
cursorNoOptional pagination cursor from a previous response.
space_idYesNumeric ID of the Confluence space. This is the internal space ID, not the space key. Example: '98304'. You can find the space ID from the Confluence REST API (GET /wiki/api/v2/spaces) or from the space URL.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Addedv1.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: the Cloud-only platform constraint and the backing endpoint (GET /wiki/api/v2/spaces/{id}/permissions). With readOnlyHint/idempotentHint already declaring safety, the remaining gap is pagination behavior, which is only implied by the cursor parameter.

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?

Front-loaded purpose sentence, then platform caveat, then return shape and use case — every line contributes. No filler or restatement of the title.

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?

Covers platform applicability, the underlying endpoint, and the shape of the response, which is more than enough given an output schema exists. The only omission is explicit guidance on iterating with the cursor, a minor gap for a paginated read.

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% and the space_id description already explains internal ID vs. key with an example, so the schema carries the parameter burden. The description adds no parameter-level detail beyond what is documented.

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 all permission assignments for a Confluence space') and the space-level scope implicitly separates it from page-level siblings like confluence_get_page_restrictions and confluence_check_content_permissions.

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?

'Use this to audit who has access to a space' gives a concrete context, and the Cloud-only note acts as a when-not-to-use exclusion. It stops short of naming the alternative tools for page-level or Server/DC permission checks.

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