Skip to main content
Glama

List deploy/snapshot history for a site

list_history
Read-onlyIdempotent

Return the site's last 50 deploy and snapshot entries, newest first: how each was triggered, label, snapshot name, file count and secrets detected. Each entry's snapshot holds the content from BEFORE that entry. Restoring is done by the user in the VibeDeploy dashboard within the plan's restore window; there is no restore tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSite name as shown by list_sites, e.g. my-portfolio. Provide name or siteId.
siteIdNoSite id from list_sites or get_site. Use instead of name.

Output Schema

NameRequiredDescriptionDefault
entriesYesMost recent 50 deploy/snapshot history entries, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / entries / items / properties / label / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / entries / items / properties / label / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / entries / items / properties / snapshotName / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / entries / items / properties / snapshotName / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Site name as shown by list_sites, e.g. my-portfolio. Provide name or siteId."
    • addedInput schema / properties / siteId / description
      Added value: +"Site id from list_sites or get_site. Use instead of name."
    • changedOutput schema / properties / entries / items / properties / snapshotName / description
      Previous value: -"Longhorn snapshot taken immediately BEFORE this entry's change (pre-deploy, pre-promote, pre-restore), so restoring it brings back the content that was live before this entry, not this entry's own content. For manual-snapshot and staging entries it is the live content at that moment. To bring back the content of an older deploy, use the snapshot of the next newer entry. Null if none was taken or it was pruned by retention."New value: +"Snapshot taken just BEFORE this entry's change, so restoring it brings back what was live before this entry. For manual-snapshot and staging entries it is the live content at that moment. To get an older deploy's own content back, use the snapshot of the next newer entry. Null if none was taken or retention removed it."
  3. Changed1 schema field changed
    • changedOutput schema / properties / entries / items / properties / snapshotName / description
      Previous value: -"Longhorn snapshot name for this entry, or null if no snapshot is associated (or it was pruned by retention)."New value: +"Longhorn snapshot taken immediately BEFORE this entry's change (pre-deploy, pre-promote, pre-restore), so restoring it brings back the content that was live before this entry, not this entry's own content. For manual-snapshot and staging entries it is the live content at that moment. To bring back the content of an older deploy, use the snapshot of the next newer entry. Null if none was taken or it was pruned by retention."
  4. Changed1 schema field changed
    • removedOutput schema / properties / request_id
      Removed value: -{
      -  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      -  "type": "string"
      -}
  5. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
      +  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish a safe read-only, idempotent, closed-world operation, and the description adds real substance beyond them: a hard 50-entry cap, newest-first ordering, the fact that each entry's snapshot captures content from BEFORE that entry, and the dashboard/restore-window constraint. The pre-state snapshot semantics in particular are non-obvious and prevent misinterpretation of results.

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?

Three sentences, front-loaded with what is returned and its ordering, followed by the critical snapshot-timing caveat and the restore constraint. No filler, and each sentence carries distinct decision-relevant information.

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?

Although an output schema exists, the description still characterizes the entry contents (trigger, label, snapshot name, file count, secrets detected) enough for the agent to know the result is usable. Combined with the 50-entry cap and restore limitation, nothing an agent needs to call and interpret this correctly is missing.

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?

Schema coverage is 100%, so both name and siteId are already fully documented with examples and the "provide one or the other" rule. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return the site's last 50 deploy and snapshot entries, newest first" gives a specific verb, resource, scope, and ordering, and the combined deploy+snapshot framing implicitly separates it from the single-purpose list_deploys and list_snapshots siblings. It stops short of naming those alternatives, so an agent must infer the distinction.

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 preempts a likely wasted lookup by stating restoring happens in the VibeDeploy dashboard within the plan's restore window and that no restore tool exists. It does not explicitly say when to prefer this over list_deploys or list_snapshots, leaving that routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.