Skip to main content
Glama

browser_select_text

browser_select_text
Idempotent

Select text or place the cursor before or after text in an editable element, enabling precise focus and input positioning during browser automation.

Instructions

Select text or place the cursor before or after text in an editable element.

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": {
      "tab_id": "<tab_id>",
      "element_id": "<element_id>"
    },
    "name": "browser_select_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
tab_idYes
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
element_idYesOpaque element_id returned by browser_get_interactives.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.
selection_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the behavior that it can either select text or place a cursor before/after text, but omits focus requirements, what happens if the text is not found, and whether existing selections are replaced.

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 wasted wording. It is efficient, though its brevity reflects under-specification rather than a deliberate, complete summary.

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?

With seven parameters, only 57% schema description coverage, and no output schema, the description is too thin for the tool's complexity. It does not explain how the required element_id/tab_id relate to the selection, nor how session_id and frame_id affect execution.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 57%, so the description should compensate for undocumented parameters. It implicitly maps to the selection_type enum ('select text' vs 'before or after') but never explains the text parameter, the selection_type field by name, or the session/frame parameters, leaving meaningful gaps.

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?

The description names a specific verb and resource: 'Select text or place the cursor before or after text in an editable element.' It clearly distinguishes the two modes of operation, though it does not explicitly differentiate itself from siblings such as browser_select_option or browser_type.

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

Usage Guidelines2/5

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

It states the target context ('in an editable element') but gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is for text selection rather than option selection or typing, with no explicit routing rule.

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