Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick channel goals

kick_channel_goals_list
Read-onlyIdempotent

List a Kick channel's follower and subscriber goals with their progress by providing the channel slug.

Instructions

List a Kick channel's follower and subscriber goals with their progress. Requires slug. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Kick channel slug, case-insensitive. Most replace the username's underscores with hyphens (e.g. `alfalfa-kid`, not `alfalfa_kid`), but some keep an underscore (e.g. `pala_okey`).
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

A3.5/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 covered. The description contributes only 'Returns a list', which is thin, and says nothing about what a goal object contains or whether pagination applies, so it adds limited value beyond the structured fields.

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?

Three short sentences with the resource and progress scope front-loaded, followed by the required parameter and return shape. Almost no waste, though 'Returns a list' is a low-information sentence given the absence of an output schema.

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 list tool with fully documented parameters and annotations covering safety. The description states the resource, the required input, and the return shape, which is adequate; only minor detail about the goal objects themselves is missing.

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 all four parameters (including context, llm_model, conversation_id) are already fully documented in the schema. The description only restates the slug requirement and adds nothing about format or constraints beyond what the schema provides, so baseline 3 applies.

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 gives a specific verb and resource: listing a Kick channel's follower and subscriber goals with their progress. That is clearly distinct from siblings like kick_channel_chatters_list or kick_channel_leaderboard_get. It stops short of explicitly contrasting with the nearest alternatives, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the prerequisite 'Requires `slug`', which is a calling condition rather than a when-to-use rule. There is no statement about when an agent should pick this over kick_channel_get or the leaderboard tool, though the narrow resource name makes the intended context fairly obvious.

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