Spider MCP Server

spider_browser_content

Retrieve the full HTML or extracted visible text of the current browser page for content analysis or data extraction.

Instructions

Get the current page content. Returns the full HTML or extracted text of the page.

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": {
      "session_id": "<session_id>"
    },
    "name": "spider_browser_content"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No	Content format: html (full DOM) or text (visible text only). Default: html
`session_id`	Yes	Session ID from spider_browser_open

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.2Jul 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether JavaScript is executed, if the page state is affected, or any prerequisites. It only mentions output format.

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, front-loaded with purpose. Every word is meaningful with no 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 return types (HTML or text) but lacks details on error handling or session validity. For a tool with no output schema and no annotations, it is adequate but not comprehensive.

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 coverage is 100%, so the schema already describes both parameters. The description adds context like 'full DOM' for HTML format, but doesn't provide significant new meaning beyond the schema.

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 'get' and the resource 'current page content', and distinguishes it from sibling tools like spider_browser_screenshot by specifying that it returns HTML or text.

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?

The description implies usage for retrieving page content but offers no explicit guidance on when to use this tool versus alternatives like spider_browser_screenshot or spider_browser_evaluate.

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