Scrapeless MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRAPELESS_KEY | Yes | Your Scrapeless API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google-searchC | Fetch Google Search Results |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'google-search' has a clear and distinct purpose of fetching Google search results, so agents cannot misselect between multiple options.
The single tool name 'google-search' follows a consistent pattern of verb-noun (search as the verb, Google as the noun context), and with only one tool, there is no inconsistency to evaluate. The naming is clear and adheres to a predictable structure.
The server has only one tool, which feels thin and under-scoped for a scraping-related domain. A single tool for fetching Google search results may not provide sufficient coverage for typical scraping workflows, such as parsing results, handling pagination, or interacting with other search engines, making it borderline too few for the apparent purpose.
Inferring the domain as web scraping or search data fetching, the tool surface is severely incomplete. It only offers a basic search fetch without supporting operations like filtering results, extracting specific data, managing queries, or integrating with other scraping tasks, leading to significant gaps that could cause agent failures in broader scraping scenarios.