Skip to main content
Glama
Rootly-AI-Labs

Rootly MCP server

Official

listUsers

Retrieve and filter user data from the Rootly MCP server using parameters like email, creation date, and sorting options to manage and analyze user information efficiently.

Instructions

List users

Query Parameters:

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_email: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: comma separated if needed. eg: created_at,updated_at

  • include: comma separated if needed. eg: email_addresses,phone_numbers

Responses:

  • 200 (Success): user found

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_created_at_gtNo
filter_created_at_gteNo
filter_created_at_ltNo
filter_created_at_lteNo
filter_emailNo
filter_searchNo
includeNocomma separated if needed. eg: email_addresses,phone_numbers
page_numberNo
page_sizeNo
sortNocomma separated if needed. eg: created_at,updated_at

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • DEFAULT_ALLOWED_PATHS includes the "/users" endpoint (lines 150-152), which enables the "listUsers" tool by including the corresponding OpenAPI path in the filtered spec.
    DEFAULT_ALLOWED_PATHS = [
        "/incidents/{incident_id}/alerts",
        "/alerts",
        "/alerts/{alert_id}",
        "/severities",
        "/severities/{severity_id}",
        "/teams",
        "/teams/{team_id}",
        "/services",
        "/services/{service_id}",
        "/functionalities",
        "/functionalities/{functionality_id}",
        # Incident types
        "/incident_types",
        "/incident_types/{incident_type_id}",
        # Action items (all, by id, by incident)
        "/incident_action_items",
        "/incident_action_items/{incident_action_item_id}",
        "/incidents/{incident_id}/action_items",
        # Workflows
        "/workflows",
        "/workflows/{workflow_id}",
        # Workflow runs
        "/workflow_runs",
        "/workflow_runs/{workflow_run_id}",
        # Environments
        "/environments",
        "/environments/{environment_id}",
        # Users
        "/users",
        "/users/{user_id}",
        "/users/me",
        # Status pages
        "/status_pages",
        "/status_pages/{status_page_id}",
        # On-call schedules and shifts
        "/schedules",
        "/schedules/{schedule_id}",
        "/schedules/{schedule_id}/shifts",
        "/shifts",
        "/schedule_rotations/{schedule_rotation_id}",
        "/schedule_rotations/{schedule_rotation_id}/schedule_rotation_users",
        "/schedule_rotations/{schedule_rotation_id}/schedule_rotation_active_days",
        # On-call overrides
        "/schedules/{schedule_id}/override_shifts",
        "/override_shifts/{override_shift_id}",
        # On-call shadows and roles
        "/schedules/{schedule_id}/on_call_shadows",
        "/on_call_shadows/{on_call_shadow_id}",
        "/on_call_roles",
        "/on_call_roles/{on_call_role_id}",
    ]
  • FastMCP.from_openapi() call registers all operations from the filtered OpenAPI specification as MCP tools, including "listUsers" for GET /v1/users based on Rootly API spec.
    mcp = FastMCP.from_openapi(
        openapi_spec=filtered_spec,
        client=http_client.client,
        name=name,
        timeout=30.0,
        tags={"rootly", "incident-management"},
    )
  • AuthenticatedHTTPXClient.request() is the core proxy method that executes HTTP requests to Rootly API for all dynamic tools, including listUsers.
    async def request(self, method: str, url: str, **kwargs):
        """Override request to transform parameters."""
        # Transform query parameters
        if 'params' in kwargs:
            kwargs['params'] = self._transform_params(kwargs['params'])
    
        # Call the underlying client's request method and let it handle everything
        return await self.client.request(method, url, **kwargs)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions pagination parameters and filtering capabilities, it doesn't describe authentication requirements (though the 401 response example hints at token-based auth), rate limits, whether this is a read-only operation, what happens with large result sets, or typical response formats beyond the minimal example. The description provides some operational context but leaves critical behavioral aspects unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is poorly structured with redundant formatting. It wastes space repeating 'No description' for most parameters and includes verbose HTTP response documentation that belongs in an API spec rather than an MCP tool description. The core purpose statement is buried under unnecessary technical details, making it inefficient for an AI agent to parse quickly.

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?

For a tool with 10 parameters, no annotations, and complex filtering capabilities, this description is inadequate. While there's an output schema (implied by the context signals), the description doesn't provide enough context about the tool's behavior, usage patterns, or relationship to sibling tools. The response examples are generic and unhelpful, failing to illustrate actual user data structures.

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 description coverage is only 20% (only 'include' and 'sort' have descriptions in schema), but the description compensates by providing parameter lists with some examples. However, most parameters have 'No description' in the text, and the examples are minimal. The description adds marginal value beyond the schema but doesn't fully explain parameter purposes, formats, or constraints for the majority of parameters.

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

Purpose2/5

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

The description states 'List users' which is a tautology of the tool name 'listUsers'. It provides no additional specificity about what kind of users, from what system, or what scope. While it's clear this is a listing operation, it doesn't distinguish itself from potential sibling list tools or provide meaningful context beyond the name.

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

Usage Guidelines1/5

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

There is absolutely no guidance about when to use this tool versus alternatives. The description doesn't mention any prerequisites, context for usage, or comparison to sibling tools like 'getCurrentUser' or other list operations. The agent receives zero direction about appropriate use cases.

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

Related 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/Rootly-AI-Labs/Rootly-MCP-server'

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