Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_collector_groups

Read-only

Retrieve a list of collector groups (organizational folders) in LogicMonitor to browse collector organization and find group IDs for further operations.

Instructions

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

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

What are collector groups: Organizational folders for collectors (monitoring agents), similar to resource/device groups. Used to categorize collectors by location, function, or customer.

When to use:

  • Browse collector organization

  • Find group IDs for collector operations

  • Understand collector deployment structure

  • Navigate to specific collector folders

Common organization patterns:

  • By location: "US-West Collectors", "EU Collectors", "APAC Collectors"

  • By environment: "Production Collectors", "Dev/Test Collectors"

  • By customer: "Customer A Collectors", "Customer B Collectors" (MSP)

  • By datacenter: "DC1 Collectors", "DC2 Collectors", "AWS Collectors"

  • By function: "Network Collectors", "Server Collectors", "Cloud Collectors"

Use cases:

  • Organize collectors by geographic region

  • Group collectors by customer or tenant

  • Separate production vs non-production collectors

  • Structure multi-datacenter collector deployments

Workflow: Use this tool to browse hierarchy, then "list_collectors" filtered by groupId to see collectors 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_collector_group" (details), "list_collectors" (collectors in group), "create_collector_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 indicate readOnlyHint=true. The description adds critical behavioral context: negative total indicates incomplete results, pagination behavior, and autoPaginate option. No contradiction.

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 relatively long but well-organized with headers and bullet points. It provides valuable context, though some sections (e.g., common patterns) may be redundant for an agent.

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?

No output schema exists, so the description adequately explains the return format (fields like id, name, parentId) and pagination details. Covers all necessary information for a list tool.

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% and the description does not add parameter details beyond what the schema provides. The description includes filter syntax in the schema, but the description text itself does not elaborate on parameters.

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 the action (list) and resource (collector groups) and includes details about the returned fields. It distinguishes from siblings like get_collector_group and list_collectors by noting the purpose and related workflow.

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 clear use cases (browse organization, find group IDs) and workflow instructions (use with list_collectors). Does not explicitly state when not to use, but the context is sufficient.

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