cf_list_reviewsGet reviews for a retailer. Shows ratings and customer feedback.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number | |
| sort | No | Sort order | |
| limit | No | Reviews per page | |
| retailerId | Yes | Retailer UUID |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing the safety profile. The description adds that it 'Shows ratings and customer feedback,' which gives a hint about the response content. However, it does not describe pagination, sorting, or any other behavioral traits, which the schema already covers.
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 exceptionally concise: two short sentences, 'Get reviews for a retailer.' and 'Shows ratings and customer feedback.' It is front-loaded with the key action and provides a brief output preview without any filler. Every word 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?
Given the tool's simplicity, the description covers the core purpose and output content. It does not describe the return format in detail, but no output schema exists and the schema already documents pagination and sorting. With read-only annotations and full schema descriptions, the description is adequately complete for an agent to invoke the tool correctly.
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 all four parameters (retailerId, page, sort, limit). The description does not add any parameter-specific meaning beyond what is in the schema. The baseline of 3 is appropriate since the schema carries the heavy lifting.
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 clearly states the tool's function: 'Get reviews for a retailer.' It uses a specific verb ('Get') and resource ('reviews'), and the title 'List CenuFiltrs Retailer Reviews' reinforces this. Among sibling tools like cf_list_comments or cf_list_offers, this uniquely targets reviews, making it easily distinguishable.
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 explicit guidance is given on when to use this tool versus alternatives. The description simply states what it does, and the name implies it is for reviews. However, it does not mention when not to use it or how it differs from other list tools, such as cf_list_comments or cf_list_offers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes, particularly cf_category_hierarchy vs cf_list_categories (both provide category taxonomy paths) and cf_search_offers vs cf_list_offers (both return offers). Descriptions help, but the boundaries between category-related tools and offer listing/search could confuse an agent.
All tool names follow a consistent cf_ verb_noun snake_case pattern (e.g., cf_add_wish, cf_list_retailers, cf_search_offers). The convention is uniform and predictable, making it easy to infer tool behavior from the name.
With 22 tools, the server covers a broad domain but is slightly heavy. The count is reasonable for a price-comparison service with search, product, price, retailer, user, and comment functionality, though it exceeds the typical ideal range.
The toolset provides solid coverage of the price-comparison domain: search, categories, offers, products, retailers, price history/summary, deal analysis, wishlist, comments/reviews, and user search history. Minor gaps exist (e.g., no product-specific reviews, no comment edit/delete), but core workflows are fully supported.