Skip to main content
Glama
ihor-sokoliuk

SearXNG Server

by ihor-sokoliuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

web_url_read

Read-only

Fetch a URL and convert its text to markdown, with options to extract specific sections, headings, or paginate content.

Instructions

Fetches a URL and returns its text content converted to markdown. 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
startCharNoStarting character position for content extraction (default: 0)
maxLengthNoMaximum number of characters to return
sectionNoExtract content under a specific heading (searches for heading text)
paragraphRangeNoReturn specific paragraph ranges (e.g., '1-5', '3', '10-')
readHeadingsNoReturn only a list of headings instead of full content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.1
    • addedInput schema / properties / maxLength
      Added value: +{
+  "description": "Maximum number of characters to return",
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / paragraphRange
      Added value: +{
+  "description": "Return specific paragraph ranges (e.g., '1-5', '3', '10-')",
+  "type": "string"
+}
    • addedInput schema / properties / readHeadings
      Added value: +{
+  "description": "Return only a list of headings instead of full content",
+  "type": "boolean"
+}
    • addedInput schema / properties / section
      Added value: +{
+  "description": "Extract content under a specific heading (searches for heading text)",
+  "type": "string"
+}
    • addedInput schema / properties / startChar
      Added value: +{
+  "description": "Starting character position for content extraction (default: 0)",
+  "minimum": 0,
+  "type": "number"
+}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. Description adds behavioral details: three modes, error handling (returns error string if unreachable), and mutual exclusion. It's transparent about what the tool does but doesn't cover all edge cases (e.g., combining multiple filtering params other than readHeadings).

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 a single but well-structured paragraph that enumerates modes clearly. Every sentence adds value with no redundancy. Front-loaded with main purpose.

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?

Covers main functionality, modes, error handling, and relation to sibling tool. No output schema, but return type (text/markdown) is implied. Minor gap: doesn't specify behavior when multiple filtering params are combined beyond readHeadings.

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 parameters are documented. The description adds significant meaning by grouping parameters into modes and explaining relationships (e.g., omit filtering for full content, set section for extraction, readHeadings for headings). It clarifies mutex conditions 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 the tool fetches a URL and converts content to markdown, with three distinct modes. It distinguishes from sibling tools (search tools) by specifying it's for reading individual URLs after a search.

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 says to use after searxng_web_search to read full content of result URLs. Describes three modes and their parameter usage, including mutual exclusivity of readHeadings. Provides guidance on pagination with startChar/maxLength.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools