Skip to main content
Glama

Thread Kit: posts that fit every network

Write a thread from an article or notes (AI) ($0.010)

write_thread_from_article
Read-only

Turn an article, blog post, notes, changelog or transcript into a ready-to-post thread (hook first, one point per post, wrap-up last) for X, Bluesky, Farcaster, Mastodon or Threads. An open model on Cloudflare Workers AI writes it; Thread Kit re-measures and re-splits every post so each one fits, removes links that are not in the source and flags numbers that are not in it. A failed generation is not charged. PAID: $0.010 per call in USDC on Base via x402 over MCP, or from prepaid credits if this server is configured with an Authorization: Bearer tkc_... header (see payment_options).

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": {
      "text": "<text>"
    },
    "name": "write_thread_from_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: auto = same as the source (default), or en, zh, zh-TW, ja, ko, es, fr, de, pt, ru, id, vi, tr, it
textYesSource to turn into a thread: article, notes or transcript (100-3000 characters)
toneNoclear (default), punchy, casual or formal
postsNoNumber of posts, 3-12; omit to let the writer choose from the source length
platformNoTarget network: x (default), bluesky, farcaster, mastodon or meta-threads
numberingNoWhere to put "n/N": suffix (default), prefix or none. Counted in each post's length.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, non-destructive, open-world); the description adds substantial behavior beyond them: an open model on Cloudflare Workers AI does the writing, Thread Kit re-measures and re-splits each post to fit, strips links absent from the source, flags numbers absent from it, and failed generations are not charged. It also discloses the pricing and the two payment paths, which an agent must know before invoking.

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 sentences, front-loaded with the core purpose and output structure, then verification behavior, then the payment precondition. Dense rather than padded, though the parenthetical output-shape clause and the platform list make the opening sentence long.

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 does a fair job of conveying what comes back (a per-post thread with hook, points and wrap-up, length-adjusted) and discloses cost and auth. It stops short of describing the actual response payload, such as whether posts are returned as an array with per-post length metadata.

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% and all six parameters, including four enums, are documented in the schema itself. The description adds no parameter-level detail such as character budgets, language fallback rules, or how the posts count interacts with per-platform limits, so it stays at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Turn an article, blog post, notes, changelog or transcript into a ready-to-post thread') and enumerates the target networks. The output shape ('hook first, one point per post, wrap-up last') makes it clearly distinct from siblings like split_thread or check_post_length.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear context for when this applies: raw source material (article, notes, changelog, transcript) and a target network, and points to payment_options for the auth/credits question. It does not explicitly say when to prefer split_thread or rewrite_x402_listing instead, so the alternative routing is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources