Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_dashboards

Read-only

List all dashboards in your LogicMonitor account, including AWS/Azure/infrastructure dashboards, with details like ID, name, group, and widget count. Use filters to find dashboards by name, group, or owner.

Instructions

List all dashboards in LogicMonitor (LM) monitoring.

Returns: Array of dashboards with: id, name, description, groupId, groupName, widget count, owner.

When to use:

  • Find AWS/Azure/infrastructure dashboards

  • Discover available pre-built dashboards

  • Get dashboard IDs for generating links

  • List dashboards in specific group

Common filter patterns:

  • By name: filter:"name~*AWS*" (find all AWS dashboards)

  • By group: filter:"groupId:5" or filter:"groupName~*Cloud*"

  • By owner: filter:"owner:john.doe"

Next step: Use "generate_dashboard_link" with the dashboard ID to get the full clickable URL for sharing.

Tip: Dashboards are organized in groups. Use "list_dashboard_groups" to browse the hierarchy.

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_dashboard" (details), "generate_dashboard_link" (get URL), "list_dashboard_groups" (browse hierarchy).

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 indicate readOnlyHint: true, which the description does not contradict. The description adds important behavioral details: warning about negative 'total' indicating incomplete results, and explanation of autoPaginate behavior. This adds value beyond 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 headings, bullet points, and clear sections. It is slightly lengthy but every sentence adds value. Front-loaded with purpose and return specification.

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, but the description specifies the return format: 'Array of dashboards with: id, name, description, groupId, groupName, widget count, owner.' It also covers pagination, filtering, and related tools, making it fully complete for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters, and the description enriches them with 'Common filter patterns' (e.g., examples for filter), explanation of autoPaginate behavior, and fields usage. This adds significant meaning beyond the schema descriptions.

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 dashboards in LogicMonitor (LM) monitoring.' It specifies the verb (list), resource (dashboards), and scope (all). It distinguishes from siblings like get_dashboard (details) and generate_dashboard_link (get URL) in 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 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 specific scenarios (e.g., find AWS/Azure dashboards, discover pre-built, get IDs for links). It also provides common filter patterns, a next step, and references to related tools, making usage very clear.

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