getClubActivitiesByIdList Club Activities - Retrieve recent activities from members of a specific club. The authenticated athlete must belong to the requested club in order to hit this endpoint. Pagination is supported. Athlete profile visibility is respected for all activities.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| page | No | ||
| per_page | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already indicate read-only, but the description adds key behaviors: the authorization requirement, pagination support, and respect for athlete profile visibility. These go beyond the static annotations and help the agent understand data scope and constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief and front-loaded: the first clause gives the purpose, followed by three short sentences on constraints. Every sentence contributes value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (3 parameters, no output schema), the description covers purpose, authorization, pagination, and data filtering. Minor gaps include unspecified pagination limits and the meaning of 'recent,' but overall it's fairly self-contained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has no descriptions for id, page, or per_page (0% coverage). The description mentions 'specific club' for id and 'Pagination is supported' for page/per_page, providing some semantic context. However, it does not explain parameter formats, defaults, or boundaries, so the compensation is partial.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Retrieve recent activities from members of a specific club.' The verb 'retrieve' and resource 'activities' are specific, and it distinguishes from sibling tools like getClubById and getClubMembersById.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides explicit context that the authenticated athlete must belong to the club, which is essential for when to use it. It also notes pagination and profile visibility, but it doesn't name alternative tools explicitly, making the guidance contextually clear but not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and operation: segments, clubs, gear, athlete, routes, and stats. Even potentially similar tools like getEffortsBySegmentId and getSegmentEffortById are clearly differentiated by their descriptions (listing efforts vs. fetching a single effort).
All tool names follow a consistent camelCase pattern with a verb (get, explore) followed by a specific noun phrase. Names like getClubById, getLoggedInAthlete, and getStats are uniform and predictable, making it easy to infer their purpose.
With 13 tools, the server is well-scoped for a focused read-only API over Strava data. The count is within the ideal range and each tool covers a meaningful aspect of the domain without redundancy or bloat.
The tool surface covers several Strava domains (clubs, segments, gear, routes, athlete stats) but is missing any activity-related operations (e.g., list activities, get activity by ID) and all write operations. This creates notable gaps for a comprehensive Strava integration, though the read-only scope may be intentional.