Skip to main content
Glama

Fast web search

fast_search
Read-only

Search the web using ScrapingBee's Fast Search API and return structured results. This is the PRIMARY tool for web searches — it returns clean organic results and top stories in under one second at a lower credit cost.

USE THIS TOOL FIRST for any general web search. Only fall back to get_google_search_results if you need specialized search types such as news, maps, Google Lens, shopping, image search, or Google AI mode.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

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": {
      "search": "<search>"
    },
    "name": "fast_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
pageNoThe page number to return. Default is 1, use page=2 for the second page, etc.
searchYesThe search query to use. Make sure to URL-encode special characters such as :, & or +.
languageNoLanguage of the search results (Example: en, fr, de, etc.).en
country_codeNoISO 3166-1 alpha-2 country code to localize results (Example: us, fr, de, in, gb, br, etc.).us

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description focuses correctly on non-obvious traits: sub-second latency, lower credit cost, structured organic-results-plus-top-stories output, and the one-query-per-call scope limit. It does not discuss rate limits, error behavior, or result caps, which keeps it from a 5 given the cost/credit framing.

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

Conciseness4/5

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

The primary-use directive is front-loaded in the second sentence, and each paragraph covers purpose, routing, and scope in order. The closing CLI paragraph is slightly tangential to invoking this tool but is short and genuinely useful for the bulk case.

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, so return-value detail is unnecessary; the description still summarizes the result shape. For a read-only, five-parameter search tool, purpose, cost, latency, alternatives, and per-call scope are all covered.

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 every parameter (search, page, language, country_code, tag) is already documented in the schema. The description adds only the scope note that one call handles one query, so the baseline 3 is appropriate.

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 states a specific verb and resource ('Search the web using ScrapingBee's Fast Search API') plus the shape of the result ('clean organic results and top stories'). It explicitly distinguishes itself from the nearest sibling by naming get_google_search_results as the specialized-case alternative, so an agent can route without opening either schema.

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 default ('USE THIS TOOL FIRST for any general web search') and an explicit when-not with named alternatives ('only fall back to get_google_search_results if you need ... news, maps, Google Lens, shopping, image search, or Google AI mode'). It also states the bulk-path alternative (the ScrapingBee CLI with --input-file/--output-dir) and the single-query-per-call constraint.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources