Football Data

Get Team Matches

get_team_matches

Read-onlyIdempotent

A team's matches across competitions. Filter by status, date range, competitions, season, or venue.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Cap matches returned (default 50)
`venue`	No	HOME \| AWAY
`season`	No	Season start year
`status`	No	Match status filter
`date_to`	No	YYYY-MM-DD
`team_id`	Yes	Numeric team ID
`date_from`	No	YYYY-MM-DD

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of matches returned
`matches`	Yes
`team_id`	Yes	Team ID queried

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "team_id": 64
+  },
+  {
+    "limit": 20,
+    "status": "FINISHED",
+    "team_id": 64,
+    "venue": "HOME"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "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 '-')",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "score_half_time": {
+            "description": "Half-time score (e.g., '1-0' or '-')",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "stage": {
+            "description": "Competition 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"
+    },
+    "team_id": {
+      "description": "Team ID queried",
+      "type": "number"
+    }
+  },
+  "required": [
+    "team_id",
+    "count",
+    "matches"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to reiterate safety. However, it adds no additional behavioral details such as pagination, rate limits, or data freshness, which would be helpful.

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?

Very concise – one sentence plus a filter list. Front-loaded with the core purpose. No wasted words.

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

Completeness3/5

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

Output schema exists, so return values are covered. However, the description mentions a 'competitions' filter not in the schema, creating confusion. The tool has 7 parameters and the description could address pagination limits (covered in schema) but is otherwise adequate for a read-only tool.

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 documents all parameters. The description adds no new parameter meaning and even mentions a nonexistent 'competitions' filter, which could mislead.

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 the tool retrieves a team's matches and lists filter options. However, it inaccurately mentions a 'competitions' filter that does not exist in the input schema, slightly undermining clarity.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like get_competition_matches. It lists filter options but does not explain context or when not to use this tool.

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.