android-device-mcp

Overview Schema Source Related Servers Discussions Admin

Screen Recording

screen_recording

Record an Android device's screen by providing its serial number. Set a time limit and optionally specify a local file path to save the recording.

Instructions

Record the screen of an Android device using its serial number.

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": {
      "serial": "<serial>"
    },
    "name": "screen_recording"
  }
}

Input Schema

Name	Required	Default
`serial`	Yes
`time_limit`	No	5
`local_file_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Record the screen' without explaining whether recording starts immediately, the meaning of time_limit, what happens after time limit, or if it returns a file. This is insufficient for an agent to understand side effects or requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but insufficiently informative for a tool with three parameters. It front-loads the core action but lacks structural completeness.

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

Completeness2/5

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

Given the tool has three parameters and no output schema, the description is incomplete. It does not explain the time_limit unit, local file path behavior, return type, or how it differs from take_screenshot. An agent would likely misuse parameters or miss prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must supplement parameter meanings. It only implies 'serial' is needed but fails to explain 'time_limit' (default '5' - seconds? minutes? ), 'local_file_path' (destination format), or that 'serial' is required. No added meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Record the screen') and the resource ('screen of an Android device'). It also implies the use of a serial number, which is a required parameter. However, it does not explicitly differentiate from sibling tools like take_screenshot, leaving room for ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions using a serial number, implying a prerequisite, but gives no guidance on when to use this tool versus alternatives (e.g., for videos vs. static images). No exclusions or when-not-to-use information is provided.

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

Deploy Server