Skip to main content
Glama

Apply Brand Edit

apply_brand_edit
DestructiveIdempotent

Activate a prepared brand edit candidate. This is the operation that changes the active brand to the generated candidate. The edit must have status awaiting_approval; repeating the call on an applied edit returns it again. An edit goes stale and cannot be applied once the active brand has changed; create a new edit from the latest brand instead.

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": {
      "brand_session_id": "<brand_session_id>",
      "edit_id": "<edit_id>"
    },
    "name": "apply_brand_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
edit_idYesUse edit_id returned by create_brand_edit to identify the Brand Edit draft.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
brand_session_idYesBrand session ID from `list_brands` for the brand being edited.

Output Schema

NameRequiredDescriptionDefault
errorYes
statusYes
targetYes
edit_idYes
change_setYesDifferences between the base Brand Skill and the prepared candidate, or null before a candidate exists.
created_atYes
updated_atYes
interactionYesThe current request for user input, or null when no response is requested.
replacementYes
base_skill_idYes
change_summaryYesA summary of the candidate's proposed changes, or null when no summary is available.
status_messageYesAn explanation of the edit's current status; a prepared candidate does not change the active brand until applied.
target_profileYesThe candidate's brand profile, which becomes active only on Apply, or null before a candidate exists.
brand_session_idYes
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false; the description adds real state-machine context (precondition status, repeat-call behavior, staleness failure mode and remedy). What it omits is the consequence for the previously active brand — whether it is versioned/restorable — which matters for a destructive mutation, so it falls short of a 5.

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, front-loaded with the action and its effect before the precondition, idempotency note and staleness remedy. No filler or restatement of the title.

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?

Return values are covered by the output schema and safety profile by annotations, so the description only needs the lifecycle rules — precondition, repeat behavior, staleness — and it supplies all three. Nothing an agent needs in order to call this correctly is missing.

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%, with edit_id, brand_session_id and llm_model all documented inline, so the schema carries the parameter burden. The description adds only the implicit linkage (the edit must be awaiting_approval, produced by create_brand_edit) rather than any syntax or format guidance, which is the expected baseline 3.

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 ('Activate a prepared brand edit candidate') and clarifies the effect precisely: 'This is the operation that changes the active brand to the generated candidate.' That effect statement cleanly separates it from create/continue/discard siblings without needing to name them.

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 precondition ('must have status awaiting_approval') and an explicit when-not with a remedy: an edit goes stale once the active brand has changed, in which case 'create a new edit from the latest brand instead.' The repeat-call case is also addressed, so an agent has a full decision rule.

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