Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

type

Enters text into the focused browser element via CDP Input.insertText, enabling AI clients to fill form fields and inputs during automated browser control.

Instructions

Type text into the focused element via CDP Input.insertText

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": {
      "text": "<text>"
    },
    "name": "type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
tabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. Naming CDP Input.insertText is genuinely useful (it inserts text rather than dispatching per-key events), but it is never explained, and the description omits what happens when no element is focused, whether existing content is replaced or appended, and whether framework input handlers fire.

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 front-loaded sentence with zero padding; nothing needs trimming. It is arguably undersized for a tool with two undocumented parameters, but there is no wasted wording.

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?

With no annotations, no output schema, and 0% schema coverage, the description is the only source of behavior, yet it leaves the focus prerequisite, tab targeting, replacement semantics, and failure modes unaddressed. It is too thin to let an agent call this reliably without trial and error.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It clarifies 'text' only by restating the parameter name and says nothing about 'tabId' — notably that it is optional and presumably defaults to the active tab — leaving the more consequential parameter undocumented.

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 (type text) and a specific target (the focused element), plus the underlying mechanism (CDP Input.insertText). 'Focused element' implicitly distinguishes it from sibling 'fill' (which typically sets a value directly) and from 'press_key', but it never explicitly names an alternative.

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: typing into the focused element presupposes that something has already been focused, but the description never says to click/tab first. No when-not guidance and no reference to 'fill' or 'press_key' as alternatives, so the agent must infer the choice.

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