dolphin-anty-mcp

Export cookies via the Local API

export_cookies_local

Export cookies for each profile to a local text file in Downloads via the desktop app, even for non-synced profiles.

Instructions

Export cookies for one or more profiles through the running desktop app. As a side effect this writes a dolphin-anty-cookies--.txt file per profile into the machine's Downloads folder. Prefer export_cookies unless you need that file or the profile is not cloud-synced.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "browserProfiles": "<browserProfiles>"
    },
    "name": "export_cookies_local"
  }
}

Input Schema

Name	Required	Description	Default
`plan`	No
`browserProfiles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses a significant side effect—writing a dolphin-anty-cookies-<name>-<id>.txt file per profile to the Downloads folder—which goes beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false). It also notes the dependency on the running desktop app. No contradictions with annotations.

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 concise sentences: purpose, side effect, and usage guidance. Each sentence adds essential information without redundancy or fluff, and the most important info is front-loaded.

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?

For a tool with two parameters (one enum) and no output schema, the description covers the core behavior, side effects, and alternative choice. It lacks explicit return value details, but given the straightforward 'export' purpose, it is sufficiently complete for an agent to select and invoke correctly.

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?

The description adds meaning to the 'browserProfiles' parameters by explaining that 'name' and 'id' are used in the output file name. However, the 'plan' parameter is not mentioned at all, and schema description coverage is 0%, so the description only partially compensates for the lack of parameter explanations.

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 function: 'Export cookies for one or more profiles through the running desktop app.' It uses a specific verb ('Export') and resource ('cookies for profiles'), and immediately distinguishes itself from the sibling 'export_cookies' by noting the local API and the file side effect.

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?

Explicit usage guidance is provided in the final sentence: 'Prefer `export_cookies` unless you need that file or the profile is not cloud-synced.' This clearly tells the agent when to choose this tool over the alternative and under what conditions it is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server