MCP server for web scraping using the Scrapeless API
Single tool with minimal definition quality. Tool name 'scrape_markdown' is action-verb-based (positive), but description is extremely brief (54 chars, below 10-char minimum for context). Input schema present but lacks parameter descriptions, the 'url' parameter has only a generic description. No output schema documented. No error handling guidance. No parameter constraints (format, length, allowed values). Tool definition appears inferred from verify_mcp.py rather than explicit server registration code.
Scrape a URL and return its content as markdown
Description is too brief (54 chars). Lacks WHEN to use, WHAT it returns, and prerequisites. LLMs cannot determine when to select this tool over alternatives.
No output schema documented. LLMs cannot plan downstream operations or extract structured data from the response.
Parameter 'url' lacks description. Generic 'The URL to scrape' does not explain format constraints, valid schemes, or error cases.
No error handling guidance. Tool does not document what happens on invalid URLs, network timeouts, or unsupported content types.
Tool definition inferred from verify_mcp.py test script rather than explicit server registration. Actual server implementation (scrapeless-mcp-server) not visible in source.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |