Skip to main content
Glama
Hiru-ge
by Hiru-ge

List Customer Reviews

asc_list_customer_reviews
Read-onlyIdempotent

Retrieve customer reviews for any app from App Store Connect. Filter by rating, territory, or sort order, with pagination support.

Instructions

List customer reviews for an app.

Args:

  • appId (string, required): The App Store Connect app ID

  • sort (string): 'createdDate' | '-createdDate' (default) | 'rating' | '-rating'

  • territory (string, optional): ISO 3166-1 alpha-3 territory code filter (e.g. 'USA', 'JPN')

  • rating (number, optional): Filter by star rating, 1-5

  • limit (number): Maximum number of reviews to return (default 20, max 200)

  • nextUrl (string, optional): Pagination URL returned by a previous call

Returns: { "count": number, "items": [ { "id": string, "rating": number, // 1-5 "title": string, "body": string, "reviewerNickname": string, "createdDate": string, // ISO 8601 "territory": string // ISO 3166-1 alpha-3 } ], "nextUrl": string | undefined }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: 'createdDate' (oldest first), '-createdDate' (newest first, default), 'rating' (lowest first), '-rating' (highest first).-createdDate
appIdYesThe App Store Connect app ID to list customer reviews for.
limitNoMaximum number of items to return (default 20, max 200).
ratingNoFilter by star rating (1-5).
nextUrlNoThe nextUrl value returned by a previous call to this tool. Pass it back unchanged to fetch the next page. Omit for the first page.
territoryNoFilter by ISO 3166-1 alpha-3 territory code (e.g. 'USA', 'JPN').
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context by detailing the return structure, pagination via nextUrl, and filtering options, which goes beyond what annotations provide.

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 well-structured and front-loaded with the purpose. It includes a clear argument list and output format. While each sentence adds value, it could be slightly more concise by integrating the output format into the main text.

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?

Despite lacking an output schema, the description provides a complete return structure and explains pagination, filtering, and sorting in detail. It covers all 6 parameters and handles the complexity of paginated results effectively.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by providing examples, default values, and clarifying pagination behavior (e.g., 'Omit for the first page'). This enhances understanding beyond the schema 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 'List customer reviews for an app' with a specific verb and resource. It distinguishes from sibling tools, which are primarily create/update/delete operations on other entities.

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 implies usage (when needing to fetch reviews) but does not explicitly state when not to use or provide alternatives. The context is clear, but no exclusions are mentioned.

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/Hiru-ge/asc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server