ReadFetch

readfetch_search

Read-only

Run a web search without a separate search API subscription. Returns titles, URLs, and snippets only — not full page text; follow with readfetch_text, readfetch_probe, or readfetch_scrape on a chosen result URL. limit is 1–20 (default 5). Optional lang biases locale (e.g. en, de-DE). Optional tbs filters recency: h= past hour, d= day, w= week, m= month, y= year. Use readfetch_map/readfetch_crawl when you already know the site; readfetch_* URL tools when you have the link.

Input Schema

Name	Required	Description
`tbs`	No	Optional recency filter: h=hour, d=day, w=week, m=month, y=year.
`lang`	No	Optional language/locale hint, e.g. en or de-DE.
`limit`	No	Maximum number of results to return (default 5).
`query`	Yes	Search query string.

Output Schema

Name	Required	Description	Default
`hint`	No
`query`	No
`billed`	No
`status`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedOutput schema / properties / hint / type
```
Previous value: -"null"New value: +[
+  "string",
+  "null"
+]
```

Changed5 schema fields changedNov 1, 2026

changedInput schema / properties / lang / description

Previous value: -"e.g. en, de-DE"New value: +"Optional language/locale hint, e.g. en or de-DE."

addedInput schema / properties / limit / description

Added value: +"Maximum number of results to return (default 5)."

addedInput schema / properties / query / description
```
Added value: +"Search query string."
```

changedInput schema / properties / tbs / description

Previous value: -"Time range."New value: +"Optional recency filter: h=hour, d=day, w=week, m=month, y=year."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "billed": {
+      "type": "boolean"
+    },
+    "hint": {
+      "type": "null"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "position": {
+            "type": "integer"
+          },
+          "snippet": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 1, 2026

removedInput schema / properties / egress

Removed value: -{
-  "description": "Exit to leave through: `direct` (this service's own datacentre egress) or `residential` (a residential address pool, for targets that refuse datacentre addresses). Omit to use the default route.",
-  "title": "Egress",
-  "type": "string"
-}

First observedNov 1, 2026

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so safety semantics are covered. The description usefully adds the return-surface constraint (snippets, not page text) and the 'no separate search API subscription' framing, but says nothing about result ordering, rate limits, or empty-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and output scope, then constraints, then routing. Every clause carries information; no filler or repeated title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still gives the one detail an agent needs to decide downstream tooling (snippet-only results). Combined with the full sibling routing, an agent can select and chain this tool without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters are already documented including the tbs enum and limit bounds. The description restates the limit range and tbs values without adding syntax or edge-case guidance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource ('Run a web search') and immediately bounds the output ('Returns titles, URLs, and snippets only — not full page text'). This distinguishes it from the readfetch_text/scrape siblings that fetch page content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: follow with readfetch_text/probe/scrape on a chosen URL, use readfetch_map/crawl when the site is already known, and readfetch_* URL tools when a link exists. Both the next step and the exclusion conditions are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ReadFetch tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?