Skip to main content
Glama
Sign In
playwright-mcp-server

playwright-mcp-server

by doucej
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

press

Focus a webpage element and send keyboard keys like Enter, Tab, or Escape to automate browser interactions.

Instructions

Focus an element and press a keyboard key (e.g. Enter, Tab, Escape, ArrowDown).

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

Input Schema

NameRequiredDescriptionDefault
keyYesKey name, e.g. Enter, Tab, Escape, ArrowDown.
selectorYesCSS or XPath selector of the element to focus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/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 explaining behavior. It states the tool focuses and presses a key, but does not disclose details like whether keydown/keyup events are sent, how invalid keys are handled, or side effects if the element isn't found. This is basic transparency but adequate for a simple action.

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 concise sentence that immediately states the operation and gives examples. Every word earns its place, with no filler.

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 tool's simplicity, no output schema, and no annotations, the description plus the well-documented schema is sufficient for an agent to understand and invoke the tool. It could benefit from noting whether modifications or keyboard events are simulated, but it is complete enough for the task.

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 100%: both parameters (key and selector) have descriptions in the schema. The tool description adds no additional parameter semantics beyond the examples, so the baseline of 3 applies.

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: focus an element and press a keyboard key. It includes concrete examples (Enter, Tab, Escape, ArrowDown) and distinguishes itself from siblings like type, click, and fill.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for keyboard interactions and gives examples of relevant keys. However, it does not explicitly mention when not to use it or name alternatives like type for text entry, so it slightly lacks exclusion guidance.

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

Deploy Server

Other Tools