Skip to main content
Glama

iphone_open_url

Open web pages in Safari or app deep links to jump straight to a page or screen instead of tapping through menus. Ask before tel:, sms:, mailto:, or payment links, which trigger real actions.

Instructions

Open a web page in Safari or a deep link in the app that handles it.

Use it to jump straight to a page or screen instead of navigating by taps. Links with tel:, sms:,
mailto: or payment schemes start real actions or drafts on the phone – ask the user first. iOS may show
a confirmation dialog; check with iphone_ui_tree afterwards.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWeb URL (https://…) or deep link with an app scheme (e.g. maps://?q=Berlin, mailto:…, or an app's own scheme).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / url / description
      Added value: +"Web URL (https://…) or deep link with an app scheme (e.g. maps://?q=Berlin, mailto:…, or an app's own scheme)."
    • addedInput schema / properties / url / minLength
      Added value: +3
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that certain schemes trigger real phone actions or compose drafts, that a user confirmation must be requested first, and that iOS may display its own confirmation dialog that leaves the app state uncertain until verified.

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?

Three tight sentences, front-loaded with the action, then the usage rationale, then the risk caveat and verification step. No filler or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with an output schema and existing safety annotations, this covers everything an agent needs: what it does, when to prefer it, which inputs are risky, and how to confirm the result.

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% and the single url parameter already documents accepted forms (https://, maps://, mailto:, app schemes). The description corroborates the web-page vs deep-link distinction but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Open a web page in Safari or a deep link') and immediately scopes it against the obvious sibling approach by saying it is for jumping straight to a page 'instead of navigating by taps', which sets it apart from iphone_tap/iphone_tap_text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use guidance (direct navigation rather than tap sequences), plus an explicit precondition for dangerous schemes: tel:, sms:, mailto: or payment links start real actions or drafts, so the agent must 'ask the user first'. It also prescribes a follow-up step ('check with iphone_ui_tree afterwards').

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