Skip to main content
Glama

List Twitch profile videos

twitch_profile_videos_list
Read-only

List videos from a Twitch channel by handle. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoAlias for `sortBy`. Prefer `sortBy`.
trimNoIgnored if this tool does not support it.
urlsNoAlias for `handle`. Prefer `handle`.
userNoAlias for `handle`. Prefer `handle`.
limitNoIgnored if this tool does not support it.
handleNoTwitch handle to look up, with or without a leading @.
offsetNoIgnored if this tool does not support it.
sortByNoOptional sort order.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
filterByNoOptional filter for the type of Twitch videos to return. `archive`: full unedited past broadcasts (VODs). `highlight`: shorter clips curated/edited by the streamer from past broadcasts. `upload`: videos uploaded directly, not recorded from a live stream.
pageSizeNoIgnored if this tool does not support it.
userNameNoAlias for `handle`. Prefer `handle`.
usernameNoAlias for `handle`. Prefer `handle`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
maxResultsNoIgnored if this tool does not support it.
profileUrlNoAlias for `handle`. Prefer `handle`.
linkedinUrlNoAlias for `handle`. Prefer `handle`.
max_resultsNoIgnored if this tool does not support it.
screen_nameNoAlias for `handle`. Prefer `handle`.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / linkedinUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / linkedinUrl / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / profileUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / profileUrl / type
      Removed value: -"string"
    • addedInput schema / properties / screen_name / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / screen_name / type
      Removed value: -"string"
    • addedInput schema / properties / sort
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `sortBy`. Prefer `sortBy`."
      +}
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / urls
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `handle`. Prefer `handle`."
      +}
    • addedInput schema / properties / user / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / user / type
      Removed value: -"string"
    • addedInput schema / properties / userName / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / userName / type
      Removed value: -"string"
    • addedInput schema / properties / username / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / username / type
      Removed value: -"string"
  2. Changed2 schema fields changed
    • addedInput schema / properties / linkedinUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / profileUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • addedInput schema / properties / screen_name
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / user
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / userName
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / username
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle"
      -]New value: +[
      +  "handle",
      +  "context",
      +  "llm_model"
      +]
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed1 schema field changed
    • changedInput schema / properties / filterBy / description
      Previous value: -"Optional filter for video type."New value: +"Optional filter for the type of Twitch videos to return. `archive`: full unedited past broadcasts (VODs). `highlight`: shorter clips curated/edited by the streamer from past broadcasts. `upload`: videos uploaded directly, not recorded from a live stream."
  7. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  8. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value beyond annotations by stating that the result is a list and that cursor-based pagination should be used. This is useful behavioral context, though minimal.

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?

Two sentences with no filler. The tool's core action, resource, and return shape are front-loaded, and the pagination note is compact.

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 list tool with 20 parameters and no output schema, the description is minimal. It mentions cursor pagination, but no cursor parameter appears in the input schema, and it does not clarify which pagination parameters (limit, offset, pageSize, maxResults) are actually honored. This is a meaningful gap for correct invocation.

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 the schema already documents every parameter, including handle, sortBy, filterBy, and aliases. The description adds little beyond 'by handle' and pagination guidance, and the cursor mention does not map to any explicit cursor parameter in the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: 'List videos from a Twitch channel by handle.' It is clearly distinguishable from sibling tools like twitch_clip_get, twitch_profile_get, and twitch_profile_schedule_get, which are singular or about other profile aspects.

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 establishes a clear usage context: use when the user wants a channel's videos by handle. It does not explicitly name alternatives or exclusions, but the handle-by-list framing is sufficient for an agent to select it among the many profile/list siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.