Skip to main content
Glama

browser_fill

Read-onlyIdempotent

Fill an input or textarea with the given value. ref is either an aria-ref token from browser.snapshot ('e7') OR a CSS selector ('input[name=email]'). Prefer the aria-ref token — it's stable and matches exactly what snapshot returned. frame (optional): CSS selector of an a CSS ref lives in (nested: 'outer >>> inner').

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

Input Schema

NameRequiredDescriptionDefault
refYes
frameNo
valueYes
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / frame
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Frame"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the useful detail that the aria-ref must come from a prior browser.snapshot and that frames are addressed with 'outer >>> inner' nesting. It does not say whether existing text is replaced or appended, what happens if the ref no longer resolves, or whether input/change events fire — notable gaps for a page-mutating action.

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?

Four sentences, front-loaded with the action, then parameter guidance in the order an agent needs it. No filler. Slightly dense with parenthetical examples but each one earns its place by disambiguating syntax.

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

Completeness4/5

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

Five parameters, no output schema, and the description covers the two non-obvious ones (ref, frame) plus the prerequisite of calling snapshot first. Missing coverage of page_id/value semantics and failure behavior is a real but modest gap for a tool this narrow.

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

Parameters4/5

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

Schema coverage is only 20% (just in_workspace), so the description carries most of the burden and does so for ref and frame: it explains the two accepted ref forms with examples and the nested-iframe selector syntax. value and page_id remain undefined in both places, which keeps it short of a 5.

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 target: 'Fill an input or textarea with the given value.' An agent can tell this is a per-element text-entry operation, distinct in granularity from the form-level sibling browser_fill_form, though the description never names that sibling or explains the split.

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 rather than stated: fill a single input/textarea. The description gives real guidance on ref form ('Prefer the aria-ref token — it's stable and matches exactly what snapshot returned'), but that is parameter choice, not tool choice. There is no 'use this instead of browser_fill_form when…' or 'use browser_check for checkboxes' exclusion, which matters given many siblings mutate page state.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.