Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Ko-fi profile

ko_fi_profile_get
Read-onlyIdempotent

Retrieve a Ko-fi creator's public profile by handle or page ID to view identity, bio, links, support settings, goal, and badges.

Instructions

Get a Ko-fi creator's public profile: identity, bio, links, support settings, goal and badges. 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": "ko_fi_profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. A creator's Ko-fi handle (e.g. `ligianunes`) or page id (e.g. `A644275F`). Case-insensitive.
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, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description's one contribution beyond that is 'public profile', implying no authorization is needed for the data — a useful but modest addition, with nothing on rate limits, caching, or error behavior for an unknown handle.

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?

One sentence, front-loaded with the verb and resource, then the payload facets, then the single prerequisite. No filler and nothing that could be cut without losing information.

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 getter with full schema coverage and no output schema, the description tells the agent what data comes back and what is required. It leaves minor gaps — behavior on a nonexistent handle and whether the response is a single object — that a one-clause addition could close.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the schema itself documents handle format, case-insensitivity, and page-id support, as well as the context/llm_model/conversation_id conventions. The description's 'Requires `handle`' is redundant with the schema, so it does not push above a modest 4.

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?

Uses a specific verb and resource ('Get a Ko-fi creator's public profile') and enumerates the returned facets (identity, bio, links, support settings, goal, badges), which clearly separates it from the sibling list endpoints such as ko_fi_profile_posts_list. It does not explicitly name any sibling as an alternative, which keeps it short of a 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?

The only conditional statement is 'Requires `handle`', which merely restates a schema requirement rather than telling the agent when to call this versus the profile sub-resource tools (posts, tiers, shop items, etc.). No when-not-to-use or alternative routing is offered.

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