Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Help Center Categories

list_categories
Read-onlyIdempotent

List all Help Center categories to map your Guide hierarchy. Use returned category ids with list_sections to drill down, and pass a locale to read translated names.

Instructions

List all Help Center categories. Categories are the top level of the Guide hierarchy (category → section → article); each entry includes its id, name and locale. Results are cursor-paginated. Pair a returned category id with list_sections to drill down, then list_articles to reach articles. Pass a locale to read category names in that translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response; omit for the first page.
localeNoLocale for category names (e.g., "en-us", "fr"). Defaults to the Help Center default locale.
page_sizeNoCategories per page (1-100, default 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed3 schema fields changedv2.2.0
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor from a previous response; omit for the first page."
    • addedInput schema / properties / locale / description
      Added value: +"Locale for category names (e.g., \"en-us\", \"fr\"). Defaults to the Help Center default locale."
    • addedInput schema / properties / page_size / description
      Added value: +"Categories per page (1-100, default 100)."
  4. First observedv1.7.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile needs no repetition. The description adds genuinely new behavioral context: entries contain id/name/locale and results are cursor-paginated, which the annotations do not convey.

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?

Four short sentences, front-loaded with the purpose and followed by hierarchy, return shape, pagination, and parameters. Slightly dense with routing detail, but no sentence is wasted.

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 zero-required-param list tool with a fully documented schema and annotation-covered safety profile, nothing material is missing; return fields, pagination, locale behavior, and follow-up tools are all covered without an output schema.

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; the description earns above baseline by explaining that locale controls the translation used for category names. It also reinforces the pagination model behind the cursor parameter, adding meaning beyond the field labels.

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 Help Center categories) and immediately locates it in the Guide hierarchy, distinguishing it from list_sections and list_articles. An agent can tell exactly what this returns and where it sits.

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 drill-down path (category id → list_sections → list_articles) and a condition for using the locale parameter. It stops short of stating when NOT to use it (e.g., when you already have a category id), but the routing context is clear.

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

Deploy Server

Other Tools