Okta MCP Server

okta_list_groups

List Okta groups using optional query, search, filter, and pagination parameters to retrieve up to 200 groups at a time.

Instructions

List Okta groups. Supports q, search, filter, pagination, and a limit up to 200.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "okta_list_groups"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`after`	No
`limit`	No
`filter`	No
`search`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description discloses supported query features and a maximum limit of 200, which is helpful. However, it does not mention that the operation is read-only, potential rate limits, or pagination behavior (use of 'after' parameter). With no annotations, the description carries the full burden, and these gaps limit 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 concise: a single sentence that states the purpose and lists supported features. It is front-loaded and wastes no words. Minor improvement would be separating features for readability.

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 no output schema and no annotations, the description provides a basic overview but lacks details on return format, default ordering, or required permissions. For a simple list tool it is adequate but not complete.

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 0% schema description coverage, the description must compensate. It mentions q, search, filter, pagination, and limit, adding meaning beyond the schema. However, it does not explain differences between q, search, and filter, or detail the 'after' parameter. Partial but not thorough.

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 lists Okta groups and supports common query parameters (q, search, filter, pagination). However, it does not explicitly differentiate from sibling tools like okta_list_user_groups or okta_list_group_users, though the resource is distinct.

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. For example, if listing groups for a specific user, okta_list_user_groups would be more appropriate. The description lacks context on prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.