Skip to main content
Glama

Continue Brand Edit

continue_brand_edit
Idempotent

Continue a pending brand edit by submitting its requested selection, answer, evidence, or decline. Use this only when native MCP input is unavailable or cannot represent the response. This resumes draft preparation without changing the active brand; follow the input channels and limits advertised by the pending interaction.

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>",
      "interaction_id": "<interaction_id>",
      "response": "<response>"
    },
    "name": "continue_brand_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
edit_idYesUse edit_id returned by create_brand_edit to identify the Brand Edit draft.
responseYes
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.
interaction_idYesID of the pending interaction being answered. Use the current interaction ID returned by get_brand_edit.
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.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false but destructiveHint=false, which is ambiguous on its own; the description resolves it by stating the call advances draft preparation 'without changing the active brand'. That is real added context beyond the annotation block. It stops short of saying what happens on a rejected or expired interaction, but the safety profile is meaningfully clarified.

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 with no filler, ordered purpose first, then gating condition, then behavioral constraint and the pointer to interaction-specific limits. Nothing is repeated and nothing is missing for the length.

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 complex tool with a nested oneOf response body, the description covers what it does, when to use it, and its non-mutating-to-active-brand behavior, while the output schema handles return values. The remaining gap is lifecycle behavior, such as what a new follow-up interaction looks like or what happens to a stale interaction_id.

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?

Schema coverage is 80%, so the baseline would be 3, and the description does marginally more by naming the four response channels (selection, answer, evidence, decline) that map to the oneOf branch of the response parameter. It also points the agent at interaction-advertised limits, which explains why the schema's own caps may be overridden. It adds no guidance on brand_session_id or edit_id beyond what the schema already documents.

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?

States a specific verb (continue) and resource (a pending brand edit), and specifies the payloads accepted: selection, answer, evidence, or decline. It also draws a contrast with applying a brand edit by saying it 'resumes draft preparation without changing the active brand', so an agent can distinguish it from apply_brand_edit without opening a schema, though it never names that sibling explicitly.

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?

'Use this only when native MCP input is unavailable or cannot represent the response' is a genuine gating condition with an implied alternative. It does not name the sibling tools that supply edit_id and interaction_id (create_brand_edit, get_brand_edit), so the agent must read the schema to learn the prerequisites, but the when-to-use rule itself is clear.

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