Skip to main content
Glama

service_delete

Remove a service from a Railway project to clean up unused resources, delete test deployments, or reorganize infrastructure. Use this tool to permanently delete services you no longer need.

Instructions

[API] Delete a service from a project

⚡️ Best for: ✓ Removing unused services ✓ Cleaning up test services ✓ Project reorganization

⚠️ Not for: × Temporary service stoppage (use service_restart) × Updating service configuration (use service_update)

→ Prerequisites: service_list, service_info

→ Alternatives: service_restart

→ Related: project_delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesID of the project containing the service
serviceIdYesID of the service to delete

Implementation Reference

  • Tool registration for 'service_delete', including Zod input schema, formatted description, and handler that calls serviceService.deleteService
    createTool(
      "service_delete",
      formatToolDescription({
        type: 'API',
        description: "Delete a service from a project",
        bestFor: [
          "Removing unused services",
          "Cleaning up test services",
          "Project reorganization"
        ],
        notFor: [
          "Temporary service stoppage (use service_restart)",
          "Updating service configuration (use service_update)"
        ],
        relations: {
          prerequisites: ["service_list", "service_info"],
          alternatives: ["service_restart"],
          related: ["project_delete"]
        }
      }),
      {
        projectId: z.string().describe("ID of the project containing the service"),
        serviceId: z.string().describe("ID of the service to delete")
      },
      async ({ projectId, serviceId }) => {
        return serviceService.deleteService(projectId, serviceId);
      }
    ),
  • ServiceService.deleteService method: calls client.services.deleteService(serviceId) and handles response/error
    async deleteService(projectId: string, serviceId: string) {
      try {
        await this.client.services.deleteService(serviceId);
        return createSuccessResponse({
          text: `Service deleted successfully`
        });
      } catch (error) {
        return createErrorResponse(`Error deleting service: ${formatError(error)}`);
      }
    }
  • ServiceRepository.deleteService: executes GraphQL mutation to delete the service via Railway API
    async deleteService(serviceId: string): Promise<void> {
      await this.client.request<{ serviceDelete: boolean }>(`
        mutation serviceDelete($serviceId: String!) {
          serviceDelete(id: $serviceId)
        }
      `, { serviceId });
    }
Behavior4/5

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

With no annotations provided, the description carries full burden. It clearly indicates this is a destructive operation ('Delete'), implies permanent removal (contrasted with temporary alternatives), and mentions prerequisites that suggest authentication or access needs. However, it doesn't specify rate limits, confirmation prompts, or irreversible consequences beyond the contrast with service_restart.

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?

Well-structured with clear sections (API label, purpose, best for/not for, prerequisites, alternatives, related). Every sentence earns its place by providing distinct guidance without redundancy. The information is front-loaded with the core purpose first.

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?

For a destructive tool with no annotations and no output schema, the description provides strong contextual guidance about usage scenarios, alternatives, and prerequisites. However, it doesn't describe what happens after deletion (e.g., confirmation message, error handling, or cascading effects) which would be helpful given the tool's destructive nature.

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%, providing clear documentation for both parameters (projectId, serviceId). The description doesn't add any parameter-specific details beyond what the schema already states, so it meets the baseline of 3 where the schema does the heavy lifting.

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 specific action ('Delete a service from a project') with the exact resource ('service'), distinguishing it from siblings like service_restart or service_update. It goes beyond just restating the tool name by specifying the target context (project).

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

Usage Guidelines5/5

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

Explicitly provides 'Best for' scenarios (removing unused services, cleaning up test services, project reorganization) and 'Not for' cases (temporary stoppage, configuration updates) with named alternatives (service_restart, service_update). Also lists prerequisites (service_list, service_info) and related tools (project_delete), giving comprehensive guidance on when to use this tool.

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/epitaphe360/railway-mcp'

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