Product Outcome
Create a season-aware home for a team or player that combines identity, schedule, roster context, and season statistics in a way an AI product can explain naturally.Who Builds This
- team and athlete profile experiences
- personalization and follow flows
- editorial research assistants
- fantasy, commerce, and engagement products
Recommended Tool Chain
| Step | Tool | Why it matters |
|---|---|---|
| 1 | gns_resolve_entity | resolve a team or player name to a canonical ID |
| 2 | gns_team_info or gns_person_info | load the entity profile |
| 3 | gns_team_season_profile or gns_person_season_profile | get the season-ready bundle |
| 4 | gns_team_schedule_results | add upcoming and recent fixtures |
| 5 | gns_team_roster or gns_person_league_stats | deepen roster or individual season context |
Minimum Inputs
teamIdorpersonIdleagueIdfor the current season orleagueSeasonIdfor a specific season
Example End-User Prompts
- “Build a season page for Inter Miami.”
- “Show me Salah’s season profile.”
- “Who is on this roster and how is the team performing?”
- “What has this player done in this league this season?”
Expected Output / UX
High-quality hubs usually combine:- canonical identity and imagery
- current season schedule or recent activity
- roster or teammates when relevant
- season stats the AI can summarize without extra joins
Common Mistakes
- mixing current-season and historic-season IDs in the same flow
- using cross-league team schedule when the user expects one league only
- building player pages from match stats only instead of season context
- skipping resolution and relying on a fuzzy name in downstream tools