Uneed

Get product reviews

get_reviews

Read-only

Use this when the user wants to read what real users say about a product on uneed.best — the individual community reviews (testimonials) with their star rating. Each entry has rate (1-5, may be null), the review text, the public author_username, like_count and created_at. Only published, top-level reviews are returned — replies and any private user data are excluded. For just the aggregates (average rating and review count) use get_product's stats, which also carries a 3-review preview; call this for the full list. Sort by recent (default, newest first) or top (most liked first). Find the slug with search_products or get_product.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Slug of the product to read reviews for
`sort`	No	'recent' = newest first (default); 'top' = most liked first	recent
`limit`	No

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: only published top-level reviews returned, replies and private data excluded, rate may be null, and sort behaviors (recent vs top). This goes beyond the schema and annotations.

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?

Description is front-loaded with 'Use this when...' and each sentence carries useful information: fields returned, exclusions, alternative tool, sort options, and slug lookup. No fluff; well-structured and appropriately sized.

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

Completeness5/5

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

No output schema exists, but the description lists return fields (rate, review, author_username, like_count, created_at) and explicitly states what is excluded. Coverage is complete for a read-only list tool, addressing data shape, filtering, sorting, and prerequisites.

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 documentation covers slug and sort with descriptions, and limit has constraints. The description adds guidance on how to find the slug, but otherwise mostly repeats schema info. Since schema coverage is 67% (medium), the description provides some added value but doesn't fully compensate for missing limit semantics.

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?

Clearly states the tool reads product reviews on uneed.best, with specific verb 'read', resource 'product reviews', and distinguishes from get_product's aggregates. Mentions testimonials and star ratings, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly contrasts with get_product: use get_product's stats for aggregates, this tool for the full list. Also instructs to find the slug via search_products or get_product, providing clear when-to-use guidance and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Uneed tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation2/5

There are two pairs of tools that essentially do the same thing with different output shapes: search/search_products and fetch/get_product. The descriptions try to separate them by use case, but an agent could easily pick the wrong one, making the boundaries unclear.

Naming Consistency3/5

Tool names mix bare verbs (fetch, search) with prefixed verbs (get_, list_) and include a compound form (search_products). While readable, the naming conventions are inconsistent and lack a single predictable pattern.

Tool Count4/5

With 9 tools, the count is reasonable for the domain, but the redundant pairs (search vs search_products, fetch vs get_product) suggest the set is slightly padded and could be consolidated to around 7 tools.

Completeness4/5

The server covers the core read operations for a product directory: search, product details, categories, deals, recent launches, trending, and alternatives. Minor gaps exist, such as no direct category browse without search, but overall the surface is sufficient for the stated purpose.

Resources

Need Help?