Skip to main content
Glama
Sign In
Puppeteer Real Browser MCP Server

Puppeteer Real Browser MCP Server

by withLinda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

type

Enter text into HTML input fields using a CSS selector and text content, with an optional delay between keystrokes to control speed.

Instructions

Type text into an input field

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type
delayNoDelay between keystrokes in ms
selectorYesCSS selector of input element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It doesn't disclose whether it clears existing content, simulates individual keystrokes, or requires the element to be focused. The delay parameter is mentioned only in the schema, not in the description.

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?

The description is a single sentence of six words, front-loading the core action and target. Every word contributes value, with no redundancy or filler.

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 and no output schema, the description is too thin. It doesn't address behavior like overwriting vs. appending, event triggering, or error conditions. The schema documents parameters but not the operational context.

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 parameters are already well-documented. The description adds no additional meaning to selector, text, or delay beyond what the schema provides, so the baseline score 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?

The description 'Type text into an input field' clearly identifies the action (type) and the resource (input field). It distinguishes from siblings like click, get_content, and navigate because it's the only tool for entering text.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It doesn't mention that it's for filling form inputs or that it shouldn't be used for clicking or navigating. No exclusions or prerequisites are provided.

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