Skip to main content
Glama

delete_workouts

Destructive

Permanently remove multiple workouts from your Garmin Connect library in one call. Preview selected workout IDs first, then confirm deletion.

Instructions

Delete multiple workouts from Garmin Connect in a single call

    Permanently removes multiple workouts from your Garmin Connect workout library.
    This cannot be undone. Call once with confirm=false (the default) to
    preview the workouts, then call again with confirm=true to delete them.

    Args:
        workout_ids: List of workout IDs to delete (get IDs from get_workouts)
        confirm: Must be true to actually delete. Default false returns a preview.
    

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": {
      "workout_ids": "<workout_ids>"
    },
    "name": "delete_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
workout_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds the crucial details the annotations cannot convey: the deletion is permanent and irreversible, and there is a built-in two-call dry-run preview controlled by confirm.

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?

The irreversible warning and preview workflow come first, which is correct ordering for a destructive tool. There is minor redundancy between the header line and the body sentence, and the Args block restates what the schema already shows.

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?

For a destructive two-parameter tool with rich annotations and no output schema, everything an agent needs is present: irreversibility, the preview-then-confirm pattern, and where to source IDs. The preview call serves as the return-value description.

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 0%, so the description must carry the load, and it does: it explains workout_ids is a list obtained from get_workouts and that confirm defaults to false and must be true to actually delete. Only the ID format/length limits are left implicit.

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 ('Delete multiple workouts from Garmin Connect') and encodes batch scope via 'multiple' and 'workout library', which implicitly separates it from the singular delete_workout sibling.

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?

Gives a concrete operating procedure: fetch IDs from get_workouts first, then call with confirm=false to preview, then confirm=true to delete. It stops short of naming delete_workout as the single-item alternative, but the batch framing makes the choice inferable.

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