Skip to main content
Glama
arbadacarbaYK

gittr-mcp

by arbadacarbaYK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pushToBridge

Push files to the git server (REQUIRES signing with privkey). This replaces the branch with one new snapshot commit. It does not keep imported GitHub history.

Instructions

Push files to the git server (REQUIRES signing with privkey). This replaces the branch with one new snapshot commit. It does not keep imported GitHub history. Optional deletedPaths removes files or whole folders on that snapshot (same as gittr UI folder delete); allowTreeShrink defaults true when deletes are present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYesRepository name
filesNoArray of { path, content } objects (may be empty when only deleting)
branchNoBranch name (default: main)
privkeyNoPrivate key for authentication (auto-loaded from .nostr-keys.json if not provided)
ownerPubkeyYes64-char hex pubkey
deletedPathsNoFile or folder paths to remove from the tip before commit (prefix match for folders, same as gittr UI)
commitMessageNoCommit message
allowTreeShrinkNoAllow tip to shrink vs previous tree. Defaults true when deletedPaths is non-empty; set false to refuse shrinks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.5
    • addedInput schema / properties / allowTreeShrink
      Added value: +{
+  "description": "Allow tip to shrink vs previous tree. Defaults true when deletedPaths is non-empty; set false to refuse shrinks.",
+  "type": "boolean"
+}
    • addedInput schema / properties / deletedPaths
      Added value: +{
+  "description": "File or folder paths to remove from the tip before commit (prefix match for folders, same as gittr UI)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / files / description
      Previous value: -"Array of { path, content } objects"New value: +"Array of { path, content } objects (may be empty when only deleting)"
    • changedInput schema / required
      Previous value: -[
-  "ownerPubkey",
-  "repo",
-  "files"
-]New value: +[
+  "ownerPubkey",
+  "repo"
+]
  2. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and largely meets it: it discloses that the branch is replaced (destructive to history), that privkey signing is mandatory, and how deletedPaths/allowTreeShrink interact. It omits push-paywall or rate-limit implications hinted at by sibling tools like getPushPaywallStatus, and says nothing about the response.

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?

Four sentences, front-loaded with the operation and its prerequisite, with no filler. It is dense and slightly cramped by parentheticals, but every sentence carries information an agent needs.

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 8-parameter mutation with no annotations and no output schema, the description covers the essentials: auth requirement, destructive snapshot semantics, and delete/shrink behavior. Gaps remain around return values and any paywall/permission prerequisites, but nothing an agent needs to invoke it correctly 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?

Schema coverage is already 100%, so the baseline is 3; the description earns extra by explaining cross-parameter behavior (allowTreeShrink auto-defaults true when deletedPaths is non-empty; deletedPaths removes files or whole folders like the gittr UI). It adds interaction semantics rather than restating field docs.

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 and resource (push files to the git server) plus the exact semantics: it replaces the branch with a single new snapshot commit and discards imported GitHub history. That snapshot-vs-history framing cleanly distinguishes it from importRemoteToBridge without opening either schema.

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?

Gives clear operational context: signing with privkey is required, deletion-only calls are valid (files may be empty), and allowTreeShrink defaults on when deletes are present. It never names an alternative tool or an explicit when-not condition, so it stops short of a 5.

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