Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_articles

Retrieve paginated FanDuel Research articles with metadata and filters by sport, team, author, or publish window to find predictions, picks, and prop-bet guides.

Instructions

FanDuel Research articles. Returns a page of FanDuel Research articles (predictions, picks, prop bets, guides), newest first, without their bodies: title, description, sport, author, publish time, link, thumbnail and tags. Filter by sport, sub-category (needs a sport; cannot be combined with a date window), team (needs a sport), author, hero type and publish window. Page with cursor while has_more is true; the service reports no total.

Input Schema

NameRequiredDescriptionDefault
teamNoA team's `number_fire_id` from the `sports` route (`sport` selects the list); needs `sport`. An id of another sport returns `400`
limitNoArticles per page, 1 to 50; default 20
sportNoSport or topic slug from the `sports` route; default all sports
authorNoAuthor id (a UUID) from the `authors` route
cursorNoContinue from the previous response's `next_cursor`
playerNoA player's `number_fire_id` (`subject.number_fire_id` of the `player-news` route); keeps articles about that player. An unknown id, or one of a different `sport`, returns `400`
hero_typeNoHero media: `IMAGE` or `JWPLAYER` (video)
sub_categoryNoTopic slug from the `sub-categories` route; needs `sport` and must belong to it
exclude_sportNoDrop these sports (repeat the parameter or comma-separate), same slugs as `sport`
published_afterNoEarliest publish time, RFC 3339 or `YYYY-MM-DD`
published_beforeNoLatest publish time, RFC 3339 or `YYYY-MM-DD`; not earlier than `published_after`
hide_deprioritizedNo`true` to hide content the site ranks down; it also reorders the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose ordering (newest first), body omission, cursor/has_more pagination, and that no total is reported — genuinely useful behavioral facts. It omits permission/auth expectations and any rate limits, and error behavior (400s) is only visible in the schema, leaving the disclosure solid but incomplete.

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?

Three dense sentences, zero filler: what it returns, what can be filtered, how to paginate. The most decision-relevant facts (newest first, no bodies, cursor paging) are front-loaded.

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?

For a 12-parameter, no-annotation, no-output-schema list tool, the description covers return fields, ordering, pagination semantics and filter interactions, with the remaining parameter detail fully documented in the schema. An agent has everything needed to call it and to interpret the response envelope.

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; the description earns above baseline by adding a cross-parameter constraint absent from the schema ('cannot be combined with a date window') and restating the sport-dependency of sub_category and team. It leaves author, player, hero_type, exclude_sport, limit and hide_deprioritized to the schema, which is acceptable given full coverage.

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 ('Returns a page of FanDuel Research articles') and immediately enumerates what is returned (title, description, sport, author, publish time, link, thumbnail, tags) while explicitly excluding bodies — which implicitly separates it from the sibling fanduel_research_article detail route. An agent can identify this as the list/index tool 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?

Gives concrete usage rules: filtering is described, and constraints are spelled out ('sub-category needs a sport; cannot be combined with a date window', 'team needs a sport'), plus pagination guidance ('Page with cursor while has_more is true'). It stops short of naming alternative tools (e.g. use fanduel_research_article for full text, or fans into team/author routes), so it is clear context without explicit alternatives.

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