Skip to main content
Glama
Sign In
chromium-mcp

chromium-mcp

by gzigurella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

extract_data

Extract structured data from a web page with CSS selectors. Returns JSON with text content or attributes from single or multiple matching elements.

Instructions

Extract structured data from a web page using CSS selectors. Returns JSON with extracted text content or attribute values. Supports single element, multiple elements, and attribute extraction.

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>",
      "selectors": "<selectors>"
    },
    "name": "extract_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to extract data from (must be http or https)
selectorsYesList of CSS selectors with extraction rules
timeoutNoTimeout in seconds (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that it returns JSON with text or attributes, supports multiple and attribute extraction. Does not mention error handling or timeouts, but core behavior is clear.

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 sentences, no fluff, front-loaded with core action and returns. Efficient and clear.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description mentions JSON return with text or attribute values. For a simple 3-parameter tool, this is adequate. Could briefly mention error cases or sibling differentiators.

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?

100% schema description coverage means the schema already explains each parameter well. The description adds no extra parameter-level detail 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?

Clearly states the tool extracts structured data from a web page using CSS selectors, distinguishing it from siblings like fetch_page (raw content) and get_link (links). Specifies return type and capabilities.

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?

Does not explicitly state when to use this tool versus alternatives like fetch_page or get_link. The description implies it's for selective extraction, but no direct guidance.

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

Deploy Server

Other Tools