Skip to main content
Glama

fill_by_uid

Fill text inputs, textareas, or select options by element UID from a browser snapshot to automate form entry and testing in Firefox.

Instructions

Fill text input/textarea or pick a select option by UID.

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": {
      "uid": "<uid>",
      "value": "<value>"
    },
    "name": "fill_by_uid"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesInput element UID from snapshot
valueYesText to fill, or the value or visible text of the option to select

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / value / description
      Previous value: -"Text to fill"New value: +"Text to fill, or the value or visible text of the option to select"
  2. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / uid / description
      Previous value: -"The UID of the input element"New value: +"Input element UID from snapshot"
    • changedInput schema / properties / value / description
      Previous value: -"The text value to fill into the input"New value: +"Text to fill"
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=false already signals a mutation, and the description adds which elements are affected and whether the action is filling or selecting. It does not disclose whether filling replaces existing text, whether input/change events fire, how select options are matched, or what happens on 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?

It is a single front-loaded sentence with no filler, immediately stating the action and supported targets.

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 with full schema coverage and no output schema, this is minimally adequate. It still omits the usage boundary against fill_form_by_uid and other control types, and gives no behavioral detail about replacement or selection semantics.

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?

The schema already documents both parameters: uid as an input element UID from a snapshot, and value as text to fill or the option value/visible text to select. The description adds no format, matching, or mapping details beyond that.

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 ('Fill') and the affected resources ('text input/textarea or pick a select option') scoped by UID. The purpose is clear, but it does not explicitly distinguish this single-control operation from the sibling fill_form_by_uid.

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 naming the supported element types: text input, textarea, and select. It gives no explicit when-not guidance for other controls such as checkboxes or radios, and does not say when to prefer this over fill_form_by_uid.

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