Skip to main content
Glama
Sign In
Strava MCP Server

Strava MCP Server

by justmytwospence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Activity

strava_create_activity

Create a manual activity entry (one API request). Requires activity:write scope and intent. Do not blindly retry a lost response; duplicate creation is possible.

Instructions

Create a manual activity entry (one API request). Requires activity:write scope and intent. Do not blindly retry a lost response; duplicate creation is possible.

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the activity
commuteNoWhether this was a commute
trainerNoWhether this was a trainer/indoor activity
distanceNoDistance in meters
sport_typeYesThe sport type (e.g. Run, Ride, Swim, Hike)
descriptionNoActivity description
elapsed_timeYesTotal elapsed time in seconds
start_date_localYesISO 8601 date/time for activity start in local timezone (e.g. 2024-01-15T08:30:00Z)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv4.4.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / elapsed_time / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / name / maxLength
      Added value: +1000
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / start_date_local / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d))|(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?)$"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag non-idempotency and non-read-only behavior; the description adds the practical consequence (duplicate creation on retry) plus the OAuth scope requirement, which the annotations do not cover. It does not describe what the call returns or any rate-limit behavior.

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?

Two short sentences with zero filler; the what and the scope/retry hazard are both front-loaded. Nothing is repeated from the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the mutation risk, auth scope, and request cost, which is substantial for an unannotated return path. However, with no output schema, the description should state what a successful create returns (e.g., the new activity ID needed for strava_get_activity), which it omits.

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 description coverage is 100% across all 8 parameters, including units (meters, seconds) and the ISO 8601 pattern, so the schema carries the semantics. The description adds no field-level guidance beyond what the schema states, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Create a manual activity entry,' which implicitly separates it from the file-based strava_create_upload sibling. The parenthetical '(one API request)' adds a cost hint but the description never names the alternative tool explicitly.

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 a concrete prerequisite ('Requires activity:write scope and intent') and a clear retry exclusion ('Do not blindly retry a lost response'), which is actionable when-to/when-not guidance. It stops short of routing the agent between this and strava_create_upload for file-based activities.

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