Skip to main content
Glama

list_safari_bookmarks

List all Safari bookmarks on your Mac. Access your saved web links for better organization.

Instructions

List Safari bookmarks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:93-93 (registration)
    Tool is registered under the name 'list_safari_bookmarks' with description 'List Safari bookmarks' in the TOOLS array.
    ["list_safari_bookmarks", "List Safari bookmarks"],
  • The handler for 'list_safari_bookmarks' (and all other tools) is a stub that returns an inspection placeholder message. The real implementation is in a native binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose any behavioral traits such as read-only nature, permission requirements, or return format. The minimal description does not add value beyond the name.

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 a single, front-loaded sentence with no wasted words. It maximally concise for the purpose stated.

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?

Given no output schema, the description lacks details about the return format or structure. While the tool is simple, an agent would benefit from knowing what it receives (e.g., array of bookmark objects). The description is minimally viable but incomplete.

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?

There are no parameters, so the description does not need to explain them. Baseline is 3, but the description adds no additional semantics about the tool's behavior or output, missing an opportunity to clarify what the agent can expect.

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 'List Safari bookmarks' clearly states the action (list) and the resource (Safari bookmarks). There are no sibling tools with similar functionality, making the purpose unambiguous.

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?

No explicit when-to-use or alternative guidance is given, but the tool is straightforward and has no competing siblings. The description implies it is for retrieving bookmarks, which is clear enough for an agent.

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/lanchuske/local-mcp-releases'

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