Skip to main content
Glama

page_links

Read-only

Page metadata and links: title, description, canonical, OpenGraph image, language, RSS/Atom feeds, plus every internal and external link with its anchor text. Respects robots.txt; not charged on failure. — $0.001 USDC per call via x402 v2 (Base or Solana).

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 of the page

Output Schema

NameRequiredDescriptionDefault
okYes
urlNo
metaNo
countsNo
externalNo
internalNo
final_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only cover readOnly and openWorld, but the description adds substantive behavioral context: robots.txt compliance, no charge on failed calls, and the exact payment model ($0.001 USDC per call via x402 v2 on Base or Solana). That cost/failure disclosure is genuinely useful for an agent deciding whether to invoke. It does not say what a robots-blocked or failed response looks like, which keeps it below a 5.

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?

Output contents are front-loaded in the first sentence and cost/behavioral caveats come second, with no wasted wording. The pricing sentence is dense but earns its place by disclosing a real per-call charge.

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?

An output schema exists, so return-value detail is not strictly required, and the description still enumerates the main fields. Combined with cost and failure-charging disclosure, an agent has enough to call it correctly; only failure/robots-blocked response behavior is unstated.

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?

With a single parameter at 100% schema description coverage, the schema already fully specifies the required public http(s) URL. The description adds no further constraint, format, or edge-case detail about the url argument, so the baseline applies.

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 enumerates exactly what the tool extracts — title, description, canonical, OpenGraph image, language, feeds, and all internal/external links with anchor text — so the resource and output are unambiguous. It does not explicitly contrast itself with read_url or domain_intel, so an agent must infer that this is metadata/link extraction rather than page-body retrieval.

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?

There is no when-to-use guidance, no exclusions, and no mention of the siblings read_url or domain_intel. The only conditional statements (respects robots.txt, not charged on failure) describe behavior, not selection criteria.

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