Skip to main content
Glama

yelp_scraper

Extract Yelp business listings by keyword and location, with category, sort, attribute filters, and pagination support.

Instructions

Extract business listings from Yelp by keyword and location, with support for category filters, sorting, attribute filters, and pagination. [Credits: 4 credits per successful request] Notes: Pagination uses the 'start' offset param in increments of 10 (matches Yelp's own pagination scheme); response includes a pagination.next URL. yelp_domain allows targeting international Yelp TLDs. Returns: Object with: filters { category[]: {text,value}, price[]: {text,value}, distance[]: {text,value} }, inline_ads[], sponsored_ads[]: {title,url,rating,review_count,price,categories[],neighborhood}, organic_results[]: {title,url,rating,review_count,price,categories[],neighborhood,thumbnail}, pagination: {next}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lNoDistance or map radius string to narrow results by geographic area.
cfltNoCategory filter to narrow results to a specific Yelp category (e.g., 'restaurants', 'bars').
attrsNoRefine results by business attributes (e.g., 'GoodForKids', 'WheelchairAccessible').
startNoPagination offset. Use multiples of 10 to paginate through results (e.g., 10, 20). (default: 0)
sortbyNoSort method for results. Accepted values: recommended, rating, review_count. (default: recommended)
find_locYesTarget location for the search (e.g., 'San Francisco, CA').
find_descNoThe search query term (e.g., 'burger', 'pizza', 'coffee').
yelp_domainNoThe Yelp domain to scrape (e.g., 'yelp.com', 'yelp.co.uk').
Behavior3/5

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

Discloses credit cost (4 credits) and pagination scheme (start offset in increments of 10, next URL). However, lacks details on potential restrictions, rate limiting, or authentication requirements. Without annotations, more behavioral context would be beneficial.

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?

Description is three sentences, front-loaded with purpose, and contains no unnecessary words. Efficient and clear.

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?

Despite no output schema, the description adequately explains the return structure (filters, ads, organic_results, pagination). Covers pagination details, credit cost, and domain targeting. Missing some nuance on parameter interdependencies but generally complete for a scraper tool.

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%—every parameter is described in the schema. The tool description adds marginal semantics like pagination explanation and domain targeting, but overall adds limited value beyond the schema.

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?

Clearly states the verb (extract), resource (business listings from Yelp), and key parameter categories (keyword, location, filters, sorting, pagination). Distinguishes from sibling scraper tools by targeting Yelp specifically.

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?

Does not provide when-to-use or when-not-to-use guidance. With many sibling scraper tools (e.g., google_search, amazon_search), explicit guidance on selecting this tool for Yelp-specific scraping is missing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server