Skip to main content
Glama
burakaydinofficial

searxng-deepdive

search_by_category

Search across all engines in one or more categories for broad coverage of a content type.

Instructions

Search within one or more categories — runs every engine tagged with each (e.g. categories: ["science"]).

Use when you want broad coverage of a content type without enumerating engines.

NOTE: this instance's live engine/category list is currently unavailable — SearXNG was unreachable when the server started. Names you pass are forwarded and validated once SearXNG is reachable; restart the server after SearXNG is up to see the enabled list here.

Multi-page fanout (pages=N) and other knobs work the same as the broad search tool.

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).
categoriesYesCategory names to constrain the search. SearXNG runs every engine tagged with these categories. The available categories are enumerated in this tool's description above.
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?

No annotations provided, so description carries full burden. Discloses that engine/category list is currently unavailable due to SearXNG unreachability, and explains validation behavior. Also describes multi-page fanout and dedup behavior. Sufficient for a search tool.

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?

Description is concise at about 10 sentences, front-loading the purpose. The note about server unreachability is important but adds length. Overall no wasted words, well-structured.

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?

Given 8 parameters and no output schema, description covers category behavior, multi-page fanout, error conditions (SearXNG unreachable), and references to sibling tool. Lacks explicit return format but acceptable since no output schema.

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 baseline 3. The tool description does not add additional meaning beyond what the schema already provides for each parameter; the only extra context is the note about categories availability, which is minor.

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?

Description clearly specifies verb 'Search' within 'one or more categories', running engines tagged with each. Distinguishes from siblings by focusing on category-based broad coverage without enumerating engines, and explicitly compares to 'search' tool.

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?

Describes when to use: for broad coverage of content type without enumerating engines. Also notes caveats about engine list unavailability and how to fix. Implicitly advises against using when engine list is needed, but lacks explicit when-not or comparison to 'search_on_engines'.

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