Spider MCP Server

spider_transform

Already have HTML? Convert it to markdown, text, or XML without web requests. Includes readability and cleaning options for AI-friendly output.

Instructions

Transform HTML content to markdown, text, or other formats without making any web requests. Use when you already have HTML and need to convert it.

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": {
      "data": "<data>"
    },
    "name": "spider_transform"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	Array of HTML documents to transform
`clean`	No	Clean output for AI consumption (strip nav, footers)
`clean_full`	No	Aggressively clean HTML attributes
`readability`	No	Apply readability preprocessing
`return_format`	No	Output format. Default: raw

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.2Jul 6, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. However, it does not disclose any behavioral traits beyond the basic transformation, such as side effects, size limits, or output handling. It only restates the purpose.

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?

The description is a single concise sentence with no wasted words. It is appropriately sized for a simple tool but could benefit from a slightly more structured format.

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?

Given no output schema and 5 input parameters, the description is somewhat complete but lacks details on supported formats, error handling, or behavior with invalid input. It provides the essential context but leaves gaps.

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 description does not add any additional meaning beyond the schema; it merely repeats the transformation concept already clear in the purpose.

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 verb 'Transform' and resource 'HTML content', and explicitly distinguishes itself from tools that make web requests, making the purpose very specific.

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 says 'without making any web requests' and 'Use when you already have HTML and need to convert it', which provides clear context for when to use the tool. It does not explicitly name alternatives but the context implies when not to use it.

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