Skip to main content
Glama

adb_open_url

Opens a URL on an Android device using the default browser or handling app via Android’s VIEW intent, so agents can launch web links directly on the device.

Instructions

Open a URL on the device in the default browser or handling app. Uses Android's VIEW intent action.

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": {
      "url": "<url>"
    },
    "name": "adb_open_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to open (must be a valid URL with scheme)
deviceNoDevice serial

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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the intent mechanism (VIEW action) and that the default handler resolves it, which is useful behavior beyond the schema. However, it omits failure modes (no handler registered, malformed scheme), whether the call waits for the activity, and any permission or device-selection requirements.

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?

Two short sentences, front-loaded with the action and the resource, with the second sentence adding non-redundant mechanism detail. Nothing is wasted.

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 simple two-parameter tool with fully documented parameters and no output schema, the description covers the essentials. It still leaves an agent guessing about error behavior and device-defaulting rules, which matter for reliable invocation.

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 100%, so both 'url' (with scheme requirement) and 'device' serial are already documented. The description adds only the dispatch context, no additional meaning about format, scheme restrictions, or device defaults. 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 ('Open a URL on the device') plus the dispatch target ('default browser or handling app'), and adds the underlying mechanism (VIEW intent action). It distinguishes the tool from generic launchers like adb_start_activity, though it never names the sibling it overlaps with.

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 implied by the name and description - use it to launch a URL - but there is no explicit when-to-use versus adb_start_activity or adb_resolve_intents, and no guidance on what happens when no app handles the URL or when multiple devices are attached.

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