Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yelp_search

Search Yelp businesses by term and location without login or API keys. Returns structured JSON from Yelp's Android app backend.

Instructions

Search Yelp businesses. Searches Yelp's real Android app business-search backend for a term and location. Credential-free: no login, no API key, no cookie required from the caller.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term
limitNoMax results to return, 1-50
offsetNoPagination offset
locationYesNeighborhood, city, state, or zip code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job by disclosing a key behavioral trait: credential-free access (no login, API key, or cookie). It also reveals that it uses Yelp's real Android app backend, which hints at an unofficial integration. This goes beyond a typical minimal description, though it does not cover rate limits or output structure.

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?

The description is two sentences, front-loaded with the core purpose, and every word adds value. It is efficient and well-structured without redundancy.

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?

For a tool with 4 parameters and no output schema, the description is adequate but not complete. It covers the essential auth trait and search scope but does not describe the return format or any pagination behavior. Given the absence of an output schema, the agent would benefit from more detail on what results look like.

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 the schema already documents all four parameters. The description only mentions 'term and location' in a general sense, adding no new semantics beyond what the schema provides. It does not enhance understanding of limit/offset behaviors.

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 description clearly states the tool's function: 'Search Yelp businesses.' It specifies the resource (Yelp businesses) and the action (search), which distinguishes it from other Yelp tools like yelp_business (details) and yelp_business_reviews. The added detail about using Yelp's real Android app business-search backend further clarifies its scope.

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 description implies usage context (for term+location business searches, credential-free) but does not explicitly state when to use this tool over alternatives or mention any exclusions. There is no reference to sibling tools or conditions where another tool might be more appropriate.

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