Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_website_groups

Read-only

List website group folders in LogicMonitor to browse monitoring hierarchy, find group IDs, and organize website monitors. Returns details like id, name, parentId, and number of websites.

Instructions

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

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

What are website groups: Organizational folders for website monitors (synthetic checks), similar to resource/device groups. Used to categorize monitored URLs/services by application, environment, or customer.

When to use:

  • Browse website organization before creating monitors

  • Find group IDs for website operations

  • Understand monitoring hierarchy

  • Navigate to specific website folders

Common organization patterns:

  • By application: "E-Commerce Site", "API Endpoints", "Marketing Pages"

  • By environment: "Production URLs", "Staging URLs", "DR Sites"

  • By location: "US Sites", "EU Sites", "APAC Sites"

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

  • By type: "Public Websites", "Internal Apps", "Third-Party APIs"

Use cases:

  • Organize monitors by application or service

  • Group customer-facing vs internal endpoints

  • Separate production vs non-production monitoring

  • Structure multi-region website monitoring

Workflow: Use this tool to browse hierarchy, then "list_websites" filtered by groupId to see monitors 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_website_group" (details), "list_websites" (websites in group), "create_website_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.
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds valuable context: the return structure (array with id, name, parentId, etc.), handling of negative 'total' for incomplete results, and pagination behavior. No contradiction 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 website groups, When to use, etc.) and front-loaded purpose. Some sections are explanatory (e.g., 'What are website groups') which is helpful for context but could be trimmed for an AI agent. Overall efficient.

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 is comprehensive: it explains the concept, usage scenarios, organizational patterns, workflow, pagination pitfalls, and related tools. No output schema exists, so the description compensates by detailing the return array fields. Fully satisfies information needs.

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 100% (all 5 parameters have descriptions). The description adds minimal extra meaning for parameters, only mentioning pagination and filter syntax. Baseline 3 is appropriate as the schema already fully documents 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 starts with 'List all website groups (folders) in LogicMonitor (LM) monitoring.' It clearly specifies the verb (list), resource (website groups), and scope (all). It distinguishes from siblings like get_website_group and list_websites by explaining its role in 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?

Explicit when-to-use scenarios are provided, e.g., 'Browse website organization before creating monitors', 'Find group IDs for website operations'. It also includes a workflow: 'Use this tool to browse hierarchy, then list_websites filtered by groupId to see monitors in specific folder.'

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