Skip to main content
Glama

ninja_configure_webhook

Configure a webhook endpoint to receive NinjaOne events. Subscribe to activity types and add HMAC secret for verification.

Instructions

Configure a webhook endpoint to receive NinjaOne events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL to receive webhook payloads
secretNoSecret for HMAC signature verification
activitiesNoActivity types to subscribe to

Implementation Reference

  • The handler for ninja_configure_webhook — makes a PUT request to /webhook with the provided args (url, secret, activities).
    handler: async (args, client: NinjaOneClient) => client.put('/webhook', args),
  • The tool definition object for ninja_configure_webhook, registered as part of the systemTools array. Defines name, description, and inputSchema (schema).
      tool: {
        name: 'ninja_configure_webhook',
        description: 'Configure a webhook endpoint to receive NinjaOne events.',
        inputSchema: {
          type: 'object',
          required: ['url'],
          properties: {
            url: { type: 'string', description: 'HTTPS URL to receive webhook payloads' },
            secret: { type: 'string', description: 'Secret for HMAC signature verification' },
            activities: {
              type: 'array',
              items: { type: 'string' },
              description: 'Activity types to subscribe to',
            },
          },
        },
      },
      handler: async (args, client: NinjaOneClient) => client.put('/webhook', args),
    },
  • Input schema for ninja_configure_webhook: requires 'url' (string), optional 'secret' (string), and optional 'activities' (array of strings).
    inputSchema: {
      type: 'object',
      required: ['url'],
      properties: {
        url: { type: 'string', description: 'HTTPS URL to receive webhook payloads' },
        secret: { type: 'string', description: 'Secret for HMAC signature verification' },
        activities: {
          type: 'array',
          items: { type: 'string' },
          description: 'Activity types to subscribe to',
        },
      },
  • systemTools is spread into ALL_TOOLS, which is the final exported array used to register all tools with MCP.
    ...systemTools,
  • ToolDef interface that defines the shape of each tool: a 'tool' (name, description, inputSchema) and a 'handler' function.
    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?

Without annotations, the description should disclose behavioral traits. It only states 'configure' without mentioning side effects (e.g., overwriting existing webhook), required permissions, or authentication beyond the 'secret' parameter.

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

Conciseness3/5

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

The description is a single sentence, very concise, but it sacrifices necessary detail. While efficient, it could be expanded without verbosity.

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 tool is a configuration action with multiple parameters and no output schema, the description lacks crucial context about update behavior, error states, and response format, making it insufficient for safe agent invocation.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds no additional parameter information beyond the schema, so baseline score of 3 is appropriate.

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 tool configures a webhook endpoint to receive events, distinguishing it from the sibling tool 'ninja_disable_webhook'. However, it lacks details on whether this creates or updates an existing configuration.

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 like disabling or testing webhooks. No prerequisites or context for appropriate use are provided.

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