Skip to main content
Glama

find

Searches interactive page elements by query and returns refs usable with click, type, and select, avoiding a full page read.

Instructions

List only the interactive elements whose read_page line contains query, ignoring case.

Cheaper than read_page on a long page when you need one control, e.g. find("save") or
find("email"). Its refs work with click, type and select, and replace earlier refs like read_page's.

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": {
      "query": "<query>"
    },
    "name": "find"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
tab_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses that returned refs are usable with click/type/select and that they supersede refs from an earlier read_page, which is the key stateful side effect an agent must know. It omits no-match behavior and whether the result includes surrounding context.

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?

Two sentences, front-loaded with the what, then the cost/routing rationale, then ref semantics. No filler; the examples do real work in showing expected query granularity.

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?

For a simple two-parameter lookup tool with no output schema, this covers purpose, relative cost, and ref lifecycle, which is what an agent needs to call it correctly. The remaining gap is the undocumented tab_id and the absence of any statement about what an empty result looks like.

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 0%, so the description must compensate. It explains query semantics well (case-insensitive substring match against the element's read_page line) and gives examples, but tab_id is never mentioned, leaving half the parameters undocumented anywhere.

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?

Specific verb and resource: 'List only the interactive elements whose read_page line contains query, ignoring case.' It explicitly scopes what is returned and ties it to the read_page line model, which cleanly separates it from read_page itself and from get_text.

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?

Names the alternative (read_page) and the condition that favors this tool: 'Cheaper than read_page on a long page when you need one control,' reinforced with two concrete query examples. It stops short of an explicit 'use read_page when you need many elements' exclusion, but the implied split is clear.

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