HelpCenter.io

by io.helpcenter

Overview Discussions Admin

List Article Publication History

helpcenter_list_article_versions

Read-onlyIdempotent

List the archived previous versions of an article, so a past wording can be restored.

Every publish archives the version it replaced. Read-only.

Args:

article_id (number, required).
response_format ('markdown' | 'json'): default 'markdown'.

Returns: { status: "success", versions: [{ id, locale, title, created_at, ... }] }. Pass a version id to helpcenter_restore_article_version.

Only the last 20 snapshots per article per language are kept; older ones are pruned. History starts accruing when staged changes are enabled for the site, so an article published before that legitimately has an empty history — that is not an error.

Errors: 404 if the article is unknown or belongs to another help center.

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": {
      "article_id": "<article_id>"
    },
    "name": "helpcenter_list_article_versions"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`article_id`	Yes	Id of the article whose publication history to read.
`response_format`	No	Output format: 'markdown' for a human-readable summary or 'json' for the full structured payload.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: history is created by each publish, only the last 20 snapshots per article per language are retained, and history only accrues once staged changes are enabled. It also specifies the 404 condition for unknown or cross-help-center articles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose followed by clearly labeled Returns and Errors sections; the retention and empty-history notes are high-value sentences. The Args block is largely redundant given full schema coverage and could be dropped without loss.

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?

Covers return shape, the follow-up tool for restoration, retention limits, the legitimate empty-history scenario, and the 404 case — everything an agent needs to call this correctly and interpret an empty result, even without an output schema.

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 each parameter already carries its own description, so the Args block mainly restates article_id and the response_format default. Notably the description omits site_id, the one parameter with non-obvious multi-help-center semantics, leaving that entirely to the schema.

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 ("List the archived previous versions of an article") plus the intent behind it (restoring past wording). This clearly separates it from helpcenter_list_articles (current articles) and helpcenter_restore_article_version (the mutation), so an agent can pick it without inspecting either 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?

Explicitly routes the agent forward: "Pass a version id to helpcenter_restore_article_version," and explains the empty-history case so the agent doesn't treat it as failure. It stops short of naming when to use history vs. staged-changes tools (helpcenter_get_staged_changes), so no true exclusions are given.

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?