league-loom

Get Trending Players (platform-wide adds/drops)

fantasy_get_trending_players

Read-onlyIdempotent

The most-added or most-dropped players across the whole platform right now ("who's trending", "who's everyone dropping"). Sleeper platform-wide data ONLY — not league-specific and not availability-aware, so for anything you could actually add in YOUR league use fantasy_get_available_players instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max players (1-100).
`sport`	Yes	Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups.
`provider`	No	Fantasy platform. Optional: defaults to your connected platform ('sleeper').
`direction`	No	'add' = most added, 'drop' = most dropped.	add
`credentials`	No	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.
`lookback_hours`	No	Lookback window in hours (default 24).
`response_format`	No	'markdown' (default) or 'json' (raw payload).	markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 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 / 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 / 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 / required

Previous value: -[
-  "provider",
-  "sport"
-]New value: +[
+  "sport"
+]

First observedJun 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it emphasizes that the data is platform-wide, not league-specific, and not availability-aware, which prevents misuse. It also clarifies that Sleeper data is the default and that the tool is not for league-specific actions. This goes beyond the annotations without contradicting them.

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 two sentences long, front-loaded with the core purpose, and includes a clear exclusion and alternative. Every sentence earns its place, and there is no redundant information.

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?

Given the tool's complexity (7 parameters, 1 required, 3 enums, nested credentials object) and the absence of an output schema, the description is quite complete. It covers the core behavior, the key limitation (not availability-aware), and the alternative. It doesn't describe the return format, but the response_format parameter handles that, and the description's focus on usage guidance is appropriate. A 4 is warranted because the description could have added a bit more about the output structure, but it is largely sufficient.

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 description coverage is 100%, so the schema already documents all parameters. The description adds context by explaining the meaning of 'trending' (platform-wide adds/drops) and by clarifying the distinction between this tool and fantasy_get_available_players, which helps an agent understand the 'direction' and 'provider' parameters. However, it doesn't add much detail beyond the schema for individual parameters, so a 4 is appropriate rather than a 5.

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?

The description clearly states the tool's function: retrieving the most-added or most-dropped players platform-wide. It uses specific verbs ('most-added or most-dropped') and a clear resource ('players across the whole platform right now'), and it explicitly distinguishes itself from fantasy_get_available_players, which is a sibling tool. The title and description align well.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('who's trending', 'who's everyone dropping') and when not to use it ('not league-specific and not availability-aware'), and it names the alternative tool (fantasy_get_available_players) for league-specific, availability-aware needs. This is clear, actionable guidance.

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?