gittr-mcp

createRelease

Tag a commit with a version and publish markdown release notes to a repository on the Nostr Git platform.

Instructions

Not supported for UI release notes. For Zapstore/NIP-82 announce use announceSoftwareFromForgeRelease. For git tags use listReleases + publishRepoState.

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": {
      "ownerPubkey": "<ownerPubkey>",
      "repoId": "<repoId>",
      "version": "<version>"
    },
    "name": "createRelease"
  }
}

Input Schema

Name	Required	Description
`relays`	No
`repoId`	Yes	Repository ID
`privkey`	No	Private key (auto-loaded)
`version`	Yes	Version (e.g., v1.0.0)
`ownerPubkey`	Yes	Repository owner pubkey
`releaseNotes`	No	Markdown release notes
`targetCommit`	No	Commit SHA to tag

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Jul 31, 2026

TDQS

D1.9/5.0

Behavior1/5

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

No annotations are provided, and the description reveals no behavioral details: no side effects, permissions, mutability, output, or even a positive statement of what the operation performs. The only behavioral signal is a negative support restriction, which is insufficient for an agent to call this tool safely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded with the limitation, but it is incomplete rather than appropriately concise. Every sentence earns its place for routing, yet no sentence addresses the tool's actual purpose.

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

Completeness1/5

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

This is a 7-parameter tool with 3 required fields, no annotations, and no output schema, but the description only redirects users away from it. An agent cannot determine what createRelease does, what inputs mean in context, or what happens when it is invoked, so the definition is far from complete.

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 86%, so most parameters already carry their own descriptions. The description adds no additional meaning to parameters like targetCommit, releaseNotes, or relays, earning the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what createRelease actually does. It only says it is 'Not supported for UI release notes' and redirects to sibling tools, so the agent is left guessing whether this creates a release, a git tag, or something else.

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

Usage Guidelines3/5

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

It provides explicit alternatives for two specific cases: 'announceSoftwareFromForgeRelease' for Zapstore/NIP-82 announce and 'listReleases + publishRepoState' for git tags. However, it never says when to use createRelease itself, so the positive usage condition is missing.

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

Deploy Server