Skip to main content
Glama

browser_fill

Destructive

Fills a single exact browser locator by role, text, or CSS to enter values in forms. Requires explicit authorization and confirm=true because autosave may trigger.

Instructions

Fill one exact locator. May trigger autosave; requires explicit authorization and confirm=true.

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": {
      "kind": "<kind>",
      "target": "<target>",
      "value": "<value>"
    },
    "name": "browser_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
roleNo
valueYes
targetYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, so the safety profile is partly known. The description adds genuinely new behavioral facts beyond that: filling may trigger an autosave side effect, and authorization plus an explicit confirm=true flag are mandatory, which tells the agent this is a guarded mutation rather than a casual write.

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?

Two short sentences, front-loaded with the action and followed by the side effect and the gate; there is no filler. The brevity is efficient, though part of it comes from omitting parameter detail rather than from tight editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, five-parameter mutation with no output schema and no schema descriptions, so the description needs to do substantial work. It covers the confirm gate and autosave risk but says nothing about how to construct the locator, what happens to the field's prior content, or what a success/failure response looks like — significant gaps for a destructive tool.

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% across five parameters, so the description must carry the burden and largely fails. It only clarifies the meaning of 'confirm' (must be true, tied to authorization); 'kind', 'role', 'target', and 'value' — including how the role/text/css enum interacts with the role and target fields — are left entirely undocumented.

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

Purpose3/5

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

The description pairs a concrete verb ('Fill') with a resource ('one exact locator'), so the basic action is graspable. However, 'locator' is unexplained jargon and nothing distinguishes this from the nearby 'browser_click' or 'browser_snapshot' tools, leaving the agent to infer that this is the form-input counterpart to clicking.

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?

The description states a precondition ('requires explicit authorization and confirm=true') but never says when this tool should be chosen over alternatives such as browser_click, nor when it should not be used. An agent learns a gate exists but gets no routing guidance.

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