Skip to main content
Glama
Sign In
mcp-red-web-utils

mcp-red-web-utils

by hsharmanov02
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

links

Extract all hyperlinks from a web page URL to analyze or index site content. Returns every link found; paid per call in USDC via x402.

Instructions

Extract all links from a web page (paid per call, USDC on Base via x402)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does valuable work disclosing that each call is paid in USDC on Base via x402 — a critical pre-call consideration — but says nothing about cost amount, failure modes (non-HTML pages, paywalls, redirects), or whether relative links are resolved.

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?

One sentence, front-loaded with the action and resource, with the payment caveat as a trailing clause. No wasted words and nothing essential buried.

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?

There is no output schema, so the description should say roughly what comes back (a list of URLs? resolved absolute links? includes anchors/text?). It also omits the actual price, which matters for a paid endpoint. Adequate to identify the tool but not to call it confidently.

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?

Only one parameter exists and the schema alone defines it (string, uri format). The phrase 'web page' implicitly constrains the URL to an HTML document, adding a small amount of meaning beyond the schema, which is reasonable for a single-param tool.

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?

States a specific verb and resource: 'Extract all links from a web page.' It's clear what the tool does, but it never distinguishes itself from the sibling 'reader' (which likely extracts page content) or 'metadata,' so the agent must guess which page-scraping tool to pick.

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?

No when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only selection signal is the implicit 'links' vs 'reader' naming, which the description does not reinforce.

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