Skip to main content
Glama
rustem-shiriiazdanov

atlassian-marketplace-mcp

by rustem-shiriiazdanov
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

metrics_details_export

Read-onlyIdempotent

Export license-event details for sale metrics (churn, conversion, renewal) as CSV or JSON, with filters for app, hosting, date range, and partner type.

Instructions

Export of license-event details for a sale metric. accept=csv (default) returns the 17-column CSV (addonName,addonKey,hosting,lastUpdated,eventDate,transactionId,licenseId,maintenanceStartDate,maintenanceEndDate,monthsValid,appEntitlementId,appEntitlementNumber,cloudId,inGracePeriod,multiInstanceEntitlementId,multiInstanceEntitlementNumber,appEdition); accept=json returns a JSON array. Same filters as metrics_details_by_metric EXCEPT no offset/limit (full dump). 10-minute timeout (override via EXPORT_TIMEOUT_MS). Large exports spill to a tmp file via the truncation envelope.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoFree-text search across event identifiers (SEN / appEntitlementNumber, transactionId, customer email, etc). Verified to narrow correctly.
addonNoApp key (e.g. `com.example.your-app`). Undocumented but works as an app filter. Prefer `productId`.
orderNoSort direction. **`asc` works; `desc` is unreliable on this endpoint** — Atlassian returns a non-monotonic ordering for `order=desc` (verified 2026-06-03). With no `sortBy`, `order` is ignored entirely. Prefer `sortBy=date&order=asc` and reverse client-side if you need descending.
acceptNoOutput format: `csv` (default for these exports — header-rowed CSV string) or `json` (array of records). Invalid → HTTP 400.
sortByNoSort field. Allowed per Atlassian: `addonName`, `date`, `hosting`, `transactionId`, `licenseId`. Anything else → HTTP 400. Only meaningful combined with `order=asc` (see `order`).
endDateNoISO date YYYY-MM-DD (filters by eventDate).
hostingNoFilter events by hosting. Response objects use capitalized 'Cloud'/'Server'/'Data Center'.
productIdNoProduct UUID — narrows events to one app (documented + verified 2026-06-03; all returned rows match).
startDateNoISO date YYYY-MM-DD (filters by eventDate).
appEditionNoFilter by app edition (free/standard/advanced).
saleMetricYesWhich underlying metric's events to export.
lastUpdatedNoISO date YYYY-MM-DD — events whose lastUpdated is on/after this date. Verified to narrow correctly.
partnerTypeNoFilter by partner attribution channel: `direct`, `expert`, `reseller`. NOTE: Atlassian's error message also lists `upgrade` as allowable, but passing it returns HTTP 400 (Atlassian-side contradiction, verified 2026-06-03) — so it's excluded here.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations declare read-only, open-world, idempotent, non-destructive. Description adds beyond: 10-minute timeout, large export spill, order=desc unreliability, partnerType exclusion of upgrade. This provides rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is fairly long but well-organized, front-loaded with core purpose and format. Each sentence adds specific value (timeout, spill, parameter quirks). A minor reduction could improve conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description details return formats (CSV columns, JSON array). Covers all 13 parameters thoroughly, includes timeout and spill behavior. For a complex export tool, this is highly complete.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant context: text is verified, addon is undocumented, order unreliability, accept defaults, sortBy allowed values, partnerType edge case. This exceeds the schema's descriptions.

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 it exports license-event details for a sale metric, specifying CSV or JSON output. It distinguishes from sibling metrics_details_by_metric by noting no offset/limit and full dump. This meets 'specific verb+resource, distinguishes 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?

The description explicitly compares to metrics_details_by_metric, noting the same filters but no pagination, which guides use for full dumps. Lacks explicit when-not-to-use or alternatives list, but context is clear.

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