Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Help Center Article

create_article

Create a new Zendesk Help Center article in a section and return its ID. Requires section, title, body, and permission group; locale becomes the source.

Instructions

Create a new article in a section and return the created article with its id. The locale becomes the article's source_locale. Requires a permission_group_id (use list_permission_groups to find available IDs). To add content in other locales afterwards, use create_article_translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesArticle body as HTML (this becomes the source-locale content).
draftNoWhen true (default), the article is created unpublished; set false to publish immediately.
titleYesTitle of the new article, in its source locale.
localeNoSource locale for the article, e.g. "en-us" or "fr". Defaults to the Help Center's default locale; becomes the article's source_locale.
promotedNoWhen true, marks the article as promoted (featured) in its section. Defaults to false.
author_idNoAuthor user ID. Defaults to the authenticated user.
section_idYesSection that will contain the article (numeric id from list_sections).
label_namesNoLabel names for search ranking (use list_labels to see existing labels)
content_tag_idsNoContent tag IDs (use list_content_tags to find them)
user_segment_idNoUser segment ID for visibility (use list_user_segments to find it; if that is forbidden because the token is not a Guide admin, reuse the user_segment_id of an existing article from get_article). Defaults to everyone.
permission_group_idYesPermission group ID (use list_permission_groups to find it; if that is forbidden because the token is not a Guide admin, reuse the permission_group_id of an existing article from get_article).

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. Addedv2.15.0
  3. Removedv2.14.0
  4. Changed2 schema fields changedv2.12.1
    • changedInput schema / properties / permission_group_id / description
      Previous value: -"Permission group ID (use list_permission_groups to find it)"New value: +"Permission group ID (use list_permission_groups to find it; if that is forbidden because the token is not a Guide admin, reuse the permission_group_id of an existing article from get_article)."
    • changedInput schema / properties / user_segment_id / description
      Previous value: -"User segment ID for visibility (use list_user_segments to find it). Defaults to everyone."New value: +"User segment ID for visibility (use list_user_segments to find it; if that is forbidden because the token is not a Guide admin, reuse the user_segment_id of an existing article from get_article). Defaults to everyone."
  5. Changed6 schema fields changedv2.6.0
    • changedInput schema / properties / body / description
      Previous value: -"Article body (HTML)"New value: +"Article body as HTML (this becomes the source-locale content)."
    • addedInput schema / properties / draft / description
      Added value: +"When true (default), the article is created unpublished; set false to publish immediately."
    • addedInput schema / properties / locale / description
      Added value: +"Source locale for the article, e.g. \"en-us\" or \"fr\". Defaults to the Help Center's default locale; becomes the article's source_locale."
    • addedInput schema / properties / promoted / description
      Added value: +"When true, marks the article as promoted (featured) in its section. Defaults to false."
    • addedInput schema / properties / section_id / description
      Added value: +"Section that will contain the article (numeric id from list_sections)."
    • addedInput schema / properties / title / description
      Added value: +"Title of the new article, in its source locale."
  6. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  7. First observedv1.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive). The description adds genuinely useful behavior beyond them: the tool returns the created article with its id, and the supplied locale becomes the article's source_locale. It does not mention the draft/publish default or any rate/permission constraints, which keeps it short of a 5.

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?

Three compact sentences, front-loaded with the core action and return value, then the permission prerequisite, then the sibling handoff. No filler.

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?

For an 11-parameter creation tool with no output schema, the description covers the key gaps an agent needs: the return value, the critical required permission_group_id, and the translation follow-up path. It leaves some behavioral detail (draft default behavior, author default) to the schema, which is acceptable given full schema coverage.

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 usage hints like list_sections/list_labels/list_user_segments, so the schema carries parameter explanation. The description only reinforces permission_group_id and the locale↔source_locale relationship, adding marginal value over structured data.

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?

Specific verb (Create) plus resource (article in a section) and it states the return (created article with id). It is clearly distinguishable from sibling create_article_translation, which it explicitly names as the follow-up for other locales.

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 sequencing guidance: use list_permission_groups to obtain the required permission_group_id, and use create_article_translation afterwards for other locales. It does not state when-not-to-use this tool (e.g. for existing articles, where update_article applies), so it stops short of full routing.

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