Zendesk · Support

ZENDESK_GET_TICKET

Get one Zendesk ticket by numeric id. Returns the trimmed ticket object.

Provider
Zendesk
Access
Read
Category
Support
Version
v1

Input schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "number",
      "description": "Numeric ticket id."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

How to call it

Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls zendesk_get_ticket with arguments matching the schema above.

CybrLink validates the input, injects the connected Zendesk credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.

Frequently asked

How do I let an AI agent zendesk get ticket?
Connect Zendesk to CybrLink, then expose the `zendesk_get_ticket` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Zendesk credential server-side and runs one scoped API call. Get one Zendesk ticket by numeric id. Returns the trimmed ticket object.
Does the AI model see my Zendesk credentials when using ZENDESK_GET_TICKET?
No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can read this data from Zendesk without the OAuth token or API key ever entering its context.