Skip to main content
Glama

Make a brand theme the default

make_default_brand_theme
DestructiveIdempotent

Make a Brand Theme the workspace's default: new ebooks use it, and so do the public Library, its guide pages and the emails new leads receive. Only the workspace owner can change it. While there is a public Library the first call returns the change; repeat with confirmLiveChange: true after the user agrees (needs magnets:publish).

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": {
      "brandThemeId": "<brandThemeId>"
    },
    "name": "make_default_brand_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandThemeIdYesThe Brand Theme to make the default (list_brand_themes gives ids).
confirmLiveChangeNoWhile there is a public Library: call first without it, then with true after the user agrees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint and openWorldHint, and the description adds the specifics those hints cannot: exactly which surfaces are affected (ebooks, Library, guide pages, outgoing lead emails), who is authorized, and the required scope. It also explains the unusual two-call confirmation behavior, which is the highest-risk aspect of the tool.

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?

Two sentences, front-loaded with the core action and its effects, then the authorization and confirmation mechanics. The first sentence is a dense clause chain, but no sentence is filler and nothing could be cut without losing behavioral detail.

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?

No output schema exists, yet the description still tells the agent what the first call returns. Combined with authorization, scope requirements, and the full set of downstream surfaces affected by a destructive default change, an agent has everything needed to invoke this correctly.

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 both parameters are already documented and the baseline is 3. The description still adds value by framing confirmLiveChange as a second-call gate whose first call 'returns the change,' clarifying the observable outcome of the two-step flow rather than just restating the field.

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?

Specific verb+resource ('Make a Brand Theme the workspace's default') immediately followed by the concrete blast radius: new ebooks, the public Library, guide pages, and lead emails. That effect list distinguishes it from update_brand_theme or set_brand_theme_logo, which alter a theme rather than designate the workspace-wide default.

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?

Explicit preconditions and sequencing: owner-only, and a two-step flow while a public Library exists (first call, then repeat with confirmLiveChange: true after the user agrees), plus the magnets:publish requirement. An agent knows both when it may call and how to sequence the calls without inference.

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