Skip to main content
Glama
rustem-shiriiazdanov

atlassian-marketplace-mcp

licenses_export_sync

Read-onlyIdempotent

Export marketplace license data synchronously in CSV or JSON format with extensive filtering options for reporting.

Instructions

Synchronous export of licenses. accept=csv (default) returns a CSV string; accept=json returns a JSON array. May 5xx on large ranges — prefer the async variant. Request timeout is bumped to 10 min (overridable via EXPORT_TIMEOUT_MS env).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoFree-text search across identifiers: SEN, appEntitlementNumber (Cloud), appEntitlementId (UUID), cloudId, cloudSiteHostname, email, organization name.
tierNo
limitNo
orderNo
acceptNoOutput format: `csv` (default for these exports — header-rowed CSV string) or `json` (array of records). Invalid → HTTP 400.
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?

While annotations already provide readOnlyHint, idempotentHint, etc., the description adds valuable behavioral context: potential 5xx errors on large ranges, specific timeout behavior, and format handling (accept parameter). No contradictions with annotations.

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?

Description is concise and well-structured: opens with purpose, then key caveats, then spec link. Every sentence adds necessary information without redundancy.

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?

Given the tool's complexity (24 parameters, no output schema), the description covers critical behavioral aspects (sync vs async, timeout, error cases, format). Could mention exact return type (CSV string vs JSON array) but the 'accept' description helps. Spec link provides fallback.

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 58%, and the description does not significantly enrich parameter understanding beyond the schema. It mentions the 'accept' parameter's effect but doesn't elaborate on other parameters. Baseline 3 is appropriate.

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's function: synchronous export of licenses. It specifies output formats (CSV/JSON) and distinguishes from sibling async variants, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicit guidance: 'May 5xx on large ranges — prefer the async variant' provides clear when-to-use and when-not-to-use criteria. Also mentions configurable timeout, aiding correct invocation.

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