Crawlora MCP

yelp_search

Read-only

Search Yelp businesses by term and location. Credential-free: no login, no cookie required.

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": {
      "term": "<term>",
      "location": "<location>"
    },
    "name": "yelp_search"
  }
}

Input Schema

Name	Required	Description
`term`	Yes	Search term
`limit`	No	Max results to return, 1-50
`offset`	No	Pagination offset
`location`	Yes	Neighborhood, city, state, or zip code

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 7, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Max results to return, 1-50"
```
- addedInput schema / properties / location / description
```
Added value: +"Neighborhood, city, state, or zip code"
```
- addedInput schema / properties / offset / description
```
Added value: +"Pagination offset"
```
- addedInput schema / properties / term / description
```
Added value: +"Search term"
```
First observedOct 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds value beyond that by disclosing the credential-free auth requirement, which is a real behavioral trait an agent needs when planning calls. It stops short of mentioning rate limits, pagination behavior, or result-count semantics.

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 short sentences, zero filler, purpose front-loaded and the auth constraint immediately after. Every clause carries information.

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 an output schema present and annotations covering safety, the description only needed to add auth/access context, which it does. Nothing critical is missing, though it could route agents away from the sibling Yelp lookup tools.

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 term, location, limit, and offset are already documented with types and, for limit, a range. The description's phrase 'by term and location' adds nothing beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (Search) plus resource (Yelp businesses) and scoping inputs (term, location), so the operation is unambiguous. However, it does not distinguish itself from siblings such as yelp_business, yelp_geocode, or yelp_business_reviews_search, which also live in the Yelp namespace.

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

Usage Guidelines3/5

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

The 'credential-free: no login, no cookie required' line implicitly tells the agent when this tool is preferable (no auth available), but no sibling tool or condition is named as an alternative. Usage is implied by the generic search semantics rather than stated.

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

All Crawlora MCP tools Inspect

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.