Skip to main content
Glama

Open URL

mobile_open_url
Destructive

Open URLs in mobile device browsers using the Mobile Next MCP server. Specify device identifier and URL to launch web content on iOS or Android devices.

Instructions

Open a URL in browser on device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
urlYesThe URL to open

Implementation Reference

  • src/server.ts:327-338 (registration)
    Registration of the MCP tool 'mobile_open_url' using the 'tool' helper function. Includes the tool name, description, input schema (url: string), and inline handler that requires a selected robot/device and calls robot.openUrl(url).
    tool(
    	"mobile_open_url",
    	"Open a URL in browser on device",
    	{
    		url: z.string().describe("The URL to open"),
    	},
    	async ({ url }) => {
    		requireRobot();
    		await robot!.openUrl(url);
    		return `Opened URL: ${url}`;
    	}
    );
  • Inline handler function for the 'mobile_open_url' tool. Ensures a device/robot is selected via requireRobot(), then invokes the platform-specific robot.openUrl(url) method, and returns a success message.
    async ({ url }) => {
    	requireRobot();
    	await robot!.openUrl(url);
    	return `Opened URL: ${url}`;
    }
  • Android-specific implementation of openUrl in AndroidRobot class, using ADB to start an intent with ACTION_VIEW and the provided URL.
    public async openUrl(url: string): Promise<void> {
    	this.adb("shell", "am", "start", "-a", "android.intent.action.VIEW", "-d", url);
    }
  • iOS physical device implementation of openUrl in IosRobot, delegating to WebDriverAgent (WDA).
    public async openUrl(url: string): Promise<void> {
    	const wda = await this.wda();
    	await wda.openUrl(url);
    }
  • iOS Simulator implementation of openUrl in Simctl class (extends Robot), delegating to WebDriverAgent (WDA), with commented alternative using simctl.
    public async openUrl(url: string) {
    	const wda = await this.wda();
    	await wda.openUrl(url);
    	// alternative: this.simctl("openurl", this.simulatorUuid, url);
    }
Behavior3/5

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

Annotations provide destructiveHint: true, indicating potential side effects. The description adds context by specifying 'in browser on device,' which clarifies the action's scope, but doesn't elaborate on what 'destructive' entails (e.g., interrupting current app, requiring permissions). It doesn't contradict annotations, but offers limited behavioral details beyond them.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, making it easy to understand quickly.

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?

Given the tool's moderate complexity (2 required parameters, destructive hint, no output schema), the description is minimal but functional. It covers the basic action but lacks details on outcomes, error handling, or integration with sibling tools like mobile_list_available_devices, leaving some gaps in context.

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%, with clear parameter descriptions in the schema. The description doesn't add meaning beyond the schema, as it doesn't explain parameter interactions or usage nuances. Baseline score of 3 is appropriate since the schema handles parameter documentation adequately.

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 clearly states the action ('Open a URL') and target ('in browser on device'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like mobile_launch_app or mobile_install_app, which might also involve opening applications or content on the device.

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 description implies usage for opening URLs in a browser context on a mobile device, but doesn't explicitly state when to use this tool versus alternatives like mobile_launch_app for apps or other navigation tools. It provides basic context but lacks explicit exclusions or comparisons with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EmpathySlainLovers/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server