Skip to main content
Glama

browser_computer

Control a browser tab with mouse, keyboard, and screenshots via DevTools Protocol. Perform clicks, typing, scrolling, and capture viewport images.

Instructions

Mouse, keyboard, and screenshots in a browser tab via the DevTools protocol; the tab does not need to be active (first use shows Chrome's "started debugging" info bar — that is expected). Actions: screenshot (viewport image in CSS pixels — its coordinates map 1:1 to click coordinates), zoom (magnified region [x0,y0,x1,y1]), left_click, right_click, double_click, triple_click, hover, left_click_drag (start_coordinate→coordinate), type (insert text at the current focus), key (space-separated combos, e.g. "cmd+a Backspace"), scroll (scroll_direction+scroll_amount), scroll_to (ref), wait (duration, max 10 s). Clicks, typing, and key presses are real input events and mutate page state; screenshot/zoom/hover/wait are read-only. Positions come from coordinate:[x,y] or from a ref returned by browser_read_page/browser_find — refs are more reliable than eyeballed coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoelement ref from browser_read_page/browser_find — alternative to coordinate
textNotext for type, or key combos for key
tabIdYestab id from browser_tabs_list or browser_tab_create
actionYeswhat to do; see the tool description for each action's required parameters
regionNo[x0, y0, x1, y1] for zoom
repeatNorepeat count for key
durationNoseconds for wait (max 10)
modifiersNoclick modifiers: cmd, ctrl, alt, shift (joined with +)
coordinateNo[x, y] in pixels
scroll_amountNowheel ticks, default 3
scroll_directionNofor scroll; default down
start_coordinateNodrag start for left_click_drag
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it explains that clicks/keypresses mutate state while screenshot/zoom/hover/wait are read-only, notes that the tab need not be active, and mentions the Chrome info bar. This is comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: it starts with the overall purpose, lists actions with brief explanations, and notes constraints. It is fairly long but every sentence adds value; could be slightly more concise without losing information.

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?

The description covers usage and behavior thoroughly, but since there is no output schema, it does not specify return formats (e.g., screenshot output type). For a complex tool with many actions, it is mostly complete.

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 the schema already documents all 12 parameters. The description adds context (e.g., coordinate mapping, ref alternatives) but does not substantially alter or extend the meaning of individual parameters beyond what the schema provides.

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 tool is for mouse, keyboard, and screenshots via DevTools protocol. It lists all actions and differentiates from siblings like browser_read_page (reading content) and browser_form_input (filling forms).

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 provides clear context on when to use the tool (for browser interactions) and which actions are safe vs. destructive. It hints at alternatives (e.g., 'refs are more reliable than eyeballed coordinates') but does not explicitly list cases when not to use it or how to choose between siblings.

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/dashi96/chromium-bridge'

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