Skip to main content
Glama
munimtechnologies

Computer Use

by munimtechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Press key in browser

browser_press_key
Destructive

Press Enter, Tab, Escape, or Backspace in an agent's browser tab to submit forms, move focus, cancel dialogs, or delete text. Only these four keys are supported; use browser_type for characters.

Instructions

Press Enter, Tab, Escape or Backspace in one of the agent's tabs, for example Enter to submit a form after browser_type. Only these four keys are supported; use browser_type for characters. Enter can submit forms and Backspace deletes, so check the page state with browser_snapshot first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesKey to press
tab_idYestab_id of one of the agent's tabs, from browser_open_tab or browser_list_tabs
session_idNoStable task or thread ID. Pass the same value on every browser call for this task. Different IDs isolate tabs and cleanup within one MCP process. Omit for the default process session.
return_stateNoAfter acting, wait for the page to settle (and finish loading, if the action navigated) and append a fresh browser_snapshot of this tab, so you can pick the next index in the same call. Its indices replace earlier ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.2
    • addedInput schema / properties / return_state
      Added value: +{
+  "description": "After acting, wait for the page to settle (and finish loading, if the action navigated) and append a fresh browser_snapshot of this tab, so you can pick the next index in the same call. Its indices replace earlier ones.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.4.3
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Stable task or thread ID. Pass the same value on every browser call for this task. Different IDs isolate tabs and cleanup within one MCP process. Omit for the default process session.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  3. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / key / description
      Added value: +"Key to press"
    • addedInput schema / properties / tab_id / description
      Added value: +"tab_id of one of the agent's tabs, from browser_open_tab or browser_list_tabs"
  4. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the mutation risk is covered structurally. The description goes beyond that by naming the concrete side effects ('Enter can submit forms and Backspace deletes') and the key limitation, though it says nothing about failure modes or what happens on an invalid tab_id.

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?

Three tight sentences, all earning their place: capability first, then the exclusivity constraint, then the caution and precondition. No filler or repetition of name/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 4-parameter tool with full schema coverage and annotations, the description supplies the essentials: supported keys, side effects, the sibling route for typing, and the snapshot precondition. It does not mention session_id isolation or the return_state snapshot behavior, but the schema covers both, so the gaps are minor.

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 the schema already documents tab_id, session_id, and return_state in detail, and the enum defines the allowed keys. The description only restates the key restriction already encoded in the enum, adding no new per-parameter meaning; baseline 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?

States a specific verb and resource ('Press Enter, Tab, Escape or Backspace in one of the agent's tabs') and enumerates the exact supported key set. It explicitly distinguishes itself from browser_type, so an agent can pick the right sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives when-to-use with a concrete example ('Enter to submit a form after browser_type'), names the alternative and its exclusion condition ('use browser_type for characters'), and prescribes a precondition ('check the page state with browser_snapshot first').

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