Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitch profile schedule

twitch_profile_schedule_get
Read-onlyIdempotent

Retrieve the stream schedule for a Twitch channel by handle, so you can check upcoming broadcast times and plan viewing.

Instructions

Get the stream schedule for a Twitch channel by handle. Requires handle.

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitch_profile_schedule_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Twitch handle to look up, with or without a leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
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. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — not what the schedule contains (recurring weekly slots vs upcoming broadcasts), nor whether it includes timezone or live status. For a read tool the bar is lower, but the description contributes essentially zero behavioral context.

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 short sentences, front-loaded with the purpose, with no wasted framing. The second sentence is largely redundant with the schema's required-field marker, which keeps it from a 5.

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?

This is a simple read-only lookup with a fully documented four-parameter schema and no output schema to explain, so the description does not need to be elaborate. The only real gap is what 'schedule' returns, but the essential call contract is complete.

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 handle, context, llm_model and conversation_id are all documented in the schema itself. The description only repeats the handle requirement (including the schema's '@-optional' detail nowhere beyond the schema), so the baseline 3 applies with no added meaning.

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 — 'Get the stream schedule for a Twitch channel' — which is clearly distinct from a plain profile lookup. It does not explicitly distinguish itself from siblings like twitch_profile_get or twitch_profile_videos_list, but the resource noun 'stream schedule' does most of that work.

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 when-to-use guidance: nothing says to call this for upcoming/live broadcast times versus using twitch_profile_get for general channel info. 'Requires `handle`' restates a schema constraint rather than telling the agent when this tool is the right choice.

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