Skip to main content
Glama

Thread Kit: posts that fit every network

Count a post's length the way the network counts it (free)

count_post_length
Read-onlyIdempotent

FREE. Exact length of one post for X, Bluesky, Farcaster, Mastodon or Threads (Meta), in that network's own unit, with the limit, remaining and whether it fits. X: weighted, CJK and emoji count 2, every link 23, limit 280. Bluesky: 300 graphemes and 3000 bytes. Farcaster: UTF-8 bytes, 320 per cast (1024 long cast). Mastodon: 500, links 23. Threads (Meta): 500, emoji count as their UTF-8 bytes. Use it before posting; if it does not fit, check_post_length returns a shortened version and split_thread a thread.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe post text
limitNoOptional limit; default is the network's own limit
networkNoTarget network: x (X/Twitter, default), bluesky, farcaster, mastodon or meta-threads (Threads by Meta)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real value: the 'FREE' pricing signal and per-network counting rules (X weighted/CJK 2/link 23, Bluesky graphemes vs bytes, Farcaster 320/1024, Mastodon 500, Threads UTF-8 emoji) that determine the result. It also names the result fields (limit, remaining, fits). No rate limits or latency caveats, so not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and the 'FREE' qualifier, then per-network rules in compact clauses, then the routing sentence. Dense but every clause carries a distinct rule; slightly list-like and close to overload for a single description.

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?

No output schema exists, and the description compensates by enumerating the returned fields (limit, remaining, fits) along with the exact counting semantics that make the result interpretable. Only minor gaps — error behavior for unsupported input or how an overridden limit interacts with network rules.

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 coverage is 100%, so the baseline is 3, but the description goes further by explaining what each network's unit actually means (e.g. X weights, Bluesky graphemes vs bytes) and that 'limit' defaults to the network's own limit. That interpretive context is not recoverable from the raw enum values alone.

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 ('Exact length of one post') and scopes it to five named networks with their own counting units. An agent can immediately distinguish it from check_post_length (shortening) or split_thread.

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

Usage Guidelines5/5

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

Explicitly says 'Use it before posting' and routes the agent onward: if the text does not fit, 'check_post_length returns a shortened version and split_thread a thread.' That is a concrete when-to-use plus named alternatives with the condition that selects them.

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