Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Ko-fi shop item

ko_fi_shop_item_get
Read-onlyIdempotent

Fetch a Ko-fi shop item’s description, images, contents, stock, and seller using its required alias.

Instructions

Get a Ko-fi shop item with its full description, images, contents, stock and seller. Requires alias.

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

Input Schema

NameRequiredDescriptionDefault
aliasYesRequired. Shop item alias from `https://ko-fi.com/s/{alias}`.
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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful context by listing the response payload (description, images, contents, stock, seller), which matters because no output schema exists. It does not mention not-found behavior or rate limits, keeping it short of a 5.

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 no waste: verb+resource first, returned fields second, required input last. Every clause earns its place.

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-item fetch with full schema coverage and no output schema, the description is nearly sufficient: it names the input and sketches the returned fields. Only edge behavior, such as what happens when the alias does not resolve, 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 coverage is 100%, so the schema already documents alias, context, llm_model and conversation_id. The description's only parameter contribution is reiterating that alias is required, adding no format, resolution or error semantics beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 Ko-fi shop item") and enumerates what comes back: full description, images, contents, stock and seller. An agent can distinguish this from a list-style sibling, though the description never names ko_fi_profile_shop_items_list or any alternative, so sibling differentiation is left implicit.

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 implied rather than stated: "Requires `alias`" plus the alias pattern pointing at ko-fi.com/s/{alias} tells the agent what input is needed, but there is no explicit when-to-use-this-vs-a-list-call guidance or exclusion. An agent can infer it fetches a single item, but must reason about when a list call would be preferable.

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