Skip to main content
Glama

vibedeploy

by be.vibedeploy

Commit a staged deploy

commit_deploy
Destructive

Atomically apply a staging session's files to the live site. Runs preflight + secret/malware scan against the complete staged set; on failure the session stays open and can be re-attempted or aborted. For replace-mode against a site with existing files, requires confirm:"I-want-to-replace-all-files".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deleteNoPatch-mode only: site-relative paths to remove from the live site as part of this commit. Useful for renames (write new path via add_files, delete old path here).
dryRunNoIf true, preview what commit would do without touching the live site or scratch dir. Returns the diff (filesDeployed, deletedFiles) plus would-be confirmation gate / preflight outcomes. Skips the secret/malware scan to keep the preview fast — the real commit will still scan. Recommended before any replace-mode commit on a populated site.
confirmNoRequired only for replace-mode commits against a site that already has files. Pass exactly "I-want-to-replace-all-files" to acknowledge that the live files will be deleted and replaced with the staged set.
deployIdYesSession id returned by begin_deploy.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
modeYes
dryRunNoTrue if this was a dry-run; nothing was committed.
siteIdYes
deployIdYes
warningsYes
request_idNoServer-assigned request correlation id. Quote it when contacting support.
deletedFilesYes
customHeadersNoResult of the Netlify-style _headers sync: overrides applied to the site's response headers, plus any validation warnings.
filesDeployedYes

TDQS

A5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true. The description adds valuable context: atomicity, preflight/scan, failure leaves session open, confirmation requirement, and dryRun behavior (skips scan for preview but real commit will scan). This exceeds annotation coverage and fully informs the agent about side effects.

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 pack core behavior and safety warnings, with no filler. Parameter descriptions are detailed the moment they appear. Front-loaded with the main action, then flows logically to conditions and mitigations.

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?

Despite being complex (destructive, multi-modal, confirmation gate), the description covers failure paths, preflight outcomes, dryRun preview, and what the real commit does (scan). All four params are covered. Output schema exists, so return values need no description. Exceptionally complete without being bloated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description enhances parameters: clarifies delete applies to live site paths, explains dryRun returns diff and tells agent to use it for replace-mode, and specifies exact confirm string. This adds genuine value beyond the schema.

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?

Clearly identifies the tool's action (atomically apply staged files to live site), the resource (staging session), and its distinctive characteristic (atomic, with preflight/scan, failure keeps session open). It distinguishes from siblings like apply_edits (edits vs staged files), deploy_site (direct deploy), and begin_deploy (starts session, this commits).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: commit a staging session, and mentions related tools and actions: abort, re-attempt, dry-run before replace-mode, and how to handle renames via delete + add_files. While it doesn't name sibling tools directly, it describes the workflow context and guidance clearly.

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

All vibedeploy toolsInspect
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.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, from deployment and file management to domain configuration and analytics. Even similar-sounding tools like add_files and add_file_chunk are well-differentiated by context and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_custom_domain, list_sites, delete_source_file). The naming is predictable and easy to understand.

Tool Count4/5

39 tools is higher than the typical 3-15 range, but each tool serves a necessary function for a comprehensive deployment platform. The count is justified by the broad feature set, though slightly heavy.

Completeness5/5

The tool set covers the full lifecycle of site deployment, management, backup, custom domains, form handling, analytics, and source editing. There are no obvious gaps for the intended functionality.

Resources