Skip to main content
Glama
achiya-automation

Safari MCP Server

by achiya-automation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

safari_paste_image

Paste a local image file into the focused browser element using JS DataTransfer, avoiding clipboard use and focus changes on sites like Medium and dev.to.

Instructions

Paste an image from a local file into the focused element via JS DataTransfer (no clipboard, no focus steal). Works on Medium, dev.to, HackerNoon, TOI, etc.

Input Schema

NameRequiredDescriptionDefault
receiptNoTab receipt from safari_new_tab — pins this call to that tab (survives reconnects/subagents)
filePathYesAbsolute path to the image file (PNG, JPG, WebP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.22.13
    • 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

A3.9/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 usefully discloses the mechanism (JS DataTransfer, no clipboard, no focus steal), but omits prerequisites such as needing a focused contenteditable/rich-text editor, failure behavior when nothing is focused, and whether the local file is consumed or left in place.

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 compact sentences, no filler, and the core action plus destination are front-loaded before the site list. Every clause earns its place.

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 two-parameter, no-output-schema tool the description is serviceable, but the critical dependency — that the target element must already have focus and be a rich-text/upload-capable editor — is left implicit, which is exactly the fact an agent needs to invoke this successfully.

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% for both parameters (filePath with format hints, receipt with a clear pinning explanation), so the schema already does the work. The description adds no syntax or format detail beyond it, making the baseline 3 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?

States a specific verb (paste), resource (image from local file), destination (focused element), and mechanism (JS DataTransfer). This distinguishes it cleanly from safari_upload_file and safari_clipboard_write in the sibling list.

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

Usage Guidelines4/5

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

Explains the operating context ('no clipboard, no focus steal') and enumerates supported sites (Medium, dev.to, HackerNoon, TOI), which tells the agent when the tool applies. It does not explicitly name safari_upload_file or safari_clipboard_write as alternatives or state when-not to use it.

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