Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

mlb_league_stats

Fetch ranked MLB league statistics and stat splits across both leagues by group, season, team, league, position, or player pool, with pagination.

Instructions

Get ranked MLB league statistics. Returns ranked MLB stat splits across both leagues. group is required (hitting, pitching, fielding, catching, running, game, team or streak). season defaults to the current year and stat_type to season. Narrow with league_id, team_id, position, player_pool, and page with limit (1 to 100) and offset (0 to 10000).

Input Schema

Name	Required	Description
`group`	Yes	Stat group
`limit`	No	Results to return (1-100)
`offset`	No	Zero-based result offset (0-10000)
`season`	No	Four-digit season; defaults to current year
`team_id`	No	Optional MLB team id; discover current team ids with mlb_teams
`end_date`	No	End date for byDateRange stat types; requires start_date
`position`	No	Hitter position; use only with group=hitting
`game_type`	No	MLB game type
`league_id`	No	MLB league id
`stat_type`	No	Stats API stat type; defaults to season
`start_date`	No	Start date for byDateRange stat types; requires end_date
`player_pool`	No	Qualified-player pool
`opponent_team_id`	No	Required by vsTeam stat types
`opponent_player_id`	No	Required by vsPlayer stat types

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.17.7Oct 1, 2026

addedInput schema / properties / end_date

Added value: +{
+  "description": "End date for byDateRange stat types; requires start_date",
+  "type": "string"
+}

addedInput schema / properties / game_type

Added value: +{
+  "description": "MLB game type",
+  "enum": [
+    "S",
+    "R",
+    "F",
+    "D",
+    "L",
+    "W",
+    "C",
+    "P",
+    "A",
+    "I",
+    "E"
+  ],
+  "type": "string"
+}

changedInput schema / properties / group / enum

Previous value: -[
-  "hitting",
-  "pitching",
-  "fielding"
-]New value: +[
+  "hitting",
+  "pitching",
+  "fielding",
+  "catching",
+  "running",
+  "game",
+  "team",
+  "streak"
+]

addedInput schema / properties / league_id

Added value: +{
+  "description": "MLB league id",
+  "enum": [
+    "103",
+    "104"
+  ],
+  "type": "string"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Zero-based result offset (0-10000)",
+  "type": "integer"
+}

addedInput schema / properties / opponent_player_id

Added value: +{
+  "description": "Required by vsPlayer stat types",
+  "type": "string"
+}

addedInput schema / properties / opponent_team_id

Added value: +{
+  "description": "Required by vsTeam stat types",
+  "type": "string"
+}

addedInput schema / properties / player_pool

Added value: +{
+  "description": "Qualified-player pool",
+  "enum": [
+    "QUALIFIED",
+    "ALL"
+  ],
+  "type": "string"
+}

addedInput schema / properties / position

Added value: +{
+  "description": "Hitter position; use only with group=hitting",
+  "enum": [
+    "C",
+    "1B",
+    "2B",
+    "3B",
+    "SS",
+    "LF",
+    "CF",
+    "RF",
+    "DH",
+    "OF",
+    "IF"
+  ],
+  "type": "string"
+}

addedInput schema / properties / start_date

Added value: +{
+  "description": "Start date for byDateRange stat types; requires end_date",
+  "type": "string"
+}

addedInput schema / properties / stat_type

Added value: +{
+  "description": "Stats API stat type; defaults to season",
+  "enum": [
+    "projected",
+    "projectedRos",
+    "yearByYear",
+    "yearByYearAdvanced",
+    "yearByYearPlayoffs",
+    "season",
+    "standard",
+    "advanced",
+    "career",
+    "careerRegularSeason",
+    "careerAdvanced",
+    "seasonAdvanced",
+    "careerStatSplits",
+    "careerPlayoffs",
+    "gameLog",
+    "playLog",
+    "pitchLog",
+    "pitchArsenal",
+    "outsAboveAverage",
+    "expectedStatistics",
+    "sabermetrics",
+    "sprayChart",
+    "tracking",
+    "vsPlayer",
+    "vsPlayerTotal",
+    "vsPlayer5Y",
+    "vsTeam",
+    "vsTeam5Y",
+    "vsTeamTotal",
+    "lastXGames",
+    "byDateRange",
+    "byDateRangeAdvanced",
+    "byMonth",
+    "byMonthPlayoffs",
+    "byDayOfWeek",
+    "byDayOfWeekPlayoffs",
+    "homeAndAway",
+    "homeAndAwayPlayoffs",
+    "winLoss",
+    "winLossPlayoffs",
+    "rankings",
+    "rankingsByYear",
+    "statsSingleSeason",
+    "statsSingleSeasonAdvanced",
+    "hotColdZones",
+    "availableStats",
+    "opponentsFaced",
+    "gameTypeStats",
+    "firstYearStats",
+    "lastYearStats",
+    "statSplits",
+    "statSplitsAdvanced",
+    "atGameStart",
+    "vsOpponents",
+    "sabermetricsMultiTeam",
+    "projected_Zips",
+    "projected_ZipsRos",
+    "projected_Zips2YR",
+    "projected_Zips3YR"
+  ],
+  "type": "string"
+}

addedInput schema / properties / team_id

Added value: +{
+  "description": "Optional MLB team id; discover current team ids with mlb_teams",
+  "type": "string"
+}

Changed1 schema field changedv1.17.5Sep 26, 2026
- addedInput schema / properties / group / enum
```
Added value: +[
+  "hitting",
+  "pitching",
+  "fielding"
+]
```
AddedAug 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the required param, the season/stat_type defaults, and pagination bounds, but says nothing about read-only nature, permissions, rate limits, or what 'ranked' output actually contains for a 14-param tool.

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?

Front-loads the purpose before enumerating constraints, and stays compact at four sentences. Slightly wasteful in re-listing the group enum values that the schema already enumerates, but overall tight and well-ordered.

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?

For a 14-parameter, no-annotation, no-output-schema tool the description covers purpose, the required field, defaults, and paging, but omits behavioral context such as read-only status, conditional param relationships (start_date/end_date, opponent ids), and response shape. Adequate but with clear gaps.

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 the schema already documents every parameter and enum. The description mostly restates that content (group values, defaults, limit/offset ranges) and adds marginal framing by calling league_id/team_id/position/player_pool 'narrows'. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Get ranked MLB league statistics') and clarifies scope ('ranked stat splits across both leagues'), which separates it from team- and player-level siblings. It never names an alternative (e.g., mlb_team_stats), so differentiation is implied rather than explicit.

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?

No when-to-use / when-not-to-use guidance. The 'Narrow with league_id, team_id...' sentence describes filters, not the conditions under which this tool should be chosen over mlb_league_leaders or mlb_team_stats. Usage is left entirely to inference.

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

Deploy Server

mlb_league_stats

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools