Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Ko-fi post

ko_fi_post_get
Read-onlyIdempotent

Fetches a Ko-fi post's title, author, date, full body, images, and tags using its slug. Use it to pull complete post content for reading, archiving, or summarizing.

Instructions

Get a Ko-fi post's title, author, date, full body, image and tags. Requires slug.

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": "ko_fi_post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Post slug from the post URL, e.g. `Shipping-profiles-digital-variants-and-more-D0K429XOFY`.
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

B3.2/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 structurally. The description adds genuine value by naming the payload contents (body, image, tags), but says nothing about auth requirements, whether private/supporter-only posts are visible, or failure behavior for an invalid slug.

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?

Two short sentences, front-loaded with the returned fields and ending with the one hard requirement. The only waste is the redundant "Requires `slug`" sentence, which the schema already enforces.

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?

With no output schema, the description usefully compensates by enumerating the returned fields. For a single-resource read tool with fully documented parameters and rich annotations, the remaining gap (no note on visibility of supporter-only content) is minor.

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 slug, context, llm_model and conversation_id are all documented in the schema with format and examples. The description's "Requires `slug`" merely restates the required array and adds no new meaning, so the baseline 3 is appropriate.

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?

"Get a Ko-fi post's title, author, date, full body, image and tags" pairs a specific verb with a specific resource and even enumerates the returned fields, so an agent knows exactly what comes back. It stops short of differentiating itself from siblings such as ko_fi_profile_posts_list, 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 Guidelines2/5

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

The only conditional statement is "Requires `slug`", which is a prerequisite rather than usage guidance. There is no mention of when to pick this over ko_fi_profile_posts_list or ko_fi_post_comments_list, and no exclusions or edge cases.

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