Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

fill

Enter or update text in an input or textarea using a CSS selector and dispatch input/change events so browser forms and scripts react correctly.

Instructions

Fill an input/textarea by CSS selector, dispatching input/change events

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
tabIdNo
valueYes
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does surface one genuinely useful behavioral fact: it dispatches input/change events, which matters for framework-controlled fields. However, it omits whether the existing value is replaced or appended, what happens on zero or multiple selector matches, and whether a target tab must be active — all material for a browser mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single clause, front-loaded with the verb and resource, with no filler or redundancy. It is efficient rather than padded, though the terseness leaves the gaps noted in other dimensions.

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?

No output schema and no annotations mean the description is the sole source of behavioral information, and for a three-parameter browser-mutation tool it is thin. The core mechanic is captured, but tab targeting, failure modes, and value-replacement semantics are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and only partly does: it clarifies that 'selector' is a CSS selector and implies 'value' is the text written. 'tabId' is never mentioned in the description or the schema, and the replace-vs-append semantics of 'value' remain undefined.

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?

The description names a specific action (fill) applied to a specific target (input/textarea) via a stated mechanism (CSS selector). An agent can picture the operation immediately. It loses a point because it never distinguishes itself from the sibling 'type', which plausibly targets the same elements, leaving the choice ambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when 'fill' is preferable to 'type' or 'press_key', no prerequisites such as a page being loaded or a tab being selected. The agent must infer placement in a workflow from the one-line description alone.

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