Skip to main content
Glama
gaforov

selenium-mcp

by gaforov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

type

Fill input, textarea, or editable fields using a selector or ref; clears the current value first, then sends keystrokes, with optional Enter to submit.

Instructions

Type text into an input, textarea, or other editable element. Waits for it to be visible, clears the current value first (clearFirst: false appends instead), then sends the text as keystrokes so the page's input events fire; submit: true presses Enter afterwards. Target it by selector or by a ref from capture_page. For dropdowns use select_option; for single keys like Tab or Escape use press_key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoElement ref from the latest capture_page result (e.g. 'e12'). Use instead of selector; refs go stale after navigation, so capture again if one is rejected.
textYesThe text to type, e.g. 'standard_user'.
submitNoPress Enter after typing (default false), e.g. to submit a search box or login form.
selectorNoHow to find the element, e.g. { by: 'id', value: 'user-name' } or { by: 'css', value: '#login-button' }. Provide either selector or ref.
timeoutMsNoHow long to wait for the field to become visible, in milliseconds (default 10000).
clearFirstNoClear the field before typing (default true). Set false to append to the existing value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • addedInput schema / properties / clearFirst / description
      Added value: +"Clear the field before typing (default true). Set false to append to the existing value."
    • addedInput schema / properties / ref / description
      Added value: +"Element ref from the latest capture_page result (e.g. 'e12'). Use instead of selector; refs go stale after navigation, so capture again if one is rejected."
    • addedInput schema / properties / selector / description
      Added value: +"How to find the element, e.g. { by: 'id', value: 'user-name' } or { by: 'css', value: '#login-button' }. Provide either selector or ref."
    • addedInput schema / properties / selector / properties / by / description
      Added value: +"Locator strategy: css, xpath, id, name, class/className, tag/tagName, linkText, or partialLinkText."
    • addedInput schema / properties / selector / properties / value / description
      Added value: +"The locator for that strategy, e.g. '#login-button' for css, 'user-name' for id, or //button[@type=\"submit\"] for xpath."
    • addedInput schema / properties / submit / description
      Added value: +"Press Enter after typing (default false), e.g. to submit a search box or login form."
    • addedInput schema / properties / text / description
      Added value: +"The text to type, e.g. 'standard_user'."
    • addedInput schema / properties / timeoutMs / description
      Added value: +"How long to wait for the field to become visible, in milliseconds (default 10000)."
  2. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / ref
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "selector",
-  "text"
-]New value: +[
+  "text"
+]
  3. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the visibility wait, that the field is cleared first (clearFirst: false appends), that text is sent as keystrokes so the page's input events fire, and that submit: true presses Enter. It does not cover failure behavior (e.g., what happens if the element is not found within timeoutMs) or the return payload, which keeps it short of a 5.

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?

Three dense sentences, front-loaded with the core action and behavior, then the submit/clearing modifiers, then the sibling routing. No filler and nothing buried.

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?

For a 6-parameter mutation-style tool with no annotations and no output schema, the description covers action, waiting, clearing, keystroke semantics, submit behavior, and alternative tools. It leaves failure/retry behavior and the response undefined, which is a modest gap rather than a blocker.

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%, so the schema already documents ref, text, submit, selector, timeoutMs and clearFirst in detail; baseline is 3. The description restates clearFirst/submit semantics rather than adding new syntax or format information, so it adds little beyond the structured fields.

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

Purpose5/5

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

States a specific verb and resource ('Type text into an input, textarea, or other editable element') and explicitly disambiguates from siblings by naming select_option for dropdowns and press_key for single keys. An agent can distinguish this from click/press_key/select_option without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this for editable text fields, use select_option for dropdowns, use press_key for single keys like Tab/Escape. It also states the two targeting modes (selector or a ref from capture_page), so when-to-use and how-to-target are both covered.

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

Deploy Server

Other Tools