Skip to main content
Glama
Sign In

HelpCenter.io

by io.helpcenter
OverviewDiscussionsAdmin

Create HelpCenter Category

helpcenter_create_category

Create a category in the HelpCenter.io help center bound to your API key.

Requires a write-scoped API key. This is what lets you build a help center's structure rather than only fill it in: create the categories first, then file articles into them with helpcenter_create_article's category_id.

Args:

  • name (object, required): per-language category name, e.g. { "en": "Billing" }. Every key must be a language enabled on this help center.

  • description (object, optional): per-language description.

  • parent_id (number, optional): parent category id, for nesting. Omit or pass 0 for a top-level category.

  • icon (string, optional): icon identifier, max 190 chars.

  • position (number, optional): sibling order, ascending. Omit to place the category after everything already arranged.

Returns: { status: "success", category: {...} } with the new id, 201.

Categories are created public. Privacy (unlisted, team-only, private) stays a dashboard setting, because a private category with no shares would be invisible to everyone including its author.

Errors: 403 if the key is read-scoped; 422 for a language the help center does not have, or a parent_id outside it.

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

Input Schema

NameRequiredDescriptionDefault
iconNoIcon identifier for the category (max 190 chars).
nameYesPer-language category name, e.g. { "en": "Billing" }. Required.
site_idNoWhich 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.
positionNoSibling order, ascending. Omit to place the category after everything already arranged.
parent_idNoId of the parent category, for nesting. Must belong to this site. Use 0 or omit for a top-level category.
descriptionNoPer-language category description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so mutability and non-idempotency are covered. The description goes beyond that with auth requirements, the 403/403/422 error conditions, the 201 return shape, and the default position behavior. The one substantive gap is that it never explains the rationale-adjacent behavior of what happens on duplicate names or how the created category relates to staged change sets, which matters in a help center product with staging siblings.

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, then prerequisites, then a structured Args/Returns/Errors layout that is easy to scan. The Args block largely duplicates field descriptions already present in the schema at 100% coverage, so a few lines do not earn their place, though the overall shape is disciplined.

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?

No output schema exists, yet the description supplies the return shape and status code, and it covers auth, validation failure modes, and nesting defaults. For a single-required-parameter create call, an agent has everything needed to invoke it correctly.

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 100%, so the baseline is 3, and the description mostly restates the schema's field docs. It does add real meaning in one place: every key in the per-language name object must be a language enabled on this help center, which is the direct cause of the documented 422. The site_id parameter, the most consequential one for multi-site connections, is not mentioned at all.

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 (Create) and resource (a category in the HelpCenter.io help center) and scopes it to the bound API key. It also distinguishes the action from sibling writes by placing it in the content-structure workflow: create the category first, then file articles into it via helpcenter_create_article's category_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when this tool is the right one (building a help center's structure rather than only filling it in) and names the downstream tool that consumes its output. It also gives an explicit exclusion — privacy (unlisted, team-only, private) cannot be set here and stays a dashboard setting — plus a hard prerequisite (write-scoped API key).

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

All HelpCenter.io toolsInspect
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