Skip to main content
Glama

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

NameRequiredDescriptionDefault
workoutsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (non-idempotent, open-world write), the description discloses genuinely non-obvious behavior: silent corruption of repeat counts when conditionTypeId is omitted, and that mismatched condition IDs are rejected before upload. It omits batch semantics an agent needs — whether one invalid workout fails the whole list, and any rate/size limits — which keeps it below 5.

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 purpose line, then grouped under IMPORTANT headings that make the dense rules scannable, and the trailing Args block covers the only parameter. It is somewhat redundant at the top ("Upload multiple workouts..." restated as "Creates multiple new workouts...") and heavy in DTO detail for what is fundamentally a one-parameter batch wrapper.

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?

Input-format guidance is thorough for a batch mutation with no output schema, but the description never says what is returned (created workout IDs?), whether the operation is all-or-nothing, or how many workouts can be sent per call — all decision-relevant for a non-idempotent, open-world bulk write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter is an untyped object array, so the description carries the full burden and does so in depth: the item shape, DTO step types, stepOrder depth-first numbering, zoneNumber vs targetValueOne/Two, target type IDs and keys, and m/s pace conversion. This adds substantial meaning the schema cannot convey.

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?

Specific verb and resource with scope: "Upload multiple workouts from JSON data in a single call" and "Creates multiple new workouts in Garmin Connect." It explicitly frames the batch nature and points to upload_workout as the per-item format reference, which separates it from the single-workout sibling without needing 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 Guidelines4/5

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

"Upload multiple workouts ... in a single call" plus "Each item in the list uses the same structure as upload_workout" gives an agent a clear condition for choosing this tool over the single-workout sibling. There is no explicit "use X when you have only one workout" exclusion, so the routing is strong but not fully stated.

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