gecko-mcp

Overview Schema Source Related Servers Discussions Admin

find

Read-only

Locate page elements by visible text or HTML tag and return ready-to-use CSS selectors. Use this instead of reading the entire page to find buttons, links, or fields.

Instructions

Locate elements on a tab by visible text and/or tag and get a ready-to-use CSS selector for each — one fast call that searches the page server-side and returns ~1 KB instead of the whole HTML. Use this INSTEAD of read_page to find a button, link, or field, then pass the returned selector straight to click/type/etc. Provide text, tag, or both. Active tab unless browserId given.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find"
  }
}

Input Schema

Name	Required	Description
`text`	No	Visible text to match (substring, case-insensitive).
`tag`	No	Restrict to a tag, e.g. "button", "a", "input", "select".
`limit`	No	Max matches to return. Default 25.
`browserId`	No	Target tab (from list_tabs). Defaults to active.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.4Jun 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds value beyond annotations by disclosing server-side search and a typical response size of ~1 KB. It also clarifies active tab behavior. Annotations already indicate readOnlyHint=true, which aligns.

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?

The description is four sentences, each carrying distinct information: purpose, efficiency benefit, usage guidance, and parameter instruction. No fluff or redundancy.

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?

Despite no output schema, the description explains what is returned (CSS selectors) and the efficiency gain. It covers key use cases and integration with sibling tools. Lacks details on error handling or return format, but sufficient for most scenarios.

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?

With 100% schema coverage, the description still adds context: it recommends providing at least one of text or tag, and specifies that browserId defaults to the active tab. This supplements the schema's optional declarations.

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?

The description clearly states the tool's purpose: locating elements by visible text and/or tag and returning CSS selectors. It explicitly distinguishes itself from read_page, a sibling tool, by positioning find as a lighter alternative.

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?

The description gives explicit guidance to use this tool instead of read_page for finding elements and to pass the returned selectors to click/type etc. It also mentions providing text, tag, or both. However, it does not contrast with other siblings like get_attribute or wait_for_element.

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