Crawlora MCP

yelp_business_reviews

Read-only

Reviews for a Yelp business by alias or encoded id. 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": {
      "id": "<id>",
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "yelp_business_reviews"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Yelp business alias or encoded id
`limit`	Yes	Max reviews to return, 1-50
`offset`	Yes	Pagination offset

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.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / id / description
```
Added value: +"Yelp business alias or encoded id"
```
- addedInput schema / properties / limit / description
```
Added value: +"Max reviews to return, 1-50"
```
- addedInput schema / properties / offset / description
```
Added value: +"Pagination offset"
```
First observedOct 7, 2026

TDQS

A3.6/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 genuinely new behavioral context: the endpoint is credential-free ('no login, no cookie required'), which is an auth fact the annotations do not convey. It stops short of describing pagination limits or total-result 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 tight sentences with the resource and key type front-loaded and the credential note trailing. No filler or redundancy.

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, return values need not be explained, and annotations carry the safety profile. The description covers the lookup key and auth model, leaving only minor gaps (pagination semantics, business-not-found behavior) for a simple read-only fetch.

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 id, limit (1-50), and offset are already fully documented in the schema. The description's 'alias or encoded id' merely restates the id parameter and adds no syntax, format, or default detail beyond the schema.

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 clear verb+resource ('Reviews for a Yelp business') and adds the lookup key ('by alias or encoded id'). It does not name the close siblings yelp_business_reviews_search or yelp_business_review_highlights, so an agent must infer the distinction from the name alone.

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?

There is no when-to-use guidance and no routing to alternatives, despite an obvious near-duplicate sibling in yelp_business_reviews_search. The agent gets no help deciding between fetching a business's reviews here versus searching them elsewhere.

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.