Skip to main content
Glama
cloudbring

New Relic MCP Server

by cloudbring

create_deployment

Creates a deployment marker for an APM application to track releases and changes.

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 `create` method on `RestDeploymentsTool` class that executes the create_deployment logic. It builds a POST request to /applications/{id}/deployments with the deployment payload (revision, changelog, description, user) via the NewRelicRestClient.
    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 };
    }
  • The TypeScript type `CreateDeploymentArgs` defining input parameters: application_id (number), revision (string), optional changelog, description, user, and region.
    type CreateDeploymentArgs = {
      application_id: number;
      revision: string;
      changelog?: string;
      description?: string;
      user?: string;
      region?: Region;
    };
  • The `getCreateTool()` method returns the Tool definition with name 'create_deployment', description, and inputSchema (JSON schema) specifying required application_id and revision, plus optional fields.
    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'],
        },
      };
  • src/server.ts:175-178 (registration)
    Registration in the executeTool switch-case that maps the string 'create_deployment' to instantiate RestDeploymentsTool and call its create method.
    case 'create_deployment':
      return await new RestDeploymentsTool().create(
        args as Parameters<RestDeploymentsTool['create']>[0]
      );
  • src/server.ts:81-82 (registration)
    Tool registration in registerTools() where restDeployments.getCreateTool() is added to the tools list for MCP tool discovery.
    restDeployments.getCreateTool(),
    restDeployments.getListTool(),
Behavior2/5

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

With no annotations, the description must reveal behavioral traits. It only indicates creation, omitting side effects, idempotency, authorization needs, or output details. The lack of disclosure 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.

Conciseness3/5

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

The description is a single sentence, which is concise, but it omits critical information about parameters and usage. It is not front-loaded effectively, and the brevity comes at the cost of informativeness.

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

Completeness1/5

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

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is severely incomplete. It fails to cover parameter meanings, expected behavior, or any operational context necessary for correct invocation.

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

Parameters1/5

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

Schema coverage is 0%, and the description does not explain any of the six parameters (application_id, revision, changelog, description, user, region). The region enum is present in schema but unmentioned. The description adds no semantic value beyond the schema.

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 the tool creates a deployment marker for an APM application, specifying the REST API version. This verb+resource construction differentiates it from sibling tools like delete_deployment or list_deployments_rest.

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?

The description provides no guidance on when to use this tool versus alternatives, such as delete_deployment or list_deployments_rest. No context about prerequisites, limitations, or typical use cases is given.

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