GitHub PR Issue Analyser

Overview Schema Source Related Servers Discussions Admin

Github Update Release

github_update_release

Idempotent

Update a published GitHub release's title, notes, draft, or prerelease flag in place, preserving all fields you don't specify.

Instructions

Changes a published release in place. Only the fields supplied are sent, so correcting a title does not wipe the notes. make_latest is settable on github_create_release alone, and only on the call that first publishes the tag, since publishing again falls through to here and this tool does not send it. Move the latest badge by deleting the release and publishing it again, or in the GitHub UI.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	No	Replacement notes. Omit to leave them alone
`name`	No	Replacement title. Omit to leave it alone
`draft`	No
`tag_name`	Yes	Tag of the release to change
`repo_name`	Yes
`prerelease`	No
`repo_owner`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv42.0.0Sep 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the partial-update behavior ('Only the fields supplied are sent'), the fact that make_latest is intentionally not sent by this tool, and the fall-through behavior when publishing again. This is rich, non-obvious behavioral context.

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 front-loaded with the core action and then delivers dense, useful edge-case guidance in four sentences. Every sentence earns its place, with no filler or repetition of schema fields.

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

Completeness5/5

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

Given the output schema exists and the annotations already indicate mutation, idempotency, and non-destructiveness, the description covers the operation, partial-update behavior, make_latest routing, and the alternative workflow for moving the badge. Nothing essential to correctly invoking this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 43% schema description coverage, the description compensates by explaining the central parameter semantics: supplied fields are sent, omitted fields are untouched, and make_latest is not a parameter here. It does not spell out draft/prerelease null semantics, but the partial-update principle plus the boolean types give the agent enough to work with.

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 opens with a specific verb and resource: 'Changes a published release in place.' It clearly differentiates this update operation from create_release, delete_release, and get_release among the sibling tools.

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

Usage Guidelines5/5

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

The description explicitly names github_create_release as the only place make_latest can be set, and explains the delete-and-republish alternative for moving the latest badge. This gives the agent concrete when-to-use and when-not-to-use guidance against sibling tools.

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

Deploy Server