Skip to main content
Glama

browser_fill

Destructive

Fill non-password browser form fields by CSS selector, enabling controlled form entry after browser and GUI permissions are explicitly enabled.

Instructions

Fill a non-password browser form field by CSS selector; requires browser+GUI opt-in

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>",
      "text": "<text>"
    },
    "name": "browser_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this as destructive and non-read-only. The description adds valuable context that the tool targets browser form fields, specifically excludes passwords, and requires browser+GUI opt-in, but it does not explain whether existing field content is overwritten, whether events are triggered, or what happens on selector failure.

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 definition is a single compact sentence with no filler. The core action, selector mechanism, restriction, and prerequisite are front-loaded.

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 two-parameter mutation tool, the description covers the essential action and opt-in prerequisite. However, with no output schema and 0% schema description coverage, it should explain the text parameter's role and the effect of filling a field that may already contain content.

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 should compensate for both parameters. It clarifies that selector is a CSS selector, but it says nothing about the text parameter, such as that it is the value written into the field or how existing content is handled.

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 states a specific verb and resource: fill a browser form field by CSS selector. The non-password restriction and browser/GUI opt-in condition add useful scope, though it does not explicitly distinguish itself from siblings like gui_type or browser_click.

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?

It gives a prerequisite (browser+GUI opt-in) and a field type restriction (non-password), which imply when the tool is usable. However, it does not state when to prefer browser_fill over gui_type, browser_click, or other input tools.

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