Skip to main content
Glama

type

Inserts text at the cursor in a referenced element or the focused field; use form_input instead when replacing a field's entire value.

Instructions

Type text into an element (by ref), or into whatever is focused. Inserts at the cursor; use form_input to replace a field's whole value.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement reference from read_page or find, e.g. "e12"
textYes
tabIdYesTab ID, from tabs_list or tab_create
submitNoPress Enter afterwards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

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 burden and does disclose the key behavioral trait: text is inserted at the cursor rather than replacing content, and omission of ref targets whatever is focused. It does not cover failure behavior for a missing/uneditable element, which is the main remaining gap.

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 short sentences, zero filler, with the core behavior front-loaded and the sibling disambiguation placed immediately after.

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 four-parameter browser-automation tool with no annotations or output schema, this covers targeting, insertion semantics, and the main alternative. Only error/edge-case behavior and the ref-vs-focus choice are left implicit.

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

Parameters4/5

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

Schema coverage is 75%, so text and submit rely on the schema alone (submit is at least self-describing). The description adds real meaning the schema lacks: ref is optional and, when omitted, input goes to the currently focused element.

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 text) and the two possible targets (an element by ref, or the focused element), and explicitly contrasts with the sibling form_input. An agent can distinguish it from form_input 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?

Gives an explicit alternative and the condition that selects it: use form_input when the field's whole value should be replaced. It does not spell out when to prefer the ref form over the focused-element form, but the guidance is clear enough to route correctly.

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