StrikerAPI

Player props

get_player_props

Read-onlyIdempotent

Use for player prop lines by sportsbook: the anytime goalscorer price (Yes in over_odds, No in under_odds where posted, no line) and, for the top five leagues, MLS and the Champions League, shots on target, shots and assists over/unders (most books post only the over), from DraftKings, FanDuel, William Hill and Pinnacle as the archive holds them. Pass game_id for every player's props in one game, or player_id with from_date (and to_date) for one player across games (up to 100). A game costs 10 credits before it starts and 20 once it has (accounts opened before October 30 2026 pay 10 for every game). Returns the closing line by default (the last before the game starts) or the opening line, with each book's over and under prices. Each row has captured_at, scheduled_start and minutes_before_scheduled_start (negative when captured after the scheduled start); a row is kept when it was captured before the sportsbooks' listed start, which in the NBA is usually about 10 minutes after the scheduled one, so filter on minutes_before_scheduled_start > 0 for a strictly before-schedule backtest. Outside football the archive mostly holds one pre-game capture per line, so the opening and closing lines are usually the same; the opening line differs only where a second capture was taken (live capture from October 2026, and wherever else it is held). Set estimate_only to get the price without being charged. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Input Schema

Name	Required	Description
`league`	No	League. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl.
`market`	No	One market: player_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists)
`game_id`	No	Game id: every player's props for that game.
`to_date`	No	With player_id: last date (default: no end), YYYY-MM-DD (the game's date).
`bookmaker`	No	Bookmaker key, e.g. draftkings, fanduel, pinnacle.
`from_date`	No	With player_id: first date, YYYY-MM-DD (the game's date).
`player_id`	No	Player id (e.g. 280555) from search_players. With from_date: that player's props across games.
`estimate_only`	No	Return what this call would cost, without charging or running it.
`snapshot_type`	No	closing (default): the last line before the game starts. opening: the first one captured, which is the same capture as the close wherever only one was taken.

Output Schema

Name	Required	Description	Default
`note`	No
`tool`	No
`count`	No
`games`	No
`props`	No
`credits`	No
`estimate_only`	No
`snapshot_type`	No
`next_from_date`	No
`credits_per_game`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

changedInput schema / properties / market / description

Previous value: -"One market: player_goal_scorer_anytime (anytime goalscorer (over = scores))"New value: +"One market: player_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists)"

changedInput schema / properties / market / enum

Previous value: -[
-  "player_goal_scorer_anytime"
-]New value: +[
+  "player_goal_scorer_anytime",
+  "player_shots_on_target",
+  "player_shots",
+  "player_assists"
+]

Changed2 schema fields changedOct 27, 2026
- addedOutput schema / properties / props / items / properties / minutes_before_scheduled_start
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / props / items / properties / scheduled_start
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / snapshot_type / description

Previous value: -"closing (default): the last line before the game starts. opening: the first one captured."New value: +"closing (default): the last line before the game starts. opening: the first one captured, which is the same capture as the close wherever only one was taken."

First observedOct 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: credit pricing (10 before game start, 20 after, with a legacy-account exception), closing-vs-opening snapshot behavior, capture-time fields, and the caveat about NBA listed start times. It also explains that outside football the archive usually has one pre-game capture, so opening and closing lines often match. The policy constraint around not calculating stakes or recommending bets is explicitly stated.

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 front-loaded and information-dense, and nearly every sentence carries operational value for a complex 9-parameter tool with pricing and capture semantics. It is still a single long paragraph with several caveats packed together, which makes it less scannable than it could be.

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?

Given the tool's complexity, the description is complete enough to call it correctly: it covers market coverage, bookmakers, parameter selection, pricing, snapshot defaults, capture-time backtest filtering, and market-information constraints. An output schema exists, but the description still helpfully explains return shape and line semantics.

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

Parameters5/5

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

Schema coverage is already 100%, but the description still adds meaningful semantics: game_id returns every player's props for one game, player_id plus from_date/to_date returns one player across games with a 100-row cap, and snapshot_type defaults to closing with opening defined as the first captured line. It also clarifies market-specific encoding, such as Yes in over_odds and No in under_odds for anytime goalscorer.

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 states a specific resource and scope: player prop lines by sportsbook, with named markets, bookmakers, and league coverage. It is unmistakably about player props, but it does not explicitly distinguish itself from related siblings such as get_prop_history, get_odds, or get_market_odds.

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 clearly explains how to query: game_id for every player's props in one game, or player_id with from_date and to_date for one player across games, up to 100. It also notes estimate_only as a no-charge dry run. It does not, however, state when to prefer this over related sibling tools.

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