Skip to main content
Glama

Type text

type_text
Destructive

Type text into an 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": {
      "sessionId": "<sessionId>",
      "selector": "<selector>",
      "text": "<text>"
    },
    "name": "type_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type
clearNoClear the field before typing
selectorYesCSS selector of the element to type into
sessionIdYesSession ID of the connected browser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"ID de sesión del navegador conectado"New value: +"Session ID of the connected browser"
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. But the most consequential behavior is left undisclosed: the schema's clear parameter defaults to true, meaning existing field content is wiped before typing — a detail the description never surfaces, nor does it mention failure when the selector matches nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single short sentence, front-loaded and free of waste. Its brevity is also its weakness: the description is under-specified rather than efficient, spending no words on the destructive overwrite default.

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 destructive, open-world mutation tool with no output schema, the description should at minimum explain the clear=default-true overwrite risk, session prerequisite, and selector failure behavior. None of these are present, so an agent cannot anticipate the data-loss scenario this tool enables.

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 four parameters (sessionId, selector, text, clear) are documented in the schema itself. The description adds no meaning beyond that — no format hints for selectors, no typing behavior (per-character vs. instant), no notes on clear semantics — so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Type text into an element" gives a concrete verb (type) and resource (text into an element), so the basic action is unambiguous. However, it largely restates the tool name/title and offers no differentiation from siblings like click_element or get_elements, leaving the agent to infer positioning in the browser-automation workflow.

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 when-to-use guidance, no prerequisites (e.g., requiring an active session from connect_to_browser), and no mention of alternatives for entering values. The agent gets no signal about ordering relative to siblings or when this tool is the wrong choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources