Skip to main content
Glama

Update GitHub Milestone

update_github_milestone

Modify a GitHub milestone's title, description, due date, or state. Set state to 'closed' to close a completed milestone.

Instructions

Update a GitHub milestone (title, description, due date, or state). Use state "closed" to close a completed milestone.

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": "update_github_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoLEAVE EMPTY to auto-detect
ownerNoLEAVE EMPTY to auto-detect
stateNoSet to "closed" to close the milestone
titleNoNew title
due_onNoNew due date in YYYY-MM-DD format
descriptionNoNew description
use_test_dbNo
milestone_numberNoMilestone number to update

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)
milestoneNo
suggestionNoSuggested fix for the error
instructionNo
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation
requiresUserInputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • changedInput schema / properties / milestone_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world behavior, so the safety profile is covered. The description adds a little context on state semantics, but omits important behavior for a mutation tool: whether this is a partial update (fields not supplied are left untouched) or a full replacement, and whether closed milestones can be reopened. With no annotation on idempotency semantics, that gap matters.

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 the field list up front and the most actionable rule (closing) second. Nothing is wasted or buried.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, with 8 parameters and zero required, the definition never clarifies that milestone_number (plus repo/owner resolution) is effectively needed to identify the target — a meaningful omission for a tool where every argument is technically optional.

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 88%, so the schema already documents nearly every parameter, including the state="closed" semantics that the description repeats. The description adds no new meaning, such as how repo/owner auto-detection interacts with milestone_number, which is a non-obvious targeting mechanic.

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?

The description names a specific verb and resource ('Update a GitHub milestone') and enumerates the mutable fields, so the operation is unambiguous. It does not distinguish itself from the sibling set (create_github_milestone, get_github_milestone, delete_github_milestone), but the verb alone makes the distinction reasonably clear.

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

Usage Guidelines3/5

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

It gives one concrete usage cue: use state "closed" to close a completed milestone. There is no guidance on prerequisites (which milestone, how to obtain milestone_number), no mention of when to prefer create/delete siblings, and no note on whether unspecified fields are preserved.

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