StrikerAPI

Lineups

get_lineups

Read-onlyIdempotent

Use for a match's lineups: each club's formation, starting XI with positions and formation slots, the substitutes used with the minute they came on (and who went off when), and the unused bench. Before kick-off it returns the club-confirmed team sheet (source live) from about an hour before the match; until clubs publish, lineups is empty with a note and nothing is charged. Costs 5 credits.

Input Schema

Name	Required	Description	Default
`league`	No	League. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
`game_id`	Yes	Match id, from list_games or get_schedule.

Output Schema

Name	Required	Description	Default
`game`	Yes
`note`	No
`source`	No
`lineups`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / game_id / description

Previous value: -"ESPN match id, from list_games or get_schedule."New value: +"Match id, from list_games or get_schedule."

changedOutput schema / properties / source / enum

Previous value: -[
-  "espn_live",
-  "none"
-]New value: +[
+  "live",
+  "none"
+]

Changed2 schema fields changedOct 17, 2026

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / source

Added value: +{
+  "enum": [
+    "espn_live",
+    "none"
+  ],
+  "type": "string"
+}

First observedOct 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the read-only annotations: it discloses the 5-credit cost, the club-confirmed live source, the pre-match timing window, and that nothing is charged when lineups are empty. This is exactly the kind of operational context an agent needs before invoking the tool.

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 front-loaded with the resource and returned contents, then moves to timing and cost without wasted sentences. Every sentence adds useful information for invocation.

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

Completeness5/5

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

With an output schema present and full parameter coverage, the description still supplies the key operational facts: what is returned, when it is available, what happens before publication, and the credit cost. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so both game_id and league are fully documented in the schema. The description mentions the match context implicitly but does not add meaning beyond the schema for either parameter.

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 identifies the resource and its specific contents: each club's formation, starting XI, substitutes, and unused bench. It is unambiguous against siblings like get_game or get_events, though it does not explicitly name an alternative tool.

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

Usage Guidelines4/5

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

It provides clear context for when to use the tool, including pre-kick-off behavior from about an hour before the match and the empty response before clubs publish. It does not state when to use a different sibling tool instead.

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

All StrikerAPI 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.