Skip to main content
Glama

CookiePilot – cookie banner & Consent Mode v2

Scan the website for cookies

scan_cookies
Idempotent

Runs CookiePilot's cookie scan of a website on the confirmed account (public pages, no JavaScript) and returns the cookie declaration: cookies by consent category, unclassified ones and a panel link. Takes up to a minute.

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

Input Schema

NameRequiredDescriptionDefault
hostnameNoWebsite hostname, e.g. example.com; defaults to the website added last (or given to create_account)
setup_tokenYessetup_token returned by create_account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses meaningful scan limitations (public pages only, no JavaScript) and a latency expectation of up to a minute, plus the shape of the result. It does not say what happens on failure or whether a rescan overwrites prior data, keeping it short of a 5.

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?

Two sentences, front-loaded with the action and scope, then the return payload and duration. Every clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description carries the return-value burden and does it well by naming the cookie declaration parts. It is nearly complete for a two-parameter scan tool, missing only error or retry behavior.

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 coverage is 100%, so hostname and setup_token are already fully documented, including the 'defaults to the website added last' behavior. The description adds only the phrase 'on the confirmed account', which does not deepen parameter meaning beyond the schema.

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?

Names a specific verb and resource ('Runs CookiePilot's cookie scan of a website') and scopes it to the confirmed account, public pages, no JavaScript. It does not explicitly distinguish itself from siblings like analyze_site or verify_installation, so an agent must infer the boundary from the word 'cookie'.

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?

'On the confirmed account' and the required setup_token imply the prerequisite that create_account must run first, and 'Takes up to a minute' signals a slow call. There is no explicit when-to-use versus analyze_site or verify_installation, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources