Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

etsy_shop_reviews

Fetch buyer reviews for any Etsy shop by name or numeric id, including ratings, review text, dates, and seller replies, with pagination and average rating.

Instructions

Get Etsy shop reviews. Returns buyer reviews for an Etsy shop, identified by the required id (a numeric shop id or a shop name). Page with offset (default 0) and limit (default 14). The response has the average rating and total rating count. Each review has buyer, date, rating, text, language, the reviewed listing, and whether the seller replied.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Etsy shop id or shop name
limitNoPage size (default 14)
offsetNo0-based review offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 it does add real behavioral context: it discloses pagination defaults (offset 0, limit 14) and the full shape of the response (average rating, total count, and per-review fields including seller reply). It omits auth requirements, rate limits, and ordering, but the return-value disclosure is meaningful given there is no output schema.

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?

Front-loaded with the core purpose, then identity, then pagination, then response shape. Sentences are tight; the enumeration of review fields is slightly long but earns its place since no output schema exists.

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 annotations and no output schema, the description covers the essentials an agent needs: what is returned, how to page, and how to identify the shop. It is only short on the when-to-use-vs-siblings dimension, which is captured separately.

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 all three parameters (id, limit, offset) are already documented. The description largely restates the schema, adding only a note that `id` accepts a numeric id or a name, which is already in the schema. Baseline 3 is appropriate.

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/Returns buyer reviews for an Etsy shop') and scopes it to shop-level reviews, which implicitly separates it from the sibling etsy_listing_reviews. An agent can tell what it retrieves without opening the schema.

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 establishes the scope (shop reviews vs listing reviews) but never states when to use this tool over alternatives like etsy_listing_reviews, etsy_shop, or etsy_shop_listings. Usage is only implied by the resource name.

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