Skip to main content
Glama
Sign In
Safari MCP Server

Safari MCP Server

by achiya-automation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

safari_navigate_and_read

Navigate to a URL and return the page content in one step, replacing a separate navigate plus read call and saving a round-trip.

Instructions

Navigate to a URL and return the page content in one step — saves 1 full round-trip vs navigate+read_page. Use instead of safari_navigate + safari_read_page. Like safari_navigate, returns a fresh receipt when the origin changed; use that one from then on.

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to
receiptNoTab receipt from safari_new_tab — pins this call to that tab (survives reconnects/subagents)
timeoutNoLoad timeout in ms (default: 30000)
maxLengthNoMax chars to return (default: 50000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.18.1
    • addedInput schema / properties / receipt
      Added value: +{
+  "description": "Tab receipt from safari_new_tab — pins this call to that tab (survives reconnects/subagents)",
+  "type": "string"
+}
  2. Addedv2.11.6
  3. Removedv2.11.3
  4. Addedv2.10.9
  5. Removedv2.10.8
  6. Addedv2.10.5
  7. Removedv2.10.4
  8. First observed

TDQS

A4.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses a non-obvious trait — a fresh `receipt` is returned when the origin changes and should be reused — but says nothing about waiting/load-completion semantics, truncation behavior, or failure modes, which matter for a navigation tool.

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 short sentences, no filler, and the primary value proposition (one step, saves a round-trip) is front-loaded before the alternative and the receipt nuance.

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?

With 100% schema description coverage and no output schema, the remaining descriptive burden is small: params are documented in the schema and return content is described inline. The description covers the routing decision and the one tricky stateful behavior (receipt rotation).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: it explains the receipt's lifecycle (it can change on origin switch and the new value must be used thereafter), which is more than the schema's static "Tab receipt from safari_new_tab" note.

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 concrete compound action (navigate to a URL and return page content in one step) and explicitly frames itself against the two-tool alternative safari_navigate + safari_read_page. An agent can distinguish it from siblings like safari_read_page or safari_navigate without opening any schema.

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?

Explicitly says "Use instead of safari_navigate + safari_read_page" and gives the reason (saves a round-trip), so the selection condition is unambiguous. It also gives follow-up guidance: if a fresh receipt is returned due to an origin change, use that one from then on.

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