Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

delete_cookie

Destructive

Deletes a cookie by name from a target Electron app, using a URL or domain and optional path to clear specific cookie data.

Instructions

Delete a cookie by name. Provide url or domain, same as set_cookie. Defaults url to the page location.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
nameYes
pathNo
domainNo
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

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

The destructiveHint=true annotation already declares that this mutates state, and the description is consistent with it by describing a delete operation. Beyond that, it adds the default-url behavior and the url/domain alternative, but does not disclose irreversibility, error behavior for missing cookies, or whether path must match the stored cookie.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the core action is front-loaded before the parameter guidance. The wording is slightly telegraphic ('same as set_cookie'), but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with six parameters, no output schema, and low schema description coverage, the definition is only moderately complete. It covers the common path but leaves an agent without guidance on path matching, target/process selection, or failure behavior.

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

Parameters2/5

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

Schema coverage is only 17%, so the description must carry the parameter burden, and it only partially does. It clarifies name scoping and the url/domain alternative with a documented default, but path, targetId, and processId receive no explanation at all in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Delete a cookie by name') and scopes it to a single cookie rather than all cookies, which distinguishes it from bulk-clearing siblings. It also ties itself to set_cookie for parameter semantics, giving an agent a clear counterpart to reason from.

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

Usage Guidelines3/5

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

It gives concrete invocation guidance ('Provide url or domain', 'Defaults url to the page location'), which tells the agent how to scope the deletion. However, it offers no explicit when-to-use versus when-not-to-use framing, nor does it say what happens if the cookie does not exist or whether a broader cookie-clearing path exists.

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