Record screen
record_screenUse this when the task calls for a short bounded screen recording when motion/timing is necessary to diagnose a UI issue. Prefer screenshot_region for static visual verification because it is cheaper and easier to inspect.
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": {
"device": "<device>"
},
"name": "record_screen"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fps | No | 1..60. | |
| device | Yes | ReMCP device id returned by list_devices. Required for every device operation. | |
| destination | No | Permitted output path. Omit the extension to accept the native format. GNOME may produce .webm or .mp4; other backends produce .mp4. An explicit extension must match the recorded format. | |
| duration_seconds | No | 1..120 seconds. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Record screen structured result for record_screen. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload. | |
| text | Yes | Concise human-readable result of the tool call. |