Skip to main content
Glama

type

Enter text into inputs, textareas, or editable elements, optionally clearing existing content or submitting the form after confirmation.

Instructions

Type text into an input, textarea or editable element.

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
textYesText to type.
clearNoReplace existing value. Default true.
indexNoElement number from page_elements.
tabIdNoAgent tab id from tabs_list. Omit to use the last agent tab.
submitNoSubmit the form or press Enter after typing. Needs confirm. Default false.
confirmNoSet true ONLY after the user approved this exact submit/irreversible action in chat.
selectorNoCSS selector.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it omits the most consequential behavior: 'clear' defaults to true, so existing content is replaced by default. It also says nothing about the confirm-gated submit path or how the element is located when both selector and index are supplied.

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 no filler, so nothing is wasted. It is terse to the point of under-specification, but that gap is scored under transparency and completeness rather than length.

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?

A seven-parameter interaction tool with no annotations and no output schema needs more than one sentence, particularly around the destructive default replace behavior and the approval requirement for submit. The description leaves an agent to discover these from the schema or by causing unintended data loss.

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 all seven parameters, including defaults and the confirm approval rule, are already documented in the schema. The description adds no semantics beyond that, which is the baseline 3 case.

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 description gives a specific verb (type) and the target element classes (input, textarea, editable element), which clearly distinguishes it from siblings like click, navigate or page_text. It does not name any sibling or state what this tool is not for, so it falls short of 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 Guidelines2/5

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

There is no guidance on when to pick this tool versus clicking or submitting, nor on choosing between the 'selector' and 'index' targeting parameters. The element-type hint implies a form-filling context, but no prerequisites or exclusions are stated.

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