VibeKit

VibeKit Rollback Deploy

vibekit_rollback_deploy

Idempotent

Roll an app back to a previous deploy (get the deployId from vibekit_list_deploys). The container restarts on the rolled-back build; reversible by rolling forward again.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`appId`	Yes	App ID (from vibekit_list_apps)
`deployId`	Yes	Deploy ID to roll back to (from vibekit_list_deploys)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	Rollback confirmation for the selected deploy snapshot.
`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. Dates show when Glama detected each change.

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": "Rollback confirmation for the selected deploy snapshot."
+    },
+    "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.3/5.0

Behavior4/5

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

Annotations already indicate idempotent and non-destructive behavior. The description adds valuable behavioral details: the container restarts on the rolled-back build and the action is reversible by rolling forward again. No contradiction with annotations.

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 two sentences, each serving a purpose: the first states the core action and data source, the second describes the effect and reversibility. No unnecessary words, well-structured.

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

Completeness5/5

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

For a tool with only two parameters fully documented in the schema, presence of annotations, and an output schema, the description provides sufficient context: purpose, prerequisite, effect, and reversibility. It is complete for an agent to use correctly.

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?

Both parameters are fully described in the input schema (100% coverage). The description reiterates that deployId comes from vibekit_list_deploys but adds no new semantic meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 it rolls back an app to a previous deploy, specifying the action on a specific resource and directing to get deployId from vibekit_list_deploys. This distinguishes it from siblings like vibekit_deploy, vibekit_redeploy, and vibekit_restart_app.

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 explains when to use the tool (to revert to a previous deploy), mentions the prerequisite (get deployId from vibekit_list_deploys), and notes reversibility. It does not explicitly state when not to use it or list alternatives, but the context is sufficient.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools have distinct purposes, but vibekit_chat and vibekit_submit_task both handle AI-driven code changes, leading to potential confusion. Descriptions help differentiate, but overlap exists.

Naming Consistency4/5

All tools use the 'vibekit_' prefix and lowercase with underscores. Most follow a verb_noun pattern, but a few (e.g., 'vibekit_account') are noun-only, causing minor inconsistency.

Tool Count3/5

36 tools is on the high side, covering many aspects of the platform. While mostly justified, the count feels slightly excessive and could be streamlined.

Completeness5/5

The tool set covers the full lifecycle of apps, databases, tasks, schedules, skills, QA, and environment variables. No obvious gaps for the stated domain.

VibeKit Rollback Deploy

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources