Skip to main content
Glama

List a GitHub repository's latest releases

github_releases
Read-only

The latest releases of a GitHub repository: tag, name, date, pre-release flag, the first 1,500 characters of the notes, and the number of assets. Related tools on this server, for a different need: github_issues when you need to search a GitHub repository's issues or pull requests; github_repo when you need a public GitHub repository: stars, forks, watchers, open. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo": "<repo>"
    },
    "name": "github_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name or a github.com URL
limitNo1 to 10 (default 5)

Output Schema

NameRequiredDescriptionDefault
repoNo
sourceNo
releasesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses real behavioral traits: notes are truncated to 1,500 characters, assets are only counted rather than listed, and each successful call costs $0.002 via x402 (USDC on Base, Solana and 10 more networks) with failures free. The payment/auth requirement is exactly the kind of pre-call knowledge an agent needs and cannot get from annotations or schema.

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?

The return payload is front-loaded in the first sentence, followed by sibling routing and then cost, which is a sensible priority order. The pricing sentence is long and slightly dense with network details, but every clause carries information an agent would otherwise lack.

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?

An output schema exists, so the field enumeration is extra rather than required, and the description still covers cost, truncation, and alternatives. Minor omissions such as release ordering or whether pagination beyond 10 is possible are low-impact for a tool with a hard limit cap.

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 100%, so the schema already explains that repo accepts owner/name or a github.com URL and that limit is a string from 1 to 10 (default 5). The description adds only indirect meaning via 'latest releases' and the returned-field list; it adds no new format or ordering detail beyond the schema.

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 names the resource (a GitHub repository's latest releases) and enumerates exactly what comes back: tag, name, date, pre-release flag, first 1,500 characters of notes, and asset count. It also explicitly distinguishes itself from github_issues and github_repo by stating those serve different needs.

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

Usage Guidelines4/5

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

It routes the agent away from this tool with concrete conditions: use github_issues for issues/pull requests and github_repo for stars/forks/watchers. There is no explicit statement of when this tool is the right choice versus e.g. github_search, but the positive case ('latest releases') is clear from the purpose sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources