Skip to main content
Glama

ui

Inspect and interact with mobile UI via accessibility tree. Search elements by text, label, or resource ID. Perform taps, analyze screens, and assert element visibility. Supports Android, iOS, desktop, and browser platforms.

Instructions

UI inspection and interaction. tree: accessibility tree. find: search elements. find_tap: fuzzy tap (Android). tap_text: tap by text (Desktop). analyze: screen analysis. wait/assert_visible/assert_gone: element checks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
textNoElement text to search/check (partial match, case-insensitive)
labelNoiOS: Find by accessibility label
resourceIdNoAndroid: Find by resource ID (partial match)
classNameNoFind by class name
clickableNoAndroid: Filter by clickable state
visibleNoiOS: Filter by visibility
showAllNoShow all elements including non-interactive (tree only)
compactNoCompact output: only interactive elements, short format (tree only)
formatNoOutput format. semantic = grouped by role, minimal tokens
descriptionNoNatural language description of element to tap (find_tap only)
minConfidenceNoMinimum confidence score 0-100 for find_tap (default: 30)
pidNoProcess ID of target application (tap_text only)
exactMatchNoRequire exact text match for tap_text (default: false)
freshNoForce bypass cache and fetch live UI tree
timeoutNoMax wait time in ms for wait (default: 5000)
intervalNoPoll interval in ms for wait (default: 500)
platformNoTarget platform. If not specified, uses the active target.
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not explain side effects, safety, or what each action returns. Information like caching, mutability, or permissions is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise and front-loaded, but the list format is a bit dense and could be more structured for readability. Still, every word earns its place.

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

Completeness2/5

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

Given the tool has 18 parameters and 8 distinct actions, the description is insufficient. It does not explain outputs, return values, or provide enough context for agents to effectively use the tool.

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 94%, so the schema already documents most parameters. The description does not add additional meaning to parameters beyond the action names.

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 clearly states the tool is for UI inspection and interaction, listing sub-actions with brief explanations. However, some actions like 'tree' and 'analyze' are vague, and the description does not differentiate when to use specific actions beyond platform hints.

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?

No guidance on when to use this tool versus sibling tools (app, device, flow, etc.) or when to choose one action over another. The description lacks context for decision-making.

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/AlexGladkov/claude-in-mobile'

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