jina_readerExtract readable content from web pages by providing a URL, with options for paginated content and custom timeouts on slow sites.
Read and extract content from web page.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL of the webpage to read and extract content from | |
| page | No | Page number for paginated content (1-indexed) | |
| customTimeout | No | Override timeout in whole seconds (1-2147483) for slow sites |
Changes observed during successful MCP inspections.
v1.3.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / customTimeout / descriptionPrevious value: -"Override timeout in seconds for slow sites"New value: +"Override timeout in whole seconds (1-2147483) for slow sites"Input schema / properties / customTimeout / exclusiveMinimumAdded value: +0Input schema / properties / customTimeout / maximumAdded value: +2147483Input schema / properties / customTimeout / typePrevious value: -"number"New value: +"integer"Input schema / properties / page / exclusiveMinimumAdded value: +0Input schema / properties / page / maximumAdded value: +9007199254740991Input schema / properties / page / typePrevious value: -"number"New value: +"integer"v1.2.4Input schema / additionalPropertiesRemoved value: -falsev1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, but it discloses nothing about authentication requirements, rate limits, JavaScript rendering, truncation/pagination behavior, or error handling. The presence of customTimeout implies slow sites exist but the description never explains that tradeoff.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single short sentence that is front-loaded with the core action, with zero filler. However, the extreme brevity is under-specification rather than true efficiency for a tool this thin on context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description must explain what comes back and how pagination and timeouts behave; it does neither. An agent cannot tell whether the response is raw HTML, markdown, or plain text, nor how paginated content is returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so url, page, and customTimeout are each documented in the schema itself; baseline 3 applies. The description adds no extra meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb pair (read/extract) and resource (web page), so an agent knows this fetches and parses page content. With no sibling tools to distinguish from, there is nothing more to disambiguate, but it does not clarify output form (markdown vs HTML vs text).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of alternatives, and no conditions under which this tool should be preferred or avoided. The description is purely a statement of function.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.