Skip to main content
Glama

Create site

create_site

Add a domain to PrivacyPill and create its cookie banner. Returns the site, its banner settings and the embed snippet. The free plan includes one site.

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": {
      "domain": "<domain>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFriendly name shown in the dashboard.
designNoOptional starting banner settings; see configure_banner for the fields.
domainYesBare domain such as example.com (no https://).
license_idNoAttach a Pro or Lifetime license from get_account.

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 / license_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 readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the write-but-non-destructive profile is covered. The description adds genuinely new behavioral context: the response payload shape (site, banner settings, embed snippet) and the plan quota limiting free accounts to one site, which affects whether a call will succeed. It stops short of describing failure modes for duplicate domains or quota exhaustion.

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?

Three short sentences with no filler: action first, return values second, constraint last. Every sentence carries distinct information and nothing is repeated from the schema.

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 correctly compensates by enumerating what the call returns, and the deeply nested design object is fully documented in the schema with a redirect to configure_banner. The gap is around error/quota behavior and idempotency semantics for an operation flagged as non-idempotent, which an agent creating sites would benefit from knowing.

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 domain, name, design and license_id are already documented in the schema, including a pointer to configure_banner for design fields. The description adds nothing parameter-specific beyond the implicit notion that a domain is required and that license_id relates to paid tiers; the quota sentence hints at licensing but does not explain the parameter's role.

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?

States a concrete verb and resource: 'Add a domain to PrivacyPill and create its cookie banner', plus what it returns (site, banner settings, embed snippet). The purpose is unambiguous and clearly a creation operation, but the description never names configure_banner or list_sites, so the reader must infer the boundary from the sibling list rather than from the text.

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?

Usage is only implied by 'Add a domain' and the quota note 'The free plan includes one site'. There is no explicit statement of when to use this versus configure_banner (which the schema points to for banner settings), and no guidance on what to do when the domain already exists or the free-plan limit is exceeded.

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