Skip to main content
Glama
cloudbring

New Relic MCP Server

by cloudbring

delete_deployment

Remove deployment records from New Relic to manage application lifecycle and maintain accurate monitoring data.

Instructions

Delete a deployment record (REST v2). Requires admin role permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
application_idYes
idYes
confirmYes
regionNo

Implementation Reference

  • The primary handler function that validates the confirmation flag and performs the DELETE request to the New Relic REST API endpoint for deployments.
    async delete(args: DeleteDeploymentArgs): Promise<unknown> {
      if (args.confirm !== true) {
        throw new Error('delete_deployment: confirm must be true');
      }
      const client = this.restFor(args.region);
      const path = `/applications/${args.application_id}/deployments/${args.id}`;
      const res = await client.delete<unknown>(path);
      return { ...res };
    }
  • TypeScript type definition for the input parameters expected by the delete_deployment handler.
    type DeleteDeploymentArgs = {
      application_id: number;
      id: number;
      confirm: true;
      region?: Region;
    };
  • Method that returns the MCP Tool object for 'delete_deployment', including name, description, and input schema for validation.
    getDeleteTool(): Tool {
      return {
        name: 'delete_deployment',
        description: 'Delete a deployment record (REST v2). Requires admin role permissions.',
        inputSchema: {
          type: 'object',
          properties: {
            application_id: { type: 'number' },
            id: { type: 'number' },
            confirm: { type: 'boolean' },
            region: { type: 'string', enum: ['US', 'EU'] },
          },
          required: ['application_id', 'id', 'confirm'],
        },
      };
    }
  • src/server.ts:81-83 (registration)
    Includes the getDeleteTool() in the array of tools registered with the MCP server.
    restDeployments.getCreateTool(),
    restDeployments.getListTool(),
    restDeployments.getDeleteTool(),
  • Server-side dispatch logic that routes 'delete_deployment' tool calls to the RestDeploymentsTool instance's delete method.
    case 'delete_deployment':
      return await new RestDeploymentsTool().delete(
        args as Parameters<RestDeploymentsTool['delete']>[0]
      );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the permission requirement, which is valuable, but doesn't describe what 'delete' actually means (permanent vs. soft deletion, cascading effects, confirmation process), rate limits, or what happens after deletion. For a destructive operation with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just two clauses that each add value: the core action and a critical permission requirement. There's no wasted language, repetition, or unnecessary elaboration. It's front-loaded with the primary purpose.

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?

For a destructive deletion tool with 4 parameters (3 required), 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It mentions permissions but doesn't explain the deletion behavior, parameter meanings, confirmation process, or what happens after deletion. The agent would struggle to use this tool correctly without significant guessing.

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?

With 0% schema description coverage for 4 parameters, the description provides no information about what any parameter means or how they relate to the deletion operation. It doesn't explain what 'application_id', 'id', 'confirm', or 'region' represent or how they should be used together. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the action ('Delete') and resource ('deployment record'), with additional technical context ('REST v2') that helps distinguish it from potential non-REST alternatives. However, it doesn't explicitly differentiate from sibling tools like 'list_deployments_rest' or 'create_deployment' beyond the obvious action difference.

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

Usage Guidelines3/5

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

The description provides one explicit usage constraint ('Requires admin role permissions'), which gives important context about when this tool can be used. However, it doesn't mention when to use this vs. alternatives (e.g., when deletion is appropriate vs. other modifications) or any other contextual guidance about prerequisites beyond permissions.

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/cloudbring/newrelic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server