Skip to main content
Glama

List my backups

list_my_backups
Read-onlyIdempotent

Lists the restore points held for one of the customer's SHARED hosting sites, newest first: the nightly backups of the whole site (source "nightly") and the edit points (source "edit") — the previous version of each file an assistant replaced with write_site_files, listed with the files it holds. Restoring a nightly point merges the whole site back; restoring an edit point puts back ONLY those files. For "undo that last change" pick the newest edit point; for "my site was fine yesterday" pick a nightly one. Use for "what backups do I have?", "can I roll my site back?", and ALWAYS before restore_my_site_backup so the backupId is a real one. A VPS is not covered here (its snapshots live in its own panel). Read-only.

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": {
      "domain": "<domain>"
    },
    "name": "list_my_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe hosted site's domain, e.g. "example.com". Must be on the customer's account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real behavior: results are newest-first, entries include the files an edit point holds, and restoring a nightly point merges the whole site while an edit point restores only those files. That restore-semantics distinction is exactly the kind of consequence an agent needs and no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core verb and scope, then routing cues, then the sibling dependency; nearly every clause carries actionable information. It runs long and repeats the annotation with a trailing "Read-only," which is the only wasted element.

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?

With no output schema, the description carries the burden of describing what comes back, and it does: restore points with a source label, ordering, and per-entry file listings plus the backupId needed downstream. Nothing essential for a correct call is missing.

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% for the single domain parameter, so the baseline is high; the description still adds meaningful constraint by framing the domain as belonging to a shared hosting site and implying VPS domains do not qualify. It does not add format or edge-case detail beyond what the schema already states.

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?

States a specific verb and resource (lists restore points for a shared hosting site) and immediately scopes it by naming the two sources, "nightly" and "edit". It also explicitly excludes VPS snapshots, so the agent can distinguish it from adjacent hosting tools without opening the schema.

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?

Gives explicit when-to-use mappings (undo last change → newest edit point; site fine yesterday → nightly) and a hard ordering rule: always call this before restore_my_site_backup so the backupId is real. Exclusions are stated too (VPS not covered here).

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.

Resources