Skip to main content
Glama

Yelp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Businesses

search_businesses
Read-onlyIdempotent

Search for local businesses and restaurants on Yelp by term and location. Returns matching businesses with star ratings, review counts, price, categories, address, and phone. Example: search_businesses({ term: "pizza", location: "San Francisco, CA" }).

Input Schema

NameRequiredDescriptionDefault
termNoSearch term, e.g. "coffee", "pizza", "plumber". Optional.
limitNoNumber of results to return (default 20, max 50).
priceNoPrice filter as comma-separated levels 1-4, e.g. "1,2,3" for $ to $$$.
_apiKeyNoRequired — your own Yelp Fusion key. Pipeworx fronts no platform key for Yelp (Fusion plan is $229/mo, #2275 open); every call is refused with none.
sort_byNoSort order: "best_match" (default), "rating", "review_count", or "distance".
latitudeNoLatitude of the search center. Use with longitude instead of location.
locationNoLocation to search, e.g. "San Francisco, CA" or "New York". Provide this OR latitude+longitude.
open_nowNoIf true, only return businesses currently open.
longitudeNoLongitude of the search center. Use with latitude instead of location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Yelp Fusion API key for higher limits; omit to use the shared Pipeworx key."New value: +"Required — your own Yelp Fusion key. Pipeworx fronts no platform key for Yelp (Fusion plan is $229/mo, #2275 open); every call is refused with none."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "location": "San Francisco, CA",
+    "term": "pizza"
+  },
+  {
+    "latitude": 37.7749,
+    "longitude": -122.4194,
+    "term": "coffee"
+  }
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds useful output-shape information (star ratings, review counts, price, categories, address, phone) and a concrete example, but it does not disclose practical behavioral details such as API-key requirements or rate limits beyond what the schema already notes.

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 compact, front-loads the core purpose, and includes a helpful usage example. Every sentence contributes value without repetition or filler.

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?

While the core call pattern is clear and the schema fully documents parameters, the description is thin for a tool with nine optional parameters and no output schema. It does not cover filtering options, result limits, or the fact that location can be replaced by coordinates, though these are present in the schema.

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 description coverage is 100%, so the schema already documents each parameter. The description's example reinforces the use of term and location but adds no new semantic understanding beyond what the properties already state.

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 identifies a specific verb ('Search') and resource ('local businesses and restaurants on Yelp'), and clarifies the search mechanism (term and location). It also previews the returned data fields, distinguishing it from more focused tools like get_business or get_reviews.

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?

The description provides no explicit guidance on when to choose this tool over siblings like get_business or get_reviews, and it does not mention alternative search modes (e.g., latitude/longitude) or cases where those would be preferable. Usage context is only implied through the example.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources