Skip to main content
Glama

SolSignal Web Tools

Extract links & metadata

web_links
Read-only

Extract all links (internal/external, anchor text), title, description, OpenGraph image, canonical URL and RSS/Atom feeds from a web page.

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": "web_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network reach are covered structurally. The description adds little beyond them: it does not say whether the page is fetched live, what happens on non-HTML, unreachable, or redirected targets, or whether extraction is bounded in size. Enumeration of output fields is informative but largely restates the tool's purpose.

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 verb, and the field list is dense rather than padded. Every item listed is a distinct output an agent would care about, so nothing feels like filler.

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?

With no output schema, the enumerated field list usefully conveys the return shape, and the single parameter is fully specified by the schema. What is missing is failure-mode context for a live-network fetch, but for a simple read-only extractor the definition is close to sufficient.

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?

There is a single required parameter at 100% schema coverage; the schema already documents it as a public http(s) URL with a 2000-character cap and URI format. The description adds no meaning beyond that, so the baseline applies.

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?

States a specific verb ("extract") and resource ("a web page") and enumerates exactly what is returned: links with internal/external classification and anchor text, title, description, OpenGraph image, canonical URL, RSS/Atom feeds. That enumeration makes it unmistakably distinct from siblings like web_to_markdown or pdf_to_text without needing to open any schema.

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

Usage Guidelines3/5

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

Implicit guidance only: an agent can infer it should call this when it needs links or page metadata rather than converted text. There is no explicit when-to-use framing, no exclusions, and no mention of choosing this over web_to_markdown when both would work on a URL.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources