Skip to main content
Glama

deep_link_navigate

Navigate to a specific screen in a mobile app using deep links or Universal Links. Supports custom URL schemes and HTTPS URLs for Android and iOS apps. Specify the URI, platform, and optional device or app identifiers.

Instructions

Navigate to a specific screen in the app using a deep link or Universal Link. Supports custom URL schemes (myapp://path) and HTTPS URLs for App Links/Universal Links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesDeep link URI to navigate to (e.g., myapp://home/profile or https://example.com/app/products/123)
platformYesTarget platform
deviceIdNoDevice ID (optional, uses first available). For Android: emulator-5554. For iOS: UDID or "booted"
packageNameNoAndroid package name to target specific app (e.g., com.example.myapp)
bundleIdNoiOS bundle ID to target specific app (e.g., com.example.myapp)
waitAfterMsNoTime to wait after navigation in milliseconds (default: 1000)
extrasNoAndroid intent extras to pass with the deep link
timeoutMsNoTimeout in milliseconds (default: 15000)
Behavior2/5

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

With no annotations, the description fails to disclose failure behavior, authentication needs, side effects (e.g., app switching), or requirements (app must be installed). The term 'navigate' is vague.

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 focused sentences with no superfluous text. Front-loaded with purpose, then supported URL formats. Efficient.

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?

For a tool with 8 parameters, the description is too brief. It lacks context on required parameters (platform), optional dependencies (deviceId), and behavior of extras/timeout. Insufficient for a complete understanding.

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% with descriptions for all parameters. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool navigates to a specific screen using deep links or Universal Links, and differentiates from siblings like launch_app by specifying the mechanism (URI).

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 deep link navigation but does not provide when-to-use or alternatives (e.g., interact_with_ui, launch_app). No exclusions or prerequisites are mentioned.

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/abd3lraouf/specter-mcp'

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