garmin-connect-api

List activities

list_activities

Read-onlyIdempotent

Retrieve completed Garmin Connect activities newest first. Filter by type or date range, page results, and locate strength sessions to fetch sets, reps, and weights.

Instructions

List activities, newest first.

Completed activities, not planned workouts. Filter by type and by date range; end_date needs start_date. For strength sessions pass activity_type=strength_training, then fetch the sets of one to see the exercises, reps and weights.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Most activities to return.
`start`	No	Activities to skip, for paging. An offset, not a date.
`end_date`	No	Latest date, inclusive.
`start_date`	No	Earliest date, inclusive.
`activity_type`	No	Garmin type key, e.g. "strength_training", "running", "cycling".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description's added value is the sort order, the cross-parameter dependency constraint, and the strength-session follow-up workflow. It does not discuss pagination behavior, though the schema's start/limit fields imply it.

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?

Four short sentences, each carrying distinct information: ordering, scope exclusion, filter constraints, and the strength-session workflow. Front-loaded and free of filler.

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?

With an output schema present, return values need no explanation. The description covers ordering, scope, filter dependencies, and the follow-up tool for strength data, leaving no gap an agent would need in order to call it correctly.

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 100%, so the baseline is 3, but the description adds genuinely new meaning: the end_date-depends-on-start_date constraint (a cross-field rule not encoded in the schema) and a concrete value example for activity_type. It also clarifies that a separate call is needed for exercise-level detail.

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 ('List activities') plus an ordering guarantee ('newest first'), and immediately distinguishes scope from the sibling list_workouts by clarifying these are 'Completed activities, not planned workouts.' An agent can separate this from get_activity (single fetch) and list_workouts without opening a 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?

Gives concrete usage conditions: filter by type and date range, end_date requires start_date, and route strength sessions through activity_type=strength_training followed by the sets fetch. It excludes planned workouts but never names the alternative (list_workouts) explicitly, so routing is implied rather than stated.

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