Zendesk tools
Every Zendesk tool in the developer API, with arguments and examples: search, read, reply to, update and create tickets.
Needs: A Zendesk connection. 9 tools.
These tools appear in GET /v1/tools only when the API key's MCP server includes a connection of this kind. Call each one with POST /v1/tools/\<name>, sending its arguments as a JSON object. See Calling tools for the request and response format.
| Tool | What it does | Kind |
|---|---|---|
zendesk_search_tickets |
Search Zendesk tickets | Read |
zendesk_get_ticket |
Read a Zendesk ticket | Read |
zendesk_find_users |
Find Zendesk users | Read |
zendesk_add_comment |
Reply or add a note | Change |
zendesk_update_ticket |
Update a Zendesk ticket | Change |
zendesk_ticket_stats |
Zendesk ticket counts | Read |
zendesk_list_macros |
List Zendesk macros | Read |
zendesk_apply_macro |
Apply a Zendesk macro | Change |
zendesk_create_ticket |
Create a Zendesk ticket | Change |
Change tools in this group: zendesk_add_comment, zendesk_update_ticket, zendesk_apply_macro, zendesk_create_ticket. Check each tool's notes below for what it needs before it runs.
The example requests fill in only the required arguments, with placeholder values.
zendesk_search_tickets
Search Zendesk tickets · Read
Searches tickets with Zendesk search syntax, e.g. "status:open", "requester:jane@acme.com", "assignee:me status<solved", "tags:refund created>2026-01-01", or plain words. Newest updated first.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
query |
string | No | Zendesk search query (type:ticket is added automatically) |
sort_by |
string | No | Field to sort by. One of: updated_at, created_at, priority, status. Default "updated_at". |
sort_order |
string | No | asc or desc. One of: desc, asc. Default "desc". |
limit |
integer | No | Most results to return. Default 25. |
page |
integer | No | Page of results, from 1. Default 1. |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_search_tickets \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'
zendesk_get_ticket
Read a Zendesk ticket · Read
Returns a ticket with requester, assignee, organisation, custom fields and the full conversation (public replies and internal notes, oldest first), including attachment links.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
ticket_id |
integer | Yes | Ticket number |
include_comments |
boolean | No | Include the ticket's comments. Default true. |
max_chars_per_comment |
integer | No | Longest comment text returned; longer ones are cut. Default 4000. |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_get_ticket \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ticket_id": 1}'
zendesk_find_users
Find Zendesk users · Read
Finds people (customers or agents) by name, email or phone. Use the id for assignee changes.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
query |
string | Yes | Search text |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_find_users \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "…"}'
zendesk_add_comment
Reply or add a note · Change
Adds a public reply (emailed to the requester) or an internal note to a ticket, optionally changing its status. Internal notes are only seen by agents. Needs changes allowed for this Zendesk account and MCP server.
This tool makes a change, so the request must include
"confirm": true, and changes must be allowed. See Making changes.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
ticket_id |
integer | Yes | Ticket number |
body |
string | Yes | Text of the reply or note |
public |
boolean | Yes | true = public reply to the customer, false = internal note |
status |
string | No | Also set the ticket status. One of: open, pending, hold, solved. |
confirm |
boolean | Yes | Must be true: the user approved this exact text |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_add_comment \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ticket_id": 1, "body": "…", "public": true, "confirm": true}'
zendesk_update_ticket
Update a Zendesk ticket · Change
Changes a ticket's status, priority, type, assignee or tags. Needs changes allowed for this Zendesk account and MCP server.
This tool makes a change, so the request must include
"confirm": true, and changes must be allowed. See Making changes.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
ticket_id |
integer | Yes | Ticket number |
status |
string | No | Status. One of: new, open, pending, hold, solved, closed. |
priority |
string | No | Priority. One of: low, normal, high, urgent. |
type |
string | No | Type. One of: question, incident, problem, task. |
assignee_id |
integer | No | Agent user id (zendesk_find_users) |
add_tags |
array of string | No | Tags to add |
remove_tags |
array of string | No | Tags to remove |
confirm |
boolean | Yes | Must be true: the user approved these exact changes |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_update_ticket \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ticket_id": 1, "confirm": true}'
zendesk_ticket_stats
Zendesk ticket counts · Read
Counts tickets for a quick overview: open, pending, on hold, new and unsolved right now, plus created and solved in a period. Narrow it with a Zendesk query, e.g. "tags:refund", "group:Billing" or "assignee:me". For trends, call it for each period.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
from |
string | Yes | Period start, YYYY-MM-DD |
to |
string | Yes | Period end, YYYY-MM-DD (inclusive) |
query |
string | No | Extra Zendesk search filter applied to every count |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_ticket_stats \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-01", "to": "2026-11-15"}'
zendesk_list_macros
List Zendesk macros · Read
The saved replies and actions (macros) this agent can use, optionally filtered by words in the title. Use zendesk_apply_macro to use one.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
search |
string | No | Words in the macro title |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_list_macros \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'
zendesk_apply_macro
Apply a Zendesk macro · Change
Applies a macro to a ticket (its reply text, status, tags and other changes). Needs changes allowed for this Zendesk account and MCP server.
Call it first with
previewleft attrueto see what the macro would do. To apply it, call again with"preview": falseand"confirm": true. Changes must be allowed. See Making changes.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
ticket_id |
integer | Yes | Ticket number |
macro_id |
integer | Yes | Macro id from zendesk_list_macros |
preview |
boolean | No | true = only show what would change. Default true. |
confirm |
boolean | No | Must be true to apply: the user approved the previewed changes. Default false. |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_apply_macro \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ticket_id": 1, "macro_id": 1, "preview": false, "confirm": true}'
zendesk_create_ticket
Create a Zendesk ticket · Change
Opens a new ticket for a customer (by email; Zendesk creates the person if new), with a first message, priority, type and tags. By default the first message is an internal note, so the customer isn't emailed; set notify_requester: true to email them. Needs changes allowed for this Zendesk account and MCP server.
This tool makes a change, so the request must include
"confirm": true, and changes must be allowed. See Making changes.
| Argument | Type | Required | What it is |
|---|---|---|---|
account |
string | No | Zendesk account id from list_accounts (optional when there's only one) |
subject |
string | Yes | Subject |
body |
string | Yes | The first message |
requester_email |
string | Yes | Requester's email address |
requester_name |
string | No | Requester's name |
notify_requester |
boolean | No | true = the first message is a public reply emailed to the requester. Default false. |
priority |
string | No | Priority. One of: low, normal, high, urgent. |
type |
string | No | Type. One of: question, incident, problem, task. |
tags |
array of string | No | Tags |
assignee_id |
integer | No | Agent user id (zendesk_find_users) |
confirm |
boolean | Yes | Must be true: the user approved these exact details |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/zendesk_create_ticket \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"subject": "…", "body": "…", "requester_email": "someone@example.com", "confirm": true}'