Skip to main content
Glama
WYRE-AI

superops-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

superops_tickets_list

List SuperOps.ai tickets with pagination and combined filters by status, priority, client, or assigned technician to find and review service requests.

Instructions

List tickets in SuperOps.ai. Results are paginated with page/pageSize. All supplied filters are combined: a ticket must match every one of status, priority, clientId and technicianId that you provide, and within status and priority it may match any of the listed values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based (default: 1, max: 2147483647)
statusNoFilter by status(es). SuperOps ships with: Open, On Hold, Resolved, Closed, Waiting on third party. Your tenant may rename or extend this list. Values must match it exactly.
clientIdNoFilter by client account ID
pageSizeNoResults per page (default: 50, max: 100)
priorityNoFilter by priority(ies). SuperOps ships with: Critical, High, Medium, Low, Very Low. Your tenant may rename or extend this list.
technicianIdNoFilter by assigned technician user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.0.2
    • removedInput schema / properties / assigneeId
      Removed value: -{
-  "description": "Filter by assigned technician ID",
-  "type": "string"
-}
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Pagination cursor for fetching next page",
-  "type": "string"
-}
    • removedInput schema / properties / max
      Removed value: -{
-  "default": 50,
-  "description": "Maximum number of results (default: 50, max: 500)",
-  "type": "number"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number, 1-based (default: 1, max: 2147483647)",
+  "type": "number"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "default": 50,
+  "description": "Results per page (default: 50, max: 100)",
+  "type": "number"
+}
    • changedInput schema / properties / priority / description
      Previous value: -"Filter by priority(ies): Low, Medium, High, Critical"New value: +"Filter by priority(ies). SuperOps ships with: Critical, High, Medium, Low, Very Low. Your tenant may rename or extend this list."
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status(es): Open, In Progress, Pending, Resolved, Closed"New value: +"Filter by status(es). SuperOps ships with: Open, On Hold, Resolved, Closed, Waiting on third party. Your tenant may rename or extend this list. Values must match it exactly."
    • addedInput schema / properties / technicianId
      Added value: +{
+  "description": "Filter by assigned technician user ID",
+  "type": "string"
+}
    • removedInput schema / properties / unassigned
      Removed value: -{
-  "description": "Show only unassigned tickets",
-  "type": "boolean"
-}
  2. Addedv1.6.3
  3. Removedv1.6.0
  4. First observedv1.2.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses pagination via page/pageSize and the AND-across-filters / OR-within-array matching rule, which is non-obvious behavior. However, it says nothing about permission requirements, default sort order, or whether a total count is returned, leaving notable behavioral gaps for an unannotated tool.

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?

Three tight sentences with zero filler. The core action is front-loaded, pagination is stated next, and the filter-combination rule follows; every sentence carries distinct information.

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

Completeness4/5

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

For a six-parameter list tool with no output schema and no annotations, the description covers the essentials an agent needs: scope, paging, and filter-combination logic. It stops short of describing the returned ticket shape, default ordering, or total-count behavior, which would complete the picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by specifying the boolean combination semantics: every provided filter must match, while status and priority accept any of the listed values. That disambiguates how multiple array values interact, which the schema alone does not state.

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 opens with a specific verb+resource pair ('List tickets in SuperOps.ai'), so the agent immediately knows this is a read/list operation on the tickets collection. It does not, however, explicitly distinguish itself from siblings like superops_tickets_get or superops_tickets_search, so it falls short of the top band.

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

Usage Guidelines3/5

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

Usage is only implied: listing tickets is self-evidently what the tool is for, and the filter-combination sentence hints at when each filter applies. There is no explicit statement of when to choose this over superops_tickets_get, superops_custom_query, or a search-style sibling, and no exclusions or prerequisites are given.

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

Deploy Server

Other Tools