Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Article Attachment

create_article_attachment

Upload a file to a Help Center article and return the created attachment's ID, file name, content type, size, and content URL.

Instructions

Upload a file to a Help Center article and return the created attachment (its id, file name, content type, size and content URL). Not idempotent: calling it again uploads another copy rather than replacing the previous one. This is for article assets — for files on support tickets use get_ticket_attachments, and to see an article's existing attachments use list_article_attachments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_nameYesName to store the file under, including its extension (e.g. "screenshot.png"); used as the download name.
article_idYesArticle ID — the numeric id of the Help Center article. Obtain it from list_articles or search_articles.
file_base64YesThe file's raw bytes as a base64-encoded string; the server decodes them before upload. At most 10420224 characters (about 7.45 MB of file); the HTTP transport additionally caps request bodies at 4 MB.
content_typeNoMIME type of the file, e.g. "image/png" or "application/pdf". Defaults to application/octet-stream when omitted.application/octet-stream

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. Changed2 schema fields changedv2.20.2
    • changedInput schema / properties / file_base64 / description
      Previous value: -"The file's raw bytes as a base64-encoded string; the server decodes them before upload."New value: +"The file's raw bytes as a base64-encoded string; the server decodes them before upload. At most 10420224 characters (about 7.45 MB of file); the HTTP transport additionally caps request bodies at 4 MB."
    • addedInput schema / properties / file_base64 / maxLength
      Added value: +10420224
  3. Addedv2.15.0
  4. Removedv2.14.0
  5. Changed3 schema fields changedv2.6.1
    • changedInput schema / properties / content_type / description
      Previous value: -"MIME type (e.g., \"image/png\", \"application/pdf\")"New value: +"MIME type of the file, e.g. \"image/png\" or \"application/pdf\". Defaults to application/octet-stream when omitted."
    • changedInput schema / properties / file_base64 / description
      Previous value: -"File content encoded as base64"New value: +"The file's raw bytes as a base64-encoded string; the server decodes them before upload."
    • changedInput schema / properties / file_name / description
      Previous value: -"File name (e.g., \"screenshot.png\")"New value: +"Name to store the file under, including its extension (e.g. \"screenshot.png\"); used as the download name."
  6. Changed1 schema field changedv2.6.0
    • changedInput schema / properties / article_id / description
      Previous value: -"Article ID"New value: +"Article ID — the numeric id of the Help Center article. Obtain it from list_articles or search_articles."
  7. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  8. First observedv1.7.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds the concrete consequence of non-idempotency ('uploads another copy rather than replacing'), which is actionable beyond the boolean. It also compensates for the absent output schema by enumerating the returned fields. It does not mention auth/permission requirements, so not a full 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 sentences, front-loaded with the core action and return value, followed by the important non-idempotency caveat and sibling routing. No filler; every sentence earns its place.

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 write tool with no output schema, the description supplies what the schema cannot: the shape of the return value, the non-idempotency behavior, and disambiguation from related attachment tools. Nothing an agent needs to call it correctly is missing.

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 the schema already documents all four parameters including base64 encoding, size limits and MIME type. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 (upload) and resource (file to a Help Center article), and explicitly describes the return payload. It distinguishes itself from siblings by naming both get_ticket_attachments and list_article_attachments, so an agent can tell it apart without opening other schemas.

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?

Explicitly routes the agent: 'for files on support tickets use get_ticket_attachments' and 'to see an article's existing attachments use list_article_attachments.' Both the when-to-use and the alternatives are stated.

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