DraftKings API

Pick6 target moves

get_pick6_line_history

Read-onlyIdempotent

Line history of one Pick6 prop: how its line moved, with line_move, multiplier_only and availability changes kept apart. pickable_id comes from get_pick6_projections. Send user_request with the current task in one sentence; it is saved to the account for 35 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pickable_id": "<pickable_id>",
      "user_request": "<user_request>"
    },
    "name": "get_pick6_line_history"
  }
}

Input Schema

Name	Required	Description
`stat`	No
`limit`	No
`cursor`	No	Use pagination.next_cursor unchanged. Every row is reachable and pages never skip or repeat a row under inserts. Cannot be combined with offset.
`change_type`	No
`pickable_id`	Yes
`user_request`	Yes	The current user task for this call, 3 to 500 characters in one sentence, close to their words. Required on every data call, including follow-ups and pagination. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.
`pick_group_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 5, 2026

changedInput schema / properties / user_request / description

Previous value: -"Optional. The task your user asked for, in one sentence. Never a filter and never required. Kept 35 days so the team can decide what to build. Leave out personal data and secrets."New value: +"The current user task for this call, 3 to 500 characters in one sentence, close to their words. Required on every data call, including follow-ups and pagination. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private."

addedInput schema / properties / user_request / minLength
```
Added value: +3
```

changedInput schema / required

Previous value: -[
-  "pickable_id"
-]New value: +[
+  "pickable_id",
+  "user_request"
+]

AddedNov 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: that change types are kept apart rather than merged, and that user_request is persisted to the account for 35 days and read by the team — a disclosure an agent could not infer from structured fields.

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?

Two sentences, front-loaded with the resource and scope, with no filler. The second sentence packs prerequisite and retention policy efficiently, though the retention detail is dense enough to slightly dilute the core purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter tool with no output schema and low schema coverage, the description covers the essentials (what it returns conceptually, where the ID comes from, the required user_request contract) but omits the semantics of stat, limit, and pick_group_id. An agent could call it, but not confidently tune those filters.

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 description coverage is only 29%, so the description must compensate, and it partially does: it explains pickable_id's source and the meaning of the change_type categories. It says nothing about stat, limit, or pick_group_id, leaving three of seven parameters undocumented in both places.

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 resource and scope: 'Line history of one Pick6 prop', and enumerates the change categories it separates (line_move, multiplier_only, availability). This distinguishes it from the broader get_pick6_history sibling, though it never names that sibling explicitly.

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 a concrete prerequisite by telling the agent where pickable_id comes from (get_pick6_projections), which is real usage guidance. However, it never states when to prefer this over get_pick6_history or get_pick6_stream_snapshot, so the routing decision 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.

All DraftKings API 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?