Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

fill

Clears an input field and types the provided text using a CSS selector, supporting React-compatible value updates for reliable browser automation.

Instructions

Fill an input field with text (clears existing value, React-compatible)

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": {
      "selector": "<selector>",
      "value": "<value>"
    },
    "name": "fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
valueYesText value to fill
selectorYesCSS selector of the input element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add real behavioral context: it discloses that existing content is destroyed ('clears existing value') and that it writes in a React-compatible way, which matters for framework-controlled inputs. It stops short of describing focus behavior, event firing, or what happens if the selector matches nothing.

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?

A single sentence with the action front-loaded and the two non-obvious behavioral facts tucked into a parenthetical. No filler, no repetition of the name.

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?

For a simple 3-parameter mutation tool with no annotations and no output schema, the description covers purpose and the two key side effects. It omits error/not-found behavior and any indication of what the call returns on success, which an agent needs to sequence follow-up actions.

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 selector, value, and tabId are already documented in the schema. The description adds only that the value is 'text' and that prior content is overwritten, which is modest added meaning. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Fill an input field with text'. Singular 'an input field' implicitly separates it from the multi-field sibling fill_form, though no sibling is named. An agent can tell what it does, but must infer the boundary against fill_form and select_option.

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?

Usage is implied by the wording: use this to populate a text input. There is no explicit when-to-use vs when-not, no mention that multi-field forms should use fill_form, and no statement that non-text controls (checkbox, select) are out of scope. Guidance is adequate but only inferential.

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