Skip to main content
Glama

project_delete

Delete a Railway project and all associated resources permanently. Use this tool to remove unused projects or clean up test environments.

Instructions

[API] Delete a Railway project and all its resources

⚡️ Best for: ✓ Removing unused projects ✓ Cleaning up test projects

⚠️ Not for: × Temporary project deactivation × Service-level cleanup (use service_delete)

→ Prerequisites: project_list, project_info

→ Alternatives: service_delete

→ Related: project_create

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesID of the project to delete

Implementation Reference

  • Tool registration for 'project_delete', including schema (projectId: string) and thin handler delegating to projectService
    createTool(
      "project_delete",
      formatToolDescription({
        type: 'API',
        description: "Delete a Railway project and all its resources",
        bestFor: [
          "Removing unused projects",
          "Cleaning up test projects",
        ],
        notFor: [
          "Temporary project deactivation",
          "Service-level cleanup (use service_delete)"
        ],
        relations: {
          prerequisites: ["project_list", "project_info"],
          alternatives: ["service_delete"],
          related: ["project_create"]
        }
      }),
      {
        projectId: z.string().describe("ID of the project to delete")
      },
      async ({ projectId }) => {
        return projectService.deleteProject(projectId);
      }
    ),
  • Core handler for project deletion in ProjectService, executes API call and formats response
    async deleteProject(projectId: string): Promise<CallToolResult> {
      try {
        await this.client.projects.deleteProject(projectId);
        return createSuccessResponse({
          text: "Project deleted successfully"
        });
      } catch (error) {
        return createErrorResponse(`Error deleting project: ${formatError(error)}`);
      }
    }
  • Repository helper executing GraphQL mutation to delete project via Railway API
    async deleteProject(projectId: string): Promise<void> {
      await this.client.request<{ projectDelete: boolean }>(`
        mutation projectDelete($projectId: String!) {
          projectDelete(id: $projectId)
        }
      `, { projectId });
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates that this is a destructive operation ('Delete a Railway project and all its resources'), warns against misuse for temporary deactivation, and implies irreversible deletion. However, it lacks details on permissions, rate limits, or confirmation steps, which would be helpful for a destructive tool.

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 well-structured and front-loaded with the core action, followed by bullet-pointed best practices, warnings, prerequisites, and alternatives. Each section adds value without redundancy, and the use of symbols (⚡️, ⚠️, →) enhances readability while keeping the text efficient and focused.

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?

Given the tool's destructive nature, no annotations, and no output schema, the description does a good job of covering key aspects: purpose, usage guidelines, and behavioral warnings. It could improve by mentioning error handling or return values, but for a single-parameter tool with clear schema coverage, it provides sufficient context for safe and effective use.

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?

The schema description coverage is 100%, with the single parameter 'projectId' fully documented in the schema. The description does not add any additional semantic context beyond what the schema provides (e.g., format examples or sourcing guidance), so it meets the baseline score of 3 where the schema handles parameter documentation adequately.

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 Railway project and all its resources') with the verb 'Delete' and resource 'Railway project', distinguishing it from siblings like service_delete which handles service-level cleanup. It explicitly mentions the scope ('all its resources'), making the purpose unambiguous and distinct.

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?

The description provides explicit guidance on when to use this tool ('Best for: Removing unused projects, Cleaning up test projects') and when not to use it ('Not for: Temporary project deactivation, Service-level cleanup'), with named alternatives (service_delete). It also lists prerequisites (project_list, project_info) and related tools (project_create), offering comprehensive usage context.

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