Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

Send Text/Key Input

idb-ui-input

Automate iOS form filling and navigation by sending text, pressing special keys, or executing key sequences to focused elements, with sensitive data redaction for safe test automation.

Instructions

idb-ui-input

⌨️ 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)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
textNo
udidNo
operationYes
actionNameNo
isSensitiveNo
keySequenceNo
fieldContextNo
expectedOutcomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no helpful annotations (all hints false), the description carries the full burden. It discloses that it sends input, redacts sensitive data, tracks semantic context, and returns error details with troubleshooting. It does not contradict annotations and adds meaningful behavioral context, though some specifics about UI side effects are omitted.

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 long but well-structured with clear sections (What it does, Why you'd use it, Parameters, Returns, Examples, Related Tools). It is front-loaded with the core purpose and uses examples to illustrate usage. While verbose, it is appropriately detailed for a tool with 9 parameters and 3 operation modes, so it doesn't waste words.

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 the tool's complexity (no output schema, 9 params, 3 operation types), the description covers everything an agent needs: parameter semantics, operation-specific requirements, return behavior, error handling, and related tools. It is complete for correct invocation without requiring additional lookups.

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 coverage is 0%, so the description must explain every parameter. It does so thoroughly: operation lists the enum and which parameters are required per operation, and optional parameters like actionName, fieldContext, expectedOutcome, and isSensitive are described with examples. This fully compensates for the schema's lack of 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 explicitly states it sends text and key input to focused elements on iOS targets, with a clear definition of operations (text, key, key-sequence). It distinguishes from sibling tools by mentioning idb-ui-tap for focusing fields and idb-ui-describe for finding coordinates, which differentiates its purpose.

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?

It provides a 'Why you'd use it' section listing concrete scenarios like form filling and keyboard shortcuts, and a 'Related Tools' section explicitly naming alternatives and their roles (e.g., idb-ui-tap as a prerequisite to focus fields). This gives clear when-to-use and when-not-to-use guidance.

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