Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Ko-fi gallery item

ko_fi_gallery_item_get
Read-onlyIdempotent

Retrieve a single Ko-fi gallery item by ID, including its images, owner, description, and like count for content research or moderation.

Instructions

Get one Ko-fi gallery item with its images, owner, description and like count. Requires id.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Gallery item id, e.g. `IN3G429XO7C` from `https://ko-fi.com/i/{id}`.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuine value by disclosing what the response contains (images, owner, description, like count), which the annotations do not. It omits not-found behavior, but that is a minor gap given the annotation coverage.

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?

Two sentences, no filler, and the payload description is front-loaded before the prerequisite. Every clause carries information an agent can act on.

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 simple read-only getter with full schema coverage and rich annotations but no output schema, the definition covers purpose, input requirement, and returned fields. Only error/not-found behavior is unaddressed, which is a small gap for this complexity level.

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 `id`, `context`, `llm_model`, and `conversation_id` are all documented in the schema itself. The description's "Requires `id`" merely restates the required constraint and adds no format or meaning beyond what the schema provides.

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 one Ko-fi gallery item") and enumerates the payload (images, owner, description, like count), which distinguishes it from the sibling list tool ko_fi_profile_gallery_list. It stops short of explicitly naming that sibling, so differentiation is implied by the singular "one item" rather than stated.

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: the singular "one item" plus "Requires `id`" signals single-item lookup after an id is known. There is no explicit when-to-use/when-not guidance pointing at ko_fi_profile_gallery_list for enumeration or at ko_fi_shop_item_get for shop entries.

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