Skip to main content
Glama
Sign In

VibeKit

by io.github.VibeKit-Bot
OverviewDiscussionsAdmin

VibeKit List Deploys

vibekit_list_deploys
Read-onlyIdempotent

List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy.

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_list_deploys"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp ID (from vibekit_list_apps)
limitNoMax deploys to return (default 20, max 50)

Output Schema

NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoArray of past deploys with timestamps and commit info.
errorNoError message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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": "Array of past deploys with timestamps and commit info."
+    },
+    "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"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to repeat that. It adds value by stating the result ordering and content (newest first, status, commit info), which are behavioral traits not covered by 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?

Two sentences, front-loaded with action and purpose. Every sentence is informative with no redundant words. The structure efficiently conveys what the tool does and a key use case.

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?

Given the presence of an output schema, complete parameter coverage in the schema, and annotations covering safety, the description sufficiently completes the picture by specifying ordering, content, and a clear follow-up use. No gaps remain for this simple list tool.

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 100% and both parameters have descriptions in the schema. The description adds context that the deployId returned is meant for rollback, which enhances understanding of parameter usage beyond the schema definitions.

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 action (list), resource (an app's recent deploys), ordering (newest first), and included information (status, commit info). It also distinguishes from sibling tools by specifying it's listing deploys, not apps or tasks.

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 explicitly connects the tool to a follow-up use (finding deployId for vibekit_rollback_deploy), giving clear context for when to use it. It does not explicitly state when not to use it or list alternatives, but the purpose is straightforward for a list tool.

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

All VibeKit toolsInspect
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.

Resources