Freshdesk

Freshdesk Get Ticket

freshdesk_get_ticket

Read-onlyIdempotent

Get full ticket details by ID including subject, status, priority, description, conversations, attachments, and resolution notes.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Ticket ID
`_apiKey`	Yes	Freshdesk API key
`_domain`	Yes	Freshdesk subdomain

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Ticket ID
`status`	No	Ticket status code
`subject`	No	Ticket subject
`priority`	No	Ticket priority level
`created_at`	No	ISO timestamp
`updated_at`	No	ISO timestamp
`description`	No	Ticket description
`requester_id`	No	Requester contact ID
`conversations`	No	Array of conversation objects

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conversations": {
+      "description": "Array of conversation objects",
+      "items": {
+        "properties": {
+          "body": {
+            "description": "Conversation message body",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "ISO timestamp",
+            "type": "string"
+          },
+          "id": {
+            "description": "Conversation ID",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "created_at": {
+      "description": "ISO timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Ticket description",
+      "type": "string"
+    },
+    "id": {
+      "description": "Ticket ID",
+      "type": "number"
+    },
+    "priority": {
+      "description": "Ticket priority level",
+      "type": "number"
+    },
+    "requester_id": {
+      "description": "Requester contact ID",
+      "type": "number"
+    },
+    "status": {
+      "description": "Ticket status code",
+      "type": "number"
+    },
+    "subject": {
+      "description": "Ticket subject",
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "ISO timestamp",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-freshdesk-api-key",
+    "_domain": "mycompany",
+    "id": 1234
+  }
+]

First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds context on returned fields (conversations, attachments) but does not disclose additional behavioral traits like rate limits or auth requirements beyond the schema.

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?

Single sentence that is front-loaded with the purpose and lists included fields. No wasted words.

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?

Given the presence of an output schema and comprehensive annotations, the description covers the essential details (what fields are returned) without needing to explain return structure. Complete for a simple get-by-ID tool.

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 coverage is 100% with descriptive parameter descriptions. The description does not add further semantic detail beyond the schema, landing at the baseline of 3.

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?

The description clearly states the tool retrieves full ticket details by ID, listing specific fields (subject, status, priority, etc.). This is a specific verb-resource pair that distinguishes it from list or search siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when a specific ticket ID is known, but does not explicitly contrast with list or search tools. The context is clear enough for a straightforward get-by-ID tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Freshdesk tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.