MCP server providing tools for fetching URL content and performing web searches using Jina Reader API, deployed on Vercel
Two tools with complete Zod schemas and detailed descriptions. fetch_url_content has 13 well-typed optional parameters with clear descriptions mapping to Jina API headers. search has 19 parameters including enums, arrays, and constraints. Both descriptions exceed 100 chars and explain the service (Jina Reader API). However, output schemas are not documented, LLMs cannot predict response structure. No error recovery guidance. Parameters lack dependency documentation (e.g., count vs num are alternatives). No pagination guidance for search results. Tool names follow verb_noun pattern correctly.
Fetches content from a URL using Jina Reader API (r.jina.ai). Supports options like API key, image alt generation, cookie forwarding, output formats (markdown, html, text, screenshot URL), proxy, caching, CSS selectors, timeout, JSON output, and POST method for URLs with hash fragments.
Performs a web search using Jina Reader API (s.jina.ai). Supports various search parameters including type (web/images/news), provider (Google/Bing), language, location, and search operators.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination). fetch_url_content returns text; search returns what? JSON array? Paginated? Requires reverse-engineering from Jina API docs.
search tool has two alternative parameters (count vs num) with identical constraints but no documentation of mutual exclusivity or precedence. LLMs will pass both, causing ambiguity.
No error recovery guidance. If Jina API returns 429 (rate limit), 401 (invalid key), or 404 (URL not found), the error message is raw HTTP status + text. LLM cannot determine if retry is safe or what to do next.
search tool lacks pagination guidance. No mention of result limits, total count, or next_cursor. If Jina returns 100+ results, LLM has no way to fetch page 2 or know when results are exhausted.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2026-07-28+ | v2 |
apiKey parameter exposed in tool signature for search tool. Should be injected server-side via environment variable. Agents log all parameters, API keys in params leak into traces.