Skip to main content
Glama

Create brand kit

create_brand_kit
Destructive

Create a brand kit by hand in the user's active space from what the user gave. Only name is required; colors, fonts and radius left out start from the YouSpot kit. Logos are uploaded on the kit's page. To import a brand from a website use extract_brand_kit instead. Returns the brand_kit_id.

Input Schema

NameRequiredDescriptionDefault
nameYesThe brand name.
fontsNo
colorsNoHex colors (#rrggbb). Any left out keep their current value.
domainNoThe brand website host, like acme.com.
radiusNoCorner radius in px, rem or em, like 8px.
dark_modeNo
documentsNoHow this brand lays out PDFs. Any left out use the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / fonts / properties / body / enum
      Previous value: -[
      -  "Archivo",
      -  "Barlow",
      -  "Bebas Neue",
      -  "Bricolage Grotesque",
      -  "Cormorant Garamond",
      -  "Crimson Text",
      -  "DM Sans",
      -  "DM Serif Display",
      -  "EB Garamond",
      -  "Figtree",
      -  "Fira Code",
      -  "Fraunces",
      -  "Geist",
      -  "Georgia",
      -  "IBM Plex Mono",
      -  "IBM Plex Sans",
      -  "Inter",
      -  "JetBrains Mono",
      -  "Karla",
      -  "Lato",
      -  "Libre Baskerville",
      -  "Lora",
      -  "Manrope",
      -  "Merriweather",
      -  "Montserrat",
      -  "Mulish",
      -  "Newsreader",
      -  "Nunito",
      -  "Open Sans",
      -  "Oswald",
      -  "Outfit",
      -  "PT Serif",
      -  "Playfair Display",
      -  "Plus Jakarta Sans",
      -  "Poppins",
      -  "Raleway",
      -  "Roboto",
      -  "Rubik",
      -  "Sora",
      -  "Source Sans 3",
      -  "Space Grotesk",
      -  "Urbanist",
      -  "Work Sans",
      -  "system-ui"
      -]New value: +[
      +  "Albert Sans",
      +  "Archivo",
      +  "Arimo",
      +  "Assistant",
      +  "Barlow",
      +  "Bebas Neue",
      +  "Bricolage Grotesque",
      +  "Cabin",
      +  "Cal Sans",
      +  "Cormorant Garamond",
      +  "Crimson Text",
      +  "DM Sans",
      +  "DM Serif Display",
      +  "EB Garamond",
      +  "Exo 2",
      +  "Figtree",
      +  "Fira Code",
      +  "Fraunces",
      +  "Funnel Display",
      +  "Geist",
      +  "Georgia",
      +  "Golos Text",
      +  "Heebo",
      +  "Hind",
      +  "IBM Plex Mono",
      +  "IBM Plex Sans",
      +  "Instrument Sans",
      +  "Instrument Serif",
      +  "Inter",
      +  "JetBrains Mono",
      +  "Josefin Sans",
      +  "Kanit",
      +  "Karla",
      +  "Lato",
      +  "League Spartan",
      +  "Lexend",
      +  "Libre Baskerville",
      +  "Libre Caslon Text",
      +  "Lora",
      +  "Manrope",
      +  "Merriweather",
      +  "Merriweather Sans",
      +  "Montserrat",
      +  "Mulish",
      +  "Newsreader",
      +  "Noto Sans",
      +  "Nunito",
      +  "Onest",
      +  "Open Sans",
      +  "Oswald",
      +  "Outfit",
      +  "PT Serif",
      +  "Playfair Display",
      +  "Plus Jakarta Sans",
      +  "Poppins",
      +  "Public Sans",
      +  "Quicksand",
      +  "Raleway",
      +  "Red Hat Display",
      +  "Roboto",
      +  "Rubik",
      +  "Sanchez",
      +  "Sora",
      +  "Source Sans 3",
      +  "Space Grotesk",
      +  "Syne",
      +  "Titillium Web",
      +  "Urbanist",
      +  "Work Sans",
      +  "system-ui"
      +]
    • changedInput schema / properties / fonts / properties / heading / enum
      Previous value: -[
      -  "Archivo",
      -  "Barlow",
      -  "Bebas Neue",
      -  "Bricolage Grotesque",
      -  "Cormorant Garamond",
      -  "Crimson Text",
      -  "DM Sans",
      -  "DM Serif Display",
      -  "EB Garamond",
      -  "Figtree",
      -  "Fira Code",
      -  "Fraunces",
      -  "Geist",
      -  "Georgia",
      -  "IBM Plex Mono",
      -  "IBM Plex Sans",
      -  "Inter",
      -  "JetBrains Mono",
      -  "Karla",
      -  "Lato",
      -  "Libre Baskerville",
      -  "Lora",
      -  "Manrope",
      -  "Merriweather",
      -  "Montserrat",
      -  "Mulish",
      -  "Newsreader",
      -  "Nunito",
      -  "Open Sans",
      -  "Oswald",
      -  "Outfit",
      -  "PT Serif",
      -  "Playfair Display",
      -  "Plus Jakarta Sans",
      -  "Poppins",
      -  "Raleway",
      -  "Roboto",
      -  "Rubik",
      -  "Sora",
      -  "Source Sans 3",
      -  "Space Grotesk",
      -  "Urbanist",
      -  "Work Sans",
      -  "system-ui"
      -]New value: +[
      +  "Albert Sans",
      +  "Archivo",
      +  "Arimo",
      +  "Assistant",
      +  "Barlow",
      +  "Bebas Neue",
      +  "Bricolage Grotesque",
      +  "Cabin",
      +  "Cal Sans",
      +  "Cormorant Garamond",
      +  "Crimson Text",
      +  "DM Sans",
      +  "DM Serif Display",
      +  "EB Garamond",
      +  "Exo 2",
      +  "Figtree",
      +  "Fira Code",
      +  "Fraunces",
      +  "Funnel Display",
      +  "Geist",
      +  "Georgia",
      +  "Golos Text",
      +  "Heebo",
      +  "Hind",
      +  "IBM Plex Mono",
      +  "IBM Plex Sans",
      +  "Instrument Sans",
      +  "Instrument Serif",
      +  "Inter",
      +  "JetBrains Mono",
      +  "Josefin Sans",
      +  "Kanit",
      +  "Karla",
      +  "Lato",
      +  "League Spartan",
      +  "Lexend",
      +  "Libre Baskerville",
      +  "Libre Caslon Text",
      +  "Lora",
      +  "Manrope",
      +  "Merriweather",
      +  "Merriweather Sans",
      +  "Montserrat",
      +  "Mulish",
      +  "Newsreader",
      +  "Noto Sans",
      +  "Nunito",
      +  "Onest",
      +  "Open Sans",
      +  "Oswald",
      +  "Outfit",
      +  "PT Serif",
      +  "Playfair Display",
      +  "Plus Jakarta Sans",
      +  "Poppins",
      +  "Public Sans",
      +  "Quicksand",
      +  "Raleway",
      +  "Red Hat Display",
      +  "Roboto",
      +  "Rubik",
      +  "Sanchez",
      +  "Sora",
      +  "Source Sans 3",
      +  "Space Grotesk",
      +  "Syne",
      +  "Titillium Web",
      +  "Urbanist",
      +  "Work Sans",
      +  "system-ui"
      +]
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • addedInput schema / properties / documents
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "How this brand lays out PDFs. Any left out use the default.",
      +  "properties": {
      +    "accent": {
      +      "enum": [
      +        "band",
      +        "line",
      +        "none"
      +      ],
      +      "type": "string"
      +    },
      +    "body_size": {
      +      "enum": [
      +        "small",
      +        "regular",
      +        "large"
      +      ],
      +      "type": "string"
      +    },
      +    "density": {
      +      "enum": [
      +        "compact",
      +        "comfortable",
      +        "spacious"
      +      ],
      +      "type": "string"
      +    },
      +    "footer_text": {
      +      "description": "The footer line on every page. Empty string for no footer; left out it is the brand name.",
      +      "type": "string"
      +    },
      +    "heading_scale": {
      +      "enum": [
      +        "small",
      +        "regular",
      +        "large"
      +      ],
      +      "type": "string"
      +    },
      +    "orientation": {
      +      "enum": [
      +        "portrait",
      +        "landscape"
      +      ],
      +      "type": "string"
      +    },
      +    "page_numbers": {
      +      "enum": [
      +        "on",
      +        "off"
      +      ],
      +      "type": "string"
      +    },
      +    "page_size": {
      +      "enum": [
      +        "letter",
      +        "a4"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only flag readOnlyHint=false and destructiveHint=true; the description adds substantive behavior beyond that – omitted colors/fonts/radius inherit the YouSpot kit defaults, logos are handled post-creation, and the return value is brand_kit_id. It does not explain why destructiveHint is true or what could be overwritten, which is the remaining gap.

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?

Four short sentences, all load-bearing: purpose and scope first, then the only-required-param and defaults rule, then the logo caveat, then the alternative routing. Nothing repeated.

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 7-parameter, nested-object mutation with no output schema, it covers the required-vs-optional split, defaults, and the return value. It leaves minor uncertainty around destructiveHint=true (e.g. whether an existing kit is overwritten) and how dark_mode/documents defaults resolve.

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 71% and documented fields (colors, domain, radius, footer_text, documents) already carry their own meaning. The description adds the defaulting rule for omitted fields ('left out start from the YouSpot kit'), which is genuinely beyond the schema, though dark_mode and documents inheritance are only implied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb plus resource ('Create a brand kit') and scopes it ('by hand in the user's active space'), immediately separating it from the website-import sibling. An agent can distinguish it from extract_brand_kit without opening either schema.

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?

Explicitly routes the alternative: 'To import a brand from a website use extract_brand_kit instead.' It also notes logos are not a creation parameter but are uploaded on the kit's page, closing the obvious follow-up question.

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.