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

GitHub + Linear Dev Workflows

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

github_releases_update

Update a GitHub release's details such as name, body, or draft status. Omitted fields stay unchanged; set draft to false to publish.

Instructions

Update a release; anything omitted is left unchanged. Publishing a draft is this call with draft: false.

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>",
      "releaseId": "<releaseId>"
    },
    "name": "github_releases_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoText describing the contents of the tag.
nameNoThe name of the release.
repoYesThe name of the repository without the `.git` extension. The name is not case sensitive.
draftNo`true` to make this a draft (unpublished) release, `false` to publish it. Setting it to `false` is how a draft is published.
ownerYesThe account owner of the repository. The name is not case sensitive.
tagNameNoThe name of the tag.
releaseIdYesThe unique identifier of the release.
makeLatestNoWhether this release should be set as the latest release for the repository — a string, not a boolean. Drafts and prereleases cannot be set as latest.
prereleaseNo`true` to identify the release as a prerelease.
targetCommitishNoSpecifies the commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. Unused if the Git tag already exists.
discussionCategoryNameNoIf specified, a discussion of the specified category is created and linked to the release.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a write operation (readOnlyHint false) and external scope (openWorldHint true). The description adds crucial behavioral semantics beyond annotations: partial update behavior ('anything omitted is left unchanged') and the exact mechanism for publishing a draft, which an agent needs to avoid unintended changes.

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 tightly written sentences with no filler. The partial-update constraint is front-loaded, and the draft-publishing note follows naturally. Every phrase earns its place.

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 an 11-parameter mutation tool with full schema descriptions and no output schema, the description covers the essential behavioral facts: it is a partial update and how to publish a draft. It omits explicit mention of permissions or rate limits, but those are not critical for correct invocation given the schema and annotations.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that omitted parameters leave existing values unchanged and by explicitly tying the draft parameter to the publish action. This parameter-level insight is valuable and not fully redundant.

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?

States a specific verb ('Update') and resource ('release') with scope ('anything omitted is left unchanged'). Clearly distinguishes from sibling read-only tools like github_releases_get_latest without requiring schema inspection.

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?

Provides a concrete usage scenario: 'Publishing a draft is this call with draft: false.' Gives clear context for one important case, though it does not explicitly state when not to use this tool or name alternatives beyond the partial-update note.

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