Skip to main content
Glama

press_key

Press a keyboard key using native browser events to trigger real form submission, shortcuts, and IME behavior. Optionally focus a specific element first.

Instructions

Press a keyboard key via CDP Input.dispatchKeyEvent.

    Uses real browser key events, not synthetic JS dispatch - so native
    form-submit semantics, browser shortcuts, and IME all behave as
    they would with a human keyboard. When ``selector`` is given we
    focus that element first.

    Recognised names: ``Enter``, ``Tab``, ``Escape``, ``Backspace``,
    ``Delete``, ``ArrowUp/Down/Left/Right``, ``Space``, ``Home``, ``End``,
    ``PageUp``, ``PageDown``. Any single character (e.g. ``"a"``) is also
    accepted.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
selectorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, description carries full burden. Discloses use of real browser events, native semantics, and focusing behavior. Does not mention return values, but output schema exists.

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?

Front-loaded with the main action, includes essential details without fluff. Every sentence adds value.

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?

Covers tool purpose, behavior, and parameters well. Does not discuss edge cases or prerequisites, but overall sufficient given output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds meaning: lists recognized key names, explains that selector focuses element. Both parameters are addressed.

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?

Clearly states it presses a keyboard key via CDP, distinguishes from mouse-related tools. Lists recognized key names, making the scope precise.

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

Usage Guidelines3/5

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

Implies usage for discrete key presses (not typing text) but does not explicitly differentiate from sibling tools like press_enter or type_text.

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/bituq/zendriver-mcp'

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