adb-ai

by cyberpunk2183

Overview Schema Source Related Servers Discussions Admin

Python

Local

adb_youtube_search

Send a YouTube search query to a connected Android device over ADB without using the on-screen keyboard.

Instructions

Search YouTube on the device without using the on-screen keyboard.

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": {
      "query": "<query>"
    },
    "name": "adb_youtube_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`device`	No	serial, ip[:port] or saved alias; omit to use the default device

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

C2.9/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 behavioral burden. It only discloses that the search avoids the on-screen keyboard; it does not mention device prerequisites, whether YouTube must already be installed or open, whether focus must be in a search field, side effects on device state, or what output or confirmation is returned.

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 front-loaded sentence with no wasted text. However, its brevity leaves important operational context unaddressed, so it is efficient but not fully structured for an automation tool.

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 no annotations, no output schema, and only 50% schema description coverage, the description is too sparse. It omits prerequisites, device/connection expectations, interaction behavior, and result handling, leaving the agent with insufficient context to invoke the tool confidently.

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?

The schema documents the optional 'device' parameter but leaves the required 'query' parameter undocumented. The description only implies that 'query' is a YouTube search term and adds no detail about query format, device selection behavior, or defaults beyond what the schema partially provides.

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: 'Search YouTube on the device.' It is clearer than a tautology, but it does not explicitly distinguish this tool from sibling tools such as adb_type_text, adb_open_app, or adb_open_url, which could also participate in a YouTube search workflow.

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 phrase 'without using the on-screen keyboard' implies the intended usage context, but the description gives no explicit when-to-use, when-not-to-use, prerequisites, or alternative tools. The agent can infer the use case but is not guided on selecting this tool over nearby automation tools.

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