Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_users

Read-only

List all users in LogicMonitor to audit access, check roles, find user IDs, identify inactive users, and support compliance reporting.

Instructions

List all users in LogicMonitor (LM) monitoring.

Returns: Array of users with: id, username, email, roles, status (active/suspended), last login time, created date, API token count.

When to use:

  • Audit user access

  • Find user IDs for API token management

  • Check who has admin access

  • Identify inactive users

  • Compliance reporting

Common filter patterns:

  • Active users: filter:"status:active"

  • By email: filter:"email~*@company.com"

  • By role: filter:"roles:*administrator*"

  • Recent logins: filter:"lastLoginOn>{epoch}"

  • Never logged in: filter:"lastLoginOn:0"

Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.

Related tools: "get_user" (details), "list_roles" (available roles), "list_api_tokens" (user's API tokens).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of results per page (default: 50, max: 1000).
offsetNoStarting offset for pagination (default: 0). Use this to skip a specific number of results.
autoPaginateNoAutomatically fetch all pages (default: false). When true, fetches all results across multiple pages. When false, returns only the requested page. Use false for large result sets to avoid long response times.
filterNoFilter expression using LogicMonitor query syntax. Examples: name:*prod*, displayName~*server*, id>100, hostStatus:normal. Available operators: : (equals), ~ (includes), !: (not equals), !~ (not includes), >: (greater than or equals), <: (less than or equals), > (greater than), < (less than). Multiple conditions: Use comma (,) for AND, use || for OR. Do NOT use &&.
fieldsNoComma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields.
Behavior5/5

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

Annotations declare readOnlyHint=true. The description adds value by disclosing behavior: it reveals the return structure (array of users with specific fields) and an important warning about negative 'total' values indicating incomplete results and requiring pagination. This goes beyond annotations.

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

Conciseness4/5

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

The description is well-structured with clear sections (Returns, When to use, Common filter patterns, Important, Related tools) and is front-loaded with the core purpose. It provides substantial information without being overly verbose for a tool of this complexity.

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 the 5 optional parameters, no output schema, and read-only annotation, the description covers return values, usage scenarios, pagination quirks, and filter examples adequately. It could mention error handling or rate limits but is sufficiently complete for typical use.

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 coverage is 100%, so parameters are well-defined. The description adds common filter pattern examples and emphasizes autoPaginate behavior, which provides practical meaning beyond the schema's formal definitions.

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 'List all users in LogicMonitor (LM) monitoring' with a specific verb and resource. It distinguishes from sibling tools like 'get_user' and 'list_roles' by explicitly mentioning related tools.

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?

The description includes a 'When to use' section listing concrete use cases (audit user access, find user IDs, etc.) and provides common filter patterns for real-world queries, giving clear context for when to invoke this tool.

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

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