Skip to main content
Glama
Sign In

CookieYes

by com.cookieyes
OverviewDiscussionsAdmin

Update banner colours

update_banner_colours
Idempotent

Update the theme or colour scheme of the CookieYes cookie consent banner for a website. Changes are automatically published live. If the user wants a full theme change, present FOUR options: Light, Dark, Auto-generated, or manual custom colours. Use 'theme=light' or 'theme=dark' for preset themes, and use 'theme=recommended' for the Auto-generated option from the dashboard. If the user chooses manual custom colours, do NOT offer only a short generic list. Offer the actual colourable elements for that law. GDPR manual-colour options: banner background, banner border, title text, body text, Accept button, Reject button, Customise button, Cookie Policy link, Preference Center toggle enabled, Preference Center toggle disabled, Save My Preferences button, Google Privacy link, Revisit Consent button, Blocked Content background, Blocked Content border, Blocked Content text. CCPA manual-colour options: banner background, banner border, title text, body text, Do Not Sell link, opt-out checkbox enabled, opt-out checkbox disabled, Cancel button, Save My Preferences button, Revisit Consent button, Blocked Content background, Blocked Content border, Blocked Content text. When the user picks a button or link, ask which parts to change if needed: background, border, text. Any individual colour edit automatically saves the banner theme as custom. When presenting results, refer to the banner by its law (GDPR/CCPA), not by ID. All colour values sent to this tool must be in hex format: #fff or #ffffff. If the user provides a colour in any other format (name, rgb, rgba, hsl), convert it to hex before calling this tool. PLAN CHECK: Before offering theme or colour options, check the website's plan from list_domains. If the website is on a Free plan, only offer Light and Dark themes — do NOT offer Auto-generated or manual custom colours, as these require a paid plan. Inform the user that custom colours are available on paid plans. IMPORTANT: Before making any changes, ALWAYS ask the user to confirm: (1) which website if they have multiple domains, (2) which banner (GDPR, CCPA, or both) they want to update. NEVER assume or auto-select banners. Even if there is only one website or one banner, confirm with the user before proceeding. NEVER update multiple banners in a single action without explicit user approval for each one.

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": {
      "websiteId": "<websiteId>",
      "bannerId": "<bannerId>"
    },
    "name": "update_banner_colours"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoTheme option. Present these user-facing choices as Light, Dark, Auto-generated, or manual custom colours. Use 'recommended' for Auto-generated. 'custom' means keep the current base theme but save individual colour edits as a custom theme.
bannerIdYesBanner ID — get from list_banners first
websiteIdYesNumeric website ID from list_domains — not the website URL or key
titleColorNoBanner title text colour.
acceptButtonBgNoGDPR only — Accept button background colour. Also updates the preference center Accept button.
cancelButtonBgNoCCPA only — Cancel button background colour.
rejectButtonBgNoGDPR only — Reject button background colour. Also updates the preference center Reject button.
revisitButtonBgNoRevisit Consent floating button background colour.
acceptButtonTextNoGDPR only — Accept button text colour. Also updates the preference center Accept button.
bannerBackgroundNoBanner background colour. Mirrors the frontend and also updates the GDPR preference center and the CCPA opt-out popup container background.
blockedContentBgNoBlocked-content placeholder background colour.
cancelButtonTextNoCCPA only — Cancel button text colour.
descriptionColorNoMessage/body text colour. Mirrors the frontend fan-out and updates the related GDPR preference center text, category text, IAB/DMA text, and CCPA opt-out text elements.
rejectButtonTextNoGDPR only — Reject button text colour. Also updates the preference center Reject button.
bannerBorderColorNoBanner border colour. Mirrors the frontend and also updates the GDPR preference center and the CCPA opt-out popup container border.
customiseButtonBgNoGDPR only — Customise button background colour.
doNotSellLinkTextNoCCPA only — Do Not Sell link text colour.
blockedContentTextNoBlocked-content placeholder text colour.
cookiePolicyLinkBgNoGDPR only — Cookie Policy link background colour.
optOutSaveButtonBgNoCCPA only — Save My Preferences button background colour in the opt-out center.
customiseButtonTextNoGDPR only — Customise button text colour.
googlePrivacyLinkBgNoGDPR only — Google Privacy link background colour.
cookiePolicyLinkTextNoGDPR only — Cookie Policy link text colour.
optOutSaveButtonTextNoCCPA only — Save My Preferences button text colour in the opt-out center.
googlePrivacyLinkTextNoGDPR only — Google Privacy link text colour.
acceptButtonBorderColorNoGDPR only — Accept button border colour. Also updates the preference center Accept button.
cancelButtonBorderColorNoCCPA only — Cancel button border colour.
optOutCheckboxEnabledBgNoCCPA only — Opt-out checkbox enabled-state background colour.
rejectButtonBorderColorNoGDPR only — Reject button border colour. Also updates the preference center Reject button.
savePreferencesButtonBgNoGDPR only — Save My Preferences button background colour. Also updates the category preview save button.
optOutCheckboxDisabledBgNoCCPA only — Opt-out checkbox disabled-state background colour.
blockedContentBorderColorNoBlocked-content placeholder border colour.
savePreferencesButtonTextNoGDPR only — Save My Preferences button text colour. Also updates the category preview save button.
customiseButtonBorderColorNoGDPR only — Customise button border colour.
cookiePolicyLinkBorderColorNoGDPR only — Cookie Policy link border colour.
optOutSaveButtonBorderColorNoCCPA only — Save My Preferences button border colour in the opt-out center.
googlePrivacyLinkBorderColorNoGDPR only — Google Privacy link border colour.
preferenceCenterToggleEnabledBgNoGDPR only — Preference Center toggle enabled-state background colour. Also updates category preview and IAB toggle enabled-state colours.
preferenceCenterToggleDisabledBgNoGDPR only — Preference Center toggle disabled-state background colour. Also updates category preview and IAB toggle disabled-state colours.
savePreferencesButtonBorderColorNoGDPR only — Save My Preferences button border colour. Also updates the category preview save button.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses that changes are automatically published live, that custom theme edits are saved automatically, that Free plans cannot use Auto-generated or manual custom colours, and that all colours must be converted to hex before calling. These are substantive behavioral details for a live mutation tool.

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

Conciseness3/5

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

The purpose is front-loaded and the law-specific colour lists are useful, but the description is very long and repeats several confirmation and non-auto-selection instructions. It is adequate for a 40-parameter tool, though tighter structuring would improve readability.

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?

Given the tool's complexity and large schema, the description covers the key operational concerns: plan gating, theme choices, law-specific manual colour elements, hex conversion, and confirmation requirements. It does not describe success or error responses, but otherwise provides enough context for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning by mapping user-facing theme names to enum values such as theme=recommended for Auto-generated, explaining that custom means individual colour edits under the current base theme, and specifying hex formatting.

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 states a specific verb and resource: updating the theme or colour scheme of the CookieYes consent banner for a website. This is clearly distinct from layout changes, although it does not explicitly name update_banner_layout as the alternative for non-colour banner changes.

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

Usage Guidelines5/5

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

It gives explicit usage rules: check the website plan from list_domains, restrict Free-plan users to Light and Dark themes, confirm the website and banner before acting, and never update multiple banners without approval. These conditions make it clear when to use the tool and when not to offer paid/custom options.

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

All CookieYes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources