Skip to main content
Glama

find

Locates page elements by matching visible text, labels, placeholders, roles, or CSS selectors in a specified tab, returning refs for interaction.

Instructions

Find elements whose text, label, placeholder, role or CSS selector matches a query. Returns refs. Plain text match, not natural language: use words that appear on the element ("Sign in", "search"), or a CSS selector.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
tabIdYesTab ID, from tabs_list or tab_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does disclose the key behaviors: matching is literal text rather than natural language, and the call returns refs. It omits scope details such as whether the search covers only the given tab, iframes/shadow DOM, case sensitivity, or result limits, which matters for a lookup tool.

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?

Three short sentences, front-loaded with what is matched, then the return value, then the crucial constraint about literal matching. Nothing is redundant and the negative example ('Sign in', 'search') earns its place.

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 two-parameter lookup with no output schema, the description covers the match semantics and states that refs are returned. It could say slightly more about how those refs are consumed by click/type, but nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

Schema coverage is 50% because the required `query` parameter has no schema description; the description compensates by explaining exactly what query accepts (visible words, or a CSS selector) and what it will not accept (natural language). `tabId` is already documented in the schema as coming from tabs_list or tab_create.

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 states a specific verb (find) and resource (elements) and enumerates the match dimensions: text, label, placeholder, role, CSS selector. It does not name a sibling tool to differentiate from (e.g. read_page or get_page_text), so it stops short of a 5.

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

Usage Guidelines3/5

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

It gives query-construction guidance — plain text match, not natural language, use visible words or a CSS selector — which implies 'use this to locate an element before acting on it.' However, it never states when to prefer this over read_page/get_page_text or what to do if nothing matches, so usage is only implied.

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