Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fanduel_sportsbook_promotions

Lists public FanDuel Sportsbook promotions for a chosen state and page, including tags, offer links, end times, artwork, and carousel order so you can discover and compare offers.

Instructions

FanDuel Sportsbook promotions. Lists the public promotions the Sportsbook shows to an anonymous visitor on its homepage, a league page or a sport page, with each promotion's tags, offer link, end time and artwork, and the carousel placement that orders them. Offers differ by state and by page. tags is the census of promotion tags on the page and is always unfiltered, so valid tag values are discoverable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fanduel_sportsbook_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoKeep only promotions with one of these tags (repeat the parameter or comma-separate), for example `nfl` or `basketball`; valid tags are listed in the response `tags`
stateNoMarket to query (offers differ by state); default nj
contextNoWhich page's promotions: `home` (default), `league` or `sport`
event_type_idNoSport id, required for `context=sport`: 6423 American Football; 1 Soccer; 7522 Basketball; 3 Golf; 7511 Baseball; 7524 Ice Hockey; 2 Tennis; 26420387 Mixed Martial Arts; 2593174 Table Tennis; 3503 Darts; 6 Boxing; 5 Rugby Union; 4 Cricket; 8 Motor Sport; 1477 Rugby League; 6422 Snooker; 468328 Handball; 28608997 Lacrosse; 998917 Volleyball, 4726642 Surfing, 10 Special Bets and 2378961 Politics; availability differs by market (Volleyball is also offered in NJ, PA, CO and AZ), and a sport a market does not offer returns 404
custom_page_idNoLeague page id, required for `context=league` (for example `nfl`)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it makes clear this is a public, anonymous-visitor read of promotions, that results vary by market and page, and that the `tags` field is an unfiltered census used for discoverability of `tag` values. It does not state pagination behavior or note that unavailable sports return 404 (left to the schema), so it is not fully exhaustive.

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?

Three sentences, front-loaded with the resource and scope, and the state/page and tag-discovery caveats are placed sensibly. The opening fragment 'FanDuel Sportsbook promotions.' is slightly redundant with the tool name, keeping this below a perfect score.

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?

There is no output schema, so the description must explain return content, and it does: each promotion's tags, offer link, end time, artwork, and carousel placement ordering. Combined with the state/page variability notes, an agent has enough to call this correctly.

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 coverage is 100%, with enums and defaults already documented, so the baseline is 3. The description adds a little meaning by clarifying that `tags` is an unfiltered census of the page and that valid `tag` values come from the response, but it largely restates the state/page dependency already present in the schema.

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 verb and resource ('Lists the public promotions the Sportsbook shows') and scopes it to anonymous visitors across homepage, league and sport pages. The sibling tool names in this cluster are almost entirely event/odds/team oriented, so this is clearly distinguishable without opening the schema.

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?

Clearly conveys when this tool applies: public promotions per state and per page context, with the caveat that offers differ by state and page. It does not explicitly say when not to use it or name a specific alternative sibling, but for a distinct promotions endpoint the context is sufficient.

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

Deploy Server

Other Tools