Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Clear Cookies

clear_cookies

Wipe all browser cookies for a specified tab to test logged-out flows, simulate a fresh visitor, or recover a stuck auth state; re-login is required.

Instructions

Wipe ALL cookies. Returns count cleared.

When: testing logged-out flow, simulating a fresh visitor without spawning a new browser, or recovering from a stuck auth state. Note: also wipes OAuth/SSO state — re-login required after.

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": {
      "tab_id": "<tab_id>"
    },
    "name": "clear_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations, so the description carries the full disclosure burden and does most of it: it flags that ALL cookies go, that OAuth/SSO state is included, and that re-login is required afterwards. It leaves one real ambiguity for a destructive operation — whether the wipe is scoped to the given tab_id or affects the whole browser profile.

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 short front-loaded sentences with a clear 'When:' block and a 'Note:' warning; every sentence adds something an agent needs (scope, use cases, side effects).

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?

An output schema covers the return shape, and the description covers the destructive side effects and intended use. The remaining gap is the blast radius: it doesn't say whether clearing is per-tab or profile-wide, which matters for a destructive tool and cannot be inferred from the schema.

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?

One parameter (tab_id) with 0% schema description coverage and no mention in the description, so the agent learns nothing about its meaning or format. The note about what gets destroyed partly compensates for the impact but not for the parameter's semantics.

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?

Specific verb and resource with explicit scope: 'Wipe ALL cookies' plus the return value ('Returns count cleared'). Readily distinguishable from siblings like get_cookies, set_cookies, and close_browser without opening a schema.

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?

Gives three concrete when-to-use scenarios (logged-out flow testing, fresh-visitor simulation without spawning a new browser, stuck auth recovery) and implicitly rules out the spawn-based alternative. It does not name a sibling tool as the alternative or state an explicit when-not condition, so it stops short of a 5.

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