Android Studio MCP

Overview Schema Source Related Servers Discussions Admin

Push / pull file

file_transfer

Destructive

Copies files between your local machine and an Android device using adb push or pull, so you can deploy assets or retrieve device files.

Instructions

Copy a file between this machine and the device (adb push / adb pull).

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": {
      "direction": "<direction>",
      "localPath": "<localPath>",
      "devicePath": "<devicePath>"
    },
    "name": "file_transfer"
  }
}

Input Schema

Name	Required	Description
`serial`	No	Device serial from devices_list. Optional when exactly one device is online.
`direction`	Yes
`localPath`	Yes
`devicePath`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With destructiveHint=true, the annotation already flags that this operation can overwrite data. The description adds no behavioral context beyond 'Copy a file' - it does not state that destination files may be overwritten, what permissions are required, or how errors are handled. That leaves a significant gap for a destructive file operation.

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?

A single sentence with no filler, and the core idea - copying files in either direction between host and device - is front-loaded. Nothing is wasted, even if more detail would be useful.

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?

For a destructive 4-parameter tool with low schema coverage and no output schema, the description is too thin. It omits direction semantics, localPath/devicePath distinction, serial behavior, and overwrite implications, leaving the agent to infer critical operational details.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description must compensate but largely does not. It parenthetically references push/pull, which hints at the direction enum, but it never explains which path is local versus device-side, nor mentions the optional serial parameter's role.

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 states a specific verb and resource: 'Copy a file between this machine and the device', and names the underlying adb push/pull operations. This clearly distinguishes it from sibling tools like adb_shell and ide_read_file, though it does not explicitly call out those alternatives.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives such as adb_shell, ide_read_file, or ide_find_files. The push/pull direction is implied, but prerequisites and exclusions are absent.

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