Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitch profile

twitch_profile_get
Read-onlyIdempotent

Fetch a Twitch channel profile by handle to view account details. Look up any streamer's public profile data from a handle, with or without a leading @.

Instructions

Get a Twitch profile for a 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_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

C2.9/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. The description adds nothing beyond that: no note on what the profile payload includes, no rate-limit or error behavior for a bad handle, and 'Requires `handle`' merely repeats the schema's required list.

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 core purpose, with no filler or hedging. The second sentence is effectively redundant with the schema's required array, which costs it a point.

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 simple idempotent read with full annotation coverage, a 100%-documented schema, and no output schema, the definition is serviceable. It is still thin on the one thing an agent might wonder about, namely what a 'profile' returns and how it fails for a non-existent channel.

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% and the handle description already documents the '@'-optional format, so the schema carries the meaning. The description only restates the required handle and says nothing about the context, llm_model, or conversation_id parameters, which is the baseline 3 case.

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 ('Get a Twitch profile for a channel by handle'), which is unambiguous and distinguishes it from the list/engagement/schedule siblings by scope. It stops short of explicitly contrasting with the other Twitch profile-adjacent tools, so it lands at 4 rather than 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 when-to-use guidance: nothing says when to prefer this over twitch_profile_schedule_get or twitch_profile_videos_list, nor what happens for an unknown or suspended channel. The only guidance is a restated prerequisite ('Requires handle'), which is not usage routing.

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