New Relic MCP Server

by piekstra

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List Dashboards

list_dashboards

Retrieve all dashboards for a New Relic account to review monitoring views and manage observability content.

Instructions

List all dashboards for an account

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dashboards"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.3.2Nov 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / account_id / title
```
Removed value: -"Account Id"
```
- removedInput schema / title
```
Removed value: -"list_dashboardsArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"list_dashboardsOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
Changed1 schema field changedv1.0.0Jan 4, 2026
- addedInput schema / title
```
Added value: +"list_dashboardsArguments"
```
First observedNov 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about pagination, result ordering, permissions, or whether the list is truncated. An output schema exists, which relieves it of describing return values, but for a listing operation the absence of any paging or scope behavior is a real gap.

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?

A single front-loaded sentence with no filler and no repetition of the title. Its brevity is appropriate in form, though the space saved is not reinvested in any useful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing evidence: the sentence reads 'List all dashboards for an account' and is complete enough to call the tool, with the output schema covering return values.

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

Parameters2/5

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

Schema description coverage is 0% for the single account_id parameter, which is nullable and defaults to null. The description's 'for an account' faintly signals that the param scopes the listing, but it never says what happens when account_id is omitted or which account is used by default, leaving the key semantic undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List all dashboards') with the account scope, so the agent knows exactly what enumeration it performs. It does not distinguish itself from sibling get_dashboard or explain the 'all' scope versus a filtered search, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use guidance and no named alternatives, even though get_dashboard is the obvious sibling for single-dashboard retrieval. The phrase 'for an account' only weakly implies the listing context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.