Skip to main content
Glama
81117105108108

Blinkwire

Clear cookies

browser_cookie_clear

Delete all cookies from the browser to eliminate session data and tracking identifiers, giving you a clean slate for testing or privacy.

Instructions

Delete every cookie in the browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

While the description clearly states the destructive effect (deleting all cookies), it directly contradicts the annotation 'destructiveHint: false'. This inconsistency reduces transparency about the tool's side effects and could mislead an agent about the action's severity.

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, concise sentence that conveys the entire purpose without extraneous words or redundancy.

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 parameterless action, the description covers the essential effect. However, it does not mention potential side effects (e.g., clearing cookies across all browser contexts) or confirm the action's irreversibility, though this is minor given the simple nature of the task.

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?

The tool schema has no parameters, so there is nothing to clarify. The description appropriately omits parameter details, and no additional explanation is needed.

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 'Delete every cookie in the browser' is specific and unambiguous, clearly distinguishing this tool from sibling cookie functions (e.g., browser_cookie_delete which removes a single cookie).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives like browser_cookie_delete or browser_cookie_set. It only states what the tool does, leaving the agent to infer the appropriate context.

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

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/81117105108108/Blinkwire'

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