Skip to main content
Glama
Sign In
android-emulator

android-emulator

by Sajinthan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_media

Add a photo or video to the Android emulator's media library (Photos/Gallery) using the file's absolute path.

Instructions

Add a photo or video to the device's media library (Photos/Gallery)

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": {
      "file_path": "<file_path>"
    },
    "name": "add_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNoDevice serial (e.g. emulator-5554). Optional when exactly one device is connected.
file_pathYesAbsolute path to image or video file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the destination and type of media, without mentioning whether the file is copied, whether a media scan is triggered, what happens on invalid input, or what permissions/side effects are involved.

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

Conciseness4/5

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

The description is a single clear sentence with no wasted words. It is front-loaded with the main action and resource, though it could have used additional space to include usage or behavioral guidance without becoming bloated.

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

Completeness3/5

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

For a tool with only two parameters and full schema coverage, the description provides the core invocation context: what to add and where. However, with no annotations and no output schema, an agent is left without information about side effects, return behavior, or when to prefer this over related tools.

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 description coverage is 100%, so the schema already documents both serial and file_path. The description adds little beyond the schema, only restating that the file is an image or video and the destination. Baseline 3 applies because the schema carries the parameter documentation.

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 action ('Add') on a specific resource ('photo or video to the device's media library'). It distinguishes the tool from siblings like push_file (which places files generally) and record_video (which captures new media). The parenthetical '(Photos/Gallery)' further pins down the intended destination.

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?

No guidance is given about when to use this tool versus alternatives such as push_file or screenshot. The only usage signal is implied by the purpose itself, with no exclusions, prerequisites, or comparison to sibling tools.

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