Skip to main content
Glama
cloudbring

New Relic MCP Server

by cloudbring

create_deployment

Create deployment markers for APM applications to track releases and changes in New Relic.

Instructions

Create a deployment marker for an APM application (REST v2).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
application_idYes
revisionYes
changelogNo
descriptionNo
userNo
regionNo

Implementation Reference

  • The core handler function that executes the tool logic by posting to the New Relic REST API to create a deployment marker for an APM application.
    async create(args: CreateDeploymentArgs): Promise<unknown> {
      const client = this.restFor(args.region);
      const path = `/applications/${args.application_id}/deployments`;
      const payload = {
        deployment: {
          revision: args.revision,
          changelog: args.changelog,
          description: args.description,
          user: args.user,
        },
      };
      const res = await client.post<unknown>(path, payload);
      return { ...res };
    }
  • Defines the tool's name, description, and input schema for validation.
    getCreateTool(): Tool {
      return {
        name: 'create_deployment',
        description: 'Create a deployment marker for an APM application (REST v2).',
        inputSchema: {
          type: 'object',
          properties: {
            application_id: { type: 'number' },
            revision: { type: 'string' },
            changelog: { type: 'string' },
            description: { type: 'string' },
            user: { type: 'string' },
            region: { type: 'string', enum: ['US', 'EU'] },
          },
          required: ['application_id', 'revision'],
        },
      };
    }
  • TypeScript type definition for the input arguments used in the handler.
    type CreateDeploymentArgs = {
      application_id: number;
      revision: string;
      changelog?: string;
      description?: string;
      user?: string;
      region?: Region;
    };
  • src/server.ts:175-178 (registration)
    Registers the handler execution in the main tool dispatcher switch statement.
    case 'create_deployment':
      return await new RestDeploymentsTool().create(
        args as Parameters<RestDeploymentsTool['create']>[0]
      );
  • src/server.ts:81-81 (registration)
    Registers the tool definition (from getCreateTool) into the server's tools map for listing.
    restDeployments.getCreateTool(),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create' implying a write operation but doesn't disclose behavioral traits such as permissions required, whether it's idempotent, rate limits, or what happens on success/failure. This leaves critical gaps for a mutation tool with no structured safety hints.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan. Every part earns its place by conveying essential purpose without redundancy.

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?

Given the complexity (a write operation with 6 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover parameter meanings, behavioral context, or return values, leaving the agent under-informed for proper tool invocation in this APM context.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'application_id', 'revision', or other parameters mean, their formats, or examples. With 6 parameters (2 required) and no schema descriptions, this is a significant shortfall.

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 ('Create') and the resource ('deployment marker for an APM application'), specifying it's for REST v2. However, it doesn't distinguish this from sibling tools like 'delete_deployment' or 'list_deployments_rest' beyond the basic verb difference, missing explicit differentiation in scope or purpose.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing application), exclusions, or compare to siblings like 'list_deployments_rest' for retrieval. The description is standalone with no context for selection.

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