Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_recipient_groups

Read-only

Retrieve all recipient groups to simplify team notifications and manage escalation chains. Find group IDs, members, and descriptions for audit or updates.

Instructions

List all recipient groups in LogicMonitor (LM) monitoring.

Returns: Array of recipient groups with: id, name, description, member count, recipients list.

What are recipient groups: Collections of recipients treated as a single notification target. Simplify escalation chains by notifying entire teams at once. Example: "Database Team" group contains 5 team members - notify group = notify all 5.

When to use:

  • Find group IDs for escalation chains

  • Audit team notification lists

  • Review group membership before changes

  • Simplify notification management

Benefits over individual recipients:

  • Easier management: Update team once, applies to all escalation chains using that group

  • Team notifications: Notify entire team simultaneously

  • Organized: Group by function (DB team, Network team, On-call rotation)

Common recipient groups:

  • "On-Call Engineers" - Current on-call rotation members

  • "Database Team" - All database administrators

  • "Network Operations" - NOC team members

  • "Management" - For escalation to leadership

Use cases:

  • "Notify entire team for critical alerts" → Use group instead of 5 individual recipients

  • "Rotate on-call" → Update group members without touching escalation chains

  • "Add new team member" → Add to group, automatically included in alerts

Workflow: Use this tool to find groups, then use in escalation chains to notify multiple people at once.

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_recipient_group" (details), "list_recipients" (individual members), "list_escalation_chains" (see usage).

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.
Behavior4/5

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

Annotations already declare readOnlyHint: true, so the description does not need to reiterate safety. It adds valuable behavioral context: negative total indicates incomplete results, pagination handling with autoPaginate, and explanation of recipient groups. No contradictions.

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?

The description is well-structured with sections (returns, what are, when to use, benefits, etc.) and is front-loaded with core purpose. Every sentence adds meaning, and the length is appropriate for the context provided.

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?

Given the complexity and absence of output schema, the description is comprehensive. It explains return format, pagination, examples of groups, use cases, and workflow integration with related tools. No gaps.

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?

Input schema has 100% description coverage for 5 parameters. The description adds context about pagination behavior (negative total) and autoPaginate, which goes beyond schema descriptions. Baseline 3 increased to 4 due to added value.

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 recipient groups in LogicMonitor (LM) monitoring' and specifies the return value. It distinguishes from sibling tools like 'list_recipients' and 'list_escalation_chains' by mentioning related tools, and provides specific use cases and examples.

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?

The description provides explicit 'When to use' bullet points (find group IDs, audit teams, etc.) and contrasts with individual recipients. It includes benefits and workflow. However, it lacks explicit 'when not to use' guidelines, though 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