web_fetch_exaRead a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL.
Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | URLs to read. Batch multiple URLs in one call. | |
| maxCharacters | No | Maximum characters to extract per page (default: 3000) |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "errors": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "error": {
- "type": "string"
- },
- "url": {
- "type": "string"
- }
- },
- "required": [
- "url",
- "error"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "results": {
- "items": {
- "additionalProperties": true,
- "properties": {
- "author": {
- "type": "string"
- },
- "publishedDate": {
- "type": "string"
- },
- "text": {
- "type": "string"
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "url": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "searchTime": {
- "type": "number"
- }
- },
- "required": [
- "results",
- "errors"
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "errors": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "url",
+ "error"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "results": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "author": {
+ "type": "string"
+ },
+ "publishedDate": {
+ "type": "string"
+ },
+ "text": {
+ "type": "string"
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "searchTime": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "results",
+ "errors"
+ ],
+ "type": "object"
+}Input schema / properties / maxCharacters / descriptionPrevious value: -"Maximum characters to extract per page (must be a positive number, default: 3000)"New value: +"Maximum characters to extract per page (default: 3000)"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description only needs to add context. It contributes the output shape (clean text plus metadata) and batching behavior, but says nothing about truncation at maxCharacters or rate limits.
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?
Front-loads the core action, then uses tight 'Best for' and 'Returns' labels. Every sentence earns its place with no redundancy.
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?
No output schema exists, so the description appropriately covers the return value (clean text and metadata). It is complete for the core fetch operation, though edge behaviors like truncation are left implicit.
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 both parameters are already documented in the schema. The description's 'Batch multiple URLs in one call' merely restates the urls parameter and adds no syntax or format detail beyond it.
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?
States a specific verb+resource ('Read a webpage's full content as clean markdown') and distinguishes itself from its sibling by naming web_search_exa and its relationship to it. An agent can tell exactly what this tool does versus search.
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?
Explicitly states when to use it ('after web_search_exa when highlights are insufficient or to read any URL'), naming both the triggering alternative and the general case. The 'Best for' line reinforces the intended context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.