FleetDeckDocs

Action payload · devices:control

text

Type into the focused control. value allows up to 16,000 characters, including empty text. ADB input supports ASCII only and rejects literal %s; use a compatible relay/IME or native tool for other text.

Payload

json
{
  "type": "text",
  "value": "Hello from FleetDeck"
}

Payload fields

typestringrequired

Discriminator that selects the action or content shape.

Allowed:"text"
valuestringrequired

Text to type or write; for a clipboard read, the returned plaintext value. Writing the clipboard does not paste it.

max 16,000 characters
Example: "Hello from FleetDeck"

Unknown fields are rejected.

View JSON Schema
json
{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "text"
      ],
      "description": "Discriminator that selects the action or content shape."
    },
    "value": {
      "type": "string",
      "maxLength": 16000,
      "description": "Text to type or write; for a clipboard read, the returned plaintext value. Writing the clipboard does not paste it."
    }
  },
  "required": [
    "type",
    "value"
  ],
  "additionalProperties": false,
  "description": "Type into the focused control. value allows up to 16,000 characters, including empty text. ADB input supports ASCII only and rejects literal %s; use a compatible relay/IME or native tool for other text.",
  "example": {
    "type": "text",
    "value": "Hello from FleetDeck"
  }
}

REST wraps this payload inside {requestId, command}. The matching MCP tool takes sessionId and requestId plus these fields, without the type discriminator.

Contract

Submit this as command to POST /sessions/{sessionId}/actions, pass it as the CLI action JSON, or use the matching MCP convenience tool. Command objects are strict and reject unknown fields.

Execution

Type into the focused control. value allows up to 16,000 characters, including empty text. ADB input supports ASCII only and rejects literal %s; use a compatible relay/IME or native tool for other text.

Action status and driver result remain separate. A completed result can still require a fresh screenshot or hierarchy check to prove the intended visible effect.