Decant the web. Extract pure, AI-ready content from any page — Markdown, JSON, MCP.
Scoring was not performed
Output schemas completely undocumented. No visibility into what extract_active_tab, extract_tab, or extract_url return. LLMs cannot plan downstream operations or extract structured data from responses.
Parameter 'format' lacks constraints. Description says '(optional)' but does not specify allowed values. LLMs may hallucinate formats like 'html', 'xml', 'pdf' instead of the documented 'markdown, json, or mcp'. Should use enum constraint.
No error handling documentation. What happens if a tab is closed? If extract fails due to CSP? If the URL is unreachable? LLMs have no recovery guidance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 24 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 28 | - | v1 |
Tool definitions appear inferred from site documentation (site/app/guides/mcp-bridge/page.js reference) rather than visible in explicit MCP tool registration code. Actual server implementation not provided. Cannot verify schema compliance or registration patterns.
Parameter descriptions are minimal. 'Tab ID (required)' and 'URL to extract (required)' lack context on format, type, or example. LLMs need richer descriptions to select tools correctly.
No indication of what data structures are returned or what fields can be expected. For extract_url, is the content returned as a string? Object with metadata? Array of blocks? Undocumented output forces LLMs to guess.