Zendesk MCP Server

create_article

Create a new draft article in the Zendesk Help Center for review before publishing. Requires a section ID; supports HTML body content.

Instructions

Create a new article in the Zendesk Help Center. The article is created as a draft by default to allow review before publishing. Requires a section_id — use read_articles with include_sections=true to discover available sections.

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>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "create_article"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Article body content. Supports HTML formatting.
`draft`	No	Whether the article should be created as a draft (default: true for safety).
`title`	Yes	Article title.
`locale`	No	Article locale (default: "en-us").	en-us
`section_id`	Yes	ID of the section to create the article in. Use read_articles with include_sections=true to discover section IDs.
`label_names`	No	Labels to apply to the article.
`notify_subscribers`	No	Whether to notify section subscribers (default: false).
`permission_group_id`	No	Permission group ID. If omitted, uses the default.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=false), the description discloses a key behavioral trait: 'The article is created as a draft by default to allow review before publishing.' This adds context not captured in the annotation hints, though it doesn't detail error cases or response structure.

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?

The description is two sentences, front-loaded with the core purpose, and contains no redundant words. Every sentence earns its place, with the second sentence providing crucial usage guidance.

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 8-parameter tool with no output schema, the description covers the essential context: the action, the draft default, and the prerequisite section_id discovery. However, it does not mention what the response contains (e.g., the created article with ID), which would improve completeness. Still, the schema is rich and the guidance is solid.

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?

All 8 parameters are documented in the schema (100% coverage), so the baseline is 3. The description only restates the draft default and section_id requirement, which are already present in the schema descriptions. It adds no new parameter-level semantics.

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 the Zendesk Help Center', identifying the specific action (create) and resource (article). It differentiates from siblings like update_article (modifies existing) and read_articles (reads), making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Requires a section_id — use read_articles with include_sections=true to discover available sections.' This tells the agent exactly when to use this tool and how to obtain a prerequisite using a sibling, which is strong guidance.

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

Deploy Server