Skip to main content
Glama

list_backup_jobs

Retrieve recent AWS backup jobs with optional filtering by state and time window to monitor backup operations and identify issues.

Instructions

Lists recent backup jobs, optionally filtering by state (default: FAILED).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoFilter by job state (e.g., COMPLETED, FAILED, RUNNING). Default: FAILED.
hoursNoLook back window in hours (default: 24).

Implementation Reference

  • Executes the list_backup_jobs tool by calling AWS BackupClient.ListBackupJobsCommand with optional filters for state and time window, formats and returns the job list.
    if (name === "list_backup_jobs") {
        const state = (args as any)?.state || "FAILED";
        const hours = (args as any)?.hours || 24;
        const sinceDate = new Date(Date.now() - hours * 60 * 60 * 1000);
    
        const command = new ListBackupJobsCommand({
            ByState: state,
            ByCreatedAfter: sinceDate
        });
        const response = await backupClient.send(command);
    
        const jobs = response.BackupJobs?.map(j => ({
            BackupJobId: j.BackupJobId,
            State: j.State,
            CreationDate: j.CreationDate,
            BackupVaultName: j.BackupVaultName,
            ResourceArn: j.ResourceArn,
            StatusMessage: j.StatusMessage
        })) || [];
    
        return {
            content: [{ type: "text", text: JSON.stringify(jobs, null, 2) }]
        };
    }
  • Input schema definition for the list_backup_jobs tool, including optional state and hours parameters.
    {
        name: "list_backup_jobs",
        description: "Lists recent backup jobs, optionally filtering by state (default: FAILED).",
        inputSchema: {
            type: "object",
            properties: {
                state: {
                    type: "string",
                    description: "Filter by job state (e.g., COMPLETED, FAILED, RUNNING). Default: FAILED."
                },
                hours: {
                    type: "number",
                    description: "Look back window in hours (default: 24)."
                }
            }
        }
    },
  • src/index.ts:400-416 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema.
    {
        name: "list_backup_jobs",
        description: "Lists recent backup jobs, optionally filtering by state (default: FAILED).",
        inputSchema: {
            type: "object",
            properties: {
                state: {
                    type: "string",
                    description: "Filter by job state (e.g., COMPLETED, FAILED, RUNNING). Default: FAILED."
                },
                hours: {
                    type: "number",
                    description: "Look back window in hours (default: 24)."
                }
            }
        }
    },
  • Initialization of the AWS BackupClient used by the list_backup_jobs handler.
    const backupClient = new BackupClient({});
  • Import of BackupClient and ListBackupJobsCommand required for the tool implementation.
    import { BackupClient, ListBackupJobsCommand } from "@aws-sdk/client-backup";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions filtering and defaults but fails to describe critical aspects like pagination, rate limits, authentication needs, or what 'recent' means beyond the hours parameter. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that front-loads the core purpose and includes key details without waste. Every word contributes to understanding, making it appropriately sized and well-structured for quick comprehension.

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

Completeness3/5

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

Given the tool's low complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic action and parameters but lacks behavioral context (e.g., response format, limitations), which is needed for a read operation without annotations to fill those gaps.

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?

The input schema has 100% description coverage, so the schema already documents both parameters thoroughly. The description adds minimal value by mentioning the optional state filter and its default, but doesn't provide additional context beyond what's in the schema, aligning with the baseline for high schema coverage.

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 clearly states the tool's purpose with a specific verb ('Lists') and resource ('recent backup jobs'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'list_ec2_instances' or 'list_s3_buckets' beyond the resource type, which keeps it from a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It mentions optional filtering by state but doesn't explain prerequisites, typical use cases, or how it relates to other list tools in the server, leaving the agent with minimal context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bhaveshopss/MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server