Skip to main content
Glama

browser_secondary

Invoke listed element snapshot actions (Expand, Collapse, Increment, Decrement) to operate UI controls during Chrome or Firefox browser automation.

Instructions

Invoke an action listed in the element's snapshot actions field.

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": {
      "tabId": "<tabId>",
      "action": "<action>"
    },
    "name": "browser_secondary"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot in this document.
tabIdYesTab id from browser_tabs.
actionYes
expectNoPost-action condition. Default timeout is 1.2 seconds in visible pages and 3 seconds in hidden pages. A mismatch does not undo the action; inspect before retrying.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
revisionNoReject if the DOM revision differs from the snapshot.
selectorNoCSS selector. Must identify exactly one element.
documentIdNoReject the action if this snapshot document has changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only says an action is invoked. It does not disclose whether actions mutate page state, whether they require a valid snapshot revision, what happens on failure, or how the post-action expect condition behaves.

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 definition is a single front-loaded sentence with no filler. Its brevity is efficient, though the phrase 'listed in the element's snapshot actions field' is slightly awkward and leaves important context unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 9-parameter tool with a nested expect object and no output schema or annotations, so the description should do more than identify the invocation target. It omits the connection to browser_snapshot, action semantics, failure behavior, and when this tool is preferred over similar interaction tools.

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 89%, so the input schema already documents nearly all parameters in detail. The description adds no parameter-level meaning beyond loosely pointing to the element's snapshot actions field, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb (Invoke) and a resource (an action listed in the element's snapshot actions field), so the general operation is identifiable. However, it does not explain what a 'secondary' action is, what kinds of actions are covered, or how this differs from siblings such as browser_click, browser_press, or browser_select.

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?

There is an implied precondition: the action must be listed in the element's snapshot actions field. But the description does not say when to use this tool instead of browser_click, browser_press, or other interaction tools, nor does it include exclusions or prerequisites such as requiring a fresh snapshot.

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