switch

Save Brand Kit

save_brand_kit

Idempotent

Save your brand kit, or change one you already have: the brand's name, its colors, its fonts, light or dark as the usual look, a few words on how the brand sounds, a folder in your library, and its logos and pictures. Logos and pictures are pictures from your own Switch library, passed by their asset ids from list_my_assets or search_my_library; a file the person has not added yet goes in first with upload_media, then its returned asset id goes here. Saving with the name of a kit you already have updates that kit, and only the parts you pass change (a list you pass replaces that list). Your first kit becomes your default. Up to 24 colors, 12 fonts, 12 logos and 60 pictures per kit. Free.

Input Schema

Name	Required	Description
`name`	No	The brand name, up to 80 letters. Required for a new kit; with an existing name it updates that kit.
`fonts`	No	The brand fonts.
`colors`	No	The brand colors, most important first.
`folder`	No	Optional. One of your library folders by name or id; a new name makes a brand folder.
`kit_id`	No	Optional. The id of one of your kits to update, from list_brand_kits (lets you rename it).
`team_id`	No	Optional. Which of your teams sees a shared kit, when you are on more than one.
`website`	No	Optional. The brand's own website the kit was read from, a full https address.
`is_default`	No	Optional. true makes this your default kit.
`personality`	No	Optional. One line on how the brand feels, up to 200 letters, e.g. "Bright and playful: a juicy pour and bold type".
`voice_notes`	No	Optional. How the brand sounds in words, up to 2000 letters in total, e.g. "warm, short sentences, no slang". Keep it to the voice; a long brand guide belongs in a file.
`default_mode`	No	The usual look: light (white) or dark.
`motion_notes`	No	Optional. How the brand moves in video, up to 300 letters, e.g. "a juicy pour and bold type".
`logo_asset_ids`	No	Asset ids of the logos, from your own library.
`share_with_team`	No	Optional. true lets your team see this kit; false keeps it yours alone.
`picture_asset_ids`	No	Asset ids of the brand pictures, from your own library.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / motion_notes

Added value: +{
+  "description": "Optional. How the brand moves in video, up to 300 letters, e.g. \"a juicy pour and bold type\".",
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / personality

Added value: +{
+  "description": "Optional. One line on how the brand feels, up to 200 letters, e.g. \"Bright and playful: a juicy pour and bold type\".",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / website

Added value: +{
+  "description": "Optional. The brand's own website the kit was read from, a full https address.",
+  "maxLength": 300,
+  "type": "string"
+}

Changed6 schema fields changedOct 23, 2026

addedInput schema / properties / colors / maxItems
```
Added value: +24
```
addedInput schema / properties / fonts / maxItems
```
Added value: +12
```

changedInput schema / properties / name / description

Previous value: -"The brand name. Required for a new kit; with an existing name it updates that kit."New value: +"The brand name, up to 80 letters. Required for a new kit; with an existing name it updates that kit."

addedInput schema / properties / name / maxLength
```
Added value: +80
```

changedInput schema / properties / voice_notes / description

Previous value: -"Optional. How the brand sounds in words, e.g. \"warm, short sentences, no slang\"."New value: +"Optional. How the brand sounds in words, up to 2000 letters in total, e.g. \"warm, short sentences, no slang\". Keep it to the voice; a long brand guide belongs in a file."

addedInput schema / properties / voice_notes / maxLength
```
Added value: +2000
```

AddedOct 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: partial-update semantics ("only the parts you pass change", lists replace wholesale), hard caps (24 colors, 12 fonts, 12 logos, 60 pictures), first-kit-becomes-default, and cost ("Free"). The annotations already declare idempotent/non-destructive, so this is solid added context rather than the full burden.

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?

The core upsert rule and limits are front-loaded and each clause carries information. It is a single dense run-on paragraph, which makes it slightly harder to scan than a bulleted or sentence-split version, but there's little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter, zero-required mutation tool with no output schema, the definition still covers limits, update semantics, asset sourcing, defaults, and billing. An agent has enough to call it correctly on the first attempt.

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 still earns a bump by explaining that folder names create folders, kit_id enables renaming, and asset ids must come from the library or upload_media. It doesn't cover every one of the 15 params (e.g. team_id, share_with_team, motion_notes), so not a 5.

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+resource (save/update a brand kit) and immediately enumerates the fields it owns. An agent can distinguish it from get_brand_kit and list_brand_kits without opening a 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 explains the upsert rule ("saving with the name of a kit you already have updates that kit"), routes asset-id sourcing to list_my_assets / search_my_library, and sends not-yet-uploaded files through upload_media first. That is when-to-use plus the alternative path, spelled out.

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

All switch tools Inspect

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

Need Help?