Skip to main content
Glama

type_text

Enter text into specified input fields using CSS selectors with customizable keystroke delays. Enables precise automation in browser interactions via MCP Browser Server.

Instructions

Type text into an input field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delayNoDelay between keystrokes in milliseconds
selectorYesCSS selector for the input element
textYesText to type

Implementation Reference

  • Handler for the 'type_text' tool. Validates arguments with TypeTextSchema, uses Playwright's page.fill() to input text into the specified selector, ignores delay parameter, and returns a confirmation message.
    case 'type_text': {
      if (!currentPage) {
        throw new Error('No browser page available. Launch a browser first.');
      }
    
      const params = TypeTextSchema.parse(args);
      await currentPage.fill(params.selector, params.text);
    
      return {
        content: [
          {
            type: 'text',
            text: `Typed "${params.text}" into element: ${params.selector}`
          }
        ]
      };
    }
  • Zod schema defining the input parameters for the type_text tool: selector (CSS selector), text (string to type), delay (optional ms between keystrokes, default 100).
    const TypeTextSchema = z.object({
      selector: z.string(),
      text: z.string(),
      delay: z.number().default(100)
    });
  • src/index.ts:196-218 (registration)
    Registration of the 'type_text' tool in the ListToolsRequestSchema handler response, providing name, description, and JSON schema matching the Zod schema.
    {
      name: 'type_text',
      description: 'Type text into an input field',
      inputSchema: {
        type: 'object',
        properties: {
          selector: {
            type: 'string',
            description: 'CSS selector for the input element'
          },
          text: {
            type: 'string',
            description: 'Text to type'
          },
          delay: {
            type: 'number',
            default: 100,
            description: 'Delay between keystrokes in milliseconds'
          }
        },
        required: ['selector', 'text']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the basic action but lacks critical details: it doesn't mention that this simulates human-like typing with delays (implied by the 'delay' parameter in schema), whether it handles special keys or events, or potential side effects like triggering input validation. For a UI automation tool, this is a significant gap in transparency.

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?

The description is extremely concise—a single, clear sentence that front-loads the core action. There's no wasted verbiage or redundancy, making it efficient for quick understanding while covering the essential purpose.

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?

Given the complexity of UI automation and the absence of annotations and output schema, the description is incomplete. It doesn't address behavioral nuances (e.g., error handling if selector fails), return values, or integration with sibling tools like 'wait_for_element'. For a tool with 3 parameters and no structured safety hints, more context is needed.

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?

The description adds no parameter semantics beyond what the schema provides. Since schema description coverage is 100%, with clear descriptions for 'selector', 'text', and 'delay', the baseline score of 3 is appropriate. The description doesn't explain parameter interactions or provide additional context like selector best practices.

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 'Type text into an input field' clearly states the action (type) and target (input field), making the purpose immediately understandable. However, it doesn't differentiate from potential alternatives like 'paste_text' or 'set_input_value' that might exist in other contexts, though among the provided sibling tools, it's distinct as the only text-input operation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an input field to be present or focused), nor does it compare to sibling tools like 'evaluate_javascript' for more complex input scenarios. Usage is implied by the action but without explicit context.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Wladastic/mcp-browser-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server