Skip to main content
Glama

fetch

Fetch URLs and return their content as clean markdown for reading articles, documentation, and PDFs. Extracts text without snippets, with optional raw HTML.

Instructions

Fetch one or more URLs and return their content as clean markdown. Use this to read articles, documentation, blog posts, or any page where you need the complete text, not just a snippet from search. Also supports PDF, DOCX, and other document formats. Costs 1 credit per URL. Max 10 URLs per request. Failed URLs are not charged.

Set include_raw_html=true to also get the raw HTML source in each result. Useful for inspecting embedded URLs, data attributes, iframes, or script tags that are stripped during markdown conversion. Returns null for non-HTML content (PDF, DOCX, etc.). Same cost.

Returns: results (array of {title, url, content, raw_html, published_time, success, error}), credits_used, credits_remaining.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesList of URLs to fetch (max 10)
include_raw_htmlNoInclude raw HTML source in each result (default false)
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses credit cost, max URLs, failed URL charging, and behavior of 'include_raw_html' (returns null for non-HTML). It does not mention rate limits or robots.txt, but the disclosed info is solid.

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 well-organized with clear paragraphs. It is concise but covers all key points. Slight redundancy like repeating 'max 10 URLs' could be trimmed, but overall efficient.

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?

Given the lack of output schema, the description compensates by listing the return fields (title, url, etc.). It also addresses error handling, credit usage, and format support. For a tool with two parameters, this is sufficiently complete.

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%, but the description adds value by explaining the purpose of 'include_raw_html' (inspecting embedded elements) and its behavior for non-HTML content. It also clarifies credit usage per URL, which is not in 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 verb 'fetch', resource 'URLs', and output 'clean markdown'. It distinguishes from siblings by contrasting with 'snippet from search' and mentioning support for PDF/DOCX formats, making the purpose unambiguous.

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 tells when to use the tool ('read articles, documentation, blog posts') and implicitly suggests when not to use it ('not just a snippet'). It also provides constraints like credit cost, max URLs, and failed URL policy. However, it does not directly compare with sibling tools 'extract' or 'research'.

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/sofya-co/sofya-mcp'

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