Skip to main content
Glama

get-recent-activities

Retrieve recent Strava activities to analyze workouts and track fitness progress. Fetches activity stats, heart rate data, and segment insights for performance monitoring.

Instructions

Fetches the most recent activities for the authenticated athlete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
perPageNoNumber of activities to retrieve (default: 30)

Implementation Reference

  • The 'execute' function within the 'getRecentActivities' object contains the logic to fetch recent activities, handle authentication, and format the output.
    execute: async ({ perPage }: GetRecentActivitiesInput) => {
      const token = process.env.STRAVA_ACCESS_TOKEN;
    
      // --- DEBUGGING: Print the token being used --- 
      console.error(`[DEBUG] Using STRAVA_ACCESS_TOKEN: ${token?.substring(0, 5)}...${token?.slice(-5)}`);
      // ---------------------------------------------
    
      if (!token || token === 'YOUR_STRAVA_ACCESS_TOKEN_HERE') {
        console.error("Missing or placeholder STRAVA_ACCESS_TOKEN in .env");
        // Use literal type for content item
        return {
          content: [{ type: "text" as const, text: "❌ Configuration Error: STRAVA_ACCESS_TOKEN is missing or not set in the .env file." }],
          isError: true,
        };
      }
    
      try {
        console.error(`Fetching ${perPage} recent activities...`);
        const athlete = await getAuthenticatedAthlete(token);
        const activities = await fetchActivities(token, perPage);
        console.error(`Successfully fetched ${activities?.length ?? 0} activities.`);
    
        if (!activities || activities.length === 0) {
           return {
             content: [{ type: "text" as const, text: " MNo recent activities found." }]
            };
        }
    
        const distanceFactor = athlete.measurement_preference === 'feet' ? 0.000621371 : 0.001;
        const distanceUnit = athlete.measurement_preference === 'feet' ? 'mi' : 'km';
    
        // Map to content items with literal type
        const contentItems = activities.map(activity => {
          const dateStr = activity.start_date ? new Date(activity.start_date).toLocaleDateString() : 'N/A';
          const distanceStr = activity.distance ? `${(activity.distance * distanceFactor).toFixed(2)} ${distanceUnit}` : 'N/A';
          // Ensure each item conforms to { type: "text", text: string }
          const item: { type: "text", text: string } = {
             type: "text" as const,
             text: `🏃 ${activity.name} (ID: ${activity.id ?? 'N/A'}) — ${distanceStr} on ${dateStr}`
            };
          return item;
        });
    
        // Return the basic McpResponse structure
        return { content: contentItems };
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : "An unknown error occurred";
        console.error("Error in get-recent-activities tool:", errorMessage);
        return {
          content: [{ type: "text" as const, text: `❌ API Error: ${errorMessage}` }],
          isError: true,
        };
      }
    }
  • Zod schema definition for validating the 'perPage' input parameter.
    const GetRecentActivitiesInputSchema = z.object({
      perPage: z.number().int().positive().optional().default(30).describe("Number of activities to retrieve (default: 30)"),
    });
  • Tool definition including name, description, input schema, and execution handler.
    export const getRecentActivities = {
        name: "get-recent-activities",
        description: "Fetches the most recent activities for the authenticated athlete.",
        inputSchema: GetRecentActivitiesInputSchema,
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'fetches' data (implying read-only) but doesn't mention authentication requirements, rate limits, pagination behavior, or what 'most recent' means (e.g., time window, ordering). This leaves significant gaps for an agent to understand operational constraints.

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?

The description is a single, efficient sentence that immediately conveys the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description should provide more context about what 'most recent activities' means, how results are structured, and how this differs from sibling activity tools. The current description is insufficient for an agent to fully understand the tool's behavior and appropriate usage context.

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%, so the input schema fully documents the single parameter 'perPage'. The description adds no additional parameter semantics beyond what's already in the schema (which defines type, constraints, and default). This meets the baseline for high schema coverage.

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?

The description clearly states the action ('fetches') and resource ('most recent activities for the authenticated athlete'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-all-activities' or 'get-activity-details', which would require more specific scope clarification.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get-all-activities' or 'get-activity-details'. It mentions 'most recent activities' but doesn't specify if this is paginated, limited by date, or how it differs from other activity retrieval tools in the sibling list.

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/LimeON-source/Strava-MCP'

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