VibeKit

VibeKit Redeploy

vibekit_redeploy

Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.

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": {
      "appId": "<appId>"
    },
    "name": "vibekit_redeploy"
  }
}

Input Schema

Name	Required	Description	Default
`appId`	Yes	App ID (from vibekit_list_apps)

Output Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	Redeploy confirmation with deploy/task status.
`error`	No	Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result envelope: ok=true with data on success, ok=false with error on failure.",
+  "properties": {
+    "data": {
+      "description": "Redeploy confirmation with deploy/task status."
+    },
+    "error": {
+      "description": "Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations show readOnlyHint:false, idempotentHint:false, destructiveHint:false, indicating mutation but not destruction. The description adds 'pull and ship the latest code', implying the app is updated, but does not disclose potential downtime, restart behavior, or that the operation is not idempotent. With annotations providing some baseline, a score of 3 is appropriate.

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?

The description is only two sentences, front-loaded with the action and followed by usage context. Every word earns its place; no redundancy or fluff.

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?

Given that an output schema exists, the description does not need to explain return values. However, it omits potential behavioral details like async deployment or downtime. For a redeploy tool, this is a minor gap, but overall the description is complete enough for most use cases.

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?

The schema already describes the single parameter 'appId' as coming from vibekit_list_apps. The description adds no additional semantic value beyond what the schema provides. With 100% schema coverage, the baseline is 3.

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?

The description clearly states the verb 'redeploy' and the resource 'existing app', and specifies the context of pulling the latest code after a GitHub push. It distinguishes this from sibling tools like vibekit_deploy (initial deployment) and vibekit_restart_app (restart without code update).

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?

The description gives clear guidance on when to use the tool: 'Use after pushing changes to the app's GitHub repo.' It does not explicitly mention when not to use it or alternatives, but the context is sufficient for an AI agent to make a correct decision.

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

All VibeKit tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.