Skip to main content
Glama

ninja_list_automation_scripts

Lists all automation scripts in your NinjaOne platform for quick access and management.

Instructions

List all automation scripts available in NinjaOne.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'ninja_list_automation_scripts' makes a GET request to '/automation/scripts' via the NinjaOneClient.
    {
      tool: {
        name: 'ninja_list_automation_scripts',
        description: 'List all automation scripts available in NinjaOne.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/automation/scripts'),
  • The input schema for 'ninja_list_automation_scripts' - no parameters required (empty object).
    description: 'List all automation scripts available in NinjaOne.',
    inputSchema: { type: 'object', properties: {} },
  • The tool is registered in the ALL_TOOLS array via the systemTools export, which is combined into the global tool map.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • src/index.ts:24-24 (registration)
    The tool is registered in the MCP server via toolMap, which maps tool names to their handler functions.
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
  • The NinjaOneClient.get() method that performs the actual GET request for '/automation/scripts'.
      async get<T = unknown>(path: string, params?: Record<string, unknown>): Promise<T> {
        try {
          const res = await this.http.get<T>(path, {
            params,
            headers: await this.authHeader(),
          });
          return res.data;
        } catch (err) {
          throw new Error(`GET ${path} failed: ${apiError(err)}`);
        }
      }
    
      async post<T = unknown>(path: string, body?: unknown): Promise<T> {
        try {
          const res = await this.http.post<T>(path, body, {
            headers: await this.authHeader(),
          });
          return res.data;
        } catch (err) {
          throw new Error(`POST ${path} failed: ${apiError(err)}`);
        }
      }
    
      async patch<T = unknown>(path: string, body?: unknown): Promise<T> {
        try {
          const res = await this.http.patch<T>(path, body, {
            headers: await this.authHeader(),
          });
          return res.data;
        } catch (err) {
          throw new Error(`PATCH ${path} failed: ${apiError(err)}`);
        }
      }
    
      async put<T = unknown>(path: string, body?: unknown): Promise<T> {
        try {
          const res = await this.http.put<T>(path, body, {
            headers: await this.authHeader(),
          });
          return res.data;
        } catch (err) {
          throw new Error(`PUT ${path} failed: ${apiError(err)}`);
        }
      }
    
      async delete<T = unknown>(path: string): Promise<T> {
        try {
          const res = await this.http.delete<T>(path, {
            headers: await this.authHeader(),
          });
          return res.data;
        } catch (err) {
          throw new Error(`DELETE ${path} failed: ${apiError(err)}`);
        }
      }
    }
    
    function apiError(err: unknown): string {
      if (err instanceof AxiosError) {
        const data = err.response?.data;
        if (data && typeof data === 'object') return JSON.stringify(data);
        if (typeof data === 'string' && data) return data;
        return err.message;
      }
      return String(err);
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states a read operation but does not mention authentication, rate limits, or any other behavioral traits. The description is insufficient for a tool with zero annotation coverage.

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 a single, concise sentence with no unnecessary words. It is front-loaded and efficient.

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?

Despite no parameters and trivial operation, the description lacks details about return format or pagination. Without an output schema, the agent needs more context to understand the tool's output.

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?

With no parameters and 100% schema coverage, the baseline is 3. The description adds no additional parameter information, as there are none to describe.

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?

Description clearly states the tool lists all automation scripts in NinjaOne, with a specific verb and resource. It distinguishes itself from sibling tools, as no other tool explicitly lists automation scripts.

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, such as before running a script or checking available scripts. The description provides no context about prerequisites or typical use cases.

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