Fetch buyer reviews for a specific Etsy listing using its numeric ID. Sort by newest, oldest, rating, or relevance with offset pagination.
Get Etsy listing reviews. Returns buyer reviews for an Etsy listing.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric Etsy listing id | |
| sort | No | Review sort order | |
| offset | No | 0-based review offset |
Changes observed during successful MCP inspections.
v1.17.5Input schema / properties / sort / enumAdded value: +[
+ "newest",
+ "oldest",
+ "highest_rating",
+ "lowest_rating",
+ "most_relevant"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Returns buyer reviews.' It does not mention pagination behavior, default sort order, rate limits, or any other operational traits beyond the basic read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded, with the core action in the first sentence. The second sentence is slightly redundant but adds the 'buyer reviews' specificity, so it earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 3-parameter tool with full schema coverage, the description is minimally adequate. However, with no output schema and no annotations, it lacks details on pagination limits, default sort, or response structure, leaving some gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 id, sort, and offset. The description adds no additional parameter meaning, which is acceptable given the schema's completeness.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Get Etsy listing reviews' and clarifies it returns buyer reviews for an Etsy listing. It is clear and distinct from sibling tools like etsy_shop_reviews, though it does not explicitly name or contrast those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as etsy_shop_reviews or etsy_listing. The description only states what the tool does, leaving the agent to infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.