Freshdesk

Freshdesk List Tickets

freshdesk_list_tickets

Read-onlyIdempotent

List support tickets filtered by status (e.g., "open", "closed") and priority (e.g., "1" for urgent). Returns ticket ID, subject, status, priority, and requester.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for pagination (default 1)
`filter`	No	Predefined filter: new_and_my_open, watching, spam, deleted (default: new_and_my_open)
`_apiKey`	Yes	Freshdesk API key
`_domain`	Yes	Freshdesk subdomain (e.g., "mycompany" for mycompany.freshdesk.com)
`order_by`	No	Sort by: created_at, due_by, updated_at, status (default: created_at)
`per_page`	No	Results per page (default 30, max 100)
`order_type`	No	Sort order: asc or desc (default: desc)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tickets`	No	Array of ticket objects

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "tickets": {
+      "description": "Array of ticket objects",
+      "items": {
+        "properties": {
+          "created_at": {
+            "description": "ISO timestamp",
+            "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"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-freshdesk-api-key",
+    "_domain": "mycompany",
+    "filter": "new_and_my_open"
+  },
+  {
+    "_apiKey": "your-freshdesk-api-key",
+    "_domain": "mycompany",
+    "order_by": "updated_at",
+    "order_type": "desc",
+    "page": 2,
+    "per_page": 50
+  }
+]

First observedApr 22, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds return fields but does not disclose pagination behavior, rate limits, or auth requirements beyond schema. Value added is minimal.

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, front-loaded with purpose and return fields. No extraneous content; every word serves a function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 7 parameters and an output schema, the description is brief. It omits details on pagination, sorting, and filter options. Output fields are mentioned, providing some completeness, but more context would aid agent understanding.

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 has 100% parameter description coverage. The description adds examples of status and priority filtering but these are not direct parameters, so it provides only marginal additional meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists support tickets with filtering and specifies return fields. However, it mentions filtering by status/priority, which does not directly match the schema's 'filter' parameter with predefined options, causing some ambiguity compared to the sibling 'freshdesk_search_tickets'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'freshdesk_search_tickets' or 'freshdesk_get_ticket'. The description lacks explicit context for selection.

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.