Skip to main content
Glama

anysearch_extract

Fetch any web page URL and return its full content as clean Markdown. Use to read articles, documentation, or verify details from original sources.

Instructions

This is Anysearch's URL extraction tool. Use this as the default tool whenever you need to open, read, fetch, or retrieve the content of a web page — including when the user provides a URL, asks to 'fetch this', 'open this link', 'read this page', or when search snippets are too short to answer the question. Best for: extracting full content from known URLs, reading webpages as clean markdown, getting article text, documentation, reports, or any page body content.

IMPORTANT: Use this whenever search results lack detail. Fetches a URL and returns its full content as clean Markdown.

When to use — call extract after search whenever:

  • The search snippet is too short or truncated to answer the question

  • User asks to 'read', 'open', 'summarize', or 'get details from' a specific URL

  • You need to verify a specific claim, statistic, or fact from the original source

  • The result points to a full article, report, documentation page, or paper worth reading in full

  • The answer requires data only visible in the page body (tables, sections, code blocks not captured in snippet)

  • User provides a URL directly and asks about its content

When NOT to use

  • The search snippet already contains a complete, sufficient answer

  • You only need the URL or title (not the page body)

Constraints

  • url must start with http:// or https://

  • Only HTML pages are supported; PDF/binary files will return an error

  • Content is truncated at 50,000 characters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe page URL to fetch. Must start with http:// or https://.
Behavior5/5

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

No annotations provided, so description carries the full burden. It discloses that only HTML pages are supported (PDF/binary returns error), content is truncated at 50,000 characters, and URL must start with http:// or https://. No contradictions.

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?

Well-structured with markdown headers for when-to-use, when-not-to-use, and constraints. Front-loaded with purpose. Some slight redundancy (e.g., 'Best for' repeats earlier statements), but overall efficient and clear for the amount of guidance provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 required param, no output schema, no annotations) and diverse sibling tools, the description is highly complete. It covers usage context, constraints, error cases (PDF/binary), and return format (clean markdown). No major gaps.

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 has 100% description coverage on the url parameter. The description adds behavioral context beyond the schema, such as constraints (only HTML pages, truncation) and that the URL must start with http:// or https://, which is also in schema but reinforces it. Minor redundancy, but adds value.

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 is a URL extraction tool for fetching web page content as clean markdown. It distinguishes itself from sibling tools like anysearch_search by specifying when to use it after search, and uses a specific verb-resource combination (extract URL content).

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?

Provides extensive when-to-use and when-not-to-use guidance, including explicit contrasts with search snippets and specific scenarios such as when snippets are too short or user asks to read a URL. Clearly states alternatives like using search if snippet is sufficient.

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/Microbiosis/mini-agent-mcp'

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