edge-mcp

Overview Schema Source Related Servers Discussions Admin

press

Sends a key such as Enter, Tab, or Escape to the focused element in the active Edge tab, enabling keyboard interaction during browser automation.

Instructions

Press a key on the active tab (sent to the currently focused element). Accepts KeyDescriptor names like Enter, Tab, Escape, ArrowDown, or single characters like 'a'.

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

Input Schema

Name	Required	Description	Default
`key`	Yes	Key name, e.g. Enter, Tab, Escape, ArrowDown, Backspace, or a single character like 'a'
`hold`	No	Hold duration in ms (0 = tap)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: the key event goes to the focused element of the active tab, which implies a focus prerequisite. It omits other relevant behavior such as whether holding is supported and what (if anything) is returned, leaving the profile partial.

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?

Two short sentences, front-loaded with the action and target, with the key-format note following. No filler or redundant restatement of the title.

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?

For a simple 2-parameter tool with full schema coverage and no output schema, the description covers the action, destination, and accepted key forms. Only the hold-duration behavior and focus precondition are left implicit, which the schema largely absorbs.

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%, so baseline is 3. The description's key-name examples duplicate the schema's own key description and add nothing about the 'hold' parameter or the format of accepted single characters beyond what is already documented.

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 states a specific verb and resource ('Press a key on the active tab') plus the precise delivery target ('sent to the currently focused element'). It does not name a distinguishing sibling such as type or fill, but the keyboard-key framing is specific enough to separate it from text-entry tools.

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?

Usage is implied by the examples (Enter, Tab, Escape, ArrowDown indicate navigation/form submission) but there is no explicit when-to-use versus type/fill guidance and no stated prerequisite that an element must already have focus.

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

Deploy Server