Skip to main content
Glama
rustem-shiriiazdanov

atlassian-marketplace-mcp

licenses_list

Read-onlyIdempotent

List paginated licenses for a developer space. Filter by product, hosting, date range, or text search for a specific SEN.

Instructions

List licenses for the developer space (paginated, offset/limit). Use 'text' to find a single license by SEN.

📖 Spec (GET /rest/3/reporting/developer-space/{developerId}/licenses): https://developer.atlassian.com/platform/marketplace/rest/v4/api-group-reporting/#api-rest-3-reporting-developer-space-developerid-licenses-get

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoFree-text search across identifiers: SEN, appEntitlementNumber (Cloud), appEntitlementId (UUID), cloudId, cloudSiteHostname, email, organization name.
tierNo
limitNo
orderNo
offsetNo
sortByNo
statusNo
endDateNoISO date YYYY-MM-DD
hostingNoNote: 'datacenter' is one word, not 'data_center'. Response objects use capitalized 'Cloud'/'Server'/'Data Center' but the filter param is lowercase one-word.
dateTypeNo
productIdNoProduct UUID (or comma-separated list). Use apps_list / apps_known to discover.
startDateNoISO date YYYY-MM-DD
appEditionNoFilter by app edition (case-insensitive in practice but lowercase per Atlassian's error spec).
lastUpdatedNoISO datetime — licenses updated on/after this instant.
licenseTypeNo
partnerTypeNo
licenseLevelNo
withAttributionNoDEPRECATED by Atlassian; use withDataInsights instead. Both add evaluation/attribution fields when true.
withDataInsightsNoAdds 10 extra fields to each license: evaluationOpportunitySize, evaluationLicense, daysToConvertEval, evaluationStartDate, evaluationEndDate, evaluationSaleDate, parentProductBillingCycle, parentProductName, installedOnSandbox, parentProductEdition.
showLicensesHistoryNoIf true, returns the full history of license events for matched SENs (multiple rows per license). Not formally in the swagger but the runtime API accepts it.
includeAtlassianLicensesNoIf true, include internal Atlassian licenses in the result.
showLifeTimeFreeLicensesNoIf true, scope the response to lifetime-free-tier licenses. If false (default), excludes them.
cloudComplianceBoundariesNoCloud compliance boundary. Valid values: 'commercial' (default), 'fedramp_moderate', 'isolated_cloud'. **Cloud-hosted apps only — silently ignored for server/datacenter apps.** Defaults to 'commercial' when omitted on cloud apps. NOTE: This MCP currently accepts a single value; to query multiple boundaries make separate calls (probed 2026-06-01: comma-separated lists are silently mis-parsed by the API — only repeated-param form works server-side).
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context about pagination, offset/limit, and searching by SEN, which is useful beyond annotations. No contradiction.

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?

The description is two sentences plus a link, with front-loaded purpose and key usage. Every sentence adds value, and the link provides additional detail. No wasted words.

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 is minimal for a 23-parameter tool with no output schema. It provides enough to get started (pagination, search), but many filtering options are not addressed. The link to the spec helps, but the description alone lacks completeness for full understanding.

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 57%, so moderate. The description adds meaning for pagination (offset/limit) and the 'text' parameter (find by SEN), but does not explain most other parameters. It partially compensates but not fully.

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 the tool lists licenses for the developer space, is paginated with offset/limit, and highlights a specific use case (using 'text' to find by SEN). This verb+resource combination is distinct from sibling tools like licenses_export_sync or licenses_export_async_start.

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 implies when to use the tool (to list licenses, paginated) and hints at a specific use (find by SEN). However, it does not explicitly exclude alternatives or provide guidance on when to use sibling tools like exports. The context is clear but lacks explicit exclusions.

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/rustem-shiriiazdanov/atlassian-marketplace-mcp'

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