HelpCenter.io

Delete an FAQ Section

helpcenter_delete_faq_section

DestructiveIdempotent

Delete an FAQ section. Pages that still carry its snippet show nothing in its place. The FAQ articles themselves are kept. Only when the user asks for it. Needs an admin or owner of the help center.

Args:

section_id (number, required).

Returns: { status, message }.

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

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.
`section_id`	Yes	The section's id (not its key).

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 destructiveHint=true and idempotentHint=true, yet the description still adds information annotations cannot carry: pages using the snippet render empty in its place, and article content survives the deletion. Combined with the admin/owner requirement, this is a strong disclosure of blast radius and preserved data.

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, then consequence, then constraint, in four tight sentences. The 'Args: - section_id (number, required)' line is redundant with the schema, costing a point, but the 'Returns' line earns its place since no output schema exists.

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 two-parameter destructive tool with no output schema, everything an agent needs is present: the effect on live pages, what is retained, the permission bar, the confirmation requirement, and the shape of the return value. The multi-site ambiguity is fully handled by the schema's site_id description.

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%, including a detailed site_id explanation sourced from helpcenter_list_sites. The description only restates section_id as a required number and says nothing about site_id, so it adds no meaning beyond the schema; baseline 3 applies.

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 ('Delete an FAQ section') and immediately disambiguates against related siblings by noting the FAQ articles themselves are kept, so it is not confused with helpcenter_remove_faq_section_article or helpcenter_delete_article.

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 an explicit gating condition ('Only when the user asks for it') and a prerequisite ('Needs an admin or owner of the help center'). It does not name an alternative sibling the way a 5 would, but the when-to-use and authorization context are clear.

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?