Social Fetch

Get Twitch profile schedule

twitch_profile_schedule_get

Read-only

Get the stream schedule for a Twitch channel by handle.

Input Schema

TableJSON Schema

Name	Required	Description
`trim`	No	Ignored if this tool does not support it.
`urls`	No	Alias for `handle`. Prefer `handle`.
`user`	No	Alias for `handle`. Prefer `handle`.
`limit`	No	Ignored if this tool does not support it.
`handle`	No	Twitch handle to look up, with or without a leading @.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`pageSize`	No	Ignored if this tool does not support it.
`userName`	No	Alias for `handle`. Prefer `handle`.
`username`	No	Alias for `handle`. Prefer `handle`.
`llm_model`	Yes	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.
`maxResults`	No	Ignored if this tool does not support it.
`profileUrl`	No	Alias for `handle`. Prefer `handle`.
`linkedinUrl`	No	Alias for `handle`. Prefer `handle`.
`max_results`	No	Ignored if this tool does not support it.
`screen_name`	No	Alias for `handle`. Prefer `handle`.
`conversation_id`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 21, 2026

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 / 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"
```

Changed2 schema fields changedSep 20, 2026

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"
+}

Changed5 schema fields changedSep 12, 2026

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"
+]

Changed5 schema fields changedSep 5, 2026

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"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJul 20, 2026

TDQS

A3.7/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, covering the safety profile. The description adds the behavioral constraint 'by handle', indicating the lookup key, which is useful context beyond the annotations. However, it does not disclose rate limits, error behavior, pagination, or what the returned schedule contains.

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?

A single sentence with no filler, directly naming the action, resource, and lookup key. It is concise and front-loaded—every word earns its place.

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?

With no output schema, the description's 'stream schedule' minimally hints at the return value, but it does not describe the schedule's format, timezone, or structure. The schema has 17 parameters with several aliases and ignored fields, and the description does nothing to help an agent triage which parameters matter; while the schema descriptions help, the tool remains noisy to invoke correctly.

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 all parameters including aliases ('Alias for handle. Prefer handle.') and ignored flags ('Ignored if this tool does not support it.'). The description's 'by handle' confirms the primary parameter but adds no new format or selection guidance beyond the schema. Baseline 3 applies.

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: 'Get the stream schedule for a Twitch channel by handle.' This unambiguously differentiates it from sibling tools like twitch_profile_get (profile info) and twitch_profile_videos_list (videos), so an agent can immediately identify what this tool does.

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?

The usage is implied clearly: use this tool when you need a Twitch channel's stream schedule, identified by handle. However, there is no explicit when-not-to-use guidance, no mention of alternatives (e.g., 'for profile info use twitch_profile_get'), and no prerequisites or context about when a schedule might not exist.

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

All Social Fetch 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.

Get Twitch profile schedule

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources