cookies_clear
Remove all cookies from the jar to reset browser session and clear tracking data.
Instructions
Drop all cookies from the jar.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Remove all cookies from the jar to reset browser session and clear tracking data.
Drop all cookies from the jar.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a destructive action (clearing all cookies) but lacks details on side effects (e.g., affecting sessions, irreversible data loss) beyond what is inferred. Adequate for a simple action but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words, directly stating the action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description adequately explains the action. Minor gap: the term 'jar' might be ambiguous, but context from sibling tools suggests it refers to browser cookies.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, and schema coverage is 100%. The description does not add additional parameter semantics beyond the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Drop all cookies from the jar' uses a specific verb ('drop') and resource ('cookies'), clearly distinguishing it from sibling tools like cookies_get and cookies_set.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, such as when to clear all cookies versus individual ones via cookies_delete (if it existed) or how it interacts with other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/protostatis/unbrowser'
If you have feedback or need assistance with the MCP directory API, please join our Discord server