bach-walmart_scraper4
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | 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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_product_data_from_urlC | This API endpoint is used to collect product information from a URL |
| monitor_statusA | Some scraping data may take longer than average. If that's the case, you'll get a task_id. Use it to retrieve your data when it's complete. |
| discover_top_products_in_a_category_by_keywordC | This endpoint if for discovering top products from a given category keyword. |
| discover_top_products_in_a_categoryB | This API endpoint scrapes top products in a given category. It takes URL as parameter. |
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 4 tools
The two 'discover_top_products' tools have overlapping purposes and could be confused, with the only clear distinction being the input type (URL vs keyword) described in the text. Other tools are distinct in function.
All names use snake_case, but there is no consistent pattern: 'get_product_data_from_url' and 'discover_top_products_in_a_category_by_keyword' are long and descriptive, while 'monitor_status' is short. Verbs vary and one pair of tools differs only by a trailing qualifier.
Four tools is a reasonable scope for a scraper server. However, having two very similar discovery tools adds slight redundancy and makes the set feel less concise than it could be.
The set covers the core scraping workflow: fetching a single product, discovering top products by two methods, and checking async task status. No obvious critical gaps are present for the stated purpose.