Skip to main content
Glama
nulab

Backlog MCP Server

delete_project

Permanently delete a Backlog project by providing its ID or key.

Instructions

Deletes a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., 'PROJECT')
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The main handler function for the 'delete_project' tool. It accepts either a projectId (number) or projectKey (string), resolves which one to use via resolveIdOrKey, then calls backlog.deleteProject() to delete the project.
    export const deleteProjectTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof deleteProjectSchema>,
      (typeof ProjectSchema)['shape']
    > => {
      return {
        name: 'delete_project',
        description: t('TOOL_DELETE_PROJECT_DESCRIPTION', 'Deletes a project'),
        schema: z.object(deleteProjectSchema(t)),
        outputSchema: ProjectSchema,
        handler: async ({ projectId, projectKey }) => {
          const result = resolveIdOrKey(
            'project',
            { id: projectId, key: projectKey },
            t
          );
          if (!result.ok) {
            throw result.error;
          }
          return backlog.deleteProject(result.value);
        },
      };
    };
  • Input schema for the delete_project tool: optional projectId (number) and optional projectKey (string). At least one must be provided.
    const deleteProjectSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_DELETE_PROJECT_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_DELETE_PROJECT_PROJECT_KEY',
            "The key of the project (e.g., 'PROJECT')"
          )
        ),
    }));
  • Output schema (ProjectSchema) returned after deleting a project. Contains project fields like id, projectKey, name, chartEnabled, etc.
    export const ProjectSchema = z.object({
      id: z.number(),
      projectKey: z.string(),
      name: z.string(),
      chartEnabled: z.boolean(),
      useResolvedForChart: z.boolean(),
      subtaskingEnabled: z.boolean(),
      projectLeaderCanEditProjectLeader: z.boolean(),
      useWiki: z.boolean(),
      useFileSharing: z.boolean(),
      useWikiTreeView: z.boolean(),
      useOriginalImageSizeAtWiki: z.boolean(),
      useSubversion: z.boolean(),
      useGit: z.boolean(),
      textFormattingRule: TextFormattingRuleSchema,
      archived: z.boolean(),
      displayOrder: z.number(),
      useDevAttributes: z.boolean(),
    });
  • Registration of deleteProjectTool in the 'project' toolset group alongside other project tools (getProjectList, addProject, getProject, updateProject).
    {
      name: 'project',
      description:
        'Tools for managing projects, categories, custom fields, and issue types.',
      enabled: false,
      tools: [
        getProjectListTool(backlog, helper),
        addProjectTool(backlog, helper),
        getProjectTool(backlog, helper),
        updateProjectTool(backlog, helper),
        deleteProjectTool(backlog, helper),
      ],
    },
  • Helper function that resolves whether to use a numeric id or string key to identify a project (or other entity). Used by the delete_project handler.
    export const resolveIdOrKey = <E extends EntityName>(
      entity: E,
      values: { id?: number; key?: string },
      t: TranslationHelper['t']
    ): ResolveResult => resolveIdOrField(entity, 'key', values, t);
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action ('Deletes a project') without revealing whether deletion is irreversible, what cascading effects occur (e.g., deletion of associated data), required permissions, or any side effects.

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 extremely concise (one sentence), but it sacrifices informativeness. While not verbose, it is too minimal for a destructive operation, lacking essential context. It is front-loaded but not appropriately sized relative to the tool's complexity.

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 destructive nature of the tool, the absence of output schema and annotations, the description fails to provide complete context. It does not explain return values, confirmation, error handling, or what happens upon success/failure. Important for guiding agent usage.

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 input schema has 100% coverage with clear descriptions for each parameter (projectId, projectKey, organization). The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 verb 'Deletes' and the resource 'project', making the action unambiguous. It distinguishes from sibling delete tools (e.g., delete_issue, delete_version) by specifying the resource type.

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 given on when to use this tool vs alternatives (e.g., updating a project to archive). There is no mention of prerequisites, consequences, or when deletion is appropriate, which is critical for a destructive action.

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/nulab/backlog-mcp-server'

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