Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Help Center Articles

list_articles
Read-onlyIdempotent

List Zendesk Help Center article metadata, filtered by section ID and locale, with sort options and optional translation locales. Returns paginated results without body content.

Instructions

List articles (metadata only, no body). Use get_article for full content. Optionally filter by section ID and locale. Supports sort_by ("title", "created_at", "updated_at") and include_translations: true to show available translation locales per article. Note: include_translations must be re-sent on each paginated request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response; omit for the first page.
localeNoRestrict to a single locale, e.g. "en-us" or "fr". Omit for the default locale.
sort_byNoField to sort by; "position" (the default) is the manual order set in Guide.position
page_sizeNoArticles per page (1-100, default 100).
section_idNoRestrict the listing to one section (numeric id from list_sections). Omit to list articles across all sections.
sort_orderNoSort direction: ascending or descending.asc
include_translationsNoInclude available translation locales per article (causes 1 extra API call per article)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.6.0
    • addedInput schema / properties / locale / description
      Added value: +"Restrict to a single locale, e.g. \"en-us\" or \"fr\". Omit for the default locale."
    • addedInput schema / properties / section_id / description
      Added value: +"Restrict the listing to one section (numeric id from list_sections). Omit to list articles across all sections."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort field"New value: +"Field to sort by; \"position\" (the default) is the manual order set in Guide."
    • changedInput schema / properties / sort_order / description
      Previous value: -"Sort direction"New value: +"Sort direction: ascending or descending."
  2. Changed3 schema fields changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor from a previous response; omit for the first page."
    • addedInput schema / properties / page_size / description
      Added value: +"Articles per page (1-100, default 100)."
  3. First observedv1.7.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses that it returns metadata only, that include_translations causes extra API calls, and pagination requirement. Adds value beyond readOnly and idempotent annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences plus a note. Front-loaded with purpose, no filler. Every sentence provides value.

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?

Covers purpose, parameters, pagination behavior, and performance cost. Lacks explicit mention that results are paginated (but schema has cursor). Adequate for the complexity.

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 baseline 3. Description adds useful context like filtering options and sort_by values, and the performance note for include_translations. Exceeds baseline slightly.

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?

Clearly states it lists articles with metadata only, distinguishes from get_article for full content. Specific verb+resource+scope.

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?

Explicitly mentions using get_article for full content and notes include_translations must be re-sent on pagination. Could be more explicit about when not to use, but adequate.

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