League Loom

Get Recent League Transactions

fantasy_get_transactions

Read-onlyIdempotent

Recent league moves (adds, drops, waiver claims, trades), newest first: "did my waiver claim go through?", "what trades happened?". Sleeper: per week, with FAAB bids. ESPN: activity feed (trade legs may be partial). Fantrax: publicly viewable leagues, or with a saved session cookie.

Input Schema

Name	Required	Description	Default
`week`	No	Week/scoring period (Sleeper defaults to current).
`limit`	No	Max transactions.
`sport`	No	e.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups.
`types`	No	Filter to these types. Omit for all.
`season`	No	Season year, e.g. 2025; ignored by Fantrax.
`provider`	No	Fantasy platform. Optional: defaults to your connected platform ('sleeper').
`league_id`	No	Omit when connected. League id (Fantrax also takes the league URL).
`credentials`	No	Only WITHOUT a connected profile: secret_id (Fantrax), espn_s2 + swid (private ESPN), username or user_id (Sleeper discovery). Public ESPN and Sleeper reads need none.
`league_query`	No	A connected league's name/id; omit to auto-pick (primary first). Never ask for ids.
`response_format`	No	'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload).	markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026

changedInput schema / properties / credentials / additionalProperties
```
Previous value: -trueNew value: +{}
```

changedInput schema / properties / season / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]

addedInput schema / properties / week / maximum
```
Added value: +9007199254740991
```

Changed7 schema fields changedSep 29, 2026

changedInput schema / properties / credentials / description

Previous value: -"Per-call credentials, only needed WITHOUT a connected profile. Keys: secret_id (Fantrax); espn_s2 + swid (private ESPN leagues); username or user_id (Sleeper discovery); session_cookie / auth_token + write_enabled:true (explicit write opt-in only). Public ESPN leagues and all Sleeper reads need none."New value: +"Only WITHOUT a connected profile: secret_id (Fantrax), espn_s2 + swid (private ESPN), username or user_id (Sleeper discovery). Public ESPN and Sleeper reads need none."

changedInput schema / properties / league_id / description

Previous value: -"The platform's league id (Fantrax also accepts the full league URL)."New value: +"Omit when connected. League id (Fantrax also takes the league URL)."

changedInput schema / properties / league_query / description

Previous value: -"League name/id filter, for when the profile has several leagues on the provider."New value: +"A connected league's name/id; omit to auto-pick (primary first). Never ask for ids."

changedInput schema / properties / limit / description

Previous value: -"Max transactions, newest first (1-100)."New value: +"Max transactions."

changedInput schema / properties / response_format / description

Previous value: -"'markdown' (default) or 'json' (raw payload)."New value: +"'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload)."

changedInput schema / properties / season / description

Previous value: -"Season year, e.g. 2025. Required for ESPN/Sleeper league discovery; ignored by Fantrax."New value: +"Season year, e.g. 2025; ignored by Fantrax."

changedInput schema / properties / sport / description

Previous value: -"Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups."New value: +"e.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups."

Changed16 schema fields changedSep 10, 2026

changedInput schema / properties / credentials / additionalProperties
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / credentials / description

Previous value: -"Per-call credentials. Fill only the keys your provider needs (see fantasy_list_providers). Public ESPN leagues and all Sleeper reads need none."New value: +"Per-call credentials, only needed WITHOUT a connected profile. Keys: secret_id (Fantrax); espn_s2 + swid (private ESPN leagues); username or user_id (Sleeper discovery); session_cookie / auth_token + write_enabled:true (explicit write opt-in only). Public ESPN leagues and all Sleeper reads need none."

removedInput schema / properties / credentials / properties / espn_s2

