Skip to main content
Glama

CookiePilot – cookie banner & Consent Mode v2

List the websites on the user's CookiePilot account

list_domains
Read-onlyIdempotent

Returns the plan, the website limit and how much of it is used, and every website on the confirmed account with whether its banner is published and its installation verified.

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": "list_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
setup_tokenYessetup_token returned by create_account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the return contents (plan, quota usage, per-site banner and installation state) and the 'confirmed account' constraint. It omits error behavior for unconfirmed accounts and whether the list is paginated, so it only partially goes beyond the annotations.

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 well-formed sentence that front-loads the return payload rather than the mechanics. It is dense but every clause describes a real attribute of the response, with no filler padding.

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 and only one parameter, the description's chief job is to explain what comes back, and it does so item by item. Remaining gaps are minor: pagination/ordering, behavior for an unconfirmed token, and the empty-list case.

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% and the single setup_token parameter is documented in-schema as coming from create_account, so the schema carries the load. The description never refers to setup_token, adds no scope or format meaning for it, and thus contributes nothing beyond structured data.

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 uses a specific verb ('Returns') and enumerates the resource contents: plan, website limit and usage, plus every website with banner-published and installation-verified flags. This is clearly a listing/read tool and goes well beyond restating the title. It stops short of distinguishing itself from the sibling check_account_status, which likely also surfaces plan information.

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?

There is no explicit when-to-use guidance, no mention of when not to use it, and no named alternative such as check_account_status for status-only queries. The phrase 'the confirmed account' faintly implies the account must exist and be confirmed first, but no prerequisite is stated outright.

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