chrome

Overview Schema Source Related Servers Discussions Admin

Type text

type

Enter text into inputs, textareas, or contenteditable elements with trusted keystrokes. Automatically focuses the target, clears the field by default, and can submit by pressing Enter.

Instructions

Type into an input, textarea or contenteditable element. When a target is provided (ref or selector), the cursor automatically moves to the element and clicks it to activate/focus it first, then executes natural typing via insertText without DOM manipulation. Clears the field by default and uses trusted CDP keystrokes. Set pressEnter=true to submit.

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

Name	Required	Description	Default
`ref`	No	Element ref to type into. Cursor moves to element and clicks it to activate first.
`text`	Yes	Text to type.
`clear`	No	Clear the field before typing. Default true.
`delay`	No	Delay per character in ms (defaults to human typing cadence).
`tabId`	No
`focused`	No	Type into the currently focused element.
`frameId`	No
`natural`	No	Use insertText for natural typing without DOM manipulation. Default true.
`timeout`	No
`trusted`	No
`selector`	No	CSS selector to type into. Cursor moves to element and clicks it to activate first.
`waitUntil`	No		domcontentloaded
`delayAfter`	No
`pressEnter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses the auto-move-and-click activation behavior, the default field-clearing, that keystrokes are trusted CDP events, that typing uses insertText without DOM manipulation, and that delay defaults to a human cadence. It does not cover failure behavior (missing ref/selector), navigation semantics from waitUntil, or what a return value looks like, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the purpose and immediately followed by the target/activation mechanics and the submit flag; every sentence adds information. There is mild redundancy with the schema descriptions of ref and selector, which repeat the 'moves to element and clicks it' clause almost verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter browser automation tool with no annotations and no output schema, the description covers the core interaction model well but leaves roughly half the parameters (tab/frame targeting, trusted, timeout, waitUntil, delayAfter) entirely undocumented. An agent can call it for the common case but is under-informed about scoping and wait behavior.

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 50% across 14 parameters, so the description must compensate and it partially does: it explains ref/selector focus behavior, the clear default, natural insertText typing, delay cadence, and pressEnter submission. However, tabId, frameId, focused, trusted, timeout, waitUntil, and delayAfter have no meaning added anywhere, leaving a substantial gap for a tool with this many controls.

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?

The first sentence gives a specific verb ('Type into') and enumerates the supported targets (input, textarea, contenteditable), so the agent knows exactly what the tool acts on. It does not explicitly distinguish itself from the sibling 'fill_form' or 'press', which is the only thing separating a 4 from a 5.

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: the description explains that supplying a ref or selector focuses the target first, and that pressEnter=true submits, which hints at when the flag is appropriate. There is no explicit when-to-use/when-not guidance and no mention of when to prefer fill_form or press over this tool.

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

Deploy Server