Skip to main content
Glama

adb_market_search

Search community-shared workflow definitions by query or tag, then view names, descriptions, authors, step counts, and local installation status to find reusable Android workflows.

Instructions

Search the workflow marketplace for community-shared workflow definitions. Shows name, description, tags, author, and step count. Indicates which workflows are already installed locally.

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": "adb_market_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by exact tag (e.g., 'testing', 'diagnostics', 'security')
queryNoFilter by name, description, or tag keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden and does add value by enumerating the returned fields (name, description, tags, author, step count) and the local-install indicator, which implicitly confirms a read-only operation. It omits pagination or result limits, whether the call requires network access, and matching semantics (substring vs exact) for the filters, which matter for a marketplace lookup.

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?

Three short sentences, purpose front-loaded, with no filler. The return-field sentence earns its place because no output schema exists, though the install-status sentence is only marginally separate from it.

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 two-optional-parameter search tool with no annotations and no output schema, the definition covers purpose and return shape adequately. It leaves gaps on default behavior when both parameters are omitted (does it return everything?), result-size limits, and how the local-install flag is determined, all of which an agent needs to call it confidently.

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% and both parameters carry their own descriptions with examples ('testing', 'diagnostics', 'security'), so the schema does the heavy lifting. The description adds no meaning about how tag and query interact or whether they can be combined, so baseline 3 applies.

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?

States a specific verb and resource: search the workflow marketplace for community-shared workflow definitions. That is clearly distinct from adb_workflow_list (local workflows) and adb_market_install/export. It stops short of naming the nearest siblings (adb_registry_search, adb_market_install), so the boundary with the registry tools must be inferred.

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?

Usage is only implied: an agent can infer this is the discovery step before adb_market_install, but the description never says so, nor does it explain when to use 'tag' versus 'query' or what happens with no arguments. No exclusions or alternative routing are provided.

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