Defame1297
dfacf051a8
Description 500 -> 211 chars, body 676 -> 462 words, Gotchas 5 entries/41% of body -> 3/21%. Clears the description FAIL and both Gotchas suggestions. Cut the second trigger register (the re-quoted user phrasings), the doubled capability enumeration across releases and tags, and the gitea-issues/gitea-prs boundary, which defended against nothing -- neither was going to win a release request. Kept the indirect trigger and the one real near-miss, gitea-branches. Releases and tags are one flow, not two: 'delete the release and its tag' is a single invocation that takes both branches, which disqualifies mutual exclusivity, so no dispatch split. Two Gotchas moved to references/ behind explicit triggers; one deleted as a paraphrase of the step below it. Refs #99
3.3 KiB
3.3 KiB
name, description, metadata
| name | description | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| gitea-releases | Use when managing Gitea releases or the git tags underneath them — list, get, create, or delete either — even when the user does not say "release" or "Gitea". Not branches or commit history -> `gitea-branches`. |
|
Gotchas
- Deleting a release never deletes its tag, and deleting a tag never deletes the release wrapping it. A release is a metadata wrapper around a tag, so removing both takes two independent destructive calls.
is_draft/is_pre_releaseare booleans the caller sets — Gitea never infers a prerelease from a-beta/-rctag name. The response object names themdraft/prerelease; passingdraftas an input key is silently ignored, not rejected.list_releases/list_tagsdefaultper_pageto 20, where most other gitea-mcp list tools default to 30 — a caller assuming 30 under-counts the pages a full sweep needs.
Dispatch table
| Action | Tool | Required params | Optional params |
|---|---|---|---|
| List releases | list_releases |
owner, repo |
is_draft, is_pre_release, page (default 1), per_page (default 20) |
| Get one release | get_release |
owner, repo, id (number) |
— |
| Get latest release | get_latest_release |
owner, repo |
— |
| Create release | create_release |
owner, repo, tag_name, target, title |
body, is_draft, is_pre_release |
| Delete release | delete_release |
owner, repo, id (number) |
— |
| List tags | list_tags |
owner, repo |
page (default 1), per_page (default 20) |
| Get one tag | get_tag |
owner, repo, tag_name |
— |
| Create tag | create_tag |
owner, repo, tag_name |
target, message |
| Delete tag | delete_tag |
owner, repo, tag_name |
— |
target (on create_release/create_tag) is a commitish — a branch name, existing tag, or commit SHA — the point the new tag is cut from.
Workflow
- Creating a release: Call
create_releasewithtag_name,target, andtitle. Gitea is assumed to create the tag fromtargetwhentag_namedoes not yet exist — plausible from the API shape, not confirmed in the research docs — so a separatecreate_tagis only needed to tag a commit without wrapping it in a release. Verify withget_tagafterward if the caller depends on it. - Deleting a release:
delete_releasetakes the numericidand never atag_name;delete_tagis the mirror opposite and never takes an id. With only a tag name in hand, resolve the id throughlist_releases(paginating if needed) orget_releasefirst. - Deleting a tag along with its release: Delete the release first, then call
delete_tag— confirm both are intended before proceeding, since each is irreversible on its own. - Listing every page: Loop
page: 1, 2, 3...until a response returns fewer thanper_pageentries. Nothing here auto-paginates.
If exact input params or response field shapes are needed, read references/call-signatures.md. If the caller raises semver tag naming, release-notes sourcing, or how a release relates to its tag, read references/conventions.md.