Skip to main content
Glama
burakaydinofficial

searxng-deepdive

search

Search the web across all enabled search engines. Returns merged, deduplicated results. Supports multi-page fetching, time range, language, and safe search filters.

Instructions

Broad web search across the SearXNG instance's full enabled engine pool.

Use this for general-purpose queries when you don't have a specific source preference. Returns a merged, deduplicated result list from across this instance's enabled engines — actual yield depends on which engines respond at query time.

Knobs: • pages=N (max 5) — fetch multiple pages and merge for more results in one call. • format='full' — full result objects with metadata; default 'compact' is token-efficient. • time_range — narrow to recent results (note: not all engines support this — see field doc).

When to reach for a different tool: • search_on_engines — you want specific sources (e.g. just ArXiv + PubMed) • search_by_category — you want all engines in a category (e.g. all science)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagesNoMulti-page fanout: fetch this many consecutive pages in parallel and merge with URL-based dedup. Default 1. Combines with pageno: pageno=3 + pages=2 fetches pages 3 and 4. Diminishing returns past page 2 (engines exhaust their result pools); going wide may also rate-limit upstream engines. Capped at 5 to bound token cost.
queryYesPlain-language search query. Forwarded to each engine's native parser; engine-specific operators (e.g. site:, filetype:) are passed through unchanged.
formatNo'compact' (default) returns only url/title/content/engine for each result — typically much smaller, recommended for ranking and triage. 'full' adds: relevance score, publishedDate, the list of all engines that surfaced the result, and engine-specific metadata (authors, DOI, etc. for academic engines). Switch to 'full' only when you specifically need one of those fields.
pagenoNo1-indexed starting page number. Default 1. Higher pages fetch additional results from each engine, deduplicated against earlier pages by URL. Per-page yield drops sharply after the first 1-2 pages as engines exhaust their result pools.
languageNoLanguage filter, e.g. 'en', 'fr', 'de', 'pt-BR', or 'all' to disable filtering. If omitted, the SearXNG instance's configured default applies (NOT autodetected from the query, despite what the name suggests).
time_rangeNoFilter to results published within this time window. WARNING: not all engines implement time-range filtering — some (notably academic engines) return ZERO results when this is set instead of ignoring it. Set time_range only when freshness genuinely matters; if a query returns 0 results with time_range set, retry without it.
safe_searchNoSafe-search level. 0 = off, 1 = moderate, 2 = strict. If omitted, the SearXNG instance's configured default applies (often 0 for self-hosted, but not guaranteed).
Behavior4/5

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

Discloses behavioral traits beyond schema: returns merged/deduplicated results, engine-dependent yield, multi-page fanout, rate-limit risks, time_range caveats, default formats. Lacks explicit read-only statement but implied for search.

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?

Well-structured with a concise opening, a 'Knobs' section for parameters, and a clear alternatives section. Front-loaded with purpose. No redundant sentences.

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?

Despite no output schema, description covers return formats and key fields. Provides complete context for correct tool selection and invocation, including behavioral quirks and alternative tools.

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?

All 7 parameters are described in detail with usage nuance, defaults, warnings, and clarifications that go far beyond the schema descriptions. Examples include pages cap, format trade-offs, time_range incompatibility, and language filter behavior.

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 'Broad web search across the SearXNG instance's full enabled engine pool' with a specific verb and resource. Explicitly distinguishes from sibling tools by indicating use when no specific source preference.

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 explicit guidance: 'Use this for general-purpose queries when you don't have a specific source preference.' Includes a dedicated section 'When to reach for a different tool' naming alternatives and their purposes.

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/burakaydinofficial/searxng-deepdive'

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