Skip to main content
Glama
achiya-automation

Safari MCP Server

by achiya-automation
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

safari_fill

Set or replace values in input fields, textareas, selects, and rich text editors. Automatically handles React controlled inputs and common editors like ProseMirror and Draft.js.

Instructions

Fill/replace value in an input, textarea, select, OR contenteditable (rich text). Handles React controlled inputs, ProseMirror, Draft.js, and Google Closure editors automatically. Use for SETTING a value (replaces existing). For code editors (Monaco/CodeMirror/Ace), use safari_replace_editor instead. For character-by-character typing in search boxes, use safari_type_text. IMPORTANT: When using ref, always take a FRESH safari_snapshot first — refs expire after each new snapshot (prefix changes: 5_xx → 6_xx).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoRef ID from safari_snapshot
valueYesValue to fill
receiptNoTab receipt from safari_new_tab — pins this call to that tab (survives reconnects/subagents)
selectorNoCSS selector

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool replaces existing values, automatically handles React/ProseMirror/Draft.js/Closure editors, and that refs expire after new snapshots. This is strong transparency, though it does not mention event side effects or failure behavior.

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 compact and front-loaded with the core action and target. Every sentence earns its place: scope, framework handling, alternative routing, and the critical snapshot warning.

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 mutation tool with no annotations and no output schema, it covers the essential information: supported element types, framework compatibility, replacement semantics, sibling-tool routing, and a critical ref-expiry caveat. An agent has enough to invoke it correctly.

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?

The schema already describes all four parameters at 100% coverage, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining the lifecycle and freshness requirement of the ref parameter, which is not captured in the schema.

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 opens with a specific verb and resource: fill/replace a value in an input, textarea, select, or contenteditable. It also distinguishes itself from code-editor tools and character-by-character typing tools, making its scope immediately clear.

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?

It explicitly says to use safari_replace_editor for code editors and safari_type_text for character-by-character typing, and frames safari_fill as the SETTING action that replaces existing content. The snapshot freshness warning also gives critical operational context for when this tool can be safely invoked.

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/achiya-automation/safari-mcp'

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