Skip to main content

​
MCP tool: get_tickets_analytics_by_status

Fetch ticket analytics grouped by status for a date range.

​
Example prompt

Get ticket analytics by status for the last week

​
Parameters

ParameterTypeRequiredDescription
dateRangeobjectYesInclusive date range to aggregate over
dateRange.startDatestringYesStart date in YYYY-MM-DD format
dateRange.endDatestringYesEnd date in YYYY-MM-DD format
includeArchivedTicketsbooleanNoInclude archived tickets (default: false)
includeTicketMetadatabooleanNoInclude minimal ticket metadata for drill-down
teamIdsarrayNoOptional array of team IDs to filter by
metadataPagenumberNoPage number for metadata pagination
metadataLimitnumberNoLimit for metadata results per page

​
Response fields

The response will contain aggregated analytics data with the following structure:
FieldTypeDescription
aggregationTypestringType of aggregation performed (“status”)
totalTicketsnumberTotal number of tickets in the date range
totalFoundnumberTotal number of tickets found matching criteria
dateRangeobjectThe date range used for the analysis
includeArchivedTicketsbooleanWhether archived tickets were included
includeTicketMetadatabooleanWhether ticket metadata was included
aggregatedDataarrayArray of team-based analytics objects with status breakdowns

​
Team analytics object fields

Each team in the aggregatedData array contains:
FieldTypeDescription
teamIdstringTeam unique identifier
teamNamestringTeam name
totalnumberTotal number of tickets for this team
ticketCountnumberNumber of tickets for this team (may be 0 for status aggregation)
assigneesobjectAssignee breakdown (empty for status aggregation)
statusBreakdownobjectStatus breakdown for this team’s tickets
assigneeBreakdownobjectAssignee breakdown for this team’s tickets
priorityBreakdownobjectPriority breakdown for this team’s tickets
sentimentBreakdownobjectSentiment breakdown for this team’s tickets

​
Status/Assignee/Priority/Sentiment breakdown fields

Each status, assignee, priority, or sentiment in the breakdowns contains:
FieldTypeDescription
ticketCountnumberNumber of tickets with this status/assignee/priority/sentiment
percentagenumberPercentage of team tickets
statusId/assigneeId/priorityId/sentimentIdstringUnique identifier for the status/assignee/priority/sentiment

​
Sample response

{
  "aggregationType": "status",
  "totalTickets": 2,
  "totalFound": 2,
  "dateRange": {
    "startDate": "2025-01-01",
    "endDate": "2025-09-16"
  },
  "includeArchivedTickets": false,
  "includeTicketMetadata": false,
  "aggregatedData": [
    {
      "teamId": "THEVVHPCCER33E",
      "teamName": "Engineering",
      "total": 2,
      "ticketCount": 0,
      "assignees": {},
      "statusBreakdown": {
        "Open": {
          "ticketCount": 2,
          "percentage": 100,
          "statusId": "3SC6BH2K10X5BSCXF2MFWVYZVYNFX"
        }
      },
      "assigneeBreakdown": {
        "John Doe": {
          "ticketCount": 2,
          "percentage": 100,
          "assigneeId": "UTHOOQNUUXZQQ3"
        }
      },
      "priorityBreakdown": {
        "Urgent": {
          "ticketCount": 1,
          "percentage": 50,
          "priorityId": "CSC6BH2K100SATQR0ZS6KHBW1DFPK"
        },
        "Medium": {
          "ticketCount": 1,
          "percentage": 50,
          "priorityId": "CSC6BH2K10XR2ZVVY84VV8506YN80"
        }
      },
      "sentimentBreakdown": {
        "Neutral": {
          "ticketCount": 1,
          "percentage": 50,
          "sentimentId": "MSC6BH2K1052GKT05M6QTFZVTPQ3S"
        },
        "Negative": {
          "ticketCount": 1,
          "percentage": 50,
          "sentimentId": "MSC6BH2K10CBVVTXD3Y6J5AC3X8R2"
        }
      }
    }
  ]
}