Skip to main content
Glama

tab_find

Search the current browser page for text, buttons, and controls, returning matching outline lines with control refs so you can locate and interact with elements without reading the entire page.

Instructions

Find controls and text on a page in the user's browser without reading all of it: returns the lines of the whole page's outline that contain the text, controls with their refs, for example [80] button "Create" for "create". A matching heading comes with the start of the section it titles, indented, so searching for a row or section title gives its controls. Cheaper than tab_read on long pages when you know what you are looking for.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to look for, case-insensitive: part of a label, a button name, a heading.
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that results are outline lines matching the text, that controls come with refs, the exact ref formatting with an example, and that a matching heading is returned with an indented start of its section. It omits what happens when nothing matches, ordering, and truncation/cost limits.

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?

Three sentences, front-loaded with the verb and scope, then return shape, then the comparison to tab_read. Nothing is filler, though the middle sentence is long and packs the example and heading-indentation rules together rather than separating them.

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?

No output schema exists, so the description must explain return values, and it does so with structure and a literal example. For a two-parameter read tool with no annotations, the main remaining gap is failure/empty-result behavior and whether results are capped.

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 both parameters are already fully documented, establishing a baseline of 3. The description reinforces matching behavior ('contain the text', 'for "create"') and that a heading match pulls in section content, but adds no new syntax or defaults beyond the schema's case-insensitive and tabId fallback notes.

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?

States a specific verb and resource ('Find controls and text on a page in the user's browser') plus the distinguishing scope ('without reading all of it'), which separates it from tab_read. The example output token `[80] button "Create"` makes the result shape concrete enough to tell apart from a full-page read.

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?

Explicitly positions the tool against the sibling tab_read: 'Cheaper than tab_read on long pages when you know what you are looking for.' That gives both the alternative and the selecting condition. It stops short of saying when not to use it (e.g. unknown text, needing surrounding structure) or naming other siblings.

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