Skip to main content
Glama

search_many

Read-only

Run multiple search queries in parallel, then deduplicate and merge results into a single ranked list to broaden coverage or compare ranking across different phrasings.

Instructions

Run several SearXNG searches in parallel, then dedupe and merge their result sets into a single ranked list. Best for: broadening coverage on one topic with synonym/angle variants, comparing how different phrasings rank, building a high-recall source pool before fetching. Returns: merged hits with per-hit queries (which inputs surfaced it), engines, hit_count, and a merged_score. Per-query raw payloads are in hidden _meta. Use search for a single query; research when you also need the top sources fetched and excerpted in the same call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queriesYesList of 1–10 search queries to run in parallel. Use distinct phrasings or angles (synonyms, related entities, opposing framings) for the best merged coverage.
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.
concurrencyNoMaximum concurrent backend requests for this fan-out (1–16). Higher is faster but puts more load on the SearXNG instance and remote pages. Omit for the server default.
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?

Annotations indicate read-only, non-destructive, open-world. Description adds valuable behavioral details: deduping, merged scoring, hidden `_meta` for raw payloads, max_results cap behavior, and concurrency/ttl options.

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?

The description is concise, well-structured with bullet points, and front-loads the core functionality. Every sentence adds value.

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 12 parameters and no output schema, the description covers return format (merged hits, per-hit fields, hidden meta) and key behaviors (caching, concurrency). Comprehensive for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3. Description adds value by explaining the meaning of 'queries' (distinct phrasings) and clarifying 'max_results' and 'concurrency' behavior beyond schema.

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 it runs multiple SearXNG searches in parallel, dedupes, and merges results. It distinguishes from siblings by naming 'search' and 'research' as alternatives.

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?

Explicit 'Best for' scenarios and direct guidance on when to use alternatives: 'Use `search` for a single query; `research` when you also need the top sources fetched and excerpted.'

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