Skip to main content
Glama

List giveaway entrants

giveaways_list_entrants
Read-only

List all users who joined a StreamElements giveaway and their ticket counts by giveaway ID to audit entries or pick winners.

Instructions

List the users who joined a giveaway and their tickets.

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": {
      "giveawayId": "<giveawayId>"
    },
    "name": "giveaways_list_entrants"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.
giveawayIdYesGiveaway id (24-character hex id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that entrants are returned with ticket counts, but says nothing about pagination, ordering, or whether a closed/completed giveaway still yields entrants. With annotations carrying the safety burden, this is adequate but thin.

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?

A single tight sentence with zero filler and the core action front-loaded. It is efficient, though it errs toward under-specification rather than being maximally informative.

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 two-parameter read tool with no output schema, the description is minimally sufficient but omits return shape details (user identifiers, ticket counts, pagination) that would let an agent use the result without surprises. Nothing contradicts the annotations, but more could be said.

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 100%, so both parameters (channel, giveawayId) including the hex id format and the channel default are fully documented in the schema. The description adds no format or fallback detail beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb and resource (list the users who joined a giveaway) plus the payload (their tickets), which cleanly separates it from giveaways_list (which enumerates giveaways) and giveaways_get. It does not explicitly name or route against those siblings, so it falls short of 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 Guidelines2/5

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

There is no guidance on when to fetch entrants versus pulling the giveaway itself, nor any prerequisite such as the giveaway needing to exist or be in a specific state. The agent must infer usage entirely from the name and schema.

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