garmin-connect-api

Delete activity

delete_activity

DestructiveIdempotent

Permanently remove one unwanted Garmin Connect activity, such as a duplicate session, with no undo.

Instructions

Permanently delete one activity from Garmin Connect. There is no undo.

Use it for an activity that should not exist, such as a session logged twice. To fix a strength session's sets use edit_activity_sets, and to rename it, update_activity; both keep the activity. A copy already shared to Strava or another connected app stays there.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "delete_activity"
  }
}

Input Schema

Name	Required	Description	Default
`activity_id`	Yes	Garmin's activity id, from list_activities.

Output Schema

Name	Required	Description	Default
No arguments

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 declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description still adds genuine value beyond them: the deletion is permanent with 'no undo', and a copy already shared to Strava or another connected app stays there — a non-obvious side effect an agent could otherwise miss.

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, front-loaded with the irreversible action, then the usage condition, then the alternatives and the external-copy caveat. Every sentence carries distinct information with no padding.

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?

An output schema exists so return values need not be explained. For a one-parameter destructive tool, the description covers purpose, condition, alternatives, irreversibility, and external side effects — nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and the single activity_id parameter is fully described in the schema as 'Garmin's activity id, from list_activities'. The description confirms single-activity scope but adds no syntax or format detail beyond that.

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 — 'Permanently delete one activity from Garmin Connect' — with the scope 'one activity' made explicit. It is readily distinguishable from siblings like update_activity or edit_activity_sets.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ('an activity that should not exist, such as a session logged twice') and names the alternatives for adjacent needs: edit_activity_sets for sets and update_activity for renaming. It also clarifies both alternatives keep the activity, sharpening the boundary against this destructive tool.

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