Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

get_zia_user_groups

Read-only

Retrieve ZIA user groups to manage access control and policies. Filter by group ID or use case-insensitive name match to find groups for assignment.

Instructions

Read ZIA user groups for access control and policy assignment. Pass name="<literal admin-supplied name>" (e.g. name="A000") for a case-insensitive substring match resolved client-side — this is the right knob for find-by-name workflows. Pass group_id= to fetch a single group. The search parameter forwards to the ZIA API and is unreliable for name-based lookups; prefer name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoOperation to perform. Use 'read' to paginate/filter groups or fetch a single group by ID.read
group_idNoID of the user group. When provided, returns a single group; otherwise returns a list of groups.
nameNoCase-insensitive substring match on the group's name field. Resolved client-side AFTER fetching the full group list, so names like 'A000', 'a000', 'HR', 'finance' all match regardless of the underlying name's casing. Use this when you have a literal group name from the admin and just need to find its ID. The server-side `search` parameter is unreliable for groups (it sometimes matches user login IDs instead of group names) — prefer `name` for find-by-name workflows.
searchNoServer-side query forwarded to the ZIA list_groups endpoint. ZIA's documented behavior here is unreliable (the API has been observed to match against user login IDs rather than group names). Prefer `name` for case-insensitive substring matching on the group's name. Use `search` only when you specifically need the server-side semantics.
defined_byNoString value defined by the group name or other applicable attributes. Used to further filter results.
pageNoPage offset for pagination when listing groups.
page_sizeNoPage size for listing groups. Default is 100; maximum is 1000.
sort_byNoSort field for listing groups. Supported: id, name, expiry, status, external_id, rank, mod_time.
sort_orderNoSort order for listing groups. Supported: asc, desc, rule_execution.
serviceNoZscaler service name. Always 'zia' for this tool.zia

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Consistent with readOnlyHint=true annotation. Adds useful details beyond annotations, such as the client-side substring matching behavior of `name` and the unreliability of `search`. No contradictions.

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?

Four sentences with no redundancy. Front-loaded with purpose, then parameter guidance. Every sentence adds value, no wasted words.

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

Completeness4/5

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

Covers main use cases (reading groups, filtering by name/ID) and highlights pitfalls (search unreliability). Pagination and output details are left to parameters and output schema, which is acceptable. Slight gap: no mention of pagination behavior, but parameters exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, baseline 3. Description adds meaningful guidance: clarifies the semantic difference between `name` (client-side) and `search` (server-side, unreliable), and the purpose of `group_id` for single group fetch. This exceeds the schema descriptions.

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 verb 'Read' and resource 'ZIA user groups for access control and policy assignment'. It is specific and contextual, but lacks explicit differentiation from sibling tools like get_zia_dlp_dictionaries, 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use `name`, `group_id`, and `search` parameters, including a clear recommendation to prefer `name` for find-by-name workflows and warning that `search` is unreliable. This covers both when and when-not to use alternatives.

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/zscaler/zscaler-mcp-server'

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