Skip to main content
Glama
Sign In
aapanel-mcp

aapanel-mcp

by devochkaskustikom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List website backups

site_list_backups
Read-onlyIdempotent

List backup records for a website by ID, newest first, so you can review available site backups.

Instructions

Backup records for a site, newest first.

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": {
      "search": "<search>"
    },
    "name": "site_list_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pNoPage number, 1-based.
typeNoBackup type: 0 = site.
limitNoRows per page.
searchYesWebsite id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1-alpha.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds useful ordering information ('newest first'), but does not mention pagination, response shape, or other behavioral details beyond the safety profile.

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 a single compact phrase with zero waste. It front-loads the resource and includes the ordering cue, making it appropriately sized for a simple list tool.

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

Completeness4/5

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

For a simple list operation with rich annotations and full schema descriptions, the description covers the resource, scope, and ordering. It omits pagination details, but those are fully specified in the schema, so the omission is minor.

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 description coverage is 100%, so all four parameters are already documented. The description only implies that 'search' maps to a site, adding no syntax or format detail beyond the schema.

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?

The description names the resource (backup records) and scope (for a site), and the title supplies the verb 'List'. It also adds the ordering ('newest first'), but it does not explicitly differentiate itself from sibling tools like db_backups or site_backup.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It relies entirely on the tool name and title for context, leaving the agent to infer usage from siblings.

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

Deploy Server

Other Tools