Skip to main content
Glama
vinas1

mcp-searxng

by vinas1

web_url_read

Read-only

Fetch a URL and get readable markdown content, converting HTML, JSON, PDFs, and more. Use options to extract a specific section or list headings for targeted reading.

Instructions

Fetches a URL and returns readable content as markdown. Content-type aware: HTML is converted to markdown; JSON is pretty-printed; plain text, YAML, TOML, and XML are returned as fenced readable text. PDF text extraction is supported with bounded input, output, page count, time, concurrency, and memory; OCR is not supported. Binary, media, archive, and octet-stream downloads other than PDFs are intentionally rejected instead of being returned as raw bytes. When the operator configures browser solvers, mcp-searxng attempts FlareSolverr first and then Byparr only after a busy or transient-unavailable acquisition; cache hits bypass acquisition and a final busy or unavailable provider uses one uncached direct-fetch fallback. Three modes: (1) Full content — omit filtering params; use startChar/maxLength to paginate large pages. (2) Section extraction — set section to return content under a specific heading. (3) Headings only — set readHeadings: true to list all headings (mutually exclusive with other filtering params). Returns an error string if the URL is unreachable or content cannot be extracted. Use after searxng_web_search to read the full content of individual result URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL
sectionNoExtract content under a specific heading (searches for heading text)
maxLengthNoMaximum number of characters to return
startCharNoStarting character position for content extraction (default: 0)
readHeadingsNoReturn only a list of headings instead of full content
paragraphRangeNoReturn specific paragraph ranges (e.g., '1-5', '3', '10-')
Behavior5/5

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

Annotations provide readOnlyHint and openWorldHint, but the description adds extensive behavioral detail: content-type conversion rules, PDF extraction limits, binary rejection, FlareSolverr/Byparr fallback logic, modes, and error return behavior. This far exceeds what annotations alone communicate, with 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 long but each sentence contributes necessary detail. It is front-loaded with the primary purpose and then branches into content types, limitations, modes, and usage. The solver fallback details are somewhat verbose and could be trimmed without losing core guidance, preventing a perfect score.

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?

With no output schema, the description adequately explains return format (markdown, fenced text, error string) and covers all major usage aspects: modes, pagination, unsupported types, and integration with the search tool. This makes it self-sufficient for an AI agent.

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 covers all parameters 100%, so baseline is 3. The description adds value by explaining how parameters combine into three modes (full content with startChar/maxLength, section extraction, readHeadings) and notes mutual exclusivity. However, paragraphRange is not mentioned in the description, so it doesn't fully elaborate every parameter.

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 first sentence clearly states 'Fetches a URL and returns readable content as markdown,' identifying the specific verb and resource. It distinctly differentiates from sibling tools (searxng_web_search, suggestions, instance info) which are search-oriented, not content retrieval.

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?

Explicitly states 'Use after searxng_web_search to read the full content of individual result URLs,' providing clear when-to-use guidance. Also lists exclusions (binary, media, OCR not supported) which inform when not to use.

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

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