valorant_matches
Read-only
Query Valorant matches: recent results, upcoming fixtures, live matches, or filtered match history by event, team, date range, or search query.
When to use:
Recent Valorant match results ("who won yesterday?")
Filtering Valorant matches by event, team, date, or date range (from/to)
Searching Valorant matchups by team or event name
Prefer over: call_api for /valorant/matches or /valorant/matches/results. For live-only across all games use live_matches; for one match's full map/player stats use match_summary or match_details.
Parallel-safe: yes. Upstream cost: 1.
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": "valorant_matches"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Case-insensitive search across team and event names. | |
| to | No | End date inclusive (YYYY-MM-DD). | |
| date | No | Exact match date (YYYY-MM-DD). | |
| from | No | Start date inclusive (YYYY-MM-DD). | |
| team | No | Filter by team id (e.g. "val-team-2") or team name. | |
| event | No | Filter by event id (e.g. "val-event-2004") or event name. | |
| limit | No | Max items to return (default 20, max 50). Example: 20. | |
| offset | No | Pagination offset (default 0). | |
| status | No | Match status filter (default completed). | completed |
| includeGames | No | Include per-map games/player stats in each match row (default false for faster list responses). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | true if the tool succeeded | |
| data | No | Result payload when ok is true; null on error | |
| meta | Yes | ||
| error | No | ||
| partial | No | ||
| pagination | No |