Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

macys_product_reviews

Retrieve a page of customer reviews for a Macy's product by numeric ID, plus rating summary with counts, average, recommendation ratio, and histogram.

Instructions

Get a Macy's product's customer reviews. Returns one page of a Macy's product's customer reviews, plus a site-wide rating summary (rating count, average rating, recommended ratio, rating histogram) for the product. product_id is a numeric id, the same one used by GET /macys/product/{productId}. A product with zero reviews, or a well-formed but unrecognized product_id, returns a normal, empty result rather than an error.

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": {
      "product_id": "<product_id>"
    },
    "name": "macys_product_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1-based, defaults to 1
product_idYesNumeric Macy's product id, from a product page's ?ID= query parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does good work: it discloses that results come as one page plus a site-wide rating summary (count, average, recommended ratio, histogram), and critically that zero-review or unrecognized ids return an empty result rather than an error. It stops short of describing pagination behavior or total page counts, so not a 5.

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?

Three sentences, tightly front-loaded: purpose, then return shape, then id semantics and the empty-result edge case. Every sentence earns its place with no redundancy.

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?

For a two-param read tool with no output schema, the description covers return contents, id sourcing, and the important empty-result behavior. Pagination navigation (page size, end-of-results signaling) is the one meaningful omission. No annotations exist to offload the burden, so this is close to complete.

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 the baseline is 3, but the description adds real meaning: it pins product_id as the same numeric id used by GET /macys/product/{productId}, establishing cross-endpoint consistency beyond the schema's 'from a product page's ?ID= parameter'. The page parameter gets no added treatment.

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 a Macy's product's customer reviews') and immediately distinguishes itself from the macys_product sibling by returning review data rather than product data. An agent can tell what this does 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 Guidelines2/5

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

No explicit when-to-use, when-not-to-use, or sibling routing guidance. The cross-reference to GET /macys/product/{productId} hints that product_id comes from macys_product, but the description never says to call this tool for reviews versus macys_product for product details, leaving selection to inference.

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