APIVerve

Link Scraper

LinkScraper

Read-only

Link Scraper: Link Scraper is a website link extractor API that pulls internal and external links from any webpage URL in real time. It resolves relative paths to absolute URLs, strips empty fragments, and returns anchor text with internal and external counts. (Cost: 25 credits)

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL of the web page to scrape links from
`maxlinks`	No	Maximum number of links to scrape and return	50
`includequery`	No	Include query strings in the scraped links

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, but the description adds substantive behavior the annotations do not: relative paths are resolved to absolute URLs, empty fragments are stripped, and internal/external counts are returned. It also discloses a 25-credit cost, which is operationally relevant for budgeting repeated scrapes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is two tight, front-loaded functional sentences, but it opens by restating the tool name twice ('Link Scraper: Link Scraper is...'), which wastes the most valuable position. The credit cost is correctly appended at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need no explanation, and the description still summarizes what is returned (anchor text plus internal/external counts). With full schema coverage and clear annotations, this is sufficient for an agent to call the tool correctly.

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 description coverage is 100%, so url, maxlinks, and includequery are already documented in the schema. The description adds nothing about parameter behavior — notably it never mentions the link cap or query-string handling, though the 'strips empty fragments' note hints at URL normalization.

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+resource ('pulls internal and external links from any webpage URL') and names the returned payload (anchor text with internal/external counts). It does not, however, distinguish itself from near-neighbours such as MarkdownLinkExtractor, WebsiteImagesScraper, or WebsitesToText, so an agent must infer the boundary.

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 implied by the phrase 'any webpage URL' and the real-time extraction framing, so an agent can infer the context. There is no explicit when-to-use/when-not, no prerequisite statement, and no routing to competing siblings, so it stops at implied guidance.

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

All APIVerve 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.