Skip to main content
Glama

browser_select_text

Selects one occurrence of text in an editable element, using prefix and suffix to disambiguate when the same text appears multiple times.

Instructions

Select one occurrence in an editable element. Use prefix/suffix to disambiguate.

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>",
      "text": "<text>"
    },
    "name": "browser_select_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot in this document.
textYes
tabIdYesTab id from browser_tabs.
prefixNo
suffixNo
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.
selectionTypeNotext

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 for a state-changing operation on a live page. It discloses the one-occurrence constraint, but says nothing about whether the element must already be focused, what error occurs if the text is absent or appears multiple times, whether the action mutates the document, or how revision/documentId mismatches are surfaced beyond what the schema already states.

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?

Two short sentences with no filler, and the core action is front-loaded before the disambiguation tip. The brevity is efficient, though it borders on under-specification for an 11-parameter tool.

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

Completeness3/5

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

For a tool with 11 parameters, an enum parameter, no annotations, and no output schema, the description is thin: it omits focus requirements, failure semantics, and how this relates to browser_select. The schema does cover the refusals (revision, documentId) and selector constraints, so the gap is partially offset, but not the behavioral gap.

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 64%, so several parameters (text, prefix, suffix, selectionType) have no schema-level explanation. The description partially compensates by explaining that prefix/suffix exist to disambiguate among multiple occurrences, which is genuine added meaning, but it says nothing about selectionType's cursor modes or the ref-vs-selector choice.

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 target: 'Select one occurrence in an editable element,' which is more precise than the bare tool name and scopes the action to editable content. It does not, however, distinguish this from the sibling browser_select (which presumably selects elements rather than text ranges), leaving that differentiation to inference.

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?

The only guidance offered is 'Use prefix/suffix to disambiguate,' which is a parameter hint rather than a when-to-use rule. There is no statement of when to choose browser_select_text over browser_select, no prerequisites such as the element needing focus, and no mention of failure conditions.

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