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). |
Interlagos
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states what is returned but lacks details on side effects, authentication requirements, rate limits, or edge cases like empty results.
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 two concise sentences with no fluff. The first sentence states the purpose, the second lists return fields. Every word earns its place.
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 simple tool with one optional parameter and no output schema, the description sufficiently explains the tool's purpose and output fields. It omits potential details like pagination or ordering, but these are not critical for basic usage.
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% (the single 'limit' parameter is described in the schema). The description adds no additional parameter information beyond the schema, but since coverage is high, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves published reviews and lists the returned fields (reviewer name, rating, title, content). It distinguishes from sibling list tools by specifying the resource type, but does not explicitly differentiate from other 'get' tools.
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 guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or exclusions mentioned. The description assumes the agent knows the context.
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
A3.9/5.0
Disambiguation5/5
Every tool targets a distinct Wix resource or action: bookings, events, store, forms, places, menus, etc. The four booking-related tools are clearly separated by domain (appointments, restaurant tables, paid events, free events), with descriptions that eliminate ambiguity.
Naming Consistency4/5
The set follows a consistent verb_noun snake_case pattern (create_, get_, list_, search_, submit_). Minor deviations exist: get_reviews and get_event_tickets return collections (could be list_), and rsvp_event uses an abbreviation, but these do not affect clarity.
Tool Count4/5
At 26 tools, the set is larger than the typical 3–15 well-scoped range, but the server covers a broad umbrella of Wix integrations for a neighborhood directory. Each tool maps to a distinct function, so the count is justified by the scope, though it is on the heavier side.
Completeness4/5
The surface covers discovery and transactional workflows: searching places/dishes, viewing menus/reviews/guides/offers, booking appointments and tables, reserving event tickets, purchasing products, submitting forms, and reading site info. Minor gaps exist (no cancel/update operations), but these are handled via external checkout links and are acceptable for a directory.