Skip to main content
Glama

Discard Brand Edit

discard_brand_edit
DestructiveIdempotent

End a brand edit without changing the active brand. The edit's status must be preparing, input_required, or awaiting_approval; repeating the call on a discarded edit returns it again. Discarding cannot be undone: discarded edits cannot publish a candidate, so create a new edit to try the change again. Cancellation is requested for ongoing preparation, but work already in progress may finish.

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": "discard_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
Behavior5/5

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

Goes well beyond the annotations: it discloses the required status states, that repeat calls are idempotent and return the same discarded edit, that the action is irreversible, and that in-flight preparation is only cancellation-requested and may still finish. This is exactly the operational context destructiveHint and idempotentHint cannot convey.

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 tight sentences, front-loaded with the core action, then preconditions, then consequences, then the cancellation caveat. No filler or repetition 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?

An output schema exists, so return values need not be described. For a destructive, idempotent lifecycle tool the description covers preconditions, irreversibility, and partial-cancellation behavior, leaving nothing an agent needs before calling it.

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 edit_id, brand_session_id, and llm_model are already documented in the schema. The description adds no parameter-level meaning, which is acceptable given the schema does the work, but it earns no credit above baseline.

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 ('End a brand edit') plus a scope qualifier ('without changing the active brand') that separates it from apply_brand_edit and the other edit-lifecycle siblings. An agent can identify the operation without opening the schema.

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?

Gives explicit preconditions (status must be preparing, input_required, or awaiting_approval) and a clear when-not path: discarding is irreversible and a discarded edit cannot publish, so a new edit must be created. It stops short of naming apply_brand_edit as the publish alternative, leaving that inference to the agent.

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