Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

idb-ui-input

Automates iOS keyboard input and text entry. Types text, presses special keys (home, return, delete, arrows), and executes key sequences for form filling and navigation. Redacts sensitive data automatically.

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
udidNo
operationYes
textNo
keyNo
keySequenceNo
actionNameNo
fieldContextNo
expectedOutcomeNo
isSensitiveNo
Behavior3/5

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

With no annotations, the description must disclose behavior fully. It mentions automatic redaction of sensitive data and metadata tracking, but does not explain failure modes (e.g., when no element is focused), side effects, or prerequisites like focus.

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 well-structured with clear sections, headings, emojis, and examples. It is front-loaded with the core purpose. However, it is slightly verbose (repeats redaction info) and could be tightened.

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

Completeness4/5

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

Given the tool has 9 parameters and no output schema or annotations, the description covers behavior, parameters, examples, and related tools adequately. It lacks a detailed return type specification but summarizes the output format sufficiently.

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?

The description provides detailed meanings for each parameter beyond the schema, e.g., 'text: String to type into focused field', 'key: Special key name', and explains the purpose of optional parameters like actionName and fieldContext. This compensates for the 0% schema description coverage.

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 opens with 'Input text and keyboard commands - automated text entry and special key presses for form automation', providing a specific verb and resource. It distinguishes itself from siblings like idb-ui-tap (focusing) and idb-ui-describe (finding coordinates) via the 'Related Tools' section.

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?

The 'Why you'd use it' section clearly lists use cases (form filling, keyboard shortcuts, sensitive data handling) and mentions related tools for alternative actions. However, it lacks an explicit 'when not to use' statement.

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/conorluddy/xc-mcp'

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