Skip to main content
Glama

fetch

Retrieve web content from URLs and convert HTML to markdown for processing, with options for content truncation and pagination.

Instructions

Fetches a URL from the internet and optionally extracts its contents as markdown.

Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to fetch
max_lengthNoMaximum number of characters to return.
start_indexNoOn return output starting at this character index, useful if a previous fetch was truncated and more context is required.
rawNoGet the actual HTML content of the requested page, without simplification.

Implementation Reference

  • The tool handler implementation for the "fetch" tool. Parses arguments into Fetch schema, checks robots.txt if not ignored, fetches and processes the URL content, handles truncation and returns as TextContent.
    async def call_tool(name: str, arguments: dict) -> list[TextContent]:
        try:
            args = Fetch(**arguments)
        except ValueError as e:
            raise McpError(INVALID_PARAMS, str(e))
    
        url = str(args.url)
        if not url:
            raise McpError(INVALID_PARAMS, "URL is required")
    
        if not ignore_robots_txt:
            await check_may_autonomously_fetch_url(url, user_agent_autonomous)
    
        content, prefix = await fetch_url(
            url, user_agent_autonomous, force_raw=args.raw
        )
        if len(content) > args.max_length:
            content = content[args.start_index : args.start_index + args.max_length]
            content += f"\n\n<error>Content truncated. Call the fetch tool with a start_index of {args.start_index + args.max_length} to get more content.</error>"
        return [TextContent(type="text", text=f"{prefix}Contents of {url}:\n{content}")]
  • Pydantic model defining the input schema for the fetch tool, including URL, max_length, start_index, and raw options.
    class Fetch(BaseModel):
        """Parameters for fetching a URL."""
    
        url: Annotated[AnyUrl, Field(description="URL to fetch")]
        max_length: Annotated[
            int,
            Field(
                default=5000,
                description="Maximum number of characters to return.",
                gt=0,
                lt=1000000,
            ),
        ]
        start_index: Annotated[
            int,
            Field(
                default=0,
                description="On return output starting at this character index, useful if a previous fetch was truncated and more context is required.",
                ge=0,
            ),
        ]
        raw: Annotated[
            bool,
            Field(
                default=False,
                description="Get the actual HTML content if the requested page, without simplification.",
            ),
        ]
  • Registers the "fetch" tool with MCP server via list_tools(), providing name, description, and input schema from Fetch model.
        @server.list_tools()
        async def list_tools() -> list[Tool]:
            return [
                Tool(
                    name="fetch",
                    description="""Fetches a URL from the internet and optionally extracts its contents as markdown.
    
    Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that.""",
                    input_schema=Fetch.model_json_schema(),
                )
            ]
  • Core helper function that performs the HTTP GET request to fetch the URL content, detects HTML and extracts/simplifies to markdown if applicable, or returns raw with prefix.
    async def fetch_url(
        url: str, user_agent: str, force_raw: bool = False
    ) -> Tuple[str, str]:
        """
        Fetch the URL and return the content in a form ready for the LLM, as well as a prefix string with status information.
        """
        from httpx import AsyncClient, HTTPError
    
        async with AsyncClient() as client:
            try:
                response = await client.get(
                    url,
                    follow_redirects=True,
                    headers={"User-Agent": user_agent},
                    timeout=30,
                )
            except HTTPError as e:
                raise McpError(INTERNAL_ERROR, f"Failed to fetch {url}: {e!r}")
            if response.status_code >= 400:
                raise McpError(
                    INTERNAL_ERROR,
                    f"Failed to fetch {url} - status code {response.status_code}",
                )
    
            page_raw = response.text
    
        content_type = response.headers.get("content-type", "")
        is_page_html = (
            "<html" in page_raw[:100] or "text/html" in content_type or not content_type
        )
    
        if is_page_html and not force_raw:
            return extract_content_from_html(page_raw), ""
    
        return (
            page_raw,
            f"Content type {content_type} cannot be simplified to markdown, but here is the raw content:\n",
        )
  • Helper function to check robots.txt compliance before autonomous fetching, raises McpError if disallowed.
    async def check_may_autonomously_fetch_url(url: str, user_agent: str) -> None:
        """
        Check if the URL can be fetched by the user agent according to the robots.txt file.
        Raises a McpError if not.
        """
        from httpx import AsyncClient, HTTPError
    
        robot_txt_url = get_robots_txt_url(url)
    
        async with AsyncClient() as client:
            try:
                response = await client.get(
                    robot_txt_url,
                    follow_redirects=True,
                    headers={"User-Agent": user_agent},
                )
            except HTTPError:
                raise McpError(
                    INTERNAL_ERROR,
                    f"Failed to fetch robots.txt {robot_txt_url} due to a connection issue",
                )
            if response.status_code in (401, 403):
                raise McpError(
                    INTERNAL_ERROR,
                    f"When fetching robots.txt ({robot_txt_url}), received status {response.status_code} so assuming that autonomous fetching is not allowed, the user can try manually fetching by using the fetch prompt",
                )
            elif 400 <= response.status_code < 500:
                return
            robot_txt = response.text
        processed_robot_txt = "\n".join(
            line for line in robot_txt.splitlines() if not line.strip().startswith("#")
        )
        robot_parser = Protego.parse(processed_robot_txt)
        if not robot_parser.can_fetch(str(url), user_agent):
            raise McpError(
                INTERNAL_ERROR,
                f"The sites robots.txt ({robot_txt_url}), specifies that autonomous fetching of this page is not allowed, "
                f"<useragent>{user_agent}</useragent>\n"
                f"<url>{url}</url>"
                f"<robots>\n{robot_txt}\n</robots>\n"
                f"The assistant must let the user know that it failed to view the page. The assistant may provide further guidance based on the above information.\n"
                f"The assistant can tell the user that they can try manually fetching the page by using the fetch prompt within their UI.",
            )

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Without annotations, the description partially covers behavior: it mentions fetching and markdown extraction but omits error handling, rate limits, or response truncation details. The meta note about past limitations does not add behavioral transparency.

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 brief with two sentences, front-loading the main action. The second sentence is slightly verbose but still concise overall.

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 no siblings or output schema, the description covers the core functionality and parameter usage adequately. It lacks mention of error scenarios but is sufficient for a fetch tool with well-defined schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds minimal value beyond parameter descriptions. It provides context by linking 'optionally extracts markdown' to the 'raw' parameter, but not enough to raise the score above baseline.

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 from the internet and optionally extracts markdown. It distinguishes this from any other tool by emphasizing internet access, and there are no siblings to differentiate.

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 tells the agent to use this tool for obtaining up-to-date internet information. Though lacking explicit when-not-to-use, the context of granting internet access implies its primary use case.

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