Skip to main content
Glama

tp_create_workout

Create a planned workout with simplified interval structure or native TrainingPeaks structured workout payload. Automatically compute duration from structure if not provided.

Instructions

Create a planned workout with optional simplified interval structure or native TrainingPeaks structured_workout payload. Duration is auto-computed only from simplified structure when not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpeNoRating of perceived exertion (RPE), 0-10.
dateYesYYYY-MM-DD or YYYY-MM-DDTHH:MM:SS
tagsNoOptional comma-separated tags
sportYes
titleYesWorkout title
athleteNoTarget athlete name or ID (coach accounts only). Omit to use your own profile.
feelingNoTrainingPeaks feeling value (0-10).
is_hiddenNoWhether to hide the workout
structureNoInterval structure as a JSON object or string. Format: {"steps": [...], "primaryIntensityMetric": "percentOfFtp"|"percentOfThresholdHr"|"percentOfThresholdPace"}. Each step is either a single interval or a repetition block. SINGLE STEP: {"name": "Endurance", "duration_seconds": 1200, "intensity_min": 65, "intensity_max": 75, "intensityClass": "active"}. REPETITION BLOCK: {"type": "repetition", "reps": 5, "steps": [{"name": "VO2max", "duration_seconds": 180, "intensity_min": 106, "intensity_max": 120, "intensityClass": "active"}, {"name": "Spin", "duration_seconds": 180, "intensity_min": 40, "intensity_max": 50, "intensityClass": "rest"}]}. FOR MULTIPLE SETS separated by longer recovery, alternate repetition blocks with single rest steps: [{"type": "repetition", "reps": 4, "steps": [...]}, {"name": "Block Recovery", "duration_seconds": 600, "intensity_min": 45, "intensity_max": 55, "intensityClass": "rest"}, {"type": "repetition", "reps": 4, "steps": [...]}]. intensityClass values: warmUp, active (work intervals), rest (all recovery), coolDown, other. Intensity values are % of threshold (FTP/HR/pace). Optional per-step: cadence_min, cadence_max (rpm).
subtype_idNoWorkout subtype ID from tp_get_workout_types
descriptionNoOptional description
distance_kmNoOptional distance in km
tss_plannedNoOptional planned TSS
duration_minutesNoPlanned duration in minutes (optional if structure provided)
structured_workoutNoNative TrainingPeaks structured workout payload in builder format. Use this only when you already have a TP structure object with keys like structure, polyline, primaryLengthMetric, primaryIntensityMetric, and primaryIntensityTargetOrRange.
Behavior2/5

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

Without annotations, the description carries full burden. It mentions auto-computation of duration for simplified structures but omits side effects, auth requirements, rate limits, success/failure behavior, or return values. For a creation tool, key behavioral traits are missing.

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 description is front-loaded with the core purpose in two sentences, then provides necessary detail for the structure parameter. While the structure explanation is long, it is valuable. Could be slightly more structured (e.g., bullet points), but overall efficient.

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?

The description adequately covers the complex structure input but lacks information about return values (no output schema), error handling, or prerequisites. For 15 parameters with nested objects, more context on post-creation behavior would improve completeness.

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 high (93%), but the description adds substantial value for the 'structure' parameter with detailed examples and explanation of the interval format, which is not fully covered by the schema's brief description. Other parameters are well-covered by the schema.

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?

The description clearly states the tool creates a planned workout and distinguishes between two input modes (simplified interval structure vs. native payload), with specific verb and resource. This differentiates it from sibling tools like tp_copy_workout or tp_delete_workout.

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

Usage Guidelines3/5

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

The description implies two approaches (simplified vs. native payload) but provides no explicit guidance on when to choose one over the other or when not to use this tool. It does not mention alternatives or context beyond the basic purpose.

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/JamsusMaximus/TrainingPeaks-MCP'

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