Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Kick VOD

kick_video_get
Read-onlyIdempotent

Fetch a Kick VOD by UUID to retrieve its stream details, channel, and categories.

Instructions

Get a Kick VOD by UUID with its stream, channel and categories. Requires videoId.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
videoIdYesRequired. VOD UUID, the id Kick pages use.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds useful context about what data is bundled into the response (stream, channel, categories), but says nothing about not-found handling or response shape beyond that enumeration.

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 action and the identifier type. The 'Requires `videoId`' clause slightly duplicates the schema's required list and UUID pattern, keeping it just short of 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?

With no output schema, the description's enumeration of returned data (stream, channel, categories) is the only signal about what comes back, which is valuable. For a single-UUID read tool with fully documented parameters and annotations covering safety, that is close to sufficient, though error behavior is unaddressed.

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 explains videoId as the UUID Kick pages use plus the context, llm_model, and conversation_id fields. The description only restates that videoId is required, adding no format or sourcing detail beyond the schema: baseline 3.

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?

States a specific verb and resource ('Get a Kick VOD by UUID') and adds scope detail by naming the related data returned: stream, channel, and categories. That distinguishes it from list-style siblings like kick_channel_videos_list, though no sibling is named explicitly.

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?

Implicitly frames usage as a lookup when a VOD UUID is already known, but gives no explicit when-to-use or when-not-to-use guidance and does not point to alternatives for discovery (e.g., a videos-list tool).

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