Skip to main content
Glama
Novpix

browsermcp-plus

by Novpix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_press_key

Destructive

Press any keyboard key or shortcut in a Chrome browser to trigger actions like submitting forms, navigating menus, or scrolling. Optionally return the updated page snapshot.

Instructions

Press a key or shortcut, e.g. Enter, Escape, Tab, ArrowDown, PageDown (scrolls), Control+a or a single character

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesName of the key to press or a character to generate, such as `ArrowLeft` or `a`
snapshotNoAlso return the page snapshot after the action (default: no). Use it when you need to see the result right away.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / snapshot
      Added value: +{
+  "description": "Also return the page snapshot after the action (default: no). Use it when you need to see the result right away.",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows key presses can have side effects. The description adds a small behavioral detail ('PageDown scrolls') but omits that keys like Enter can submit forms or trigger navigation, which is the most relevant risk for a destructive-flagged 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?

A single front-loaded sentence with the verb first and useful examples trailing; nothing is wasted and nothing needs to be skimmed past.

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 two-parameter tool with no output schema and annotations covering the safety profile, the description is nearly sufficient. It could be fuller by mentioning focus/prerequisite state and the optional snapshot behavior, but it is adequate for correct invocation.

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 100%, so both parameters are already documented and the baseline is 3. The description supplements the schema with extra examples ('Control+a', single character) but adds no syntax or format rules beyond that.

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?

States a specific verb ('Press') and resource ('a key or shortcut') and lists concrete key examples including modifier combos. It clearly separates itself from browser_type/browser_click by being a discrete keystroke action, though it never names those siblings explicitly.

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 only implied through examples (keyboard shortcuts, PageDown scrolling). There is no statement of when to prefer this over browser_type, browser_scroll, or browser_click, and no note about required focus or a prior snapshot.

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