web-fetch-tool changedagents-and-tools/tool-use/web-fetch-tool
Nearest release: v2.1.308, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−5removed
From line
522
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits16to this page, all time
The whole hunk
from line 522, old and new numbered
/
from line 522
522522
523523Here's an example response structure:
524524
525```json Output
525```text Output
526526{
527527 "role": "assistant",
528528 "content": [
from line 606
606606
607607For PDF documents, content is returned as base64-encoded data:
608608
609```json Output
609```text Output wrap
610610{
611611 "type": "web_fetch_tool_result",
612612 "tool_use_id": "srvtoolu_02",
from line 631
631631
632632When the web fetch tool encounters an error, the Claude API returns a 200 (success) response with the error represented in the response body. Claude receives the error result and continues the turn. For example:
633633
634```json Output
634```text Output wrap
635635{
636636 "type": "web_fetch_tool_result",
637637 "tool_use_id": "srvtoolu_a93jad",
from line 958
958958
959959With streaming enabled, fetch events are part of the stream with a pause during content retrieval:
960960
961```sse Output
961```text Output
962962event: message_start
963963data: {"type": "message_start", "message": {"id": "msg_abc123", "type": "message"}}
964964
from line 991
991991
992992Web fetch usage has **no additional charges** beyond standard token costs:
993993
994```json
994```text wrap
995995{
996996 "usage": {
997997 "input_tokens": 25039,
No line in this hunk matches that.