Skip to main content
Glama

find

Search for UI elements by their visible name, like button labels or link text, and get element IDs to interact with them in desktop applications.

Instructions

Search for UI elements by name — buttons, links, labels, fields.

Matches against element names (button labels, link text, field
labels), NOT body text or prose content inside articles or
documents.

Returns element IDs that you can use with click, set_value, etc.
Use the FULL visible text for best results (e.g. "Send Message"
not just "Send").

Args:
    query: Text to search for (e.g. "Send Message", "Submit", "Search").
    app: Scope to this application (e.g. "Firefox", "Slack").
    window_id: Scope to this window.
    role: Only match this role (e.g. "button", "text_field", "link").
    states: Only match elements with ALL these states (e.g. ["enabled", "visible"]).
    max_results: Maximum matches to return.
    fields: Which fields to search -- ["name"], ["name", "value"], or ["name", "value", "description"].
    source: "full" (default, merged native+web), "cdp_ax" (CDP accessibility tree only), "native" (platform only), or "dom" (live DOM). "ax" remains as a compatibility alias for "cdp_ax".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
appNo
window_idNo
roleNo
statesNo
max_resultsNo
fieldsNo
sourceNofull

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description discloses matching behavior (by name, not body text), return type (element IDs), and source options including compatibility alias. No destructive side effects mentioned, appropriate for a read search 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?

Highly efficient: two sentences for purpose/constraints, then a usage tip, then a complete parameter list. Every sentence adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema description, the description thoroughly covers input parameters and outcome (returns element IDs for interaction). Source and fields options are detailed, making it self-contained for an 8-parameter tool.

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

Parameters5/5

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

Schema has 0% description coverage, but description's docstring explains all 8 parameters with clear semantics and examples (e.g., query: 'Send Message'). Fully compensates for schema lack.

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?

Clearly states it searches UI elements by name (buttons, links, labels, etc.) and explicitly excludes body text or prose. Distinguishes purpose from other tools by specifying return of element IDs for interaction.

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?

Provides when to use (search by name) and a tip for best results (use full visible text). Could explicitly contrast with alternatives (e.g., read_text for content), but context from sibling tools implies usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Touchpoint-Labs/Touchpoint'

If you have feedback or need assistance with the MCP directory API, please join our Discord server