Skip to main content
Glama
proplineapi

PropLine

Official

propline_get_odds

Fetch live odds for sports events, with bulk game lines or per-event props, across 13 books and multiple markets.

Instructions

Get live odds. If event_id is supplied, returns full per-event props for that event; otherwise returns bulk game-line odds for the whole sport. Pass markets as a comma-separated list (e.g. 'h2h,spreads,totals' or 'player_points,player_rebounds'). Response includes a bookmakers[] array across every book that carries the requested markets (currently up to 13: Bovada, DraftKings, FanDuel, Pinnacle, BetMGM, BetRivers, Unibet, Underdog, PrizePicks, Kalshi, Polymarket, Matchbook, Smarkets — coverage varies by sport).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sport_keyYes
event_idNoOptional. If set, returns props for this event.
marketsNoComma-separated market keys. Defaults to h2h on bulk; h2h,spreads,totals on event. Pass an explicit list to fetch player props (sport-specific — e.g. player_points,player_rebounds for NBA; pitcher_strikeouts,batter_home_runs for MLB).
bookmakersNoComma-separated subset of book keys (bovada, draftkings, fanduel, pinnacle, betmgm, betrivers, unibet, underdog, prizepicks, kalshi, polymarket, matchbook, smarkets). Default returns all available.

Implementation Reference

  • The handler for 'propline_get_odds' which calls client().getOdds() with the sport_key, event_id, markets, and bookmakers arguments.
    handler: (args) =>
      client().getOdds(args.sport_key as string, {
        eventId: args.event_id as string | number | undefined,
        markets: args.markets as string | undefined,
        bookmakers: args.bookmakers as string | undefined,
      }),
  • src/index.ts:131-171 (registration)
    The tool definition/registration for 'propline_get_odds' in the tools array, including its name, description, input schema, and handler.
    {
      name: "propline_get_odds",
      description:
        "Get live odds. If event_id is supplied, returns full per-event " +
        "props for that event; otherwise returns bulk game-line odds for " +
        "the whole sport. Pass markets as a comma-separated list (e.g. " +
        "'h2h,spreads,totals' or 'player_points,player_rebounds'). " +
        "Response includes a bookmakers[] array across every book that " +
        "carries the requested markets (currently up to 13: Bovada, " +
        "DraftKings, FanDuel, Pinnacle, BetMGM, BetRivers, Unibet, " +
        "Underdog, PrizePicks, Kalshi, Polymarket, Matchbook, Smarkets " +
        "— coverage varies by sport).",
      inputSchema: {
        type: "object",
        properties: {
          sport_key: { type: "string" },
          event_id: {
            type: ["string", "number"],
            description: "Optional. If set, returns props for this event.",
          },
          markets: {
            type: "string",
            description:
              "Comma-separated market keys. Defaults to h2h on bulk; h2h,spreads,totals on event. Pass an explicit list to fetch player props (sport-specific — e.g. player_points,player_rebounds for NBA; pitcher_strikeouts,batter_home_runs for MLB).",
          },
          bookmakers: {
            type: "string",
            description:
              "Comma-separated subset of book keys (bovada, draftkings, fanduel, pinnacle, betmgm, betrivers, unibet, underdog, prizepicks, kalshi, polymarket, matchbook, smarkets). Default returns all available.",
          },
        },
        required: ["sport_key"],
        additionalProperties: false,
      },
      handler: (args) =>
        client().getOdds(args.sport_key as string, {
          eventId: args.event_id as string | number | undefined,
          markets: args.markets as string | undefined,
          bookmakers: args.bookmakers as string | undefined,
        }),
    },
  • src/index.ts:67-164 (registration)
    The tools array (ToolDef[]) that contains all tool definitions including 'propline_get_odds'.
    const tools: ToolDef[] = [
      {
        name: "propline_list_sports",
        description:
          "List all sports PropLine currently polls. Returns sport keys " +
          "(e.g. baseball_mlb, basketball_nba, soccer_epl) along with human " +
          "titles and active status. Use this first to discover what " +
          "sport_key values are valid for the other tools.",
        inputSchema: {
          type: "object",
          properties: {},
          additionalProperties: false,
        },
        handler: () => client().listSports(),
      },
      {
        name: "propline_list_events",
        description:
          "List upcoming events for a sport. Returns each event's id, " +
          "home_team, away_team, commence_time. Use the returned event_id " +
          "to drill into per-event odds, props, +EV, or results.",
        inputSchema: {
          type: "object",
          properties: {
            sport_key: {
              type: "string",
              description:
                "Sport key from propline_list_sports — e.g. baseball_mlb, basketball_nba",
            },
            live: {
              type: "boolean",
              description:
                "If true, only return in-progress (live) events. Defaults to false.",
            },
          },
          required: ["sport_key"],
          additionalProperties: false,
        },
        handler: (args) =>
          client().listEvents(args.sport_key as string, {
            live: args.live as boolean | undefined,
          }),
      },
      {
        name: "propline_list_event_markets",
        description:
          "List the market types available for a specific event (e.g. h2h, " +
          "spreads, totals, player_points, pitcher_strikeouts). Useful when " +
          "you don't know which prop markets a given event carries.",
        inputSchema: {
          type: "object",
          properties: {
            sport_key: { type: "string" },
            event_id: { type: ["string", "number"] },
          },
          required: ["sport_key", "event_id"],
          additionalProperties: false,
        },
        handler: (args) =>
          client().listEventMarkets(
            args.sport_key as string,
            args.event_id as string | number,
          ),
      },
      {
        name: "propline_get_odds",
        description:
          "Get live odds. If event_id is supplied, returns full per-event " +
          "props for that event; otherwise returns bulk game-line odds for " +
          "the whole sport. Pass markets as a comma-separated list (e.g. " +
          "'h2h,spreads,totals' or 'player_points,player_rebounds'). " +
          "Response includes a bookmakers[] array across every book that " +
          "carries the requested markets (currently up to 13: Bovada, " +
          "DraftKings, FanDuel, Pinnacle, BetMGM, BetRivers, Unibet, " +
          "Underdog, PrizePicks, Kalshi, Polymarket, Matchbook, Smarkets " +
          "— coverage varies by sport).",
        inputSchema: {
          type: "object",
          properties: {
            sport_key: { type: "string" },
            event_id: {
              type: ["string", "number"],
              description: "Optional. If set, returns props for this event.",
            },
            markets: {
              type: "string",
              description:
                "Comma-separated market keys. Defaults to h2h on bulk; h2h,spreads,totals on event. Pass an explicit list to fetch player props (sport-specific — e.g. player_points,player_rebounds for NBA; pitcher_strikeouts,batter_home_runs for MLB).",
            },
            bookmakers: {
              type: "string",
              description:
                "Comma-separated subset of book keys (bovada, draftkings, fanduel, pinnacle, betmgm, betrivers, unibet, underdog, prizepicks, kalshi, polymarket, matchbook, smarkets). Default returns all available.",
            },
          },
          required: ["sport_key"],
          additionalProperties: false,
        },
  • The client.getOdds() method that makes the actual HTTP request. If eventId is provided, hits /v1/sports/{sportKey}/events/{eventId}/odds; otherwise hits /v1/sports/{sportKey}/odds with markets and bookmakers query params.
    getOdds(
      sportKey: string,
      opts: {
        markets?: string;
        bookmakers?: string;
        eventId?: string | number;
      } = {},
    ): Promise<unknown> {
      if (opts.eventId) {
        return this.request(
          `/v1/sports/${sportKey}/events/${opts.eventId}/odds`,
          {
            markets: opts.markets,
            bookmakers: opts.bookmakers,
          },
        );
      }
      return this.request(`/v1/sports/${sportKey}/odds`, {
        markets: opts.markets,
        bookmakers: opts.bookmakers,
      });
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the response includes a bookmakers[] array with up to 13 books, that coverage varies by sport, and how parameters affect behavior. It lacks details on authentication or rate limits, but the core behavior is well 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?

The description is concise (5 sentences), front-loaded with the core action, and each sentence adds necessary detail without redundancy. It is well-structured and easy to parse.

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?

For a tool with 4 parameters and no output schema, the description adequately covers the main behaviors and response structure. It could mention error handling or supported sports, but the essentials are present.

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 75%, and the description adds value beyond schema descriptions by providing examples (e.g., 'h2h,spreads,totals' for markets) and explaining default behaviors for event_id and markets. The parameters are well explained in combination.

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 'Get live odds' and distinguishes two modes based on event_id: full per-event props when event_id supplied, bulk game-line odds otherwise. It is specific and actionable, differentiating from siblings by naming the resource (odds) and behavior.

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?

The description provides clear guidance on when to use the tool with or without event_id, and how to specify markets and bookmakers. It does not explicitly contrast with sibling tools, but the context is sufficient for common use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/proplineapi/propline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server