Skip to main content
Glama

List GitHub Milestones

get_github_milestones
Read-onlyIdempotent

Lists GitHub milestones with completion percentages and due dates to help track open work and deadlines.

Instructions

List GitHub milestones for the repository with completion percentages and due dates.

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

Input Schema

NameRequiredDescriptionDefault
repoNoLEAVE EMPTY to auto-detect from git
limitNoMax milestones to return (default: 20)
ownerNoLEAVE EMPTY to auto-detect from git
stateNoFilter by state (default: open)open
use_test_dbNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
repoNo
countNo
errorNoHuman-readable error message
ownerNo
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
milestonesNo
suggestionNoSuggested fix for the error
instructionNo
recoverableNoWhether the error is recoverable
detectedRepoNo
detectedOwnerNo
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 / limit / 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 readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results carry completion percentages and due dates, which is useful return context, but it says nothing about authentication needs, rate limiting, or that repo/owner are auto-detected when omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero filler; nothing needs trimming. It is arguably over-trimmed for a 5-parameter tool, but nothing is wasted.

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 read-only list tool with rich annotations, an output schema, and 80% schema coverage, the description covers what it does and what the results contain. The remaining gaps are mostly structured-field territory (pagination defaults, auto-detect), so it is close to adequate without being complete.

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 coverage is 80% and the description adds no parameter meaning at all — no explanation of state filtering, the limit/pagination behavior, or the auto-detect semantics for repo and owner. With high coverage the baseline of 3 applies, since the schema is doing essentially all of the parameter work.

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 ('List GitHub milestones for the repository') and adds the notable payload ('completion percentages and due dates'), which makes it distinguishable from the singular get_github_milestone and from the create/update/delete siblings. It never explicitly says how it differs from get_github_milestone, so it stops short of a 5.

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?

Usage is only implied by the verb 'List' and the phrase 'for the repository'; there is no statement of when to prefer this over get_github_milestone, get_repo_insights, or get_github_context, and no mention of filtering by open/closed state even though the state parameter exists.

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