Skip to main content
Glama

Page links

page_links
Read-onlyIdempotent

Extract up to 200 unique links from a web page with anchor text, internal/external classification, and nofollow flags. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), yet the description still adds material behavior the annotations cannot express: a mandatory two-step payment handshake, a per-call price ($0.002), accepted settlement chains/tokens, and the 'unique' deduplication and 200-item cap. It stops short of describing failure modes or what the first paymentless call actually returns beyond 'the terms'.

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?

Three tight sentences, front-loaded with what is extracted and only then the commercial details; nothing is repeated. The token/chain enumeration ('USDC on Arc, Base or Solana, or XNT on X1') is the one clause that could be trimmed for a tool-selection decision, though it is actionable payment information.

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 description does the work of describing the return fields and the 200-unique cap, and it fully resolves the non-obvious billing interaction. Remaining gaps are minor: handling of JS-rendered pages, redirects, or what happens if the signed payment is rejected.

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?

Schema coverage is 100%, so both parameters are already documented, and the schema itself explains that `payment` carries a base64 x402 payload completing the purchase. The description reinforces the two-pass usage pattern but adds little new per-parameter syntax or format detail, so the baseline 3 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 and resource ('Extract ... links from a web page') plus the exact output shape (anchor text, internal/external classification, nofollow flags) and a hard scope limit (up to 200 unique). That output signature alone separates it from sibling page readers like page_extract or page_markdown, which return content rather than a link inventory.

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?

The payment sequence ('call once without payment for the terms, sign them with your own wallet, call again with payment') is explicit operational guidance, but there is no when-to-use/when-not guidance relative to alternatives such as link_check (which validates links) or page_extract. The agent must infer the choice from the resource being read.

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