Skip to main content
Glama

web_type

Types text into an input or textarea matching a CSS selector, with an option to submit the form.

Instructions

Type 'text' into the input/textarea matching 'selector'. Set submit=true to submit the form.

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>"
    },
    "name": "web_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
submitNo
selectorYes
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and does not say whether existing field content is replaced or appended, whether the element is focused/scrolled into view, what happens if the selector matches nothing, or whether submit=true triggers navigation and a wait. It only documents the typing target and the submit flag.

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?

Two short sentences, front-loaded with the core action and following with the optional submit behavior. No wasted wording, though it is terse enough to leave behavioral questions unanswered rather than being over-long.

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 browser-automation action with four parameters, no annotations, and no output schema, the definition covers the happy path but omits failure handling, return value, and the effect of submit=true. Adequate to invoke, thin for an agent that needs to reason about consequences.

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 coverage is 25% (only target_id documented), but the description supplies meaning for the other three: text is the value to type, selector is the match target and type (input/textarea), and submit toggles form submission. That compensates well, though it adds no detail on selector syntax (CSS vs XPath) or on the tab-selection default beyond what the schema says.

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?

States a specific verb and resource: type text into the input/textarea matching a selector. An agent can distinguish this from web_click or web_navigate by the 'type into input' framing, though no sibling is named explicitly.

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 by the mechanics (use it when you need to fill a field), and the submit=true flag hints at the follow-on action. There is no explicit guidance on when to prefer this over web_eval or web_click, and no preconditions or exclusions stated.

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