Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_report_groups

Read-only

List all report groups (folders) to browse report organization and retrieve group details like ID, name, and full path.

Instructions

List all report groups (folders) in LogicMonitor (LM) monitoring.

Returns: Array of report groups with: id, name, parentId, full path, description, number of reports, number of subgroups.

What are report groups: Organizational folders for reports, like directories for files. Used to categorize reports by audience, frequency, purpose, or department.

When to use:

  • Browse report organization before creating reports

  • Find group IDs for report operations

  • Understand report hierarchy

  • Navigate to specific report folders

Common organization patterns:

  • By audience: "Executive Reports", "Operations Reports", "Customer Reports"

  • By frequency: "Daily Reports", "Weekly Reports", "Monthly Reports"

  • By department: "IT Reports", "Finance Reports", "Compliance Reports"

  • By type: "SLA Reports", "Capacity Reports", "Alert Summary Reports"

Use cases:

  • Organize reports for different stakeholders

  • Group compliance/audit reports separately

  • Separate internal vs customer-facing reports

  • Structure reports by delivery schedule

Workflow: Use this tool to browse hierarchy, then "list_reports" filtered by groupId to see reports in specific folder.

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_report_group" (details), "list_reports" (reports in group), "create_report_group" (create folder).

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 already declare readOnlyHint=true, confirming safe read. The description adds behavioral details: return format (array of groups with fields), pagination behavior, autoPaginate option, and an important caveat about negative 'total' indicating incomplete results. No contradictions with 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, what are, when to use, common patterns, use cases, workflow, important). It front-loads the main action. Some sections (e.g., common patterns) are detailed but contribute to understanding; overall not overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully covers the tool's purpose, return format, pagination behavior, use cases, related tools, and a critical caveat. No output schema exists, but the description compensates by outlining the return fields. For a list tool with a well-defined schema, this is highly complete.

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?

All 5 parameters have schema descriptions (100% coverage). The description supplements with behavioral context beyond schema, such as the autoPaginate toggle effect and the negative total warning related to pagination. This adds value without repeating schema content.

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 explicitly states 'List all report groups (folders) in LogicMonitor (LM) monitoring.' It clearly identifies the verb (list) and resource (report groups), and distinguishes from sibling tools like 'get_report_group' by explaining that this tool provides a list for browsing hierarchy.

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 dedicated 'When to use' section with bullet points (e.g., browse organization, find group IDs) and a 'Related tools' section naming alternatives like 'list_reports' and 'get_report_group'. It also outlines a workflow: browse with this tool, then use 'list_reports' filtered by groupId.

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