Skip to main content
Glama

Act on the current page

browser_act
Destructive

Use for: interacting with the page — click, fill, type, select, submit, press. Returns the resulting page title, URL and text so you can verify the action landed. Don't use when: the target element is not on the current page — navigate or snapshot first. This tool can change remote state (it can submit forms). Paid: $0.01 per call via x402 (Base USDC, Solana USDC, or XRPL XRP).

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": {
      "session_id": "<session_id>",
      "action": "<action>",
      "selector": "<selector>"
    },
    "name": "browser_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNoValue for fill/type/select, or key name for press (default Enter).
actionYesThe interaction to perform on the target element.
selectorYesCSS selector of the target element.
session_idYesSession ID. Reuse the same ID to keep cookies, login state and page position across calls; a new ID starts a fresh browser.

Output Schema

NameRequiredDescriptionDefault
urlYes
textYes
titleYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the call returns page title/URL/text for verification, warns the action can mutate remote state (form submission), and — critically — surfaces a per-call price and payment rails, which no structured field conveys. This is consistent with destructiveHint=true and openWorldHint=true.

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?

Front-loaded with labeled "Use for" / "Don't use when" segments, then verification behavior, then cost. Each of the four sentences carries distinct, load-bearing information with no restatement of the schema.

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

Completeness5/5

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

Return values are covered by an output schema and safety/mutability by annotations, so the remaining burden is routing, cost, and post-action verification — all present. For a 6-action browser mutation tool this is sufficient to call correctly.

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% and every parameter (including the action enum and the value default of Enter) is already documented in the schema, so the baseline of 3 applies. The description adds nothing new about parameter formats or selector semantics beyond listing the action verbs.

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?

"Use for: interacting with the page — click, fill, type, select, submit, press" enumerates the exact verb set and the resource, and the negative clause ("target element is not on the current page") cleanly separates it from browser_navigate and browser_snapshot. An agent can pick this over its five siblings without opening a 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?

Explicit when-to-use and when-not-to-use, and it names the correct alternatives (navigate or snapshot first) with the condition that triggers them. Nothing about routing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources