Skip to main content
Glama
Sign In
New Relic MCP Server

New Relic MCP Server

by piekstra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Dashboard

update_dashboard

Update a dashboard widget’s title, NRQL query, and visualization type by specifying its page GUID and widget ID, with optional account targeting.

Instructions

Update a widget in a dashboard page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_guid": "<page_guid>",
      "widget_id": "<widget_id>",
      "title": "<title>",
      "nrql_query": "<nrql_query>"
    },
    "name": "update_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThe new title for the widget
page_guidYesThe GUID of the dashboard page containing the widget
widget_idYesThe ID of the widget to update
account_idNoAccount ID for the query (uses default if not provided)
nrql_queryYesThe NRQL query for the widget
visualization_idNoVisualization type (viz.table, viz.billboard, etc)viz.table

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

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 burden of behavioral disclosure. It does not explain whether this is a full replacement or partial update, what happens to fields not supplied, whether the operation is destructive or reversible, or what permissions are required. For a mutation tool with zero annotation coverage, this is a significant 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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately concise, though its brevity contributes to the missing behavioral and usage context rather than being a flaw of structure alone.

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

Completeness2/5

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

The tool is a mutation with six parameters and no annotations, and the description does not address update semantics, permissions, side effects, or what happens to existing widget configuration. Although an output schema exists and the input schema is fully described, the description remains too thin for a mutation operation of this complexity.

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%, so all six parameters are already documented in the input schema with clear descriptions and defaults. The description adds no additional meaning about parameters, such as required combinations or the effect of account_id and visualization_id. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: updating a widget inside a dashboard page. This distinguishes it from read-only siblings like get_dashboard and list_dashboards. However, the name and title say 'update_dashboard' while the description says 'update a widget,' creating a minor scope mismatch that could confuse an agent about whether the dashboard itself or only a widget is modified.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites such as required permissions or dashboard edit access. The implied usage is updating an existing widget, but no when-not-to-use conditions or related tools are mentioned.

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

Deploy Server

Other Tools