Skip to main content
Glama

ninja_get_organization_end_users

Retrieve all end users associated with an organization by providing its unique ID.

Instructions

Get end users associated with an organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrganization ID

Implementation Reference

  • Handler function that executes the API call to GET /organization/{id}/end-users via the NinjaOneClient.
    handler: async ({ id }, client: NinjaOneClient) =>
      client.get(`/organization/${id}/end-users`),
  • Input schema for ninja_get_organization_end_users, requiring only 'id' (number).
      type: 'object',
      required: ['id'],
      properties: {
        id: { type: 'number', description: 'Organization ID' },
      },
    },
  • Registration of the tool in the organizationTools array as a ToolDef object with name 'ninja_get_organization_end_users'.
    {
      tool: {
        name: 'ninja_get_organization_end_users',
        description: 'Get end users associated with an organization.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Organization ID' },
          },
        },
      },
      handler: async ({ id }, client: NinjaOneClient) =>
        client.get(`/organization/${id}/end-users`),
    },
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits like read-only semantics, pagination, or what happens if the organization ID is invalid. The description carries the full burden but fails to provide adequate transparency.

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 very concise, consisting of a single sentence. It is front-loaded but could benefit from slight expansion without losing conciseness.

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

Completeness3/5

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

Given the simple one-parameter input and no output schema, the description is minimally adequate. However, it does not specify the return format or structure, which would be helpful for an agent.

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% for the single parameter 'id', and the description matches the schema's description ('Organization ID'). The description adds no additional meaning beyond what the schema provides.

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?

The description clearly states it gets end users for an organization, using a specific verb and resource. It distinguishes from siblings like ninja_get_end_user (singular) and ninja_list_end_users (all).

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 is provided on when to use this tool versus alternatives such as ninja_list_end_users or ninja_get_end_user. The description lacks context for tool selection.

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