Skip to main content
Glama

Configure banner

configure_banner
Idempotent

Update a site's cookie banner: layout (pill, bar, modal, corner), colours or preset, categories, services, Google Consent Mode v2, languages and wording. Only the fields you pass change. Pro sites can also switch geo-targeting and monthly rescans.

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": {
      "site_id": "<site_id>"
    },
    "name": "configure_banner"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
designNoBanner fields to change; nested objects merge.
domainNoChange the domain (bare domain).
site_idYesSite id from list_sites or create_site.
geo_targetingNoPro: only show the banner where consent law applies.
monthly_rescanNoPro: rescan the site automatically every month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / design / properties / wording
      Added value: +{
      +  "anyOf": [
      +    {
      +      "const": 1,
      +      "type": "number"
      +    },
      +    {
      +      "const": 2,
      +      "type": "number"
      +    }
      +  ],
      +  "description": "Built-in banner wording. 2 (new sites): the reject button is the plain opposite of accept ('Reject all', 'Alle ablehnen', 'Tout refuser', 'Alles weigeren', 'Rechazar todo', 'Rifiuta tutti') and, while the X shows, the message says that closing keeps only strictly necessary cookies; the same wording as the WordPress plugin. 1: the original texts ('Reject non-essential'), kept by sites saved before 18 Nov 2026 until this is set to 2. Texts in overrides win over either."
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / design / properties / clearX
      Added value: +{
      +  "description": "Draw the X clearly: a 44×44 px button in a colour with at least 4.5:1 contrast on the banner, labelled 'Close and reject' in the banner's language, with a focus ring. On by default for new sites; sites saved with the original small X keep it until this is set to true.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / design / properties / closeX
      Added value: +{
      +  "description": "Show an X on the banner. Closing it rejects non-essential cookies (all Consent Mode signals denied), as Italy's Garante describes. On by default for new sites.",
      +  "type": "boolean"
      +}
  4. Changed20 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / design / properties / categories / additionalProperties
      Removed value: -false
    • removedInput schema / properties / design / properties / gcm / additionalProperties
      Removed value: -false
    • removedInput schema / properties / design / properties / overrides / additionalProperties / additionalProperties
      Removed value: -false
    • addedInput schema / properties / design / properties / overrides / propertyNames / type
      Added value: +"string"
    • addedInput schema / properties / design / properties / services / propertyNames / type
      Added value: +"string"
    • removedInput schema / properties / design / properties / theme / additionalProperties
      Removed value: -false
    • removedInput schema / properties / design / properties / theme / properties / accent / $ref
      Removed value: -"#/properties/design/properties/theme/properties/bg"
    • addedInput schema / properties / design / properties / theme / properties / accent / pattern
      Added value: +"^#[0-9a-fA-F]{6}$"
    • addedInput schema / properties / design / properties / theme / properties / accent / type
      Added value: +"string"
    • removedInput schema / properties / design / properties / theme / properties / accentFg / $ref
      Removed value: -"#/properties/design/properties/theme/properties/bg"
    • addedInput schema / properties / design / properties / theme / properties / accentFg / pattern
      Added value: +"^#[0-9a-fA-F]{6}$"
    • addedInput schema / properties / design / properties / theme / properties / accentFg / type
      Added value: +"string"
    • removedInput schema / properties / design / properties / theme / properties / border / $ref
      Removed value: -"#/properties/design/properties/theme/properties/bg"
    • addedInput schema / properties / design / properties / theme / properties / border / pattern
      Added value: +"^#[0-9a-fA-F]{6}$"
    • addedInput schema / properties / design / properties / theme / properties / border / type
      Added value: +"string"
    • removedInput schema / properties / design / properties / theme / properties / fg / $ref
      Removed value: -"#/properties/design/properties/theme/properties/bg"
    • addedInput schema / properties / design / properties / theme / properties / fg / pattern
      Added value: +"^#[0-9a-fA-F]{6}$"
    • addedInput schema / properties / design / properties / theme / properties / fg / type
      Added value: +"string"
    • addedInput schema / properties / site_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive and idempotent, so the safety profile is covered; the description adds genuinely new behavior: partial patching semantics where omitted fields are untouched, and a plan gate that restricts geo-targeting and monthly rescans to Pro sites. It does not say whether the response echoes the updated banner, but with idempotentHint and destructiveHint=false already declared, this is above the annotation bar.

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 with no filler: the first front-loads the action and the editable domain, the second front-loads the key mutation semantics. Every clause carries information an agent can act on.

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?

For a 6-parameter mutation tool with deep nested objects, the description covers the editable surface, the patch semantics and the tier restrictions — enough to call it correctly. Since there is no output schema, a brief note on what is returned after a successful update, and any auth/permission requirement on the site, would close the remaining gap.

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 83%, so the schema already documents nearly every field, including rich notes on clearX, closeX, wording and preset. The description's field enumeration (layout, colours, categories, services, GCM v2, languages, wording) restates those names at a higher level and adds little syntax or meaning beyond the schema; the Pro caveats it mentions are duplicated in the schema descriptions for geo_targeting and monthly_rescan.

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 opens with a specific verb+resource ('Update a site's cookie banner') and enumerates the editable surfaces (layout, colours/preset, categories, services, GCM v2, languages, wording), which lets an agent tell this apart from get_site, list_banner_presets, or run_compliance_scan. It stops short of naming a sibling or an explicit hand-off, so it is clear but not fully differentiated.

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?

'Only the fields you pass change' establishes the tool's partial-update usage pattern, and the Pro note implies a tier prerequisite for geo-targeting and rescans. There is no explicit when-to-use vs. when-not guidance and no mention of what to do instead when the caller wants to read configuration (e.g., get_site) or just inspect presets.

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