Skip to main content
Glama

search

Read-only

Search the open web for a single query and receive a compact, token-efficient summary of top results including titles, URLs, and snippets.

Instructions

Search the open web via SearXNG for a single query and return a compact, token-efficient summary of the top results. Best for: quick fact-finding, current events, locating likely sources, single-question lookups. Returns: ranked list of {title, url, domain, snippet, engine, score} plus answers, infoboxes, suggestions and corrections when SearXNG provides them. The full SearXNG payload is also available in hidden _meta.raw_payload. Use search_many instead when running multiple parallel queries; search_and_fetch when you also need extracted page content; research for multi-query investigations with merged sources and fetched excerpts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (1–400 chars). Plain text or SearXNG syntax. SearXNG bangs like '!wikipedia foo' or '!images cats' are supported and route to specific engines.
categoriesNoComma-separated SearXNG categories to search (e.g. 'general', 'news', 'images', 'videos', 'science', 'files'). Default is the server's configured category set, typically 'general'.
enginesNoComma-separated SearXNG engine names to use for this query. Forwarded to SearXNG's 'engines' parameter. Leave unset to use the backend's default engine selection.
enabled_enginesNoComma-separated engine names to enable in addition to the backend defaults. Forwarded as SearXNG's 'enabled_engines' parameter.
disabled_enginesNoComma-separated engine names to exclude from this query. Forwarded as SearXNG's 'disabled_engines' parameter.
languageNoBCP-47 language hint for SearXNG (e.g. 'en', 'en-US', 'de', 'all'). Default is the server's configured language.
pagenoNoResult page number (1–20, default 1). Use to paginate beyond the first page.
time_rangeNoRestrict results to recent content. Valid values: 'day', 'week', 'month', 'year'. Omit for no time filter.
safesearchNoSafe search level: 0=off, 1=moderate, 2=strict. Omit to use the server default.
max_resultsNoMaximum visible results to include in the compact summary (1–50). Default comes from server settings (typically 5). The hidden `_meta.raw_payload.results` always contains the full SearXNG response regardless of this cap.
ttlNoCache TTL override in seconds (0–86400). 0 disables caching for this call. Omit to use the server's default TTL.
Behavior5/5

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

Description adds value beyond annotations by explaining the return format (compact summary, raw payload in _meta), without contradicting readOnlyHint=true. Discloses token-efficiency and hidden data, enhancing transparency.

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?

Description is concise (4 sentences), front-loaded with purpose, then usage guidance, then return details and alternatives. Every sentence earns its place.

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 (11 parameters, no output schema), the description covers purpose, return format, hidden payload, and sibling guidance. Leaves no major gaps for an agent to infer.

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 has 100% coverage of parameter descriptions, so baseline is 3. The description does not add additional meaning beyond what the schema provides.

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?

Clearly states the tool searches the open web via SearXNG for a single query and returns a compact summary. Distinct from siblings by naming alternatives explicitly.

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?

Provides a 'Best for' section and explicitly names alternatives (search_many, search_and_fetch, research) with their use cases, offering strong guidance on when to use this tool versus others.

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/88plug/searxng-mcp'

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