Skip to main content
Glama
Sign In
adb-mcp

adb-mcp

by FlashZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

record_screen_start

Start background screen recording on an Android device, with optional time limit, resolution, and bitrate, then stop it to save the MP4.

Instructions

Start recording the screen on-device (screenrecord runs in the background). time_limit_s caps duration (screenrecord max 180s per segment). size like '720x1280' to downscale. Call record_screen_stop to finish and pull the mp4.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "record_screen_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
serialNo
time_limit_sNo
bit_rate_mbpsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations the description carries the full burden and delivers real behavioral context: recording runs in the background, screenrecord caps at 180s per segment, and the mp4 is only obtainable via record_screen_stop. It omits permission/root requirements and what happens on repeated starts.

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

Conciseness5/5

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

Three short sentences, each earning its place, with the core action front-loaded and parameter notes and lifecycle handoff following in priority order. No filler.

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?

An output schema exists so return values need not be explained, and the description covers the recording lifecycle and two key parameters. It is still thin on the serial/bit_rate parameters and on any preconditions for a device-mutating capture operation.

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

Parameters3/5

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

Schema coverage is 0% for 4 parameters, so the description must compensate. It explains time_limit_s (duration cap, 180s max per segment) and size (format '720x1280' for downscaling), but serial and bit_rate_mbps are left entirely undocumented.

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?

States a specific verb and resource ('Start recording the screen on-device') and names the companion sibling record_screen_stop, so an agent can distinguish it from capture_screen variants and the stop tool without opening a schema.

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?

Makes the usage context explicit: start recording, then call record_screen_stop to finish and pull the mp4. It gives clear positive routing but no when-not-to-use guidance (e.g., versus capture_screen for stills).

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

Deploy Server

Other Tools