Skip to main content
Glama
Sign In
Camoufox MCP

Camoufox MCP

by baixianger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dismiss_popups

Automatically close cookie consent popups and overlays during web browsing to remove interruptions and access content directly.

Instructions

Dismiss cookie consent popups and overlays

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dismiss_popups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNoPage ID (uses active page if not specified)
maxAttemptsNoMaximum attempts
customSelectorsNoAdditional selectors to try

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states the action (dismissing popups), it lacks details about how dismissal works (e.g., clicking buttons, waiting for elements), what happens on failure, or side effects. The description doesn't compensate for the missing annotation coverage adequately for a tool that modifies page state.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence ('Dismiss cookie consent popups and overlays') directly contributes to understanding the tool's function, making it appropriately sized and well-structured.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral details needed for a tool that interacts with dynamic page elements, especially without annotations to fill gaps in safety or operational context.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema descriptions (like 'Page ID' or 'Maximum attempts'), meeting the baseline for high schema coverage without providing extra value.

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 clearly states the specific action ('dismiss') and target resources ('cookie consent popups and overlays'), distinguishing it from sibling tools like click or hover that perform different browser interactions. It precisely communicates what the tool does without being vague or tautological.

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?

The description implies usage context (when cookie popups appear), but doesn't explicitly state when to use this tool versus alternatives like click (which might handle similar UI elements) or when not to use it. No specific exclusions or prerequisites are mentioned, leaving some ambiguity about optimal application scenarios.

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