gittr-mcp

announceSoftwareFromForgeRelease

Announce a software release from a Git forge to Nostr/Zapstore via NIP-82. Publishes metadata, tags, and images for decentralized distribution.

Instructions

Announce software to Zapstore/NIP-82 (kinds 32267/30063/3063) from a forge Release binary. Same as gittr Nostr Apps (latest tag) or Releases → Announce on Nostr (tag=). Never a tagless app. Copies images: from the forge zapstore.yaml onto kind 32267. Optional pinToBlossom uses public Blossom; blossom.gittr.space only for the official gittr APK (space.gittr.app). Auto-loads .nostr-keys.json if privkey omitted.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Release tag to announce (omit = latest, same as Code sidebar)
`appId`	No	Package id (e.g. com.example.app). Default: space.gittr.<repo>, or space.gittr.app for the official gittr Android package
`relays`	No
`topics`	No	Optional extra t tags
`appName`	No	Display name (default: forge repo name)
`iconUrl`	No	Optional HTTPS icon. Else zapstore.yaml icon:, else official gittr bird.
`license`	No	Optional SPDX license id
`privkey`	No	nsec or hex (optional if .nostr-keys.json loaded)
`summary`	No	Short summary (max ~280 chars)
`sourceUrl`	Yes	Forge repository HTTPS URL with a Release that has an announceable binary
`homepageUrl`	No	Optional HTTPS homepage for kind 32267 url
`ownerPubkey`	No	Must match signer (default: derived from privkey)
`nip34Address`	No	Optional NIP-34 pointer 30617:<owner-hex>:<repo>
`pinToBlossom`	No	Optional: pin hashed files to public Blossom (primal/ditto/haven). Official gittr APK may also pin to blossom.gittr.space. Pin failure still announces the forge URL.
`screenshotUrls`	No	Optional extra HTTPS screenshot URLs. Default: zapstore.yaml images: (repo paths rewritten to raw forge URLs).
`selectedApkUrl`	No	Alias of selectedAssetUrl (legacy)
`selectedAssetUrl`	No	Prefer a specific hashed download URL from the release
`includeSiblingAssets`	No	Publish extra NIP-82 MIME files on the same tag (default true; skips extra APKs)

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.9Oct 7, 2026

changedInput schema / properties / appId / description

Previous value: -"Package id (e.g. com.example.app). Default: space.gittr.<repo>"New value: +"Package id (e.g. com.example.app). Default: space.gittr.<repo>, or space.gittr.app for the official gittr Android package"

addedInput schema / properties / homepageUrl

Added value: +{
+  "description": "Optional HTTPS homepage for kind 32267 url",
+  "type": "string"
+}

addedInput schema / properties / iconUrl

Added value: +{
+  "description": "Optional HTTPS icon. Else zapstore.yaml icon:, else official gittr bird.",
+  "type": "string"
+}

changedInput schema / properties / pinToBlossom / description

Previous value: -"Optional: pin hashed files to public Blossom (primal/ditto/haven). Pin failure still announces the forge URL."New value: +"Optional: pin hashed files to public Blossom (primal/ditto/haven). Official gittr APK may also pin to blossom.gittr.space. Pin failure still announces the forge URL."

addedInput schema / properties / screenshotUrls

Added value: +{
+  "description": "Optional extra HTTPS screenshot URLs. Default: zapstore.yaml images: (repo paths rewritten to raw forge URLs).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed6 schema fields changedv1.0.6Sep 8, 2026

addedInput schema / properties / includeSiblingAssets

Added value: +{
+  "description": "Publish extra NIP-82 MIME files on the same tag (default true; skips extra APKs)",
+  "type": "boolean"
+}

addedInput schema / properties / pinToBlossom

Added value: +{
+  "description": "Optional: pin hashed files to public Blossom (primal/ditto/haven). Pin failure still announces the forge URL.",
+  "type": "boolean"
+}

changedInput schema / properties / selectedApkUrl / description

Previous value: -"Prefer a specific APK download URL from the release"New value: +"Alias of selectedAssetUrl (legacy)"

addedInput schema / properties / selectedAssetUrl

Added value: +{
+  "description": "Prefer a specific hashed download URL from the release",
+  "type": "string"
+}

changedInput schema / properties / sourceUrl / description

Previous value: -"Forge repository HTTPS URL with a Release that has an .apk"New value: +"Forge repository HTTPS URL with a Release that has an announceable binary"

addedInput schema / properties / tag

Added value: +{
+  "description": "Release tag to announce (omit = latest, same as Code sidebar)",
+  "type": "string"
+}

First observedv1.0.3Jul 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and discloses important traits: it only announces release binaries, copies images from zapstore.yaml onto kind 32267, restricts blossom.gittr.space to the official gittr APK, and auto-loads .nostr-keys.json when privkey is omitted. It does not cover failure modes beyond pinning or authentication requirements in full, so it is strong but not exhaustive.

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

Conciseness4/5

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

The description is dense but front-loaded, beginning with the core action and then adding constraints and behavioral details. It avoids unnecessary filler, though the run-on sentence and jargon-heavy style reduce readability slightly.

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 18-parameter mutation tool with no annotations and no output schema, the description provides substantial context around target kinds, image handling, key loading, and pinning behavior. It leaves some gaps around return behavior and failure handling, but the high schema coverage fills most parameter-level needs.

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 94%, so the schema already documents nearly all 18 parameters in detail. The description adds only marginal parameter meaning, such as the effect of omitting tag and privkey, but mostly repeats or alludes to schema-provided details. Baseline 3 is appropriate.

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

Purpose4/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: announce software from a forge Release binary to Zapstore/NIP-82 kinds. It clearly identifies the source type and destination protocol. However, it does not explicitly differentiate itself from the sibling publishSoftwareAnnounce tool, so it stops short of a 5.

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?

The description gives contextual usage cues, saying it is the same as gittr Nostr Apps (latest tag) or Releases → Announce on Nostr (tag=), and states 'Never a tagless app.' This implies when to use it, but it does not name alternatives or explain when another tool such as publishSoftwareAnnounce would be preferred.

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

Deploy Server

announceSoftwareFromForgeRelease

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools