Skip to main content
Glama

ninja_get_backup_jobs

Retrieve backup job history and status across managed devices using device filters and pagination.

Instructions

Get backup job history and status across managed devices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dfNoDevice filter expression
pageSizeNoMax results to return
cursorNoPagination cursor from previous response

Implementation Reference

  • The handler function that executes the tool logic. It calls client.get('/backup/jobs', clean(args)) to fetch backup job data.
    handler: async (args, client: NinjaOneClient) =>
      client.get('/backup/jobs', clean(args)),
  • Input schema definition for the tool, specifying three optional properties: df (string), pageSize (number), and cursor (string).
    inputSchema: {
      type: 'object',
      properties: {
        df: { type: 'string', description: 'Device filter expression' },
        pageSize: { type: 'number', description: 'Max results to return' },
        cursor: { type: 'string', description: 'Pagination cursor from previous response' },
      },
    },
  • The tool is defined as an entry in the backupTools array (line 5-21) with the name 'ninja_get_backup_jobs'. This array is then exported and spread into ALL_TOOLS in src/tools/index.ts (line 22).
    export const backupTools: ToolDef[] = [
      {
        tool: {
          name: 'ninja_get_backup_jobs',
          description: 'Get backup job history and status across managed devices.',
          inputSchema: {
            type: 'object',
            properties: {
              df: { type: 'string', description: 'Device filter expression' },
              pageSize: { type: 'number', description: 'Max results to return' },
              cursor: { type: 'string', description: 'Pagination cursor from previous response' },
            },
          },
        },
        handler: async (args, client: NinjaOneClient) =>
          client.get('/backup/jobs', clean(args)),
      },
  • The backupTools array (containing this tool) is imported and spread into the ALL_TOOLS central registry.
      ...backupTools,
      ...systemTools,
    ];
  • The 'clean' utility is imported from '../utils.js' and used in the handler to remove undefined/null properties from args before sending the request.
    import { clean } from '../utils.js';
Behavior2/5

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

The description only says 'Get backup job history and status,' implying a read operation, but lacks details like pagination behavior, authentication requirements, rate limits, or what happens when no filter is applied. Without annotations, the description should provide more behavioral context.

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?

Single, focused sentence with zero waste. Content is front-loaded and immediately communicates the tool's purpose.

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?

Without output schema or annotations, the description is too brief. It fails to mention pagination (despite cursor parameter), filtering specifics, or how results are structured. For an informational retrieval tool, this leaves gaps.

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 100% and each parameter has a description, meeting the baseline. However, the description adds no additional meaning beyond the schema; e.g., 'df' is not elaborated on format, and pagination isn't explained.

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?

Clearly states the verb 'Get' and the resource 'backup job history and status across managed devices.' This distinguishes it from sibling tools like ninja_query_backup_usage, which focuses on usage rather than job history.

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?

Provides no guidance on when to use this tool vs. alternatives. Among many sibling tools (e.g., ninja_get_device_active_jobs, ninja_query_backup_usage), there is no explanation of how they differ or when to choose this one.

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