League of Legends MCP Server

LoL get match timeline

lol_get_match_timeline

Retrieve a minute-by-minute timeline of events for any League of Legends match using the match ID and region.

Instructions

Get minute-by-minute match timeline

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "matchId": "<matchId>"
    },
    "name": "lol_get_match_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	Region: euw, eune, na, kr, br, lan, las, oce, ru, tr, jp, ph2, sg2, th2, tw2, vn2	euw
`matchId`	Yes	Match ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It only states it 'gets' data, implying a read operation, but omits details on authentication, rate limits, or whether the timeline includes all events (e.g., vs 'lol_get_timeline_events').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that front-loads the core purpose. It is appropriately sized for a simple tool, but could be slightly more informative without being verbose.

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?

No output schema and lack of explanation about what the timeline contains (e.g., events, stats) leaves the agent uncertain about the return structure. Given the existence of 'lol_get_timeline_events', the description should clarify the difference for completeness.

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 coverage is 100%, so the schema already describes both parameters. The description adds no extra meaning beyond 'minute-by-minute', which is already implied. Baseline score of 3 is appropriate.

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 it gets a 'minute-by-minute match timeline', which is a specific resource and action. However, it does not distinguish itself from the sibling tool 'lol_get_timeline_events', which also likely returns timeline data, missing a key differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'lol_get_match_details' or 'lol_get_timeline_events'. There is no mention of prerequisites or appropriate contexts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.