Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_split_thread

Split long-form copy into platform-optimized thread posts with character-limit adherence, natural breaks, and optional numbering for social publishing.

Instructions

Split long-form copy into platform-optimized thread posts with character limit adherence, natural sentence/paragraph breaks, and numbering markers.

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

Input Schema

NameRequiredDescriptionDefault
textYesLong text content to split into thread segments.
limitNoMaximum character limit per post (defaults to platform limit).
platformNoTarget platform for character limit autodetection.twitter
numberingNoWhether to append/prepend thread numbering (e.g. 1/N).
numbering_formatNoNumbering format: 'fraction' (1/N), 'fraction_thread' (๐Ÿงต 1/N), 'bracket' ([1/N]), 'counter' (1.).fraction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose meaningful traits โ€” character-limit adherence, break strategy, and that numbering markers get inserted โ€” but omits whether the operation is purely non-destructive/stateless, what happens when text already fits under the limit, and how an unsupported 'platform' value is handled. Valuable but incomplete for an un-annotated tool.

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?

A single front-loaded sentence with no filler โ€” the core action comes first and the three behavioral clauses follow in a logical order. Slightly dense but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should indicate the return shape (e.g. an ordered list/array of post strings), which it never does โ€” a notable gap for a splitting tool whose whole value is the segmented output. Combined with zero annotations, the definition leaves an agent unsure what it will receive back.

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 the schema already documents all five parameters including the numbering_format enum values. The description adds only the general notion of 'platform-optimized' limits and 'numbering markers', which the schema fields already convey in more detail; 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?

The description uses a specific verb ('Split') plus a clear resource ('long-form copy into platform-optimized thread posts') and enumerates the transformation rules (character limits, sentence/paragraph breaks, numbering). It does not, however, distinguish itself from the sibling omni_format_post, leaving an agent to guess which of the two handles post formatting versus thread splitting.

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?

The phrase 'long-form copy' implies the triggering condition (content too long for a single post), but there is no explicit when-to-use statement, no when-not-to-use case, and no reference to omni_format_post as the single-post alternative. Usage is inferable rather than stated.

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