Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

etsy_listing_reviews

Retrieve Etsy buyer reviews by numeric listing ID, including sort order, offset pagination, average rating, total count, and seller reply status.

Instructions

Get Etsy listing reviews. Returns buyer reviews for an Etsy listing, identified by the numeric id. Start from offset (0-based, default 0) and order with sort (newest, oldest, highest_rating, lowest_rating or most_relevant). The response has the average rating and total rating count; each review has buyer, date, rating, text, language and whether the seller replied.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Etsy listing id
sortNoReview sort order
offsetNo0-based review offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "newest",
+  "oldest",
+  "highest_rating",
+  "lowest_rating",
+  "most_relevant"
+]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully describes the response shape (average rating, total count, and per-review buyer/date/rating/text/language/seller-reply fields), but says nothing about auth, rate limits, or a maximum page size — significant gaps for a paginated read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences: purpose first, then parameters, then return shape, with no filler. Every sentence carries information an agent can act on.

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

Completeness4/5

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

With no output schema, the description does the needed work of summarizing return values, and it covers all three parameters. It is nearly complete for a simple read tool, lacking only pagination limits and access requirements.

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 `id`, `sort`, and `offset`. The description adds the default value ('default 0') for offset, which the schema omits, but otherwise restates the enum values and id meaning already present in the schema.

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?

States a specific verb and resource ('Get Etsy listing reviews', 'Returns buyer reviews for an Etsy listing') and pins the target with 'identified by the numeric `id`'. The listing-level scope implicitly separates it from the shop-level sibling etsy_shop_reviews.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case (fetch reviews for a given listing) but never states when to use this versus etsy_shop_reviews or etsy_listing, nor any exclusions or prerequisites. Usage is left to inference from the tool name and id semantics.

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