Skip to main content
Glama

ninja_get_tickets_by_board

Query tickets from a specific board by board ID, with pagination and sorting options to refine results.

Instructions

Query tickets on a specific ticketing board. Use ninja_list_boards to find board IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesBoard ID
pageSizeNoMax tickets to return
pageIndexNoPage index for pagination (0-based)
sortByNoField to sort by
sortDirectionNoSort direction

Implementation Reference

  • Tool registration entry for 'ninja_get_tickets_by_board' as part of ticketingTools array
    {
      tool: {
        name: 'ninja_get_tickets_by_board',
        description: 'Query tickets on a specific ticketing board. Use ninja_list_boards to find board IDs.',
        inputSchema: {
          type: 'object',
          required: ['boardId'],
          properties: {
            boardId: { type: 'number', description: 'Board ID' },
            pageSize: { type: 'number', description: 'Max tickets to return' },
            pageIndex: { type: 'number', description: 'Page index for pagination (0-based)' },
            sortBy: { type: 'string', description: 'Field to sort by' },
            sortDirection: {
              type: 'string',
              enum: ['ASC', 'DESC'],
              description: 'Sort direction',
            },
          },
        },
      },
      handler: async ({ boardId, ...body }, client: NinjaOneClient) =>
        client.post(`/ticketing/trigger/board/${boardId}/run`, body),
    },
  • Handler function that destructures boardId from args and makes a POST request to /ticketing/trigger/board/{boardId}/run with remaining body parameters
    handler: async ({ boardId, ...body }, client: NinjaOneClient) =>
      client.post(`/ticketing/trigger/board/${boardId}/run`, body),
  • Input schema defining required boardId (number) and optional pageSize, pageIndex, sortBy, sortDirection parameters
    inputSchema: {
      type: 'object',
      required: ['boardId'],
      properties: {
        boardId: { type: 'number', description: 'Board ID' },
        pageSize: { type: 'number', description: 'Max tickets to return' },
        pageIndex: { type: 'number', description: 'Page index for pagination (0-based)' },
        sortBy: { type: 'string', description: 'Field to sort by' },
        sortDirection: {
          type: 'string',
          enum: ['ASC', 'DESC'],
          description: 'Sort direction',
        },
      },
    },
  • src/index.ts:24-24 (registration)
    MCP server registration: ALL_TOOLS are registered and looked up by name, the handler is invoked when the tool is called
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
  • ToolDef interface used by all tool definitions including ninja_get_tickets_by_board
    export interface ToolDef {
      tool: Tool;
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      handler: (args: any, client: NinjaOneClient) => Promise<unknown>;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as pagination defaults, error handling, or what happens with invalid boardId. The description is too minimal for a tool with five parameters.

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 is very concise: two sentences, front-loaded with purpose, and zero waste. Every word earns its place.

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

Completeness2/5

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

With five parameters, no output schema, and many sibling tools, the description lacks essential details like return format, pagination defaults, and error conditions. It is not complete enough for effective agent use.

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?

All parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds no extra meaning beyond the schema, which is adequate but not helpful.

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 action 'query tickets' and the resource 'on a specific ticketing board'. It provides a hint to find board IDs via ninja_list_boards, but does not explicitly differentiate from other ticket-related tools like ninja_get_ticket.

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?

The description includes a pointer to ninja_list_boards for finding board IDs, which helps with usage. However, it does not specify when to avoid using this tool (e.g., for a single ticket) or contrast with sibling tools.

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/Allied-Business-Solutions/ninjaone-mcp'

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