Skip to main content
Glama

crw_search

Search the web and retrieve relevant results with titles, URLs, and descriptions. Supports categories, country, language, and time filters.

Instructions

Search the web and return relevant results with titles, URLs, and descriptions/snippets. Backed by a SearXNG sidecar in embedded mode (no API key needed), or by the configured remote API in proxy mode (uses CRW_API_KEY).

Return shape: { "success": true, "data": { "results": [{ "url", "title", "description", "snippet", "position", "score" }, ...] } }. When sources is set, data.results is instead an object grouped by source ({ "web": [...], "news": [...], "images": [...] }). The snippet field is an alias of description — both carry the same body text so downstream LLM pipelines that ask for either get a match.

Example: crw_search(query="renewable energy trends 2024", limit=3) returns the top 3 web results with title/url/snippet.

Errors: returns search_disabled when no SearXNG backend is configured, or target_unreachable / timeout (naming the configured host) when the backend can't be reached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoriesNoBias the search towards a category. Curated values: `pdf` appends `filetype:pdf` to the query; `github`/`research` switch to topical engines. Any other value (e.g. `science`, `it`, `news`, `files`) is passed straight through to SearXNG's native `categories` routing.
countryNoCountry code for results (e.g. "us", "tr"). Hint to bias regional results; ignored if the underlying engine does not support it.
langNoLanguage code for results (e.g. "en", "tr")
limitNoMaximum number of results to return (default: 5, max: 20)
queryYesThe search query
scrapeOptionsNoIf set, each `web` result is scraped in-process and the requested formats are inlined into the response.
sourcesNoIf set, returns results grouped by source instead of a flat list
tbsNoTime filter — restrict to results from the past hour/day/week/month/year

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
errorNo
error_codeNo
successYes
warningNo
Behavior5/5

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

No annotations are provided, so the description fully bears the burden. It details return shape, grouping behavior with 'sources', scraping capabilities, error codes, and the alias between snippet and description. This is comprehensive.

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 description is well-structured, starting with the main action, then return shape, example, and errors. It is slightly lengthy but each sentence is informative. Could be more concise, but no waste.

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 complexity (8 parameters, nested objects, output schema), the description covers all aspects: purpose, behavior, parameters, return format, errors, and an example. It also explains edge cases like 'scrapeOptions' and 'sources' grouping.

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?

Schema coverage is 100%. The description adds significant value beyond the schema: it explains the return shape, behavior of 'sources', alias of 'snippet', example usage, and interpretation of 'categories' parameters. It also specifies default and max for 'limit'.

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 'Search the web and return relevant results with titles, URLs, and descriptions/snippets,' which is a specific verb and resource. It distinguishes itself from sibling tools like crw_scrape and crw_crawl by focusing on search.

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

Usage Guidelines4/5

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

It explains when to use the tool (to search the web) and provides context on modes (embedded vs proxy) and error handling. It lacks explicit 'when not to use' but the purpose is clear enough for an agent to decide.

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/us/crw'

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