Skip to main content
Glama
rustem-shiriiazdanov

atlassian-marketplace-mcp

transactions_export_sync

Read-onlyIdempotent

Synchronously export sales transactions from the Atlassian Marketplace, returning CSV or JSON output.

Instructions

Synchronous export of transactions. accept=csv (default) returns a CSV string; accept=json returns a JSON array. Prefer async for large ranges. Request timeout is 10 min (overridable via EXPORT_TIMEOUT_MS env).

πŸ“– Spec (GET /rest/3/reporting/developer-space/{developerId}/sales/transactions/export): https://developer.atlassian.com/platform/marketplace/rest/v4/api-group-reporting/#api-rest-3-reporting-developer-space-developerid-sales-transactions-export-get

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoFree-text search across identifiers: transactionId, licenseId, SEN, appEntitlementNumber, customer info, partner info.
tierNo
limitNo
orderNo
acceptNoOutput format: `csv` (default for these exports β€” header-rowed CSV string) or `json` (array of records). Invalid β†’ HTTP 400.
offsetNo
sortByNo
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.
saleTypeNo
productIdNoProduct UUID (or comma-separated list). Use apps_list / apps_known to discover.
startDateNoISO date YYYY-MM-DD
appEditionNoFilter by app edition (free / standard / advanced).
lastUpdatedNoISO date/datetime β€” returns transactions updated ON OR AFTER this date (inclusive lower bound).
partnerTypeNo
billingPeriodNoFilter by billing period. Not documented in swagger but accepted by the live API.
paymentStatusNo
includeManualInvoiceNoIf true, includes manually-invoiced transactions in the response.
excludeZeroTransactionsNoIf true, omits $0 transactions (e.g. Cloud Free tier).
cloudComplianceBoundariesNoCloud compliance boundary on the underlying license. Valid: 'commercial' (default), 'fedramp_moderate', 'isolated_cloud'. **Cloud-hosted apps only β€” ignored for server/datacenter.** Single value here; for multiple, make separate calls.
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds behavioral context: synchronous nature, output format behavior (CSV string vs JSON array), and timeout details. This goes beyond annotations without 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?

Two sentences plus a link are highly concise. The purpose and key format guidance are front-loaded. Every sentence adds valueβ€”no fluff.

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 tool with 20 parameters and no output schema, the description omits details like default sorting, pagination behavior, and full field list in output. The spec link partially compensates, but the description alone is not fully self-contained for an agent to understand all important aspects.

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?

With 60% schema description coverage, many parameters already have descriptions in the schema. The description only adds context for the 'accept' parameter (default CSV) and the timeout env variable. It does not significantly enhance parameter understanding beyond the schema.

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 'Synchronous export of transactions' and specifies the output formats (CSV default, JSON). It explicitly contrasts with async variants by recommending async for large ranges, effectively distinguishing this tool from siblings.

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?

Description provides explicit guidance to prefer async for large ranges and mentions the 10-minute timeout (overridable). While it doesn't list all alternatives among the many sibling tools, the key usage advice is clear and actionable.

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