Skip to main content
Glama

search_and_fetch

Read-only

Combine search and page extraction into one round-trip. Returns ranked results with full-page excerpts, citations, and optional browser rendering for dynamic content.

Instructions

Search SearXNG for one query and fetch+extract the top results in a single call. Combines search and fetch_many for one-query research workflows. Best for: answering one question that needs evidence from full pages, building a citation-backed answer to a single prompt, getting both ranked results and readable excerpts in one round-trip. Returns: search summary plus per-source {title, url, excerpt, citations, render_mode}. The full SearXNG payload and per-page full text are in hidden _meta. Rendered fetch is automatic for JS-heavy pages; pass rendered=true to force browser mode (slower). Use search if extraction is not needed; research for multi-query investigations.

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.
fetch_limitNoMaximum number of search results to fetch and extract (1–20, default 3). Lower is faster; higher gives more sources at the cost of latency.
fetch_excerpt_charsNoPer-source excerpt character cap (200–20000). Default comes from server settings. Smaller values keep the visible output tight; the full text is always available in hidden `_meta` for each source.
renderedNoForce browser-based rendering for fetches. Default false: the server auto-renders only when a page is JS-heavy or returns near-empty text. Set true when a previous fetch came back nearly empty or to read a known SPA. Forced rendering is several times slower than HTTP fetch.
render_wait_msNoExtra milliseconds to wait after DOM content load before extracting (0–15000). Use a higher value (e.g. 1500–4000) for SPAs that hydrate slowly.
ttlNoCache TTL override in seconds (0–86400). 0 disables caching for this call. Omit to use the server's default TTL.
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds valuable context about automatic rendered fetch, hidden _meta data, and forced rendering. No contradictions.

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 with clear sections (best for, returns, behavior details). It is somewhat lengthy but each sentence adds value. Slight improvement could be made by condensing the parameter context.

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 (15 parameters, no output schema, multiple siblings), the description is thorough, covering purpose, usage, return format, hidden data, and behavioral details. It leaves no major gaps.

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 is 3. The description does not elaborate on parameters beyond the schema, but it provides context on how the parameters relate to the combined search-and-fetch workflow.

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 that the tool combines search and fetch for a single query, and explicitly distinguishes it from sibling tools by recommending 'search' when no extraction is needed and 'research' for multi-query investigations.

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?

The description provides explicit guidance on when to use this tool: 'Best for: answering one question that needs evidence from full pages... getting both ranked results and readable excerpts in one round-trip.' It also clearly states when to use alternatives.

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