Skip to main content
Glama

Create Brand Edit

create_brand_edit
Destructive

Create a draft change to an existing brand from instructions, evidence, or exact profile changes. Preparation runs asynchronously and does not change the active brand; exact profile changes may also update related Brand Skill files. When replaces_edit_id is supplied, the existing draft is discarded only after its replacement is ready.

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>",
      "base_skill_id": "<base_skill_id>",
      "change": "<change>"
    },
    "name": "create_brand_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYes
evidenceNo
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.
base_skill_idYesCurrent version_id from get_brand
brand_session_idYesBrand to prepare this draft change for. Use its Brand session ID from list_brands.
replaces_edit_idNoEdit ID of the draft awaiting approval for the same brand and base version. That draft is discarded only after this replacement is ready.

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.6/5.0
Behavior5/5

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

Annotations already flag a destructive, non-idempotent, open-world mutation, and the description adds real context beyond them: preparation is asynchronous, the active brand is untouched, exact profile changes can also rewrite related Brand Skill files, and a replaced draft is discarded only after the new one is ready. That last point materially de-risks the destructiveHint.

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?

Three sentences, no filler, and the high-value facts (draft-only, async, replacement safety) come first. Each sentence carries distinct information an agent needs.

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?

An output schema exists, so return values need not be explained, and the mutation semantics are well covered for a six-parameter nested tool. The only gap is not saying what the agent should do next with the returned draft, but that is a routing concern rather than a call-correctness one.

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?

The schema is richly documented (67% coverage) on the nested profile-change tree, so the description correctly focuses on the two places schema text is thin: the three mutually exclusive `change` shapes and the lifecycle of `replaces_edit_id`. It does not explain `llm_model` or the evidence caps, which the schema already covers.

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 (create) and resource (draft change to an existing brand) plus the three input modes: instructions, evidence, or exact profile changes. The phrase 'draft ... does not change the active brand' separates it from apply_brand_edit without needing to name it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context for when to call it: you want a prepared draft, not a live change. The `replaces_edit_id` sentence also tells the agent when to use the replacement path. It stops short of explicitly naming apply_brand_edit or continue_brand_edit as the follow-up steps.

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