Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_list_queues

Retrieve all available ticket queues from Autotask to obtain queue IDs for filtering tickets.

Instructions

List all available ticket queues in Autotask. Use this to find queue IDs for filtering tickets by queue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'autotask_list_queues' tool. It calls picklistCache.getQueues() and maps the result to { id, name, isActive } objects.
    ['autotask_list_queues', async () => {
      const queues = await this.picklistCache.getQueues();
      return { result: queues.map(q => ({ id: q.value, name: q.label, isActive: q.isActive })), message: `Found ${queues.length} queues` };
    }],
  • Schema definition for 'autotask_list_queues' — no required input parameters.
    // Picklist / Queue tools
    {
      name: 'autotask_list_queues',
      description: 'List all available ticket queues in Autotask. Use this to find queue IDs for filtering tickets by queue.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Registration of 'autotask_list_queues' in the TOOL_CATEGORIES under the 'utility' category.
    utility: {
      description: 'Connection testing and field/picklist discovery',
      tools: ['autotask_test_connection', 'autotask_list_queues', 'autotask_list_ticket_statuses', 'autotask_list_ticket_priorities', 'autotask_get_field_info']
  • The getQueues() helper in PicklistCache that fetches picklist values for the 'queueID' field on the 'Tickets' entity.
     */
    async getQueues(): Promise<PicklistValue[]> {
      return this.getPicklistValues('Tickets', 'queueID');
    }
  • Core helper getPicklistValues that loads cached field info and filters for active picklist values.
     */
    async getPicklistValues(entityType: string, fieldName: string): Promise<PicklistValue[]> {
      const fields = await this.getFields(entityType);
      const field = fields.find(f => f.name.toLowerCase() === fieldName.toLowerCase());
    
      if (!field || !field.isPickList || !field.picklistValues) {
        return [];
      }
    
      return field.picklistValues.filter(v => v.isActive !== false);
    }
Behavior5/5

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

The description discloses that the tool lists all available queues, which is a read-only operation. Despite no annotations, the description is fully transparent about the behavior and does not contradict any structured metadata.

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?

The description consists of two concise sentences with no redundant information. It is front-loaded with the action and purpose, making it easy to parse.

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 tool has no parameters and no output schema, the description covers all necessary aspects: what it does and why to use it. The tool's simplicity is matched by a complete and clear description.

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?

The input schema is empty (0 parameters), so baseline is 4. The description adds value by explaining the purpose of the list (to find queue IDs), which is sufficient for a parameterless tool.

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 lists all available ticket queues and explicitly mentions using it to find queue IDs for filtering tickets. This is a specific verb+resource combination, and it is distinct from sibling list tools like autotask_list_categories.

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 provides a clear use case: 'Use this to find queue IDs for filtering tickets by queue.' While it does not mention when not to use or alternative tools, the guidance is explicit and contextually appropriate for a simple list tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asachs01/autotask-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server