Skip to main content
Glama
BrowserGenie

BrowserGenie MCP Server

by BrowserGenie

delete_cookie

Delete a specific cookie from a URL by providing the cookie name and URL. Removes unwanted cookies for browser management.

Instructions

Delete a specific cookie

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCookie name
urlYesURL associated with the cookie
apiKeyNoAPI key for authentication

Implementation Reference

  • The handler/implementation of the delete_cookie tool. It accepts 'name' (required), 'url' (required), and 'apiKey' (optional), sends a 'delete_cookie' command via the WebSocket bridge, and returns a success or error message.
    server.tool(
      'delete_cookie',
      'Delete a specific cookie',
      {
        name: z.string().describe('Cookie name'),
        url: z.string().describe('URL associated with the cookie'),
        apiKey: z.string().optional().describe('API key for authentication'),
      },
      async ({ name, url, apiKey }) => {
        const result = await bridge.sendCommand({ command: 'delete_cookie', params: { name, url }, apiKey });
        if (!result.success) return { content: [{ type: 'text' as const, text: `Error: ${result.error?.message}` }], isError: true };
        return { content: [{ type: 'text' as const, text: `Cookie "${name}" deleted` }] };
      }
    );
  • Input validation schema for delete_cookie using Zod. Requires 'name' (string) and 'url' (string), with optional 'apiKey'.
    {
      name: z.string().describe('Cookie name'),
      url: z.string().describe('URL associated with the cookie'),
      apiKey: z.string().optional().describe('API key for authentication'),
    },
  • Registration point where delete_cookie is registered as part of devtools storage tools via the registerDevtoolsStorageTools function called from registerAllTools.
    registerDevtoolsStorageTools(server, bridge);
  • src/server.ts:5-14 (registration)
    Top-level server creation that calls registerAllTools, which ultimately registers delete_cookie.
    export function createServer(bridge: WebSocketBridge): McpServer {
      const server = new McpServer({
        name: 'browser-genie',
        version: '1.0.0',
      });
    
      registerAllTools(server, bridge);
    
      return server;
    }
  • The WebSocketBridge.sendCommand helper that actually dispatches the 'delete_cookie' command to the Chrome extension over WebSocket and awaits the response.
    async sendCommand(cmd: BridgeCommand): Promise<BridgeResponse> {
      if (!this.isConnected()) {
        return {
          success: false,
          error: {
            code: 'NOT_CONNECTED',
            message: 'Chrome extension is not connected. Ensure the extension is installed, enabled, and the browser is running.',
          },
        };
      }
    
      const id = crypto.randomUUID();
      const timeout = cmd.timeout ?? DEFAULT_TIMEOUT;
    
      return new Promise<BridgeResponse>((resolve, reject) => {
        const timer = setTimeout(() => {
          this.pending.delete(id);
          resolve({
            success: false,
            error: {
              code: 'TIMEOUT',
              message: `Command '${cmd.command}' timed out after ${timeout}ms`,
            },
          });
        }, timeout);
    
        this.pending.set(id, { resolve, reject, timer });
    
        const message = {
          id,
          type: 'request',
          command: cmd.command,
          params: cmd.params,
          tabId: cmd.tabId,
          apiKey: cmd.apiKey,
          timestamp: Date.now(),
        };
    
        this.client!.send(JSON.stringify(message));
      });
    }
Behavior2/5

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

No annotations provided; description only says 'Delete', which implies mutation, but no details on authentication (apiKey parameter exists), side effects, or permission requirements.

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?

One sentence, no wasted words. However, slightly under-specified for a destructive operation.

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?

Without annotations or output schema, the description needs to cover more context (e.g., return value, prerequisites). Current form is adequate but minimal.

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?

Schema covers all parameters with descriptions (100%), but tool description adds no extra meaning beyond what the schema already provides.

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?

Description clearly states verb 'Delete' and resource 'a specific cookie', directly distinguishing it from sibling tools like set_cookie and get_cookies.

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?

No guidance on when to use this tool versus cookie-related siblings (e.g., set_cookie, get_cookies). Agent must infer context.

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

Install Server

Other Tools

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/BrowserGenie/mcp'

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