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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

review_submissions_get_instance

Retrieve details of a specific App Store review submission by ID, including its state, platform, and related app, items, and actors.

Instructions

GET /v1/reviewSubmissions/{id} (GET /v1/reviewSubmissions/{id})

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appsNothe fields to include for returned resources of type apps
limit_itemsNomaximum number of related items returned (when they are included)
fields_actorsNothe fields to include for returned resources of type actors
fields_appStoreVersionsNothe fields to include for returned resources of type appStoreVersions
fields_reviewSubmissionsNothe fields to include for returned resources of type reviewSubmissions
fields_reviewSubmissionItemsNothe fields to include for returned resources of type reviewSubmissionItems

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 burden, yet it discloses nothing beyond the HTTP method. It does not say whether authentication is required, what the sparse-fieldset/include parameters actually change in the response, or what happens on a missing/invalid id.

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 the brevity comes from under-specification rather than efficiency, and the route string is needlessly duplicated in parentheses. Nothing is front-loaded because there is nothing informative to front-load.

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?

For a get-instance endpoint with eight parameters (relationship inclusion, sparse fieldsets for five resource types, related-item limits) and no output schema, the description is completely inadequate. An agent cannot know the response shape or the purpose of including relationships from this text.

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 the schema already documents all eight parameters including the include relationships and fields_* sparse fieldsets; the baseline for full coverage is 3. The description contributes no additional parameter meaning whatsoever.

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 only restates the HTTP route 'GET /v1/reviewSubmissions/{id}' (duplicated verbatim in parentheses), which is a tautology of the operation rather than a statement of purpose. It gives no indication of what a review submission is or how this differs from the sibling review_submissions_get_collection, aside from the implicit single-vs-many shape of the path.

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?

There is no guidance at all on when to call this tool versus alternatives such as review_submissions_get_collection, review_submissions_items_get_to_many_related, or review_submissions_update_instance. The agent must infer usage purely from the tool name and route.

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