Skip to main content
Glama

users_list_role_assignments

Lists all role assignments for a specific user. Supports pagination for users with multiple roles.

Instructions

List role assignments for a user.

Returns all role assignments for a specific user with pagination support.

Workflow tips:

  • Shows all roles assigned to the user

  • Includes role hierarchy information

  • Use pagination for users with many role assignments

  • Cached for 10 minutes

  • Useful for auditing user permissions

Common use cases:

  • List all role assignments: { "id": 123 }

  • Paginated list: { "id": 123, "start": 0, "limit": 50 }

  • Check user's current roles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the user
startNoPagination start (default: 0)
limitNoNumber of items to return (max: 500)
Behavior4/5

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

In the absence of annotations, the description discloses caching behavior (10 minutes), inclusion of role hierarchy, and pagination support. This adds valuable behavioral context beyond a generic list operation.

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 well-organized with a clear opening sentence, bullet points for workflow tips, and use case examples. Every sentence contributes meaning without unnecessary verbosity.

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?

Given no output schema, the description explains what the tool returns (role assignments, hierarchy) and highlights caching and pagination. It is sufficiently complete for a list operation, though it could mention error handling or permission requirements.

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?

The input schema covers all three parameters with descriptions (coverage 100%). The description enhances meaning with concrete examples (e.g., listing all roles, paginated list), helping the agent understand parameter usage beyond schema definitions.

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 it lists role assignments for a user and includes workflow tips and use cases. However, it does not explicitly differentiate from sibling tools like roles_get_role_assignments, which may cause ambiguity.

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?

Workflow tips and use cases provide guidance on when to use the tool (e.g., auditing, pagination). However, it lacks explicit instructions on when not to use it or alternatives, leaving the agent without full context for decision-making.

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/iamsamuelfraga/mcp-pipedrive'

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