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

TableJSON 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 $$$.
_apiKeyNoOptional — your own Yelp Fusion API key for higher limits; omit to use the shared Pipeworx key.
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
    • addedInput schema / examples
      Added value: +[
+  {
+    "location": "San Francisco, CA",
+    "term": "pizza"
+  },
+  {
+    "latitude": 37.7749,
+    "longitude": -122.4194,
+    "term": "coffee"
+  }
+]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds return fields (ratings, reviews, price, etc.) and an example, but does not mention potential rate limits or pagination behavior.

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?

Two sentences plus example, front-loaded with purpose and return info. No redundant content.

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?

Explains return fields adequately given no output schema, but lacks mention of key parameter interplay (e.g., location vs lat/lng, limit, sort_by). Adequate but not thorough.

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% and description does not add details beyond the schema. Baseline score applies; description merely references term and location in example.

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?

Description clearly states it searches for local businesses and restaurants on Yelp by term and location, and lists return fields. However, it does not differentiate from related siblings 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?

No guidance on when to use this tool versus alternatives. Does not mention conditions like location vs lat/lng requirement, or when to use get_business for a single result.

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