Skip to main content
Glama

yelp_business_reviews_search

Read-only

Search a Yelp business's reviews by keyword, returning a highlighted excerpt per match. 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>",
      "term": "<term>"
    },
    "name": "yelp_business_reviews_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesYelp business alias or encoded id
termYesKeyword to search reviews for

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Yelp business alias or encoded id"
    • addedInput schema / properties / term / description
      Added value: +"Keyword to search reviews for"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value beyond that: it discloses the return shape ('highlighted excerpt per match') and the auth/credential profile ('no login, no cookie required'), which is meaningful context for an agent deciding whether it can call this without credentials.

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 core action front-loaded and the credential note as supporting context. There is 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?

For a read-only, fully-annotated tool with an output schema and 100% param coverage, the description covers what it must. It need not explain return values since the output schema exists, though it could have named the sibling alternative for fuller routing guidance.

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%, with 'id' documented as a Yelp alias/encoded id and 'term' as the keyword, so the schema carries the load. The description's 'by keyword' maps to term but adds no syntax, format, or narrowing detail beyond what the schema already provides.

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+resource+scope: 'Search a Yelp business's reviews by keyword', and the added 'highlighted excerpt per match' further clarifies output. However, it does not differentiate itself from close siblings like yelp_business_reviews or yelp_business_review_highlights, which an agent must disambiguate on its own.

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 when-to-use guidance, no exclusions, and no routing to alternatives such as yelp_business_reviews (full reviews) or yelp_business_review_highlights. The keyword-search angle implies a use case but the description never states when this tool is preferred over its Yelp siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.