Open a VISIBLE browser window so you can sign in to Zendesk (password, SSO, and 2FA all work). On success the session cookies are saved and reused by every other tool to call the Zendesk REST API. Run this first, and again whenever a tool reports the session has expired.

Report whether a saved Zendesk session exists and verify it is still valid by calling the API as the current user. Use to decide if zendesk_login is needed.

List the agent's active ticket views with their numeric IDs, titles, and cached ticket counts. Use a returned id with zendesk_fetch_view_tickets.

Fetch tickets listed in a Zendesk view, following pagination. Returns ticket id, subject, status, priority, requester, assignee, group, and timestamps. Get a view id from zendesk_list_views.

Search Zendesk via the REST API (/api/v2/search). Accepts any Zendesk search query string (e.g. 'type:ticket status:open assignee:me'). Returns matching results, each tagged with its result_type (ticket, user, organization, group) and the raw API record.

Fetch full details for one ticket: subject, description, status, priority, type, tags, requester/assignee/submitter, group, organization, custom fields (with titles, including the product field when present), the full comment thread with authors and timestamps, and a list of attachments. Each attachment includes a content_url — pass it to zendesk_download_attachment to save the file.

Download an attachment to the local filesystem using the authenticated Zendesk session. Provide the attachment content_url from zendesk_get_ticket and a destination. If destination is a directory, the attachment's own filename is used; otherwise it is the full file path.

List tickets requested by a user (their reported tickets), most recent first — useful for seeing whether a customer has raised this before. Get a user id from zendesk_get_ticket (requester) or zendesk_search_users.

List tickets belonging to an organization, most recent first. Get an organization id from a ticket (organization field) or a user record.

List ticket field definitions, including the valid dropdown/tagger option values. Use this to find the exact value to pass when setting a custom field via zendesk_update_ticket (e.g. the sentiment or product field).

Fetch timing and SLA metrics for one ticket: first reply time, full/agent resolution time, reopens, replies, and assignee/requester wait times.

List active macros (canned actions) with their ids and titles. Use a returned id with zendesk_apply_macro.

Find users by a free-text query (name, email, phone, etc.). Returns id, name, email, role, and organization.

Fetch one user by id (name, email, role, organization).

Fetch the full audit trail for a ticket: every change and event (field updates, status changes, comments, notifications) with authors and timestamps. More complete than the comment thread alone.

Add a comment to a ticket. By default the comment is PUBLIC (visible to the requester); set isPublic=false for an internal note. This modifies the ticket — confirm the wording with the user before sending. Returns the updated ticket.

Update fields on a ticket: status, priority, type, assignee, group, tags, and custom fields. For custom field values, look up the exact value with zendesk_ticket_fields. Optionally include a comment. This modifies the ticket — confirm changes with the user first. Returns the updated ticket.

Apply a macro (canned action) to a ticket and persist the resulting changes (status, fields, and/or a comment). Get a macro id from zendesk_list_macros. This modifies the ticket — confirm with the user first. Returns the changes applied and the updated ticket.

Make a read-only (GET) request to any Zendesk REST API v2 endpoint and return the parsed JSON. Use for anything the dedicated tools don't cover (audits, satisfaction ratings, organizations, users, ticket metrics, etc.). path may be a bare resource like 'tickets/123/audits' or a full '/api/v2/...' path. Pass query parameters via query. See https://developer.zendesk.com/api-reference/ for available endpoints.