HelpCenter.io

Reorder a Section's FAQs

helpcenter_reorder_faq_section_articles

DestructiveIdempotent

Set the order of a custom section's FAQs. Send every FAQ it lists, each once, first first: read them with helpcenter_get_faq_section. Live on the section's pages at their next load. Needs an editor, admin or owner of the help center.

Args:

section_id (number, required).
article_ids (number[], required).

Returns: { faq_section } in the new order. Refused (nothing changed) with missing_article_ids, unlisted_article_ids and repeated_article_ids when the list is not exactly the section's.

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": {
      "section_id": "<section_id>",
      "article_ids": "<article_ids>"
    },
    "name": "helpcenter_reorder_faq_section_articles"
  }
}

Input Schema

Name	Required	Description
`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.
`section_id`	Yes	The section's id (not its key).
`article_ids`	Yes	Every FAQ the section lists, each once, first first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already flag a non-read-only, destructive, idempotent mutation, and the description adds real context beyond them: the call is all-or-nothing ("Refused (nothing changed)") with specific error payloads (missing_article_ids, unlisted_article_ids, repeated_article_ids), the effect is deferred ("Live on the section's pages at their next load"), and an authorization level is required. That is exactly the behavior an agent cannot read off the annotations.

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 the action and the ordering constraint, then auth, then a Returns line that earns its place because no output schema exists. The Args list duplicates schema text that is already 100% covered 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?

For a destructive, all-or-nothing reorder with no output schema, the description covers the pre-read step, ordering convention, authorization, failure modes with named error fields, and the shape of the success return ({ faq_section }). Nothing an agent needs to call it safely is missing.

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%, so section_id, article_ids and site_id are already documented, and the Args block largely restates them. The description does clarify intent through the error vocabulary (unlisted/repeated/missing), which explains why article_ids must be an exact permutation, but that is inference rather than added parameter syntax. Baseline 3 applies.

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?

Names a specific verb and resource ("Set the order of a custom section's FAQs") and the full-replacement semantics ("Send every FAQ it lists, each once, first first") implicitly separate it from helpcenter_add_faq_section_articles and helpcenter_remove_faq_section_article. It never names those siblings explicitly, so an agent must infer the distinction rather than being routed to it.

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 concrete prerequisite and read-first workflow ("read them with helpcenter_get_faq_section") plus the permission requirement (editor, admin or owner). It does not state when not to use this tool — e.g. that adding a single FAQ should go to helpcenter_add_faq_section_articles — which is the remaining gap.

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?