HelpCenter.io

List Design Versions

helpcenter_list_template_versions

Read-onlyIdempotent

List the help center's published design versions, newest first, marking the one that is live — with when, by whom and the publish note.

Use it to find a version to bring back with helpcenter_restore_template_version.

Args:

response_format ('markdown' | 'json'): default 'markdown'.

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_list_template_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.
`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.1/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description's job is to add context beyond safety — and it does, disclosing ordering (newest first), that the live version is flagged, and the per-entry metadata returned. That is meaningful return-shape information for a tool with no output schema; only pagination/volume behavior is left unstated.

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?

Two tight, front-loaded sentences deliver purpose, ordering, return contents, and the follow-up tool. The appended Args block duplicates the schema's response_format documentation and could be dropped, but the overall size is proportionate.

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 two-parameter read tool with a fully documented schema and no output schema, the description covers purpose, ordering, returned fields, and the natural next action. The only residual gap is volume/pagination expectations when many versions exist.

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% and the site_id description already covers the multi-site rule and per-call persistence, so the schema carries the semantics. The description restates response_format's enum and default without adding meaning, which is redundant rather than helpful — baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('List the help center's published design versions') and adds distinguishing detail: newest-first ordering, which entry is marked live, and the metadata included (when, by whom, publish note). An agent can tell this apart from helpcenter_get_template or helpcenter_list_template_themes without opening a 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?

It explicitly states the reason to call it — 'find a version to bring back with helpcenter_restore_template_version' — which is a genuine when-to-use plus named follow-up tool. It stops short of any when-not-to-use guidance (e.g., use get_template to inspect the current live design), so it is not a full 5.

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?