Skip to main content
Glama

Yelp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Reviews

get_reviews
Read-onlyIdempotent

⚠️ UPSTREAM-UNRELIABLE — Yelp Fusion's /reviews endpoint has been 404-ing on most ids since mid-2026 even for valid businesses. PREFER get_business (which sometimes inlines a snippet) or search_businesses for review-context queries. If you must call get_reviews: pass the ENCRYPTED business id (long alphanumeric, e.g. "WavvLdfdP6g8aZTtbBQHTw") returned in search_businesses results — aliases / slugs (e.g. "garaje-san-francisco") reliably 404. Returns up to 3 review snippets per business (rating, text, author, timestamp); "limit" is capped by Yelp upstream regardless of what you pass.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesYelp business id or alias (from search_businesses results).
limitNoNumber of reviews to return (default 3, max 50).
_apiKeyNoOptional — your own Yelp Fusion API key for higher limits; omit to use the shared Pipeworx key.
sort_byNoSort order: "yelp_sort" (default) or "newest".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "WavvLdfdP6g8aZTtbBQHTw",
+    "limit": 3,
+    "sort_by": "yelp_sort"
+  },
+  {
+    "id": "WavvLdfdP6g8aZTtbBQHTw",
+    "limit": 5,
+    "sort_by": "newest"
+  }
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses behavioral traits beyond annotations: endpoint unreliability (404), limit capped by Yelp upstream, return format (rating, text, author, timestamp), and the need for encrypted ID. Consistent with readOnlyHint, openWorldHint, idempotentHint, and destructiveHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While informative and well-structured with a warning upfront, the description is somewhat lengthy. Every sentence adds value, but could be tightened slightly without losing clarity.

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?

Given the complexity (4 parameters, no output schema), the description fully compensates: explains return format, limit behavior, required ID format, and reliability issues. No gaps remain for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds critical context: id must be encrypted (format example), limit is capped by Yelp, sort_by options are clarified, and _apiKey is explained as optional. This adds significant value beyond the schema.

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 tool retrieves reviews from Yelp Fusion, specifies it returns up to 3 snippets, and distinguishes itself from siblings like get_business and search_businesses. The verb 'get' is appropriate and 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 advises when to prefer alternatives (get_business, search_businesses) for review-context queries, provides specific requirements (encrypted business id from search_businesses), warns against using aliases/slugs, and mentions the upstream unreliability.

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

All Yelp toolsInspect
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.

Resources