ai-agent-hub

Extract all links from a page (paid)

extract_links

Convenience wrapper around run_query with mode="links" — fetches a URL and returns every outbound link, resolved to absolute URLs and deduped. Same price and payment flow as run_query.

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

Name	Required	Description
`url`	Yes	The URL to extract links from
`agentId`	No
`paymentHeader`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the paid nature and output transformation, but does not state read-only status, authentication requirements, rate limits, or error behavior.

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?

Two tightly scoped sentences, front-loaded with purpose and pricing context. There is no filler or redundancy.

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 covers output behavior and payment context, which is important since there is no output schema. But with two undocumented parameters, no annotations, and no explicit auth or safety guidance, it is not fully complete for invocation.

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 coverage is only 33%, with just url documented in the schema. The description does not explain agentId or paymentHeader or connect the payment flow to a specific parameter, so it fails to compensate for the low coverage.

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?

The description states the exact operation: fetches a URL and returns every outbound link, resolved to absolute URLs and deduped. It also positions the tool as a wrapper around run_query with mode="links", distinguishing it from generic querying.

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

Usage Guidelines4/5

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

It implies this is the convenience alternative to run_query for link extraction, giving an agent a clear routing signal. However, it does not explicitly say when not to use it or name sibling alternatives such as extract_images.

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

All ai-agent-hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?