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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

customer_reviews_response_get_to_one_related

Retrieve the response to a single App Store customer review by ID, including optional fields and related review details.

Instructions

GET /v1/customerReviews/{id}/response (GET /v1/customerReviews/{id}/response)

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": "customer_reviews_response_get_to_one_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_customerReviewsNothe fields to include for returned resources of type customerReviews
fields_customerReviewResponsesNothe fields to include for returned resources of type customerReviewResponses

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 and delivers nothing: no statement of read-only semantics, authentication or permission requirements, error behavior, or the fact that this returns a single related resource. A bare URL path discloses no behavioral traits.

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 is under-specification rather than conciseness; the sentence is a redundant restatement of the name and path with zero informational content. Nothing is front-loaded because nothing is said.

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 4-parameter, 100%-coverage endpoint with no output schema and no annotations, the description should explain sparse fieldsets, the include relationship, and what resource is returned. It explains none of these, leaving the agent with only the path template.

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 id, include, fields_customerReviews and fields_customerReviewResponses are each documented in the schema. The description adds no meaning beyond the schema, which is the baseline 3 case when structured fields do the work.

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 but the raw HTTP route restated, duplicating the tool name. It conveys that this is a GET on a customer review response, but offers no articulation of purpose and nothing to distinguish it from near-identical siblings such as customer_reviews_response_get_to_one_relationship or customer_review_responses_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?

There is no when-to-use, when-not-to-use, or alternative guidance of any kind. An agent must infer from the name alone whether this is the right tool versus the relationship/related variants that appear as siblings.

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