Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Kick user

kick_user_get
Read-onlyIdempotent

Fetch a Kick user's profile by username to retrieve bio, social links, avatar, account creation time, level, and global badges for identity or community research.

Instructions

Get any Kick user by username: bio, socials, avatar, account creation time, level and global badges. Requires username.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
usernameYesRequired. Kick account name, with underscores where the channel slug has hyphens (e.g. `alfalfa_kid`).
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the payload field list, and says nothing about failure behavior for unknown usernames, rate limits, or latency — context that would be genuinely additive here.

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 front-loaded sentence with the required-parameter note attached and zero filler; every clause carries information about the resource or its returned fields.

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?

For a read-only single-record getter with rich annotations and 100% schema coverage, the description supplies what matters: the identifier and the returned fields. Only the not-found / invalid-username behavior is missing, which is a minor gap given there is no output schema.

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 username format, the underscore-for-hyphen convention, and the analytics/context fields. The description's 'Requires `username`' merely restates the schema and omits mention of the other required parameters (context, llm_model). Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb and resource ('Get any Kick user by username') and enumerates the data returned: bio, socials, avatar, account creation time, level and global badges. It does not, however, differentiate itself from the similarly named 'kick_channel_get' sibling, which an agent could easily confuse with a user lookup.

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?

Usage is only implied by 'Get any Kick user by username' — the word 'any' suggests broad applicability, but there is no explicit statement of when to prefer this over kick_channel_get or the channel-oriented siblings. No exclusions, prerequisites, or alternative routing are provided.

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