MCP tool: get_tickets_analytics_by_assignee
Fetch comprehensive assignee performance metrics and ticket analytics for a specified date range.
Example prompt
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| dateRange | object | Yes | Inclusive date range to aggregate over |
| dateRange.startDate | string | Yes | Start date in YYYY-MM-DD format |
| dateRange.endDate | string | Yes | End date in YYYY-MM-DD format |
| includeArchivedTickets | boolean | No | Include archived tickets (default: false) |
| includeTicketMetadata | boolean | No | Include minimal ticket metadata for drill-down (default: true) |
| teamIds | array | No | Optional array of team IDs to filter by |
| metadataPage | number | No | Page number for metadata pagination (default: 1) |
| metadataLimit | number | No | Limit for metadata results per page (default: 25) |
Response fields
The response will contain aggregated analytics data with the following structure:| Field | Type | Description |
|---|---|---|
| aggregationType | string | Type of aggregation performed (“assignee”) |
| totalTickets | number | Total number of tickets in the date range |
| totalFound | number | Total number of tickets found matching criteria |
| dateRange | object | The date range used for the analysis |
| includeArchivedTickets | boolean | Whether archived tickets were included |
| includeTicketMetadata | boolean | Whether ticket metadata was included |
| aggregatedData | array | Array of team-based analytics objects with assignee breakdowns |
Team analytics object fields
Each team in theaggregatedData array contains:
| Field | Type | Description |
|---|---|---|
| teamId | string | Team unique identifier |
| teamName | string | Team name |
| total | number | Total number of tickets for this team |
| ticketCount | number | Number of tickets for this team |
| assignees | object | Detailed assignee breakdown with nested analytics |
| percentage | number | Percentage of total tickets |
Assignee breakdown fields
Each assignee in theassignees object contains:
| Field | Type | Description |
|---|---|---|
| assigneeId | string | Assignee unique identifier |
| assigneeName | string | Assignee name |
| assigneeEmail | string | Assignee email address |
| ticketCount | number | Number of tickets assigned to this assignee |
| percentage | number | Percentage of team tickets |
| statusBreakdown | object | Status breakdown for this assignee’s tickets |
| priorityBreakdown | object | Priority breakdown for this assignee’s tickets |
| sentimentBreakdown | object | Sentiment breakdown for this assignee’s tickets |
Status/Priority/Sentiment breakdown fields
Each status, priority, or sentiment in the breakdowns contains:| Field | Type | Description |
|---|---|---|
| ticketCount | number | Number of tickets with this status/priority/sentiment |
| percentage | number | Percentage of assignee’s tickets |
| statusId/priorityId/sentimentId | string | Unique identifier for the status/priority/sentiment |