mcp-chromium-cdp

Overview Schema Source Related Servers Discussions Admin

chrome_extract_forms

Extract structured form data from web pages without custom scripting. Returns fields, submit buttons, and fieldsets, including from React and Shadow DOM forms, and identifies filled vs empty fields.

Instructions

Extract structured form data without custom scripting. Returns fields (name, type, value, placeholder, required, label, validation rules), submit buttons, and fieldsets. Works with standard forms, React forms, and Shadow DOM forms. Identifies filled vs empty fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chrome_extract_forms"
  }
}

Input Schema

Name	Required	Description	Default
`formSelector`	No	Optional CSS selector to target a specific form (e.g., "#login-form"). If not provided, extracts all forms on the page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of disclosing behavior. It states that the tool is read-only ('Extract'), lists the returned data, and highlights support for specific form types and filled/empty detection. It lacks details on error handling or behavior with no forms, but for a read-only extraction tool this is adequate.

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?

Three sentences, each adding distinct value: purpose, return payload, and supported contexts. No fluff, front-loaded with the primary verb and object.

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?

For a simple tool with one optional parameter and no output schema, the description is complete: it explains what is returned, mentions compatibility across form types, and flags filled/empty state. No critical gaps remain for typical usage.

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?

The schema description covers 100% of the single parameter (formSelector), explaining its optional nature and default behavior. The tool description itself does not add parameter-specific details, so the baseline of 3 is appropriate.

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's function: 'Extract structured form data without custom scripting.' It specifies the exact resource (forms) and the return payload (fields, submit buttons, fieldsets). This differentiates it from sibling tools like chrome_extract_interactive and chrome_execute_script.

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 phrase 'without custom scripting' signals an alternative to scripting tools, and the mention of standard forms, React forms, and Shadow DOM forms gives context for when it applies. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of the highest bar.

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