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 Zendesk Help Center article in a specified section by providing title, HTML body, and permission group ID; returns the created article with its ID and source locale.

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. Addedv2.15.0
  2. Removedv2.14.0
  3. 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."
  4. 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."
  5. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  6. First observedv1.7.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already indicate the tool is a mutation (readOnlyHint=false) and not destructive. The description adds that the locale becomes the source_locale, but this is also in the schema. No additional behavioral traits (e.g., side effects, rate limits) are disclosed beyond what annotations and schema provide.

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 sentences with front-loaded purpose: 'Create a new article in a section and return the created article with its id.' Every sentence serves a purpose without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters and no output schema, the description is minimal. It covers the return value ('with its id') and the key required parameter, but doesn't explain optional parameters like draft, promoted, etc. However, schema covers all parameters, so the description is adequate but not rich.

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 baseline is 3. The description only mentions 'permission_group_id' and 'locale' as source_locale, which repeats schema info. No new meaning is added beyond what the input schema already provides.

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?

The description clearly states 'Create a new article in a section and return the created article with its id.' It specifies the verb (create) and resource (article), and distinguishes from sibling 'create_article_translation' by noting that for other locales, that sibling should be used.

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?

The description provides explicit guidance on the required 'permission_group_id' and how to find it using 'list_permission_groups'. It also directs to 'create_article_translation' for adding content in other locales, giving clear context on when to use this tool versus alternatives.

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