Skip to main content
Glama
rustem-shiriiazdanov

atlassian-marketplace-mcp

licenses_export_async_start

Initiate an async license export job, poll the returned ID for the finished file.

Instructions

Start an async license export job. Returns {export:{id}} to poll. accept=csv|json sets the format the eventual download will produce (the start response itself is always the id envelope).

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

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?

Annotations indicate it's not read-only or destructive, and the description adds the async pattern and return envelope. It could mention resource usage or job limits, but overall it's sufficient.

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?

Two concise sentences plus a spec link. No wasted words, front-loaded purpose, and clear formatting.

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?

For a complex 24-parameter async tool with no output schema, the description covers the async flow and accept format but omits any detail about the filter parameters that define the export content. Partially complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 58% schema coverage and no description of the 24 parameters beyond `accept`, the description fails to compensate. Most parameters are crucial for filtering the export and are left to the schema, which has gaps.

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 starts an async license export job, returns an ID to poll, and distinguishes it from siblings like licenses_export_async_status (poll) and licenses_export_async_download (download). It also provides a spec link.

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 explains when to use this tool (to start an async export) and the subsequent polling/download steps. It implies the sync alternative exists but does not explicitly state when not to use it. The spec link adds context.

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