Skip to main content
Glama
zoharbabin

Google Researcher MCP

Search and Scrape

search_and_scrape
Read-only

Search Google and retrieve content from top results in one call. Returns combined, deduplicated content with source attribution.

Instructions

Search Google AND retrieve content from top results in one call. Returns combined, deduplicated content with source attribution.

When to use:

  • Primary tool for answering questions that need web research

  • Need content from multiple sources combined

  • More efficient than calling google_search + scrape_page separately

When to use other tools instead:

  • google_search: When you only need URLs without content

  • scrape_page: When you already have a specific URL

Content size control:

  • max_length_per_source: Limit content per source (default: 50KB)

  • total_max_length: Limit total combined content (default: 300KB)

  • filter_by_query: Only include paragraphs containing query keywords

Caching: Search results cached for 30 minutes, scraped pages for 1 hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesYour research question or topic. Be specific for better results. Example: 'Python async best practices 2024' rather than just 'Python'.
num_resultsNoNumber of sources to fetch (1-10). Default 3 is good for most queries. Use 5-8 for comprehensive research, 1-2 for quick factual lookups.
include_sourcesNoInclude source URLs at the end for citation. Default true - recommended for transparency.
deduplicateNoRemove duplicate content across sources. Default true - recommended to reduce noise when sources quote each other.
max_length_per_sourceNoMaximum content length per source in characters. Default: 50KB.
total_max_lengthNoMaximum total combined content length. Default: 300KB.
filter_by_queryNoFilter to only include paragraphs containing query keywords. Reduces noise but may exclude relevant context.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query that was executed
sourcesYesList of sources that were processed
combinedContentYesCombined and optionally deduplicated content from all sources
summaryYesSummary statistics for the operation
sizeMetadataYesSize information for the combined content
Behavior5/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds caching durations (30 min for search, 1 hour for scraped pages), content size controls, and deduplication behavior, with no contradictions.

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 with clear sections, bullet points, and front-loaded core purpose. Every sentence is informative and necessary, with no fluff.

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, output schema exists), the description covers purpose, usage, parameter guidance, caching, deduplication, and content limits. It is fully complete for an AI agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds extra context like default values, usage recommendations (e.g., num_results suggestions), and explanation of deduplicate purpose, going beyond the schema.

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 Google and retrieves content from top results, combining and deduplicating with source attribution. It explicitly distinguishes from sibling tools like google_search and scrape_page.

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 has explicit 'When to use' and 'When to use other tools instead' sections, providing clear guidance on when to choose this tool over google_search or scrape_page, and mentions caching behavior.

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/google-researcher-mcp'

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