HelpCenter.io

Discard Design Changes

helpcenter_discard_template_changes

DestructiveIdempotent

Throw away every unpublished change in the draft and reset it to the live design. The live help center is not affected.

Irreversible for the draft: edits that were never published cannot be recovered — including ones a person made in the Template Editor. Only discard when the customer wants to start over.

Args:

etag (string, optional): refuse if the draft changed since you read it.

Returns: the reset draft's status.

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": "helpcenter_discard_template_changes"
  }
}

Input Schema

Name	Required	Description	Default
`etag`	No	Optimistic lock: the draft etag from your last read, or the one your last edit returned. When given, the call is refused (stale_draft) if someone changed the draft since — so you never build on a state you have not seen. Omit to apply to the current draft.
`site_id`	No	Which help center to act on: an id from helpcenter_list_sites. Needed when this connection reaches more than one help center; omit it when it reaches one. Applies to this call only — pass it on every call of a task, and ask the user which help center they mean if their request does not say.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description correctly reinforces rather than restates them by naming exactly what is destroyed: unpublished draft edits, including Template Editor work that cannot be recovered. It also usefully bounds the blast radius with "The live help center is not affected." Remaining gaps are minor — no note on permissions or whether a prior version can be restored by other means.

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?

Front-loads the effect in the first sentence, then the safety boundary, then the irreversibility warning. The optional Args and Returns lines are terse and earn their place; nothing is redundant with the annotations.

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?

Covers effect, scope, irreversibility, the etag lock rationale, and a return hint (reset draft status) even though no output schema exists. The one meaningful omission is routing guidance relative to the closely related discard_staged_changes sibling in a 70+ tool namespace.

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%, and the schema descriptions for etag and site_id are already rich (stale_draft refusal semantics, multi-site routing). The description only restates etag's role in one clause, adding essentially nothing beyond the schema. Baseline 3 is appropriate when structured fields carry the parameter burden.

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 concrete verb and resource: "Throw away every unpublished change in the draft and reset it to the live design." An agent immediately knows the effect and the scope (draft only). It does not, however, distinguish itself from the near-identical sibling helpcenter_discard_staged_changes, so an agent choosing between the two gets no help.

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 a clear eligibility condition — "Only discard when the customer wants to start over" — plus an explicit irreversibility warning that supports a confirmation step. It stops short of naming an alternative tool (e.g. publish or staged-change discard) for the case where the caller does not want to start over.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HelpCenter.io tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?