@fruggr/zendesk-mcp-server 3.6.0 → 3.7.0

package/dist/index.js

@@ -30084,7 +30084,7 @@ const createHelpCenterTools = (env) => {
 			namespace: "help_center",
 			readOnly: true,
 			title: "List Permission Groups",
-			description: "List all Guide permission groups. Use this to find the permission_group_id required when creating articles.",
+			description: "List all Guide permission groups, which control who can edit and publish an article, with each group's id, name and whether it is built-in. Use this to find the permission_group_id required when creating articles with create_article, or to change it with update_article; to control who can view an article instead, use list_user_segments. Zendesk restricts this list to Guide admins and Help Center managers: without that role the call fails, and you can reuse the permission_group_id of an existing article read with get_article.",
 			inputSchema: object({}),
 			annotations: {
 				readOnlyHint: true,
@@ -30149,7 +30149,7 @@ const createHelpCenterTools = (env) => {
 			namespace: "help_center",
 			readOnly: false,
 			title: "Update Help Center Article",
-			description: "Update article metadata only (draft, promoted, labels as label_names, content tags as content_tag_ids, visibility as permission_group_id / user_segment_id, section_id, sort position, etc.) and return the updated article. Does NOT update content (title, body) — use update_article_translation for that.",
+			description: "Update article metadata only (draft, promoted, labels as label_names, content tags as content_tag_ids, visibility as permission_group_id / user_segment_id, section_id, sort position, author, etc.) and return the updated article; fields you omit keep their value. Does NOT update content (title, body) — use update_article_translation for that, or update_article_section to edit one section. To put an article first or last in its section, prefer reorder_article: a plain position write is ambiguous while articles share position 0. To remove an article from the Help Center, use archive_article (a Guide admin can restore it); draft: true only unpublishes it.",
 			inputSchema: object({
 				article_id: number$1().int().describe("Article ID — the numeric id of the article to update. Obtain it from list_articles or search_articles."),
 				draft: boolean().optional().describe("Set true to unpublish the article (revert to draft) or false to publish it."),
@@ -30336,7 +30336,7 @@ const createHelpCenterTools = (env) => {
 			namespace: "help_center",
 			readOnly: true,
 			title: "List Article Labels",
-			description: "List all article labels. Labels improve Help Center search ranking and are not visible to end users. Attach them to an article through the label_names parameter of create_article or update_article.",
+			description: "List all article labels, with each label's id and name. Labels improve Help Center search ranking and are not visible to end users. Attach them to an article through the label_names parameter of create_article or update_article, reusing an existing label rather than coining a near-duplicate. Labels are not content tags: for the end-user-visible tags readers browse by, use list_content_tags.",
 			inputSchema: object({ ...brandIdPart }),
 			annotations: {
 				readOnlyHint: true,
@@ -30360,7 +30360,7 @@ const createHelpCenterTools = (env) => {
 			namespace: "help_center",
 			readOnly: true,
 			title: "List User Segments",
-			description: "List all user segments. User segments control article visibility (who can view). Use the ID when creating or updating articles.",
+			description: "List all Help Center user segments, which control article visibility (who can view an article), with each segment's id, name, user type and whether it is built-in. Use the id as user_segment_id when creating or updating articles with create_article or update_article; to control who can edit an article instead, use list_permission_groups. Zendesk restricts this list to Guide admins and Help Center managers: without that role the call fails, and you can reuse the user_segment_id of an existing article from get_article, or omit it on create_article to make the article visible to everyone.",
 			inputSchema: object({}),
 			annotations: {
 				readOnlyHint: true,
@@ -31106,8 +31106,8 @@ const createRequestTools = (env) => {
 				body: string().min(1).describe("The request itself: what happened, what was expected, and any steps to reproduce. Becomes the first public comment on the ticket."),
 				form_id: number$1().int().optional().describe("Form id chosen from list_request_forms, deciding which questions apply. Omit to use the account default form."),
 				custom_fields: array(object({
-					id: number$1().int(),
-					value: unknown()
+					id: number$1().int().describe("Numeric id of a question on the chosen form, from get_request_form."),
+					value: unknown().describe("The answer, typed after the question: the option tag (a string, never a number) for a dropdown, an array of option tags for a multiselect, true or false for a checkbox, text otherwise.")
 				}).strict()).optional().describe("Answers to the form's own questions, as { id, value } pairs. Take both the ids and the accepted values from get_request_form; an id this form does not carry, or a value a dropdown does not offer, is refused here because Zendesk would drop it without an error. Option values are the tag strings, never numbers."),
 				attachments: attachmentsParam("Files to attach to the request, such as a screenshot or a log, with their content base64-encoded.")
 			}),
@@ -31795,6 +31795,7 @@ const fetchAllTicketComments = async (subdomain, token, ticketId) => {
 	const all = [];
 	let cursor;
 	let pages = 0;
+	let truncated = false;
 	while (pages < MAX_COMMENT_PAGES) {
 		const response = await zendeskGet(subdomain, token, `/tickets/${ticketId}/comments`, {
 			...buildCursorParams(100, cursor),
@@ -31804,9 +31805,14 @@ const fetchAllTicketComments = async (subdomain, token, ticketId) => {
 		pages += 1;
 		if (!response.meta?.has_more || !response.meta?.after_cursor) break;
 		cursor = response.meta.after_cursor;
+		truncated = pages === MAX_COMMENT_PAGES;
 	}
-	return all;
+	return {
+		comments: all,
+		truncated
+	};
 };
+const COMMENT_CAP_NOTICE = `Comment scan stopped at its page cap (${MAX_COMMENT_PAGES} pages, COMMENT_MAX_PAGES): attachments on any later comments are not listed. Pass attachment_ids taken from list_ticket_comments to fetch them.`;
 const commentPageMeta = (response, itemCount) => extractPaginationMeta({
 	...response.meta && { meta: response.meta },
 	...response.count !== void 0 && { count: response.count }
@@ -32108,6 +32114,10 @@ const createTicketTools = (env) => {
 		const ids = array(number$1().int().positive());
 		return (max === void 0 ? ids : ids.max(max)).optional().describe(description);
 	};
+	const customFieldEntry = object({
+		id: number$1().int().describe("Numeric id of the ticket field to set, as listed by list_ticket_fields."),
+		value: unknown().describe("Value typed after the field: the option tag (a string) for a dropdown, an array of option tags for a multiselect, true or false for a checkbox, text or a number for a text or numeric field. For any other type (a date, a lookup), follow the type list_ticket_fields reports; it also lists each dropdown's accepted tags.")
+	}).strict();
 	return [
 		{
 			name: "get_ticket",
@@ -32245,10 +32255,10 @@ const createTicketTools = (env) => {
 			namespace: "tickets",
 			readOnly: true,
 			title: "Get Zendesk Ticket Attachments",
-			description: "Retrieve ticket attachments. Images are embedded inline; other files are listed as text references.",
+			description: "Download the files attached to a ticket's comments so you can look at them: images come back embedded inline, other files as text references (file name, id, content type, size, download URL). Use it to see an attached image, or a file's name, size and download URL (only images come back with their content); to learn which files a comment carries, list_ticket_comments already shows their ids. Pass those ids as attachment_ids to fetch only them, or omit it to collect the attachments of the ticket's comments, read up to a page cap (10 pages of 100 comments by default); past it the response says later comments were not scanned, and attachment_ids fetches their files. An image over the per-image size limit or past the embedded-image cap comes back as a reference saying why, and once the response size budget is spent the remaining files are counted as omitted.",
 			inputSchema: object({
 				ticket_id: number$1().int().describe("Ticket ID — the numeric id of the ticket whose attachments to fetch. Obtain it from search_tickets or list_tickets."),
-				attachment_ids: array(number$1().int()).optional().describe("Attachment IDs to fetch directly (e.g. extracted from a previous list_ticket_comments or get_ticket(include_comments=true) call). When provided, skips the comments fetch entirely. When omitted, all attachments of the ticket are returned.")
+				attachment_ids: array(number$1().int()).optional().describe("Attachment IDs to fetch directly (e.g. extracted from a previous list_ticket_comments or get_ticket(include_comments=true) call). When provided, skips the comments fetch entirely. When omitted, the attachments of the ticket's comments are returned, read up to a page cap: on a very long thread the scan stops there, and the response says so.")
 			}),
 			annotations: {
 				readOnlyHint: true,
@@ -32259,16 +32269,31 @@ const createTicketTools = (env) => {
 			handler: async (params, { caller }) => {
 				const { ticket_id, attachment_ids } = params;
 				const token = await caller.getToken();
-				const attachments = attachment_ids && attachment_ids.length > 0 ? await fetchAttachmentsByIds(subdomain, token, attachment_ids) : (await fetchAllTicketComments(subdomain, token, ticket_id)).flatMap((c) => c.attachments ?? []);
+				const { attachments, truncated } = attachment_ids && attachment_ids.length > 0 ? {
+					attachments: await fetchAttachmentsByIds(subdomain, token, attachment_ids),
+					truncated: false
+				} : await fetchAllTicketComments(subdomain, token, ticket_id).then((walk) => ({
+					attachments: walk.comments.flatMap((c) => c.attachments ?? []),
+					truncated: walk.truncated
+				}));
 				if (attachments.length === 0) return { content: [{
 					type: "text",
-					text: `No attachments found on ticket #${ticket_id}.`
+					text: truncated ? `No attachments found on the first ${MAX_COMMENT_PAGES} pages of comments of ticket #${ticket_id}. ${COMMENT_CAP_NOTICE}` : `No attachments found on ticket #${ticket_id}.`
 				}] };
 				const header = {
 					type: "text",
 					text: `# Attachments for ticket #${ticket_id} (${attachments.length} total)`
 				};
-				return { content: [header, ...await collectAttachmentBlocks(subdomain, token, attachments, blockCost(header) + 1)] };
+				const notice = truncated ? [{
+					type: "text",
+					text: COMMENT_CAP_NOTICE
+				}] : [];
+				const blocks = await collectAttachmentBlocks(subdomain, token, attachments, [header, ...notice].reduce((total, block) => total + blockCost(block), 1));
+				return { content: [
+					header,
+					...notice,
+					...blocks
+				] };
 			}
 		},
 		{
@@ -32334,10 +32359,7 @@ const createTicketTools = (env) => {
 				assignee_id: number$1().int().optional().describe("User id of the agent to assign the ticket to."),
 				group_id: number$1().int().optional().describe("Id of the group to assign the ticket to."),
 				tags: array(string()).optional().describe("Tags to set on the new ticket. Each tag is a single lowercase token (join multi-word tags with an underscore). Use manage_tags later to add or remove individual tags."),
-				custom_fields: array(object({
-					id: number$1().int(),
-					value: unknown()
-				}).strict()).optional().describe("Custom field values as { id, value } pairs (field ids come from your Zendesk admin settings). Call list_ticket_fields first to discover the numeric field ids and, for dropdown/multiselect fields, the exact option values Zendesk accepts.")
+				custom_fields: array(customFieldEntry).optional().describe("Custom field values as { id, value } pairs (field ids come from your Zendesk admin settings). Call list_ticket_fields first to discover the numeric field ids and, for dropdown/multiselect fields, the exact option values Zendesk accepts.")
 			}),
 			annotations: {
 				readOnlyHint: false,
@@ -32391,10 +32413,7 @@ const createTicketTools = (env) => {
 				group_id: number$1().int().optional().describe("Id of the group to assign the ticket to."),
 				subject: string().optional().describe("New subject line for the ticket; replaces the current subject when provided."),
 				tags: array(string()).optional().describe("Replaces the full tag set on the ticket. Use manage_tags for incremental add/remove."),
-				custom_fields: array(object({
-					id: number$1().int(),
-					value: unknown()
-				}).strict()).optional().describe("Custom field values as { id, value } pairs (field ids come from your Zendesk admin settings). Call list_ticket_fields first to discover the numeric field ids and, for dropdown/multiselect fields, the exact option values Zendesk accepts."),
+				custom_fields: array(customFieldEntry).optional().describe("Custom field values as { id, value } pairs (field ids come from your Zendesk admin settings). Call list_ticket_fields first to discover the numeric field ids and, for dropdown/multiselect fields, the exact option values Zendesk accepts."),
 				followers: object({
 					add: subscriberIdList("User ids to start following the ticket. Omit to only remove."),
 					remove: subscriberIdList("User ids to stop following the ticket. Omit to only add.")
@@ -33048,7 +33067,7 @@ const createUserTools = (env) => {
 			namespace: "users",
 			readOnly: true,
 			title: "Search Zendesk Users",
-			description: "Search for users by name, email, or other criteria using Zendesk search query syntax. Returns total count.",
+			description: "Search for users by name, email, or other criteria using Zendesk search query syntax, returning each match's id, name, email, role, active flag and organization id, with the total count. Use it to turn a person into the numeric user id other tools take, such as the followers of update_ticket; a name can match several users, so confirm the right one. With an id already in hand, call get_user to read that one user, and for your own account get_current_user. Prefer it over `search` when you want users only: `search` mixes in tickets and organizations unless the query says type:user.",
 			inputSchema: object({
 				query: string().min(1).describe("Zendesk user search query — free text matched against name and email, and/or field filters like \"email:jane@acme.com\", \"role:agent\", \"organization_id:123\". A \"type:user\" scope is added automatically."),
 				per_page: number$1().int().min(1).max(100).default(100).describe(PER_PAGE_DESC),
@@ -35177,7 +35196,7 @@ const main = async () => {
 		logger,
 		cleanup: async () => (await starting?.catch(() => void 0))?.close()
 	});
-	const { startHttpTransport } = await import("./http-DkjvhtQj.js");
+	const { startHttpTransport } = await import("./http-D-Xy9BWD.js");
 	starting = startHttpTransport(config, logger);
 	await starting;
 };

package/dist/sbom.cdx.json

@@ -1,15 +1,15 @@
 {
   "bomFormat": "CycloneDX",
   "specVersion": "1.6",
-  "serialNumber": "urn:uuid:dbd14c1f-e90e-5bea-b648-7853fb8ee967",
+  "serialNumber": "urn:uuid:081eda00-f41f-539e-8e22-325ebea4a10a",
   "version": 1,
   "metadata": {
     "component": {
       "type": "application",
-      "bom-ref": "pkg:npm/%40fruggr/zendesk-mcp-server@3.6.0",
+      "bom-ref": "pkg:npm/%40fruggr/zendesk-mcp-server@3.7.0",
       "name": "@fruggr/zendesk-mcp-server",
-      "version": "3.6.0",
-      "purl": "pkg:npm/%40fruggr/zendesk-mcp-server@3.6.0"
+      "version": "3.7.0",
+      "purl": "pkg:npm/%40fruggr/zendesk-mcp-server@3.7.0"
     }
   },
   "components": [
@@ -927,10 +927,10 @@
     },
     {
       "type": "library",
-      "bom-ref": "pkg:npm/jose@6.2.12",
+      "bom-ref": "pkg:npm/jose@6.2.13",
       "name": "jose",
-      "version": "6.2.12",
-      "purl": "pkg:npm/jose@6.2.12",
+      "version": "6.2.13",
+      "purl": "pkg:npm/jose@6.2.13",
       "licenses": [
         {
           "expression": "MIT"
@@ -1539,10 +1539,10 @@
     },
     {
       "type": "library",
-      "bom-ref": "pkg:npm/oidc-provider@9.12.2",
+      "bom-ref": "pkg:npm/oidc-provider@9.13.0",
       "name": "oidc-provider",
-      "version": "9.12.2",
-      "purl": "pkg:npm/oidc-provider@9.12.2",
+      "version": "9.13.0",
+      "purl": "pkg:npm/oidc-provider@9.13.0",
       "licenses": [
         {
           "expression": "MIT"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fruggr/zendesk-mcp-server",
-  "version": "3.6.0",
+  "version": "3.7.0",
   "mcpName": "io.github.fruggr/zendesk-mcp-server",
   "description": "Deep Zendesk MCP server for your AI assistant: search, draft, update and translate Help Center articles and manage Support tickets end to end — comments, triage and image attachments.",
   "type": "module",
@@ -33,7 +33,8 @@
     "test:smoke": "pnpm build && node scripts/smoke-test.mjs",
     "test:bundle": "pnpm build && vitest run --config vitest.bundle.config.ts",
     "bundle:size": "pnpm build && node scripts/bundle-size.mjs",
-    "mcp:live": "tsx scripts/mcp-live.ts"
+    "mcp:live": "tsx scripts/mcp-live.ts",
+    "tool-definitions:report": "tsx scripts/tool-definitions-report.ts"
   },
   "keywords": [
     "mcp",
@@ -73,7 +74,7 @@
   "engines": {
     "node": ">=22"
   },
-  "packageManager": "pnpm@12.15.0+sha512.b3951d6d6ff4a9f13dc7cf56cd28d2b8eb37dbcc9c68e52e1e1191873ea9f82a017287ab50baadc5ccc494f036c67c0e47eb13608c2fa36f47711b61ea128e61",
+  "packageManager": "pnpm@12.16.1+sha512.091d1dee7927575661b25dab3c2ae31cafc1c54d6b71ed6a6600cf0c1cb10434a447eae14015f1b23e2e6bedeed79df94a932e2164d2832280dce3fb32f656d1",
   "devDependencies": {
     "@biomejs/biome": "2.6.2",
     "@modelcontextprotocol/client": "2.3.1",
@@ -97,10 +98,11 @@
     "conventional-changelog-conventionalcommits": "^10.2.1",
     "hast-util-to-html": "9.0.5",
     "hast-util-to-mdast": "10.1.2",
-    "jose": "6.2.12",
+    "jose": "6.2.13",
     "lefthook": "^2.2.2",
+    "mcp-tdqs": "0.2.0",
     "msw": "^3.0.0",
-    "oidc-provider": "~9.12.2",
+    "oidc-provider": "~9.13.0",
     "open": "11.0.4",
     "rehype-parse": "9.0.1",
     "rehype-raw": "7.0.0",