Skip to main content
Glama
Sign In
GitHub + Linear Dev Workflows

GitHub + Linear Dev Workflows

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

github_releases_get_latest

Read-onlyIdempotent

Fetch GitHub's official published release for a repository, excluding drafts and prereleases, to get the current stable version.

Instructions

Get the latest published release — GitHub's definition, meaning the most recent release that is neither a draft nor a prerelease. Not simply the newest one.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "github_releases_get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesThe name of the repository without the `.git` extension. The name is not case sensitive.
ownerYesThe account owner of the repository. The name is not case sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds valuable behavioral context by explaining the filtering logic: the result is the most recent release that is neither a draft nor a prerelease. It does not mention authentication requirements or rate limits, but those are outside the typical scope for a read-only GET.

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?

The description is two sentences, front-loaded with the core action and followed by an important clarification. Every sentence earns its place, with no redundant or wasteful phrasing.

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 simple read-only tool with no output schema and annotations that cover the safety profile, the description is nearly complete. It clarifies the return semantics (latest published release, excluding drafts and prereleases) but does not describe the structure of the returned release object, though that may be acceptable for a standard API endpoint.

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%, and both parameters (owner and repo) are fully documented in the schema. The description does not add any parameter-level semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: 'Get the latest published release.' It then explicitly defines GitHub's meaning of 'latest published' as excluding drafts and prereleases, which distinguishes it from a naive 'newest release' interpretation. No direct sibling tool offers this exact function, so the clarity is sufficient.

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?

The description gives clear context by clarifying the definition of 'latest published' and warning that it is 'not simply the newest one.' However, it does not specify when to use this tool versus other release-related operations or outline any prerequisites or exclusions beyond the semantic definition.

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