Skip to main content
Glama

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
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds error handling behavior (returns error string on failure) and mode details, which is valuable beyond annotations.

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?

Concise 4-sentence paragraph. Front-loaded with purpose. Could be slightly more structured with bullet points, but every sentence is informative.

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 modes, error handling, usage advice. No output schema, but return value (markdown text) is implied. Sufficient for a read-only tool with good annotations.

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 coverage is 100%, but the description explains how parameters work together (three modes: omit filtering, use startChar/maxLength for pagination, section for section extraction, readHeadings exclusive). Adds contextual meaning 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 fetches a URL and returns text content converted to markdown, and distinguishes three modes. It differentiates from the sibling searxng_web_search (search vs. read).

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 'Use after searxng_web_search to read the full content of individual result URLs.' Describes three mutually exclusive modes, guiding the agent on when to use each.

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

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