livetennisapi-mcp

Match detail

get_match

Read-onlyIdempotent

Retrieve full tennis match details by ID: players, score, surface, round, status, plus market prices and model analysis. Works on the free plan.

Instructions

Full detail for one match by id: players, score, surface, round and status. Includes market prices on PRO and model analysis on ULTRA. Works on the FREE plan (no card needed).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`match_id`	Yes	Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures.
`match`	No	The match.
`market`	No	Match-winner market. Requires the PRO plan; absent otherwise.
`message`	Yes	Human-readable summary. Identical to the text content, so either half can be used alone.
`analysis`	No	Model analysis. Requires the ULTRA plan; absent otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.5.0Sep 15, 2026

addedOutput schema / properties / match / properties / event_status_updated_at

Added value: +{
+  "description": "The instant the current event_status was recorded, UTC ISO-8601 (added 2026-08-19). Null while the status has never changed since the field was introduced — never backfilled.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / match / properties / has_analysis

Added value: +{
+  "description": "Whether a model thesis or profile exists for this match (added 2026-09-02, every tier). Filter on this before calling get_match_analysis, which reports the same absence. Null only when the server predates the field.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / match / properties / has_market

Added value: +{
+  "description": "Whether a match-winner market is mapped to this match (added 2026-09-02, every tier). Filter on this before calling get_match_odds, which reports the same absence. Null only when the server predates the field.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

changedOutput schema / properties / match / required

Previous value: -[
-  "id",
-  "tour",
-  "tournament",
-  "tournament_id",
-  "round",
-  "round_code",
-  "player1",
-  "player2",
-  "score",
-  "status",
-  "surface",
-  "indoor",
-  "serving",
-  "winner",
-  "event_status",
-  "withdrew",
-  "win_probability_p1"
-]New value: +[
+  "id",
+  "tour",
+  "tournament",
+  "tournament_id",
+  "round",
+  "round_code",
+  "player1",
+  "player2",
+  "score",
+  "status",
+  "surface",
+  "indoor",
+  "serving",
+  "winner",
+  "event_status",
+  "event_status_updated_at",
+  "withdrew",
+  "has_analysis",
+  "has_market",
+  "win_probability_p1"
+]

Changed6 schema fields changedv1.4.0Aug 7, 2026

addedOutput schema / properties / match / properties / event_status

Added value: +{
+  "description": "How the match ended (or paused) when it did not run its course: Retired, Cancelled, Walk Over, Postponed or Interrupted. Null means completed normally OR never resolved. Branch settlement logic here.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / match / properties / round_code

Added value: +{
+  "description": "Round in the normalized vocabulary (F, SF, QF, R16 … Q); null when the label is unrecognised, never guessed.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / match / properties / tour

Added value: +{
+  "description": "atp, wta, challenger, itf or juniors. Null when the feed never stated one (exhibitions, team events).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / match / properties / tournament_id

Added value: +{
+  "description": "Stable tournament id — pass to get_tournament. Null where uncatalogued.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / match / properties / withdrew

Added value: +{
+  "description": "Completed matches only: which player retired or conceded the walkover, 1 or 2. Null means \"not a withdrawal, or no evidence\", never a guess.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / match / required

Previous value: -[
-  "id",
-  "tournament",
-  "round",
-  "player1",
-  "player2",
-  "score",
-  "status",
-  "surface",
-  "indoor",
-  "serving",
-  "winner",
-  "win_probability_p1"
-]New value: +[
+  "id",
+  "tour",
+  "tournament",
+  "tournament_id",
+  "round",
+  "round_code",
+  "player1",
+  "player2",
+  "score",
+  "status",
+  "surface",
+  "indoor",
+  "serving",
+  "winner",
+  "event_status",
+  "withdrew",
+  "win_probability_p1"
+]

Addedv1.2.1Jul 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the description correctly avoids repeating that. It adds valuable context about plan tiers: market prices are only on PRO and model analysis on ULTRA, and it works on the FREE plan without a card. This goes beyond the annotations by disclosing access-level limitations and feature availability, which is helpful for an agent deciding whether this tool meets the user's needs.

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

Conciseness5/5

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

The description is two concise sentences, with the core purpose and contents front-loaded in the first sentence. The second sentence adds plan-tier information without unnecessary detail. Every word earns its place, making it highly efficient and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter) and the presence of an output schema, the description does not need to explain return format. It covers the core behavior and plan limitations. It could be slightly more complete by explicitly mentioning alternatives or edge cases, but overall it provides sufficient context for an agent to call the tool correctly and understand what it returns.

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?

The schema fully documents the single parameter match_id, including its type and source (from other match-listing endpoints). The description adds no additional parameter guidance, but with 100% schema coverage, that is acceptable per the baseline of 3. No extra semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves full detail for one match by id, listing the specific fields included (players, score, surface, round, status). This differentiates it from sibling tools like get_match_score or get_match_events, which focus on narrower aspects, so an agent can easily identify this as the comprehensive match lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when full match detail is needed, but it does not explicitly contrast with alternatives such as get_match_score or get_match_events, nor does it state when not to use this tool. There is no guidance on choosing between this and the many specific match-related siblings, leaving the agent to infer the appropriate context.

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