Skip to main content
Glama

roles_list

Retrieve all company roles with pagination, hierarchy details, and assignment counts for structured role management.

Instructions

List all roles within the company.

Returns all roles with pagination support, including role hierarchy and assignment counts.

Workflow tips:

  • Shows role hierarchy with parent_role_id

  • Includes assignment and sub-role counts

  • Use pagination for companies with many roles

  • Cached for 15 minutes for better performance

Common use cases:

  • List all roles: {}

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

  • View role hierarchy and structure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNoPagination start (default: 0)
limitNoNumber of items to return (default: 100, max: 500)
Behavior5/5

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

Discloses caching behavior (15 minutes), pagination support, and returned data (hierarchy, assignment counts). No annotations provided, so description fully covers behavioral traits.

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?

Concise, well-structured with bullet points. Front-loaded with clear purpose. Every sentence adds value without redundancy.

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 pagination, caching, and returned data. No output schema, but description adequately sets expectations for a simple list tool. Could mention rate limits but not necessary.

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%, with parameters for pagination described in the schema. Description mentions use cases with example values but does not add significant meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists all roles within the company, with a specific verb and resource. It distinguishes itself from sibling tools like roles_create or roles_add_role_assignment.

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

Usage Guidelines4/5

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

Provides workflow tips and common use cases, including pagination and caching. Does not explicitly exclude alternatives but offers clear context for when to use.

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