Skip to main content
Glama

Fetch URL as Text

fetch_url
Read-onlyIdempotent

Fetch a URL to get its clean readable content as plain text or Markdown, removing ads and navigation.

Instructions

Download a web page and return its readable content as clean text or Markdown (scripts, styles, nav and ads stripped).

Use after web_search to actually read a page, or whenever you have a URL whose content you need.

Args:

  • url (string): The http(s) URL to fetch.

  • format ('text' | 'markdown'): 'text' (default) for plain readable text, 'markdown' to preserve headings/links/lists.

Returns the page content. Long pages are truncated; fetch a more specific URL if needed.

Example: { "url": "https://example.com/article", "format": "markdown" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYeshttp(s) URL to fetch
formatNotext or markdowntext
Behavior4/5

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

Annotations already mark it read-only and idempotent. The description adds that scripts, styles, nav, and ads are stripped, and long pages are truncated. This provides useful behavioral context 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: a brief summary, usage context, parameter details, and an example. No extraneous content.

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?

No output schema exists, but the description explains return value and truncation behavior. It covers the tool's main aspects adequately for its simplicity.

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%. The description adds value by explaining the format parameter effect ('text' for plain, 'markdown' preserves structure) and providing an example. This aids understanding beyond the 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 web page and returns readable content as text or Markdown. It specifies the verb 'download' and the resource 'web page', and differentiates from siblings like 'web_search' by mentioning use after web_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 description explicitly says 'Use after web_search to actually read a page, or whenever you have a URL whose content you need.' This provides clear context for when to use, though it doesn't explicitly list alternatives like 'http_request'.

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/highercomve/mcptools'

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