Skip to main content
Glama
ptrken01

searxng-mcp-scraper

by ptrken01

search

Perform web queries against a SearXNG instance, returning structured results with titles, URLs, snippets, and engine metadata, with filters for categories, language, time, and safety.

Instructions

Search the web via the configured SearXNG instance.

Args:
    query: The search query string. Required.
    categories: SearXNG category list, e.g. ["general"], ["images"].
        Defaults to the server's `SEARXNG_DEFAULT_CATEGORY`.
    engines: Restrict to specific engines, e.g. ["google", "bing"].
    language: Language code, e.g. "en", "de". Defaults to server setting.
    pageno: Page number (1-indexed). Default 1.
    time_range: One of "day", "month", "year", or None.
    safesearch: 0 (none), 1 (moderate), 2 (strict). Defaults to server setting.
    max_results: Cap on results returned (1-50). Default 10.

Returns:
    Dict with `results` (list of {title, url, snippet, engine, score}),
    `suggestions`, `number_of_results`, and on error an `error` field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxNo
queryYes
pagenoNo
enginesNo
languageNo
categoriesNo
safesearchNo
time_rangeNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses defaults for categories, language, pageno, safesearch, max_results, valid time_range values, and error behavior. It doesn't mention rate limits or authentication, but for a search tool this is adequate 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?

The description is well-structured with Args and Returns sections. Every sentence carries useful information—no fluff. The length is appropriate given the parameter count.

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?

The description covers all parameters, return value structure, error handling, and default behaviors. Even with an output schema present, it adds clarity. It is complete for a web search tool.

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?

Schema description coverage is 0%, but the description compensates by explaining every parameter's purpose, allowed values, and defaults. This adds substantial meaning beyond the bare input 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 'Search the web via the configured SearXNG instance,' using a specific verb + resource. This distinguishes it from siblings like fetch and scrape_blog, which are about retrieving specific pages or content, not general search.

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?

The purpose is clear and implies when to use it (when conducting a web search), but it doesn't explicitly mention when not to use it or alternatives. However, the sibling tool names (fetch, scrape_blog) make the distinction self-evident.

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/ptrken01/searxng-mcp-scraper'

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