Skip to main content
Glama
WhiteNightShadow

camoufox-reverse-mcp

by WhiteNightShadow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cookies

Manage browser cookies by retrieving, setting, and deleting them with optional filters for domain and name.

Instructions

Cookie management (v0.9.0 unified).

Replaces get_cookies / set_cookies / delete_cookies.

Args: action: "get" — return cookies (optionally filtered by domain) "set" — set cookies (requires cookies_list: [{name, value, domain, ...}]) "delete" — delete cookies (filter by name and/or domain; no filter = clear all) domain: Host or parent domain for get/delete (boundary match, includes subdomains). With name, both filters must match. No filters deletes all cookies. cookies_list: List of cookie dicts for "set". name: Cookie name filter for "delete".

Returns: For "get": list of cookie dicts. For "set"/"delete": dict with status and count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
actionYes
domainNo
cookies_listNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.1.1
    • removedInput schema / properties / cookies_list / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / cookies_list / default
      Removed value: -null
    • addedInput schema / properties / cookies_list / items
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • addedInput schema / properties / cookies_list / type
      Added value: +"array"
    • removedInput schema / properties / domain / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / domain / default
      Removed value: -null
    • addedInput schema / properties / domain / type
      Added value: +"string"
    • removedInput schema / properties / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / name / default
      Removed value: -null
    • addedInput schema / properties / name / type
      Added value: +"string"
  2. Addedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses the destructive outcome of an unfiltered delete ('no filter = clear all'), the boundary-match/subdomain behavior of domain filtering, the requirement of cookies_list for set, and the return format for each action. This is far beyond minimal transparency.

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 well-structured with clear sections for the replacement note, args, and returns. Every sentence provides useful information—no filler. Despite moderate length, the formatting makes it easy to scan and the critical safety warning is included without bloat.

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?

The description covers all four parameters, all three actions, filter interactions, the destructive edge case, and return values. Even with an output schema present, it includes enough behavioral context for an agent to safely and correctly invoke the tool. Nothing essential is missing for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain every parameter, and it does. It defines the action values with behaviors, explains domain as a host/parent-domain filter with subdomain matching, specifies cookies_list as cookie dicts for set, and clarifies name as a delete filter. This fully compensates for the bare input 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 manages cookies with three distinct actions (get, set, delete), and explicitly notes it replaces get_cookies / set_cookies / delete_cookies. This makes the tool's scope immediately clear and distinguishes it from the legacy alternatives and unrelated siblings.

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 provides explicit action-level usage guidance, including when to use each action, filter semantics for get/delete, and the requirement of cookies_list for set. The note that it replaces three legacy tools directly tells the agent to prefer this tool over them, and the warning about no filters clearing all cookies gives a specific when-not-to behavior.

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