Skip to main content
Glama
b3nw
by b3nw

Type Text

browser_type

Enter text into web page input fields using CSS selectors for automated form filling and data entry in browser automation.

Instructions

Type text into an input field specified by selector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes
textYes

Implementation Reference

  • Executes the browser_type tool by validating input, connecting to Playwright if needed, and using page.fill() to type text into the specified selector.
    async (params: any) => {
      try {
        const input = z.object({
          selector: z.string(),
          text: z.string()
        }).parse(params);
        await this.playwright.ensureConnected();
        
        const page = this.playwright.getPage();
        await page.fill(input.selector, input.text);
        
        return {
          content: [{
            type: 'text',
            text: `Successfully typed text into element: ${input.selector}`
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Type text failed: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • src/server.ts:194-230 (registration)
    Registers the 'browser_type' tool with the MCP server, including title, description, input schema, and handler reference.
      'browser_type',
      {
        title: 'Type Text',
        description: 'Type text into an input field specified by selector',
        inputSchema: {
          selector: z.string(),
          text: z.string()
        }
      },
      async (params: any) => {
        try {
          const input = z.object({
            selector: z.string(),
            text: z.string()
          }).parse(params);
          await this.playwright.ensureConnected();
          
          const page = this.playwright.getPage();
          await page.fill(input.selector, input.text);
          
          return {
            content: [{
              type: 'text',
              text: `Successfully typed text into element: ${input.selector}`
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `Type text failed: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Zod schema defining the input structure for the browser_type tool: selector (string) and text (string). Also has corresponding TypeScript type at line 63.
    export const BrowserTypeInputSchema = z.object({
      selector: z.string(),
      text: z.string()
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states what the tool does but doesn't disclose important traits like whether it waits for the selector to exist, handles special keys, validates input, or what happens on failure. This leaves significant 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 appropriately sized and front-loaded, with every word earning its place.

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 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error conditions, return values, or integration with sibling tools, leaving the agent with insufficient context for reliable use.

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 0%, so the schema provides no parameter details. The description adds some meaning by explaining that 'selector' specifies an input field and 'text' is what to type, but it doesn't clarify selector syntax (e.g., CSS, XPath) or text handling (e.g., encoding, line breaks). This partial compensation justifies a baseline score.

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 clearly states the action ('Type text') and target ('into an input field specified by selector'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like browser_click or browser_evaluate, which might also interact with page elements.

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., whether the browser must be navigated to a page first), exclusions, or comparisons to siblings like browser_click for different interactions.

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

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/b3nw/playwright-mcp-server'

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