Skip to main content
Glama
clivejefferies

mobile-debug-mcp

type_text

Type text into the currently focused Android input field. Optionally specify device ID and platform for targeted input.

Instructions

Purpose: Type text into the currently focused Android input field.

Inputs:

  • text

  • platform/deviceId (optional)

Output Structure:

  • action_id, timestamp (ISO 8601), action_type

  • lifecycle_state: post-dispatch lifecycle state (pending_verification or failed)

  • source_module: runtime source of the action envelope

  • target.selector = { text }

  • success = true when text input was dispatched

  • failure_code/retryable when dispatch fails

  • ui_fingerprint_before/ui_fingerprint_after when available

Recommended Usage:

  1. Resolve or focus the target input first

  2. Call type_text

  3. If needed, wait for UI stabilization using wait_for_*

  4. Verify with expect_element_visible or expect_screen, depending on the intended outcome

Verification Guidance:

  • Prefer verifying the next expected element or screen state instead of inferring success from the text action alone

  • Follow RESOLVE → ACT → WAIT (if needed) → EXPECT

  • Do not use wait_for_* alone as final verification when an applicable expect_* tool exists

Failure Handling:

  • TIMEOUT → retry once

  • UNKNOWN → re-focus the input or capture a snapshot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to type
deviceIdNoDevice Serial/UDID. Defaults to connected/booted device.
platformNoPlatform to type on (currently only android supported)
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses typing into focused input, optional deviceId/platform, output structure including success, failure, lifecycle states, and ui fingerprints. No contradictions.

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?

Well-structured with clear sections (Purpose, Inputs, Output Structure, Recommended Usage, etc.). Every sentence adds value, no fluff.

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?

Comprehensive for a tool with no annotations and moderate complexity. Includes output structure, failure handling, and verification steps, fully covering agent needs.

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 100%, but description adds behavioral context (e.g., 'currently focused input', default device connection) beyond the schema descriptions.

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 'Type text into the currently focused Android input field.' This is a specific verb and resource, and it distinguishes from sibling tools like tap, swipe, and press_back.

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

Usage Guidelines5/5

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

Provides explicit step-by-step usage flow (RESOLVE → ACT → WAIT → EXPECT), verification guidance, and failure handling. Helps the agent decide when and how to use the tool.

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/clivejefferies/mobile-debug-tools'

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