Skip to main content
Glama
Novpix

browsermcp-plus

by Novpix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_type

Destructive

Type text into an editable element, replacing its content; optionally press Enter to submit. Use for single fields; for multiple fields, use the form fill tool.

Instructions

Type text into an editable element, replacing its content. To fill several fields at once, prefer browser_fill_form.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesExact target element reference from the page snapshot
textYesText to type into the element
slowlyNoType one key at a time, for inputs that format as you type (phone, card or date masks). Slower.
submitNoWhether to submit entered text (press Enter after)
elementYesHuman-readable element description used to obtain permission to interact with the element
snapshotNoAlso return the page snapshot after the action (default: no). Use it when you need to see the result right away.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / properties / slowly
      Added value: +{
+  "description": "Type one key at a time, for inputs that format as you type (phone, card or date masks). Slower.",
+  "type": "boolean"
+}
    • addedInput schema / properties / snapshot
      Added value: +{
+  "description": "Also return the page snapshot after the action (default: no). Use it when you need to see the result right away.",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description adds concrete context by stating it replaces existing element content, telling the agent what gets destroyed. It stops short of documenting auth, permissions, or limits, but that is a minor gap given annotation coverage.

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?

Two sentences, zero waste, with the core action front-loaded and the sibling routing placed second. Every clause earns its place.

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 single-field typing tool with annotations covering safety and a fully documented schema, the definition is nearly complete; the only omission is any note about return/snapshot behavior, which the schema's 'snapshot' param partially covers.

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 six parameters (ref, text, slowly, submit, element, snapshot) are already fully documented in the schema. The description adds no syntax or format detail beyond this, so the baseline of 3 applies.

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 (type) and resource (editable element) and clarifies the effect on existing content ('replacing its content'). It also names the sibling browser_fill_form, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to browser_fill_form when several fields must be filled at once, implying this tool is for single-field entry. It gives a clear positive condition and alternative but does not spell out exclusions or prerequisites beyond that.

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