Spider MCP Server

spider_ai_links

Extract and filter links from a URL using AI. Describe the links you need, and the AI finds and categorizes them based on your instructions.

Instructions

AI-powered link extraction and filtering. Describe which links you want and the AI finds and categorizes them. Requires an active AI subscription (https://spider.cloud/ai/pricing).

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>",
      "prompt": "<prompt>"
    },
    "name": "spider_ai_links"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	URL to extract links from
`limit`	No	Max links
`prompt`	Yes	Link filter instructions (e.g. 'Find all documentation links and API reference pages')
`request`	No	Request type: http (fast), chrome (JS rendering), smart (auto-detect). Default: smart
`return_format`	No	Output format. Default: raw

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.2Jul 6, 2026

TDQS

A3.9/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 full burden. It mentions the AI subscription requirement but lacks details on rate limits, error handling, or behavioral traits. The brief description offers limited transparency beyond the core capability.

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 concise sentences deliver the purpose and a key prerequisite (AI subscription). No wasted words; front-loaded with the core action.

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?

With 5 parameters (2 required) and no output schema, the description minimally explains the tool's behavior. The limit and return_format parameters are well-described in the schema, but the description does not elaborate on results or pagination. It is adequate but not rich.

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 baseline is 3. The tool description adds little beyond what the schema already provides (e.g., 'AI-powered' framing). However, the schema descriptions are clear, making this adequate.

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 clearly states the tool extracts and filters links using AI, with a directive to 'describe which links you want.' It distinguishes from sibling tools like 'spider_links' by emphasizing AI-powered functionality.

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?

The description implies use cases by saying 'describe which links you want' and notes the requirement of an active AI subscription. However, it does not explicitly state when not to use or compare to alternatives like 'spider_links' for non-AI extraction.

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