bach-yelp_business_api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for Yelp Business API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reviewsC | Get business reviews by url or id |
| C | Select any category you want to scrape. |
| popular_dishesC | Get popular_dish list of a restaurant when available on the website. |
| get_menus_betaB | Get restaurant menus if present on yelp |
| business_url_to_idC | Find biz id from url. |
| _2D | Use the same search box on yelp.com |
| business_detailsC | Scrape By Yelp URL: Ex. https://www.yelp.com/biz/capital-blossom-day-spa-washington or by business ids found from /search endpoint. You can get these business urls from the \ |
| upcheckC | Check if the api status is live! |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Several tools overlap around business lookup by URL/ID (reviews, business_details, business_url_to_id), and the empty-name and '_2' tools have vague descriptions. An agent cannot reliably distinguish search/category actions from detail/review actions.
Names mix nouns, verb_noun, and abbreviations; one tool has an empty name and another is '_2'. No predictable convention is followed.
8 tools is a reasonable count for a Yelp business scraper and avoids being too thin or too heavy. Some slots are occupied by malformed or unclear tools, but the overall count is appropriate.
The surface covers reviews, menus, popular dishes, business details, URL-to-ID, category scraping, and status checking, but it lacks a clearly named search tool and common Yelp data like photos, hours, or attributes. Notable gaps remain for a full business API surface.