Skip to main content
Glama
ClearFetch - Unblocked Web & Anti-Bot MCP Server

ClearFetch - Unblocked Web & Anti-Bot MCP Server

search_and_read

Search the live web and return clean Markdown from top results in one step, bypassing anti-bot blocks for AI agent context and RAG.

Instructions

Search the live web and return clean Markdown content bundles of top results in a single step for AI agent context / RAG.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_and_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of search results to return (1-10)
queryYesSearch query string
scrape_resultsNoWhether to fetch full clean Markdown for each result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses live web search, top results, clean Markdown output, and single-step operation, but omits permissions, rate limits, freshness, error behavior, and what happens when scrape_results is false.

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?

The description is a single, front-loaded sentence with no filler. It efficiently states the core action, output, and intended use.

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

Completeness3/5

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

There is no output schema, so the description should convey return structure, and it only broadly says 'clean Markdown content bundles.' It is adequate for a simple three-parameter search tool but leaves gaps around output shape, result fields, and scrape_results behavior.

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 description coverage is 100%, so the input schema already documents all three parameters. The description adds minimal parameter meaning beyond 'top results' and 'Markdown content bundles'; it does not explain limit semantics or the scrape_results toggle.

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

Purpose4/5

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

The description states a specific verb and resource: search the live web and return clean Markdown content bundles of top results. It does not explicitly distinguish this tool from siblings read_url or extract_structured_data, though 'in a single step' implies a combined search-and-read behavior.

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

Usage Guidelines3/5

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

The description gives a use case ('for AI agent context / RAG') and implies usage for one-step search plus content retrieval. However, it does not state when to use this instead of read_url or extract_structured_data, nor when not to use it.

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

Deploy Server

Other Tools