Product Outcome
Turn one selected match into a rich experience with context, play-by-play, lineups, stats, and optional odds without hand-stitching multiple sports services.Who Builds This
- editorial products and match hubs
- AI recap generators
- live blog and commentary experiences
- customer support or newsroom assistants
Recommended Tool Chain
| Step | Tool | Why it matters |
|---|---|---|
| 1 | gns_schedule_results | discover the match and capture the match ID |
| 2 | gns_matchboard | get the fastest one-call match-center payload |
| 3 | gns_match_tactical_view | emphasize actions, lineups, and team stats |
| 4 | gns_match_actions | go deeper on play-by-play when needed |
| 5 | gns_match_person_stats or gns_match_odds | add player-stat or betting context selectively |
Minimum Inputs
- a
matchId - optionally
actionTagsfor narrower tactical or recap views - a target locale if the experience is multilingual
Example End-User Prompts
- “What happened in the Madrid match?”
- “Show me the starting lineups and key actions.”
- “Give me a tactical summary of the second half.”
- “Who scored, who assisted, and what changed the match?”
Expected Output / UX
A good match-center experience should give users:- one clear match state
- chronological actions that are easy for an LLM to summarize
- lineups and substitutions with person IDs for deeper drill-down
- stats and optional odds only when they add value
Common Mistakes
- calling every atomic match tool before you know whether a bundle already fits
- sending unfiltered action streams into a short-answer agent prompt
- treating player stats and team stats as interchangeable
- forgetting that some sports or matches may not have odds coverage