Skip to main content
Glama
kula-ai

@kula-ai/mcp-server

Official
by kula-ai

list_users

List organization users with filters for status, role, department, office, permissions, and full-text search. Defaults to active users.

Instructions

List users in the organization. Defaults to active users; use the status filter to include pending, deactivated, or imported. Supports filtering by role, department, office, granted permissions, and a full-text query across name and email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
limitNoItems per page
sort_byNoField to sort by (default: created_at)
sort_orderNoSort direction
statusNoComma-separated user statuses: active, pending, deactivated, imported. Defaults to active when omitted.
role_idNoComma-separated role IDs to filter by
department_idNoComma-separated department IDs to filter by
office_idNoComma-separated office IDs to filter by
permissionNoComma-separated permission keys in `resource:action` format (e.g. `users:manage,jobs:read`). Matches users whose role grants any of the listed permissions.
queryNoFull-text search across user name and email
created_afterNoISO 8601 datetime lower bound on created_at
created_beforeNoISO 8601 datetime upper bound on created_at
updated_afterNoISO 8601 datetime lower bound on updated_at
updated_beforeNoISO 8601 datetime upper bound on updated_at
Behavior3/5

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

No annotations provided, so description bears full burden. It states basic behavior (listing users) and filter capabilities but omits details like pagination behavior, response structure, authorization needs, or rate limits. Not misleading but incomplete.

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?

Two concise sentences, front-loaded with purpose and key default. Every sentence adds value without redundancy. Well-structured for quick understanding.

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?

Despite 14 parameters and no output schema, the description is minimal. It lacks explanation of pagination, sort behavior, and response format. For a tool with rich filtering, more context is needed for effective usage.

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%, so baseline is 3. Description adds value by explaining default status behavior and that permission filter checks by role, but does not cover all parameters (e.g., pagination, sort, date filters are not elaborated). Marginal addition beyond schema.

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 'List users in the organization' and specifies default active users with filter options. It distinguishes from many sibling list tools by mentioning specific filtering capabilities, though it doesn't explicitly differentiate from similar tools like list_candidates or search_candidates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Description explains default behavior (active users) and how to include other statuses via filter. It lists supported filters but does not provide explicit when-to-use guidance or alternatives (e.g., when to use search_candidates instead). No exclusion criteria are mentioned.

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

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