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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_store_review_details_get_instance

Retrieve a specific App Store review detail by ID to view reviewer contact info, demo account requirements, notes, and linked app version or attachments.

Instructions

GET /v1/appStoreReviewDetails/{id} (GET /v1/appStoreReviewDetails/{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": "app_store_review_details_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appStoreVersionsNothe fields to include for returned resources of type appStoreVersions
fields_appStoreReviewDetailsNothe fields to include for returned resources of type appStoreReviewDetails
limit_appStoreReviewAttachmentsNomaximum number of related appStoreReviewAttachments returned (when they are included)
fields_appStoreReviewAttachmentsNothe fields to include for returned resources of type appStoreReviewAttachments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/5.0
Behavior1/5

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

Annotations are absent, so the description carries the full behavioral burden, and it discloses nothing: no auth requirements, no error semantics for an invalid/unknown id, no note that this is a non-mutating read. For a zero-annotation tool this is a complete transparency failure.

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 not concise in the useful sense: the identical endpoint string appears twice, so half the content is redundant repetition rather than front-loaded information.

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

Completeness2/5

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

For a six-parameter read tool with no annotations and no output schema, the agent still does not know what shape the response takes (a JSON:API resource with optional included relationships) or how include/fields interact. Only the endpoint path hints at the resource, leaving the definition materially incomplete.

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%, with all six query parameters (id, include, fields_*, limit_appStoreReviewAttachments) documented inline, so the baseline of 3 applies. The description adds nothing about sparse-fieldset or include semantics, but the schema does the heavy lifting.

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 essentially the tool name restated as an HTTP route: 'GET /v1/appStoreReviewDetails/{id}', duplicated verbatim in parentheses. It conveys only that some resource is fetched by id, with no plain-language statement of what an App Store review detail is or how it differs from siblings like app_store_review_details_update_instance or app_clip_app_store_review_details_get_instance.

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, no mention of alternatives or of the related collection/relationship endpoints (e.g. app_store_versions_app_store_review_detail_get_to_one_relationship). The agent must infer everything from the tool name alone.

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