Skip to main content
Glama
kapilduraphe

Okta MCP Server

remove_user_from_group

Remove a user from a specific group in Okta by providing the user ID and group ID through the Okta MCP Server.

Instructions

Remove a user from a group in Okta

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesID of the group
userIdYesID of the user to remove from the group

Implementation Reference

  • The main handler function for the 'remove_user_from_group' tool. It validates input using Zod schema, retrieves Okta client, calls the Okta API to unassign user from group, and returns a formatted success or error response.
    remove_user_from_group: async (request: { parameters: unknown }) => {
      const { groupId, userId } = groupSchemas.removeUserFromGroup.parse(
        request.parameters
      );
    
      try {
        const oktaClient = getOktaClient();
    
        await oktaClient.groupApi.unassignUserFromGroup({
          groupId,
          userId,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `User with ID ${userId} has been successfully removed from group with ID ${groupId}.`,
            },
          ],
        };
      } catch (error) {
        console.error("Error removing user from group:", error);
        return {
          content: [
            {
              type: "text",
              text: `Failed to remove user from group: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    },
  • Zod schema definition for validating the input parameters: groupId and userId, both required strings.
    removeUserFromGroup: z.object({
      groupId: z.string().min(1, "Group ID is required"),
      userId: z.string().min(1, "User ID is required"),
    }),
  • Tool registration entry in the groupTools array, defining the tool name, description, and JSON input schema for MCP protocol.
    {
      name: "remove_user_from_group",
      description: "Remove a user from a group in Okta",
      inputSchema: {
        type: "object",
        properties: {
          groupId: {
            type: "string",
            description: "ID of the group",
          },
          userId: {
            type: "string",
            description: "ID of the user to remove from the group",
          },
        },
        required: ["groupId", "userId"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Remove' implies a destructive mutation, the description lacks details on permissions required, whether the action is reversible, error handling, or side effects. This is inadequate for a mutation 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It lacks critical context such as return values, error conditions, or behavioral nuances, leaving significant gaps for an agent to operate safely and effectively.

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 description coverage is 100%, with clear descriptions for both parameters ('groupId' and 'userId'). The description does not add any additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('Remove') and target ('a user from a group in Okta'), making the purpose immediately understandable. However, it does not differentiate this tool from similar sibling tools like 'assign_users_to_groups' or 'assign_user_to_group', which would require explicit comparison to achieve a score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'assign_users_to_groups' and 'assign_user_to_group' available, there is no indication of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Related 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/kapilduraphe/okta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server