get_reviews
Get published reviews for this site (Wix Reviews). Returns reviewer name, rating, title, and content.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max reviews to return (default 10, max 50). |
Genesis Social
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavior like pagination, authentication, or read-only nature. It only mentions returned fields but lacks details on sorting, filtering, or side effects.
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?
The description is extremely concise with two short front-loaded sentences, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description does not fully describe return structure (e.g., sorting, pagination), leaving gaps for a retrieval tool with a single optional parameter.
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 coverage is 100% with one parameter well-documented. The description adds no additional meaning beyond the schema, returning baseline score of 3.
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?
The description clearly states the action ('Get') and the resource ('published reviews for this site (Wix Reviews)'), and lists the returned fields, distinguishing it from sibling tools that deal with other entities.
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 usage for retrieving reviews but provides no explicit guidance on when to use it versus alternatives or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool targets a distinct action and domain, with clear descriptions preventing confusion. Similar tools like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are differentiated by service type and workflow.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_categories), ensuring predictability and ease of use for agents.
Tool Count4/5
With 28 tools, the set is fairly large but appropriate for a comprehensive neighborhood directory covering multiple domains (places, events, booking, store, forms, etc.). Each tool serves a distinct purpose without redundancy.
Completeness5/5
The tool surface covers the full lifecycle of common user needs: search and discovery, detailed info, reservations, purchases, and interactions (forms, FAQs). No obvious gaps for the described purpose of a neighborhood directory.