Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Yelp businesses

yelp_businesses_search
Read-onlyIdempotent

Search Yelp businesses by name, category, or location to compare ranked listings with ratings, reviews, price, contact details, and coordinates.

Instructions

Search Yelp businesses by name, category, or location. Requires query and location. Returns Yelp's own ranked results with rating, review count, price, phone, categories, address and coordinates; sort by recommended, highest_rated or most_reviewed; 10 per page, up to 24 pages. Pass an alias to yelp_business_get or yelp_reviews_list. Credits: 1 (0 when no businesses).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "location": "<location>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yelp_businesses_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Each page has up to 10 businesses.
sortNoResult order. `recommended` is Yelp's default ranking. `highest_rated` and `most_reviewed` use Yelp's own sorts.
queryYesRequired. Business name, service, or category to search for.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
locationYesCity, neighbourhood, postcode or address to search near.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new operational context: results come from Yelp's own ranking, page size is 10 with a 24-page cap, and the credit cost is 1 with a zero-credit case when nothing matches. Cost and pagination ceilings are not derivable from the schema and are exactly what an agent needs to plan calls.

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?

It is one front-loaded paragraph that leads with the action, then requirements, then return shape, ordering, paging and cost. Every clause carries information, though the semicolon-chained structure is dense and would read faster as short sentences.

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?

With no output schema, the description compensates by enumerating the returned fields (rating, review count, price, phone, categories, address, coordinates), which an agent needs to plan follow-ups. The unusual required analytics parameters (context, llm_model, conversation_id) are left entirely to the schema, which is acceptable but is the one seam in an otherwise complete definition.

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%, so the parameters are already documented. The description restates the required query/location, the sort enum values, and the 10-per-page paging, all of which the schema already specifies, and adds no new syntax or format guidance beyond that. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opening sentence gives a specific verb and resource ('Search Yelp businesses') plus the three search dimensions (name, category, location). The closing sentence positions it relative to yelp_business_get and yelp_reviews_list by explaining that an alias from this result feeds those tools, so an agent can distinguish search from detail-retrieval without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the mandatory inputs ('Requires query and location') and routes the agent downstream by instructing it to pass an alias to yelp_business_get or yelp_reviews_list. What is missing is an explicit negative case — it never says when NOT to use this search (for example, when you already hold a business ID and should call the detail tool directly).

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

Deploy Server

Other Tools