Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

finance_reports_get_collection

Fetch finance reports from App Store Connect and filter by region, report date, report type, or vendor number to support financial analysis.

Instructions

GET /v1/financeReports (GET /v1/financeReports)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finance_reports_get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_regionCodeNofilter by attribute 'regionCode'
filter_reportDateNofilter by attribute 'reportDate'
filter_reportTypeNofilter by attribute 'reportType'
filter_vendorNumberNofilter by attribute 'vendorNumber'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no auth requirements, no read-only confirmation, no pagination behavior, no rate limits. A bare path string is the minimum possible transparency.

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

Conciseness2/5

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

It is short, but brevity here reflects under-specification rather than conciseness. The parenthetical duplicate of the path is pure waste, and nothing useful is front-loaded.

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

Completeness1/5

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

A four-parameter collection endpoint with no annotations and no output schema needs the description to explain filtering semantics and return shape. None of that is present, so the definition is inadequate for correct invocation.

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 100%, so all four filter parameters (regionCode, reportDate, reportType, vendorNumber) are documented in the schema itself. The description adds nothing, which is acceptable at this coverage level but earns no bonus.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is nothing more than the HTTP method and path repeated twice, effectively restating the tool name. An agent learns only that it retrieves finance reports via GET, with no statement of what a finance report is or what a collection response contains.

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

Usage Guidelines1/5

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

No when-to-use guidance, no prerequisites, and no differentiation from the sibling finance_reports_download tool that also targets finance reports. The agent must guess which of the two to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools