Skip to main content
Glama
Sign In
Crawl-MCP

Crawl-MCP

by walksoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_google

Read-only

Run web searches with optional result types, engines, language, region, recency, and content limits; this deprecated alias mirrors search_web, so use search_web instead.

Instructions

Deprecated alias of search_web (same request keys and results; the engine is not limited to Google). Use search_web.

Input Schema

NameRequiredDescriptionDefault
requestYesDict with: query (required), num_results, search_genre (optional, one of: pdf, documents, presentations, spreadsheets, japanese, english; adds a filetype/language operator to the query, other values return an error), engine (optional, one of: auto, google_custom, brave, exa, searxng; default from SEARCH_ENGINE, auto tries the configured engines in SEARCH_ENGINE_ORDER and moves to the next one on errors other than zero results), result_type (optional; default web; one of web, discussions, faq, videos, news, or several as a list or a comma-separated string; everything except web runs on brave only; news is a separate Brave News Search request; results holds web when requested, else the first type, and the other types go to extra_results; discussions are forum posts with the forum name, answer count, post score, question and top comment; faq are question and answer excerpts; Brave returns these sections for some queries only, and num_results only shortens them), language, region, recent_days, content_limit (int), content_offset (int). Optional persistence keys: output_path (absolute file path, auto .json extension — full unsliced results written to disk BEFORE content_limit/content_offset slicing), include_content_in_response (bool, default False — when True keeps results in the response too, still subject to slicing), overwrite (bool, default False).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • changedInput schema / properties / request / description
      Previous value: -"Dict with: query (required), num_results, search_genre, language, region, recent_days, content_limit (int), content_offset (int). Optional persistence keys: output_path (absolute file path, auto .json extension — full unsliced results written to disk BEFORE content_limit/content_offset slicing), include_content_in_response (bool, default False — when True keeps results in the response too, still subject to slicing), overwrite (bool, default False)."New value: +"Dict with: query (required), num_results, search_genre (optional, one of: pdf, documents, presentations, spreadsheets, japanese, english; adds a filetype/language operator to the query, other values return an error), engine (optional, one of: auto, google_custom, brave, exa, searxng; default from SEARCH_ENGINE, auto tries the configured engines in SEARCH_ENGINE_ORDER and moves to the next one on errors other than zero results), result_type (optional; default web; one of web, discussions, faq, videos, news, or several as a list or a comma-separated string; everything except web runs on brave only; news is a separate Brave News Search request; results holds web when requested, else the first type, and the other types go to extra_results; discussions are forum posts with the forum name, answer count, post score, question and top comment; faq are question and answer excerpts; Brave returns these sections for some queries only, and num_results only shortens them), language, region, recent_days, content_limit (int), content_offset (int). Optional persistence keys: output_path (absolute file path, auto .json extension — full unsliced results written to disk BEFORE content_limit/content_offset slicing), include_content_in_response (bool, default False — when True keeps results in the response too, still subject to slicing), overwrite (bool, default False)."
  2. Addedv0.3.2
  3. Removedv0.1.6
  4. First observedv0.1.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds genuinely non-obvious context: the tool is deprecated, and despite its name the engine is not limited to Google. It does not say whether calls emit deprecation warnings or when removal is planned, which would be useful for an agent deciding whether the alias is safe to keep calling.

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?

A single sentence that front-loads the critical fact (deprecated) and closes with the actionable directive. Nothing is wasted and nothing important is buried.

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

Completeness4/5

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

For a deprecated alias with a fully documented nested schema and an output schema, the description covers what an agent needs: what it is, what it is not (Google-only), and what to use instead. Only the lifecycle details — warnings surfaced, removal timeline — are absent.

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% and the nested request object documents every key, including engine and search_genre enums, in detail. The description only asserts 'same request keys and results,' adding no parameter meaning 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.

Purpose4/5

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

The description identifies the tool precisely as a deprecated alias of search_web with identical request keys and results, which lets an agent distinguish it from siblings like search_web or batch_search_google. It never states the underlying operation (web search) in its own words, relying on the reader knowing what search_web does, but the alias framing is 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?

It gives an explicit directive — 'Use search_web' — which is the strongest possible when-to-use guidance for a deprecated tool, and it names the alternative by name. No inference is required about which sibling to prefer.

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