Removed value: -{
-  "description": "ESPN private-league cookie 'espn_s2' (DevTools → Application → Cookies → espn.com).",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / secret_id

Removed value: -{
-  "description": "Fantrax Secret ID (User Profile → 'Your Secret ID').",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / swid

Removed value: -{
-  "description": "ESPN private-league cookie 'SWID': a GUID in curly braces, e.g. {XXXX-...}.",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / user_id

Removed value: -{
-  "description": "Sleeper numeric user_id (alternative to username).",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / username

Removed value: -{
-  "description": "Sleeper username (for league discovery).",
-  "type": "string"
-}

changedInput schema / properties / league_id / description

Previous value: -"The league id from the platform. For Fantrax, a full league URL is also accepted and the server extracts the id."New value: +"The platform's league id (Fantrax also accepts the full league URL)."

changedInput schema / properties / league_query / description

Previous value: -"Optional profile league name/id filter. Use when the profile has multiple leagues for the provider."New value: +"League name/id filter, for when the profile has several leagues on the provider."

changedInput schema / properties / provider / description

Previous value: -"Fantasy platform: 'fantrax', 'espn', or 'sleeper'. Call fantasy_list_providers first to see each provider's capabilities and required credentials."New value: +"Fantasy platform. Optional: defaults to your connected platform ('sleeper')."

changedInput schema / properties / response_format / description

Previous value: -"Output format: 'markdown' (default, human-readable) or 'json' (raw upstream payload)."New value: +"'markdown' (default) or 'json' (raw payload)."

changedInput schema / properties / season / description

Previous value: -"Season year, e.g. 2024. REQUIRED for espn and sleeper league discovery; ignored by fantrax."New value: +"Season year, e.g. 2025. Required for ESPN/Sleeper league discovery; ignored by Fantrax."

changedInput schema / properties / sport / description

Previous value: -"Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and for Fantrax player/name lookups."New value: +"Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups."

changedInput schema / properties / types / description

Previous value: -"Filter to these transaction types. Omit for all."New value: +"Filter to these types. Omit for all."

changedInput schema / properties / week / description

Previous value: -"Week/scoring period. Sleeper requires a week (defaults to current). ESPN/Fantrax return recent moves regardless."New value: +"Week/scoring period (Sleeper defaults to current)."

removedInput schema / required
```
Removed value: -[
-  "provider"
-]
```

First observedJun 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses per-provider behavior: Sleeper returns per-week results with FAAB bids, ESPN returns an activity feed where trade legs 'may be partial', and Fantrax requires a publicly viewable league or a saved session cookie — real auth and data-completeness caveats an agent needs. The partial-data warning is especially valuable since it changes how results should be reported.

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-loaded with the resource and its contents, followed by use-case questions, then terse provider notes — the ordering is right and there is no filler. The provider notes are compressed to near-telegraphic fragments ('Sleeper: per week, with FAAB bids'), which is efficient but slightly harder to parse than full sentences.

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?

For a 10-parameter, zero-required read tool with no output schema, the description covers the main risk areas: provider variance, auth requirements, partial ESPN trade legs, and result ordering. It leaves the return structure largely unstated and doesn't mention the limit/response_format knobs, which the schema carries but the agent may want framed in terms of output shape.

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%, so the baseline is 3, but the description adds provider-specific parameter semantics: 'week' is meaningful per-week on Sleeper while 'season' is ignored by Fantrax, and 'types' is echoed by the listed moves. It still says nothing about 'limit' or 'response_format' beyond what the schema states.

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?

States a specific resource ('recent league moves') with an explicit enumeration of what's included (adds, drops, waiver claims, trades) and the ordering ('newest first'). No sibling tool overlaps this surface — fantasy_analyze_trade evaluates a trade, fantasy_get_my_players lists a roster — so an agent can select it without ambiguity.

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?

The two quoted user questions ('did my waiver claim go through?', 'what trades happened?') give concrete use contexts that map directly to the tool. It stops short of explicit exclusions or pointing to alternatives such as fantasy_analyze_trade for evaluating rather than listing trades, so it falls short of a 5.

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

All League Loom 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.

Resources

Need Help?