Skip to main content
Glama

Delete GitHub Milestone

delete_github_milestone
Destructive

Permanently deletes a GitHub milestone, unassigning linked issues without deleting them.

Instructions

Permanently delete a GitHub milestone. Issues assigned to the milestone will be un-assigned but not deleted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_github_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoLEAVE EMPTY to auto-detect
ownerNoLEAVE EMPTY to auto-detect
confirmNoMust be set to true to confirm deletion
use_test_dbNo
milestone_numberNoMilestone number to delete

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
messageNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
instructionNo
recoverableNoWhether the error is recoverable
milestoneNumberNo
aggregated_errorsNoDetails of individual errors in a multi-step operation
requiresUserInputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • removedInput schema / properties / confirm / const
      Removed value: -true
    • changedInput schema / properties / milestone_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description earns credit for going beyond that by explaining the blast radius: assigned issues are un-assigned but preserved. It still omits the `confirm` gate and whether the deletion is reversible at the API level.

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?

Two short sentences with zero filler; the destructive nature is front-loaded and the side-effect caveat follows immediately. Nothing could be removed without losing information.

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 single-resource tool with an output schema and strong annotation coverage, the description covers the essential consequence of the call. The one meaningful omission is the `confirm: true` requirement, which the agent must discover from the schema alone.

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 80% and the schema already documents `repo`/`owner` auto-detect, `confirm`, and `milestone_number`. The description adds nothing about parameters, so it neither helps nor hurts beyond the baseline for a well-covered schema.

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?

States a specific verb and resource ("Permanently delete a GitHub milestone"), which cleanly separates it from get_github_milestone and update_github_milestone in the sibling list. It does not explicitly name those siblings, so the differentiation comes from the verb rather than from routing language.

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 gives no when-to-use guidance, no alternatives (e.g., close vs. delete), and no prerequisites such as the requirement that `confirm` be true. The word "Permanently" hints at caution but stops short of actionable guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools