Football Data

Get Competition Matches

get_competition_matches

Read-onlyIdempotent

List matches in a competition. Filter by status (SCHEDULED, LIVE, IN_PLAY, PAUSED, FINISHED, POSTPONED, SUSPENDED, CANCELLED), date range, matchday, stage, or season year.

Input Schema

TableJSON Schema

Name	Required	Description
`stage`	No	Stage (e.g., "GROUP_STAGE", "QUARTER_FINALS")
`season`	No	Season start year (e.g., 2025)
`status`	No	Match status filter (SCHEDULED \| LIVE \| IN_PLAY \| PAUSED \| FINISHED \| POSTPONED \| SUSPENDED \| CANCELLED)
`date_to`	No	YYYY-MM-DD
`matchday`	No	Round number
`date_from`	No	YYYY-MM-DD
`competition`	Yes	Competition code (e.g., "PL" = Premier League, "PD" = La Liga, "CL" = Champions League)

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of matches returned
`matches`	Yes
`competition`	Yes	Competition code used in the query

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "competition": "PL"
+  },
+  {
+    "competition": "CL",
+    "season": 2024,
+    "status": "FINISHED"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "competition": {
+      "description": "Competition code used in the query",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of matches returned",
+      "type": "number"
+    },
+    "matches": {
+      "items": {
+        "properties": {
+          "away": {
+            "description": "Away team name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "away_id": {
+            "description": "Away team ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "competition": {
+            "description": "Competition name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "competition_code": {
+            "description": "Competition code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "group": {
+            "description": "Group name if applicable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home": {
+            "description": "Home team name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home_id": {
+            "description": "Home team ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Match ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "matchday": {
+            "description": "Round/matchday number",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "score_full_time": {
+            "description": "Full-time score (e.g., '2-1' or '-' if not final)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "score_half_time": {
+            "description": "Half-time score (e.g., '1-0' or '-' if not played)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stage": {
+            "description": "Competition stage (e.g., GROUP_STAGE)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Match status",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "utc_date": {
+            "description": "Match date/time in UTC (ISO 8601)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "venue": {
+            "description": "Venue name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "winner": {
+            "description": "Winner ('HOME', 'AWAY', 'DRAW', or null)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "competition",
+    "count",
+    "matches"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.2/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, so the description need not repeat these. It adds context about filterable statuses and date range, which is consistent with annotations.

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?

Two concise sentences: first states the purpose, second lists filters. No wasted words, efficiently front-loaded.

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?

With complete annotations and output schema, the description adequately covers filter capabilities. It does not mention pagination or ordering, but for a list tool with openWorldHint, this is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 7 parameters. The description adds value by enumerating status filter values (e.g., SCHEDULED, LIVE) and summarizing filter options, going slightly beyond the schema.

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 uses a specific verb ('List') and resource ('matches in a competition'), clearly differentiating from sibling tools like get_competition_standings or get_team_matches.

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 for competition-level match listing with filter options, but does not explicitly state when to use this tool versus alternatives (e.g., get_team_matches) or when not to use it.

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

All Football Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.