Skip to main content
Glama
XC-MCP: XCode CLI wrapper

XC-MCP: XCode CLI wrapper

by conorluddy

Send Text/Key Input

idb-ui-input

Sends text and keyboard commands to focused iOS fields to automate form filling, login flows, searches, and multi-field navigation while redacting sensitive input.

Instructions

idb-ui-input

Hardware key aliases: home, lock/power, side, siri, apple-pay, volume-up/down (volume requires idb 1.6.3+).

⌨️ Input text and keyboard commands - automated text entry and special key presses for form automation

What it does

Sends text input and keyboard commands to focused elements on iOS targets. Types text strings into active text fields, presses special keys (home, return, delete, arrows), and executes key sequences for complex input workflows. Automatically redacts sensitive data (passwords) in responses and provides semantic field context tracking for test documentation.

Why you'd use it

  • Automate form filling without manual keyboard interaction - login flows, search, data entry

  • Execute keyboard shortcuts and navigation (tab, return, arrows) for multi-field workflows

  • Safely handle sensitive data with automatic redaction in tool responses and logs

  • Track input operations with semantic metadata (actionName, fieldContext, expectedOutcome)

Additional input operations

  • operation: clear selects all (Command+A) and deletes.

  • modifiers: shift, control, option, command apply to key/key-sequence events.

  • key and keySequence accept letters, digits and named keys; sequences send individual HID events.

Parameters

Required

  • operation (string): "text" | "key" | "key-sequence"

Operation-specific parameters

  • text (string, required for text operation): String to type into focused field

  • key (string, required for key operation): Special key name (home, return, delete, tab, arrows, etc.)

  • keySequence (string[], required for key-sequence operation): Array of key names to press in order

Optional

  • udid (string): Target identifier - auto-detects if omitted

  • actionName (string): Semantic action name (e.g., "Enter Email")

  • fieldContext (string): Field name for context (e.g., "Email TextField")

  • expectedOutcome (string): Expected result (e.g., "Email field populated")

  • isSensitive (boolean): Mark as sensitive to redact from output

Returns

Input execution status with operation details (redacted if sensitive), duration, input context metadata for test tracking, error details if failed, and troubleshooting guidance specific to text vs. key operations.

Examples

Type email into focused field

const result = await idbUiInputTool({
  operation: 'text',
  text: 'user@example.com',
  actionName: 'Enter Email',
  fieldContext: 'Email TextField'
});

Press return to submit

await idbUiInputTool({ operation: 'key', key: 'return' });
  • idb-ui-tap: Tap to focus text fields before typing

  • idb-ui-describe: Find text field coordinates

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": {
      "operation": "<operation>"
    },
    "name": "idb-ui-input"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
textNo
udidNo
modifiersNo
operationYes
actionNameNo
isSensitiveNo
keySequenceNo
fieldContextNo
expectedOutcomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.0.0
    • removedInput schema / properties / key / enum
      Removed value: -[
      -  "home",
      -  "lock",
      -  "siri",
      -  "delete",
      -  "return",
      -  "space",
      -  "escape",
      -  "tab",
      -  "up",
      -  "down",
      -  "left",
      -  "right"
      -]
    • addedInput schema / properties / modifiers
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "shift",
      +      "control",
      +      "option",
      +      "command"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "text",
      -  "key",
      -  "key-sequence"
      -]New value: +[
      +  "text",
      +  "key",
      +  "key-sequence",
      +  "clear"
      +]
  2. Addedv1.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-idempotent, non-destructive local mutation, so the bar is partly met structurally. The description adds real value beyond that: automatic redaction of sensitive values in responses and logs, semantic tracking metadata, that sequences emit individual HID events, that clear performs Command+A then delete, and an idb version prerequisite for volume keys. It stops short of stating what state is left behind on partial failure.

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?

Markdown headings make it scannable and the critical operation/parameter material is front-loaded, but there is redundancy: the emoji tagline restates the 'What it does' paragraph, and the 'Why you'd use it' bullets re-describe capabilities already listed. Two worked examples earn their place.

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?

For a ten-parameter mutation tool with no output schema, the description covers purpose, per-mode parameter rules, return contents (status, duration, redaction, error/troubleshooting info), examples, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 0%, so the description carries the full burden and does: all ten parameters are explained, including operation-specific requirements, the accepted modifier set, key-name aliases, and the meaning of the tracking fields (actionName, fieldContext, expectedOutcome, isSensitive). The only blemish is that the 'Required' enumeration lists text|key|key-sequence while 'clear' is documented separately.

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 names a specific verb and resource ('Sends text input and keyboard commands to focused elements on iOS targets') and enumerates the three input modes plus the clear operation. It also distinguishes itself from neighbors by routing focus/find work to idb-ui-tap and idb-ui-describe.

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?

A dedicated 'Why you'd use it' section spells out concrete scenarios (form filling, login flows, keyboard navigation, sensitive-data entry), and 'Related Tools' explicitly states the prerequisite chain: tap to focus a field, describe to find coordinates, then input. This is when-to-use plus alternatives, not just context.

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