Skip to main content
Glama

extract_links

Extract and categorize links from a page—internal, external, emails, scripts, forms—and list query-parameter names to map attack surface.

Instructions

Extract and categorize links from a page: internal, external, emails, scripts, forms.

Also lists query-parameter names seen, useful for mapping attack surface.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo
external_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose the shape of the result (categorized links plus query-parameter names), which is valuable given there is no output schema. However, it says nothing about whether the page is fetched live, authentication or rate-limit considerations, or how the limit behaves.

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?

Two short sentences, front-loaded with the core action and output categories. No filler, though the second sentence is slightly tacked-on rather than integrated.

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?

The description partially compensates for the missing output schema by naming what is returned, but it leaves all three undocumented parameters unexplained in a tool with no annotations. Adequate but with clear gaps for an agent trying to set limit or external_only correctly.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, so the description must compensate and largely does not: 'limit' and 'external_only' are never explained. The mention of external links is the only indirect hint that external_only filters the output.

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 gives a specific verb and resource ('Extract and categorize links from a page') and even enumerates the categories produced (internal, external, emails, scripts, forms). It does not distinguish itself from the sibling browser_extract, which is the nearest overlap, so it falls short of a 5.

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?

Usage is only implied via the closing phrase 'useful for mapping attack surface,' which hints at a reconnaissance context. There is no statement of when to prefer this over browser_extract, no prerequisites, and no exclusions.

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