Skip to main content
Glama
Sign In

Strava MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Request account export in Strava

strava_request_account_export
Read-onlyIdempotent

Request account export in the user's own Strava account from ChatGPT, Claude or any AI agent. Returns how to do it in Strava step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Strava Cloud Browser. Strava's official API: Strava has an official API and, since 1 June 2026, an official MCP connector (checked 27 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "strava_request_account_export"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The phrase 'opens nothing by itself' is valuable disclosure that, despite the 'request' verb, this tool performs no mutation — consistent with readOnlyHint=true and destructiveHint=false. It also describes the return content (screens, buttons, fields). The trailing note about Strava's official API/connector is opaque and does not clearly convey a behavioral constraint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are front-loaded and efficient, but the final sentence about Strava's official API and MCP connector adds no actionable information for calling this tool and reads as unrelated filler that dilutes the signal.

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?

For a zero-parameter, read-only guidance tool with no output schema, the description covers what it returns and what to do next. It could be complete with one caveat about prerequisites (e.g., an active Strava Cloud Browser session) it never states.

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?

Zero parameters, so there is nothing for the description to elaborate; baseline applies. The description correctly implies no inputs are needed.

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 ('Request account export in the user's own Strava account') and then clarifies the actual behavior: it returns step-by-step instructions rather than performing the action. The name/behavior tension is resolved by the second sentence, and the cotlet_browser_* reference distinguishes it from the action-performing siblings.

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?

Explicitly routes the agent to the cotlet_browser_* tools in the user's Strava Cloud Browser after getting the instructions, which is clear next-step guidance. It does not state when not to use it or what to do if the user lacks a Cloud Browser session.

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

All Strava MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources