Skip to main content
Glama
alexandru2882

URL Text Fetcher MCP Server

fetch_page_links

Extract all links from a web page by providing its URL. This tool helps identify and collect hyperlinks for web scraping and content analysis.

Instructions

Return a list of all links on the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'fetch_page_links' tool. It is decorated with @mcp.tool() for registration, fetches the webpage content using requests, parses it with BeautifulSoup, and extracts all href attributes from anchor tags returning them as a list of strings.
    @mcp.tool()
    def fetch_page_links(url: str) -> List[str]:
        """Return a list of all links on the page."""
        resp = requests.get(url, timeout=10)
        resp.raise_for_status()
        soup = BeautifulSoup(resp.text, "html.parser")
        return [a['href'] for a in soup.find_all('a', href=True)]
  • The @mcp.tool() decorator registers the fetch_page_links function as an MCP tool.
    @mcp.tool()
  • The function signature defines the input schema (url: str) and output schema (List[str]), along with the docstring describing the tool's purpose.
    def fetch_page_links(url: str) -> List[str]:
        """Return a list of all links on the page."""
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't mention potential behaviors like rate limits, error handling, or whether it follows redirects. This leaves significant gaps for a tool that interacts with external resources.

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 a single, efficient sentence that directly states the tool's function without any unnecessary words. It's front-loaded and appropriately sized for its simple purpose.

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

Completeness3/5

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

Given the tool's low complexity (one parameter) and the presence of an output schema, the description is somewhat complete but lacks details on behavioral aspects. Without annotations, it should provide more context about how the tool operates, such as handling of invalid URLs or network issues.

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?

The input schema has 0% description coverage, but the description doesn't add any details about the 'url' parameter beyond what's implied by the tool's purpose. Since there's only one parameter and its role is somewhat clear from context, this meets the baseline for minimal compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Return') and resource ('list of all links on the page'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling tool 'fetch_url_text', which might also involve page content extraction, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling 'fetch_url_text' or any alternatives. It lacks context about prerequisites, such as whether the URL must be accessible or if authentication is needed, leaving usage unclear.

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/alexandru2882/url-text-fetcher-mcp'

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