Skip to main content
Glama
raultov

chrome-debug-mcp

by raultov
OverviewSchemaRelated ServersScoreDiscussions(1)
Rust
Local

fill_input

Fills input fields via CSS selector by inserting text and triggering input/change events. Use to populate forms, search boxes, and text areas.

Instructions

Focuses an input field via CSS selector and inserts text using native input simulation, triggering input/change events. Side effects: modifies DOM input value; triggers input/change event handlers. Prerequisites: element must exist, be visible, and be an input/textarea or contenteditable element. Returns: success confirmation. Use this to populate form fields, search boxes, text areas. Alternatives: 'evaluate_js' for direct value assignment without events, 'click_element' to focus manually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText content to insert. Constraints: any string (special chars escaped automatically). Interactions: replaces any existing text after focus; triggers input/change events. Defaults to: None (required).
tab_idNoThe Tab ID of the target tab. Omit to use the active tab.
selectorYesCSS selector identifying the input element. Constraints: valid CSS selector matching an input/textarea/contenteditable element. Interactions: element must be focusable and writable. Defaults to: None (required).
instance_idNoChrome instance id from open_instance/list_instances. Omit for the default instance.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.3.2
    • removedInput schema / properties / instance_id / nullable
      Removed value: -true
    • removedInput schema / properties / tab_id / nullable
      Removed value: -true
  2. Changed2 schema fields changedv1.0.11
    • addedInput schema / properties / instance_id
      Added value: +{
+  "description": "Chrome instance id from open_instance/list_instances. Omit for the default instance.",
+  "nullable": true,
+  "type": "string"
+}
    • addedInput schema / properties / tab_id
      Added value: +{
+  "description": "The Tab ID of the target tab. Omit to use the active tab.",
+  "nullable": true,
+  "type": "string"
+}
  3. Changed2 schema fields changedv1.0.7
    • changedInput schema / properties / selector / description
      Previous value: -"CSS selector for the input element to fill"New value: +"CSS selector identifying the input element. Constraints: valid CSS selector matching an input/textarea/contenteditable element. Interactions: element must be focusable and writable. Defaults to: None (required)."
    • changedInput schema / properties / text / description
      Previous value: -"The text to insert into the input field"New value: +"Text content to insert. Constraints: any string (special chars escaped automatically). Interactions: replaces any existing text after focus; triggers input/change events. Defaults to: None (required)."
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and meets it. It discloses side effects (modifies DOM value, triggers input/change events), prerequisites (element exists, visible, input/textarea/contenteditable), and return type (success confirmation). This is thorough behavioral disclosure.

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?

The description is well structured and efficient: opening action, side effects, prerequisites, return, usage, alternatives. Every sentence provides distinct value with no redundancy or fluff.

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 4-parameter tool with no output schema, the description fully covers what the tool does, when to use it, behavioral side effects, prerequisites, and return value. It is complete enough for an agent to select and invoke it correctly without ambiguity.

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% and each parameter has a detailed description already. The tool description adds only general context ('CSS selector', 'input/textarea/contenteditable') already present in the schema. Baseline 3 is appropriate since the schema handles parameter semantics.

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?

States a specific verb ('focuses', 'inserts text') and resource ('input field via CSS selector'), and explains the native input simulation with event triggering. It distinguishes itself from siblings by naming evaluate_js and click_element as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'Use this to populate form fields, search boxes, text areas.' It also gives clear alternatives and their distinguishing conditions: evaluate_js for direct value assignment without events, click_element to focus manually.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/raultov/chrome-debug-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server