Skip to main content
Glama

Set a brand theme's logo

set_brand_theme_logo
DestructiveIdempotent

Set a Brand Theme's logo from a public picture address (PNG, JPEG, WebP or GIF; SVG is not accepted), or remove it with logoUrl: null. Ebooks that follow the theme pick the logo up. The default theme's logo is also the public Library's: while there is a Library, changing it first 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>",
      "logoUrl": "<logoUrl>"
    },
    "name": "set_brand_theme_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
logoUrlYesA public https:// address of a PNG, JPEG, WebP or GIF logo, or null to remove the logo.
brandThemeIdYesThe Brand Theme (list_brand_themes gives ids).
confirmLiveChangeNoFor the default theme while 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.1/5.0
Behavior4/5

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

Annotations already flag this as destructive, non-read-only, idempotent and open-world; the description adds genuinely new behavior: which formats are refused, that following ebooks inherit the logo, and that the default theme's logo is simultaneously the public Library's logo, requiring a confirmLiveChange round-trip. That propagation and live-side-effect disclosure is the main value add; the description stays silent on what happens on failure or what the response body contains.

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?

Front-loaded with the core action and kept to a single dense sentence chain with zero filler. The parenthetical format list and the live-change clause make it slightly run-on, but every clause carries actionable information.

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 three-parameter mutation with no output schema, the definition covers inputs, format constraints, downstream effects on followed ebooks, and the live Library confirmation loop with its permission requirement. It does not describe the return payload or error behavior, which is 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 100%, so logoUrl, brandThemeId and confirmLiveChange are already documented, including the null-to-remove and confirm semantics. The description largely restates those, only adding the detail that SVG is rejected, which is a modest gain over the structured fields.

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 gives a precise verb and resource ('Set a Brand Theme's logo') plus the exact input form (public URL) and the inverse operation (remove via logoUrl: null). It does not explicitly differentiate itself from the adjacent set_image_from_url sibling, so an agent still has to infer which of the two URL-setting tools applies to a theme logo.

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?

It states when the tool applies, the accepted and rejected formats (PNG/JPEG/WebP/GIF, explicitly 'SVG is not accepted'), the removal path, and the exact two-step protocol for the default theme while a Library exists, including the required magnets:publish scope and the user-consent gate.

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