Skip to main content
Glama
Sign In
Safari MCP Server

Safari MCP Server

by achiya-automation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

safari_react_select_list_options

List available options in a react-select v5 dropdown without opening the menu. Returns labels and values to help you find exact option text when a selection fails.

Instructions

List available options of a react-select v5 dropdown without opening the menu. Returns JSON {ok, total, options:[{label,value}…]}. Useful when safari_react_select_set returns 'option not found' and you need to see exact labels (e.g. 'Email Routing Rules' vs 'Email Routing'). Either ref or selector required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "safari_react_select_list_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoRef ID from safari_snapshot
selectorNoCSS selector

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.11.6
  2. Removedv2.11.3
  3. Addedv2.10.9
  4. Removedv2.10.8
  5. Addedv2.10.6

TDQS

A4.4/5.0
Behavior4/5

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

Discloses key behavior: 'without opening the menu' and return format. No annotations are present, so description carries the burden. Lacks details on error handling or compatibility, but sufficient for expected 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?

Concise at 3 sentences: action+return, use case, parameter requirement. No unnecessary words.

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

Completeness4/5

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

Provides return format and usage tip. Without output schema, description covers essentials. Lacks error scenarios but adequate for a simple list tool.

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 has 100% coverage describing both parameters (CSS selector and ref ID). The description adds a usage note that either is required, but does not enrich semantics beyond 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 clearly states the tool lists options of a react-select v5 dropdown without opening the menu. It specifies the return format and distinguishes itself from sibling tools like safari_react_select_set.

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 provides a concrete use case: useful when safari_react_select_set returns 'option not found' to see exact labels. Also states that either ref or selector is required.

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