Skip to main content
Glama

update_brand

Destructive

Change the active workspace's brand identity: its positioning, and its audience (ICP). The same two fields as the Brand identity card in Settings > Content topics. Use when the user says what the business or client is, or who it is for: "our audience is now CFOs, not founders". Each field you pass replaces what is there; one you leave out is kept; an empty string clears it. Stored as given, no AI. It changes the workspace chosen with select_workspace, and the reply names it. For how the user personally writes, use update_voice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
icpNoWho the posts are for (the ideal customer). Max 2000 characters.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
positioningNoWhat the business or client does and stands for. Max 2000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description goes well beyond them by spelling out the exact overwrite model (passed fields replace, omitted fields are kept, empty string clears) and confirming content is 'stored as given, no AI.' It also discloses the reply behavior ('the reply names it') and that the change lands on the workspace chosen via `select_workspace`, so the destructive hint is concretely explained rather than left abstract.

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, then usage trigger, then update semantics, then scoping and the sibling pointer — a logical ordering with no filler. It runs slightly long and the 'changes the workspace chosen with select_workspace' clause sits close enough to the `workspace` override parameter that a reader must slow down, but every sentence carries 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?

Only three optional parameters and no output schema, so the burden is modest, and the description covers fields, merge semantics, scope, and what the reply contains. The one gap is that all three fields are optional yet the description never says what happens on a call with no fields, a minor omission for a mutation tool.

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 coverage is 100%, so each parameter already carries its own description and the baseline is 3. The description adds real meaning the schema does not — per-field replacement versus retention and the empty-string clear — but it does not address the `workspace` override parameter or note that both fields are optional, leaving the merge behavior to be inferred from prose rather than tied to specific parameters.

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 and resource ('Change the active workspace's brand identity') and enumerates exactly which two fields are affected: positioning and ICP. It further anchors the resource to a concrete UI location ('the Brand identity card in Settings > Content topics'), which removes ambiguity about what is being edited.

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?

Gives an explicit trigger with a worked example ('our audience is now CFOs, not founders') and names the condition that selects the sibling instead: personal writing style belongs to `update_voice`. Both the when and the when-not are present, with the alternative tool named directly.

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