Skip to main content
Glama

search_and_scrape

Read-onlyIdempotent

Search the web and scrape full content from top results in a single call, with parallel processing and deduplication across sources.

Instructions

Search the web and extract full content from top results in one call. Scrapes in parallel (max 5 concurrent), deduplicates content across sources, and scores each source on relevance and quality. Returns JSON with fields: query, combinedContent, sources (array of {url, title, content, contentType, scores} — included when include_sources=true), summary ({urlsSearched, urlsScraped, processingTimeMs}), sizeMetadata ({totalLength, estimatedTokens, sizeCategory}). On zero search matches returns empty combinedContent with urlsSearched: 0. Individual scrape failures are silently skipped (urlsScraped < urlsSearched indicates partial failures). num_results controls sources scraped (more = slower, typically 2-15s). Subject to per-tenant rate limit with provider fallback. Use web_search instead if you only need URLs; use scrape_page for a single known URL. Not cached (combines live search + scrape).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe research question or topic to search and extract content for. Use natural language or keyword-rich queries.,required
num_resultsNoNumber of top search results to scrape (1-10, default: 3). More sources = slower but more comprehensive.
include_sourcesNoInclude per-source content and quality scores in response (default: true). Set false to reduce response size.
deduplicateNoRemove duplicate paragraphs across sources (default: true). Disable only if exact repetition matters.
max_length_per_sourceNoMax content bytes extracted per source (default: 50000).
total_max_lengthNoMax total bytes for combined output (default: 300000). Reduce for faster, more concise results.
filter_by_queryNoRemove sources with low relevance to the query (default: false). Enable for precision over recall.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
combinedContentNo
queryNo
sizeMetadataNo
sourcesNo
summaryNo
Behavior5/5

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

The description covers parallel scraping (max 5 concurrent), deduplication, source scoring, response structure, behavior on zero matches, silent failure handling, rate limits, and caching. This adds significant context beyond the annotations, which already indicate read-only and idempotent 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?

The description is well-structured, starting with the core purpose and then detailing behaviors. Every sentence adds value without redundancy, efficiently conveying a lot of information for a complex tool.

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?

Given the tool's complexity (7 parameters, parallel scraping, multiple output fields), the description covers all relevant aspects: usage, performance, failure modes, rate limits, and response structure. It is fully complete even with an output schema present.

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

Parameters5/5

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

With 100% schema coverage, baseline is 3, but the description adds substantial value: explains how num_results affects speed, the impact of include_sources, deduplicate, filter_by_query, and default values. This goes beyond the schema descriptions.

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 description clearly states the tool searches the web and extracts full content from top results in one call. It distinguishes itself from siblings like web_search (only URLs) and scrape_page (single known URL), making the purpose unambiguous.

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?

The description explicitly tells when to use alternatives: 'Use web_search instead if you only need URLs; use scrape_page for a single known URL.' It also discusses performance trade-offs (num_results affects speed) and provides guidance on default behaviors.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zoharbabin/web-researcher-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server