upload_workouts
Upload multiple workouts from JSON data to Garmin Connect in one call to create several workouts at once.
Instructions
Upload multiple workouts from JSON data in a single call
Creates multiple new workouts in Garmin Connect. Each item in the list
uses the same structure as upload_workout.
IMPORTANT: Step types must use Garmin's DTO format:
- Use "ExecutableStepDTO" for regular steps (warmup, interval, cooldown, recovery)
- Use "RepeatGroupDTO" for repeat/interval groups with numberOfIterations.
Always include endCondition with conditionTypeId 7 and conditionTypeKey
"iterations"; omitting conditionTypeId causes the API to silently corrupt
the repeat count.
- stepOrder is one depth-first counter over the whole workout: a repeat
group takes the next number and its nested steps continue from there
(group 2, children 3 and 4, cooldown 5). Do not restart at 1 inside a group.
IMPORTANT: For named heart rate zone targets, use "zoneNumber" (1-5), NOT targetValueOne/targetValueTwo.
For custom heart-rate ranges, use targetType {"workoutTargetTypeId": 4,
"workoutTargetTypeKey": "heart.rate.zone"} with targetValueOne/targetValueTwo.
Target values belong on the workout step, alongside targetType, not inside it.
For cycling power zone targets (zone-based), use workoutTargetTypeId 2, key "power.zone".
For cycling absolute watt range targets, use workoutTargetTypeId 6, key "power.between",
with targetValueOne (low watts) and targetValueTwo (high watts).
Pace targets use targetValueOne/targetValueTwo in meters per second, not
min/km: 5:00/km = 1000 m / 300 s = 3.333 m/s.
Target type IDs and keys must match Garmin's canonical mapping.
IMPORTANT: End condition IDs and keys must match Garmin's canonical mapping.
Garmin treats conditionTypeId as authoritative, so mismatches are rejected before upload.
Args:
workouts: List of workout dictionaries, each containing workout structure
(name, sport type, segments, etc.) — same format as upload_workout.
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": {
"workouts": "<workouts>"
},
"name": "upload_workouts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workouts | Yes |