Skip to main content
Glama

ninja_update_ticket

Updates an existing ticket's details including status, subject, assignee, severity, priority, and tags.

Instructions

Update an existing ticket (status, subject, assignee, severity, priority, tags, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIdYesTicket ID
statusNoNew status ID
subjectNoUpdated subject
assignedAppUserIdNoAssigned technician user ID
severityNo
priorityNo
tagsNoUpdated tags
locationIdNoUpdated location ID
nodeIdNoUpdated device ID

Implementation Reference

  • The handler function for ninja_update_ticket. It destructures ticketId from args and passes the remaining body to a PUT request to /ticketing/ticket/{ticketId}.
      handler: async ({ ticketId, ...body }, client: NinjaOneClient) =>
        client.put(`/ticketing/ticket/${ticketId}`, body),
    },
  • Input schema for ninja_update_ticket. Required: ticketId. Optional: status, subject, assignedAppUserId, severity, priority, tags, locationId, nodeId.
    inputSchema: {
      type: 'object',
      required: ['ticketId'],
      properties: {
        ticketId: { type: 'number', description: 'Ticket ID' },
        status: { type: 'string', description: 'New status ID' },
        subject: { type: 'string', maxLength: 200, description: 'Updated subject' },
        assignedAppUserId: { type: 'number', description: 'Assigned technician user ID' },
        severity: {
          type: 'string',
          enum: ['NONE', 'MINOR', 'MODERATE', 'MAJOR', 'CRITICAL'],
        },
        priority: {
          type: 'string',
          enum: ['NONE', 'LOW', 'MEDIUM', 'HIGH'],
        },
        tags: { type: 'array', items: { type: 'string' }, description: 'Updated tags' },
        locationId: { type: 'number', description: 'Updated location ID' },
        nodeId: { type: 'number', description: 'Updated device ID' },
      },
    },
  • Tool registration as part of the ticketingTools array. The tool definition includes name (ninja_update_ticket), description, inputSchema, and the handler.
    {
      tool: {
        name: 'ninja_update_ticket',
        description: 'Update an existing ticket (status, subject, assignee, severity, priority, tags, etc.).',
        inputSchema: {
          type: 'object',
          required: ['ticketId'],
          properties: {
            ticketId: { type: 'number', description: 'Ticket ID' },
            status: { type: 'string', description: 'New status ID' },
            subject: { type: 'string', maxLength: 200, description: 'Updated subject' },
            assignedAppUserId: { type: 'number', description: 'Assigned technician user ID' },
            severity: {
              type: 'string',
              enum: ['NONE', 'MINOR', 'MODERATE', 'MAJOR', 'CRITICAL'],
            },
            priority: {
              type: 'string',
              enum: ['NONE', 'LOW', 'MEDIUM', 'HIGH'],
            },
            tags: { type: 'array', items: { type: 'string' }, description: 'Updated tags' },
            locationId: { type: 'number', description: 'Updated location ID' },
            nodeId: { type: 'number', description: 'Updated device ID' },
          },
        },
      },
      handler: async ({ ticketId, ...body }, client: NinjaOneClient) =>
        client.put(`/ticketing/ticket/${ticketId}`, body),
    },
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Update', implying mutation, but does not clarify whether it performs a full replacement or partial update (patch), what permissions are needed, or side effects. This is insufficient for a 9-parameter mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, efficiently conveying the core action. However, it is so concise that it lacks critical details, crossing from brevity into under-specification. A few more words would improve it without sacrificing conciseness.

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?

Given the complexity (9 parameters, no output schema), the description is too sparse. It does not explain return values, error handling, idempotency, or required permissions. For a mutation tool, this leaves significant gaps in the agent's understanding.

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?

Schema coverage is 78%, so most parameters have clear descriptions in the schema. The description lists a few fields but maps 'assignee' to 'assignedAppUserId' indirectly, which could confuse. The 'etc.' adds no value. At best, the description marginally supplements schema documentation.

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 ('Update an existing ticket') and lists several updatable fields ('status, subject, assignee, severity, priority, tags, etc.'), distinguishing it from create tools like ninja_create_ticket. However, the trailing 'etc.' adds vagueness.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., ninja_create_ticket for new tickets). No mention of prerequisites like the ticket must exist or that only provided fields are updated. The agent is left to infer usage context.

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