Skip to main content
Glama
Sign In
zen-browser

zen-browser

by grapedjuice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

find

Locate page elements by role, accessible name, or text using a case-insensitive query, returning up to 20 references for browser automation.

Instructions

Find elements whose role, accessible name or text contains the query (case-insensitive). Returns up to 20 refs.

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
tabIdNoTab to act on. Defaults to the active tab of the focused Zen window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior: case-insensitive substring matching over role/name/text, and a hard cap of 20 results. It omits whether the search is read-only (it is implicitly), what happens on zero matches, whether refs remain valid across page changes, and pagination beyond the cap.

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 short sentences, no filler. The matching semantics are front-loaded and the result cap follows immediately; every clause carries information an agent needs.

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 read-only search tool with no output schema, the description is adequate but thin. It explains what comes back (refs) but not how those refs connect to sibling tools (form_input, computer), what a ref looks like, or how to handle the 20-result truncation — gaps that matter for a tool whose whole purpose is feeding other calls.

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%: tabId is documented in the schema, but query has no schema description. The description compensates precisely by defining what query matches against (role, accessible name, text) and that matching is case-insensitive, which is the key semantic the schema omits.

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?

States a specific verb and resource: 'Find elements whose role, accessible name or text contains the query', and adds the matching rule (case-insensitive) plus the result cap (20 refs). This clearly separates it from text-dump siblings like get_page_text or read_page, though it never names those siblings explicitly.

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 description offers no when-to-use guidance and no exclusions. It never says to prefer this over get_page_text or read_page when locating an element to interact with, nor what to do when the 20-ref cap is hit (refine the query vs. screenshot). Usage is only inferable from the return value.

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

Deploy Server

Other Tools