Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

fill_form

Fills multiple form fields at once using selector-value pairs, optionally targeting a specific browser tab, to automate repetitive data entry.

Instructions

Fill multiple form fields at once

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": {
      "fields": "<fields>"
    },
    "name": "fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
fieldsYesArray of {selector, value} pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It does not say whether filling dispatches input/change events, whether existing values are overwritten, how partial failures are handled, or what the call returns. For a DOM-mutating tool with zero annotation coverage, this is a material gap.

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 short sentence with no wasted words, and the key scope qualifier is front-loaded. It is efficient, though the brevity edges toward under-specification rather than crisp completeness.

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?

For a mutation tool with no annotations, no output schema, and a nested-ish array parameter of selector/value pairs, the description should cover event dispatch, failure behavior, and return semantics. None of that is present, so an agent has to guess how errors surface.

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?

Schema description coverage is 100%, with both tabId and the fields array documented in the schema, so the baseline of 3 applies. The description adds nothing beyond that – it does not explain selector syntax (CSS? XPath?) or why tabId would be supplied.

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?

"Fill multiple form fields at once" gives a specific verb (fill) and resource (form fields) plus a scope qualifier (multiple at once) that implicitly distinguishes it from the singular "fill" sibling. It stops short of naming that alternative explicitly, so it is clear but not fully differentiated.

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?

The phrase "multiple form fields at once" implies the batch use case versus a single-field tool, but there is no explicit guidance such as when to prefer this over "fill", whether the target page/tab must already be active, or what to do if a selector fails. Usage is inferred, not stated.

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