Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_websites

Read-only

List all synthetic website monitors to check URL/service availability, status, and performance from multiple global locations.

Instructions

List all website monitors (synthetic checks) in LogicMonitor (LM) monitoring.

Returns: Array of website monitors with: id, name, type (webcheck/pingcheck), domain/URL, status, checkpoint locations, response time, availability percentage.

What are website monitors: Synthetic checks that test URL/service availability from multiple global locations. Like "ping from the internet" to verify your services are accessible.

When to use:

  • List all monitored URLs/services

  • Check website availability status

  • Find website IDs for other operations

  • Audit monitored endpoints

Monitor types:

  • webcheck: Full HTTP/HTTPS check (status code, response time, content validation, SSL cert)

  • pingcheck: Simple ICMP ping test (faster, simpler)

Common filter patterns:

  • By domain: filter:"domain~*example.com*"

  • By type: filter:"type:webcheck" or filter:"type:pingcheck"

  • By status: filter:"overallAlertStatus:critical" (find down sites)

  • By name: filter:"name~*production*"

Use cases: Monitor public websites, API endpoints, login pages, load balancer health checks, SaaS service availability.

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" (details), "create_website" (add new), "generate_website_link" (get URL).

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 provide readOnlyHint: true, but the description adds significant behavioral context: it explains the return structure (array with id, name, type, domain, status, etc.), notes that a negative total indicates incomplete results, and details pagination behavior with autoPaginate. 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.

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 monitors, When to use, Monitor types, Common filter patterns, Use cases, Important, Related tools). It is front-loaded with the main purpose. While somewhat lengthy, each section adds distinct value.

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 no output schema and 5 parameters (100% schema coverage), the description thoroughly explains the return format, filter patterns, pagination, monitor types, and edge cases (negative total). It leaves no obvious gaps for an agent to understand the tool's usage.

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 baseline is 3. The description adds value beyond schema by providing common filter patterns with examples (e.g., filter:'domain\~\*example.com\*') and explaining pagination parameters in more context, making them more actionable.

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 website monitors (synthetic checks) in LogicMonitor (LM) monitoring.' It specifies the action (list) and resource (website monitors), and distinguishes from siblings like get_website, create_website, and generate_website_link via the 'Related tools' section.

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 includes a 'When to use' section with specific use cases (list all monitored URLs, check availability, etc.) and provides common filter patterns. Related tools are listed, but explicit 'when not to use' guidance is absent, though implied.

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