Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_quick_picks_daily

Retrieve paginated FanDuel Research Quick Picks Daily clip metadata from Omny Studio to review episode links, RSS status, and publish dates; follow the returned cursor for additional pages.

Instructions

FanDuel Research Quick Picks Daily episode archive. Returns one page of public Quick Picks Daily program clip metadata from Omny Studio's read-only Consumer API. Follow next_cursor to continue; use in_rss_playlist to distinguish clips in the default podcast feed and published_at to judge freshness. The endpoint returns listening-page links and metadata, not audio files.

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor from a previous response's `data.next_cursor`; omit for the first page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description does real work: it declares the endpoint is read-only ('read-only Consumer API'), explains pagination semantics via cursor, and explicitly clarifies that it returns listening-page links and metadata, not audio files. It doesn't state page size or rate limits, but the key behavioural gaps are covered.

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?

Four tight sentences, front-loaded with what the tool is, then pagination, then field interpretation, then a clarifying negative about audio files. Nothing repeats and every sentence earns its place.

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?

With no output schema and no annotations, the description carries the burden well: it describes the return content, the pagination mechanism, and the interpretation of key fields. Minor gaps remain (page size, whether results are ordered, freshness window), so it is strong but not exhaustive.

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 already 100% for the single `cursor` param, so the baseline is 3. The description goes further by explaining that the cursor comes from the prior response's `next_cursor` and that following it is how you continue — adding cross-field semantics the schema alone doesn't convey.

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?

The description names a specific verb and resource: it returns one page of public Quick Picks Daily clip metadata from Omny Studio's Consumer API. An agent knows exactly what it gets. It doesn't explicitly differentiate itself from podcast-ish siblings like apple_podcasts_show_episodes or the other fanduel_research_* tools, which keeps it from a 5.

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

Usage Guidelines3/5

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

It gives operational guidance — follow `next_cursor` to continue, use `in_rss_playlist` to tell feed clips apart, and `published_at` to judge freshness — which tells the agent how to interpret results. What's missing is when to choose this over the neighbouring fanduel_research_articles or fanduel_research tool; sibling routing is left 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

Other Tools