Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

type_text

Automate web interactions by typing text into specified input fields using CSS selectors. Customize keystroke delays for precise control over text input.

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 implementation for the 'type_text' tool. Validates input with TypeTextSchema, then uses Playwright's currentPage.fill() to input the text into the specified selector.
    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 (string), text (string), delay (number, default 100ms). Note: delay is not used in the handler.
    const TypeTextSchema = z.object({
      selector: z.string(),
      text: z.string(),
      delay: z.number().default(100)
    });
  • src/index.ts:196-218 (registration)
    Tool registration in the ListTools response, defining name, description, and inputSchema 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Type text' implies a write operation, it doesn't specify whether this requires the element to be visible, focused, or editable, nor does it mention error handling, timing considerations, or what happens if the selector fails. This leaves significant behavioral gaps for a mutation tool.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action, making it easy to parse and understand quickly.

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 tool's complexity (a mutation operation with 3 parameters) and lack of annotations or output schema, the description is insufficient. It doesn't address key contextual aspects like success/failure conditions, interaction with page state, or how it fits within the broader browser automation context, leaving the agent with incomplete information.

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%, with clear parameter descriptions in the schema (e.g., 'CSS selector for the input element', 'Text to type', 'Delay between keystrokes in milliseconds'). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 sibling tools like 'click_element' or 'evaluate_javascript' that might also interact with input fields, so it lacks sibling differentiation.

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), exclusions, or comparisons to other tools like 'evaluate_javascript' for programmatic input, leaving usage context entirely implicit.

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/AutoProbeMCP'

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