Skip to main content
Glama
cloudflare

Cloudflare Playwright MCP

Official
by cloudflare

browser_type

Destructive

Type text into any editable element on a web page using automated browser control. Specify target and text, with options to submit the form or type character by character to trigger key handlers.

Instructions

Type text into editable element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementNoHuman-readable element description used to obtain permission to interact with the element
targetYesExact target element reference from the page snapshot, or a unique element selector
textYesText to type into the element
submitNoWhether to submit entered text (press Enter after)
slowlyNoWhether to type one character at a time. Useful for triggering key handlers in the page. By default entire text is filled in at once.

Implementation Reference

  • The 'browser_type' tool handler function that types text into an editable element. It supports slowly (pressSequentially) and submit (press Enter) options.
    const type = defineTool({
      capability: 'core',
      schema: {
        name: 'browser_type',
        title: 'Type text',
        description: 'Type text into editable element',
        inputSchema: typeSchema,
        type: 'destructive',
      },
    
      handle: async (context, params) => {
        const snapshot = context.currentTabOrDie().snapshotOrDie();
        const locator = snapshot.refLocator(params);
    
        const code: string[] = [];
        const steps: (() => Promise<void>)[] = [];
    
        if (params.slowly) {
          code.push(`// Press "${params.text}" sequentially into "${params.element}"`);
          code.push(`await page.${await generateLocator(locator)}.pressSequentially(${javascript.quote(params.text)});`);
          steps.push(() => locator.pressSequentially(params.text));
        } else {
          code.push(`// Fill "${params.text}" into "${params.element}"`);
          code.push(`await page.${await generateLocator(locator)}.fill(${javascript.quote(params.text)});`);
          steps.push(() => locator.fill(params.text));
        }
    
        if (params.submit) {
          code.push(`// Submit text`);
          code.push(`await page.${await generateLocator(locator)}.press('Enter');`);
          steps.push(() => locator.press('Enter'));
        }
    
        return {
          code,
          action: () => steps.reduce((acc, step) => acc.then(step), Promise.resolve()),
          captureSnapshot: true,
          waitForNetwork: true,
        };
      },
    });
  • Input schema for the 'browser_type' tool, extending elementSchema with text, submit, and slowly fields.
    const typeSchema = elementSchema.extend({
      text: z.string().describe('Text to type into the element'),
      submit: z.coerce.boolean().optional().describe('Whether to submit entered text (press Enter after)'),
      slowly: z.coerce.boolean().optional().describe('Whether to type one character at a time. Useful for triggering key handlers in the page. By default entire text is filled in at once.'),
    });
  • The tool is registered with name 'browser_type' via the defineTool schema name property.
    name: 'browser_type',
Behavior3/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description does not contradict them. However, it adds no behavioral context beyond the annotations, such as confirmation prompts or character limits.

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?

A single sentence that is front-loaded with the verb, conveying the core functionality without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool and the rich parameter descriptions in the schema, the description is nearly complete. It could mention that typing overwrites existing content or that the element must be focused, but overall adequate.

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?

All 5 parameters have schema descriptions, so the description adds no extra meaning. Baseline score of 3 is appropriate.

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

Purpose5/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 the resource ('editable element'), distinguishing it from sibling tools like browser_click or browser_press_key.

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?

No guidance on when to use this tool versus alternatives. No mention of when not to use or prerequisites like element visibility or focus.

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

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