Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_format_post

Format and optimize social media posts for target platforms with character checks and Unicode typography styling.

Instructions

Format, optimize and style social media posts for target platform (twitter, linkedin, bluesky, threads, mastodon) with character checks and Unicode typography styles.

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_format_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe raw post text content to format.
trimNoWhether to strip leading/trailing whitespace.
styleNoUnicode typography style (normal, bold, italic, bold_italic, monospace, script, double_struck, sans, underline, strikethrough).normal
hashtagsNoOptional list of hashtags to append.
platformNoTarget social media platform (twitter, linkedin, bluesky, threads, mastodon).twitter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full burden. It mentions 'character checks' and 'optimize' but never says what happens when a post exceeds platform limits (error, truncate, reject), whether the input text is returned transformed or rewritten, or whether anything is published — leaving an agent unsure whether this is a pure transformation or a side-effecting action.

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 naming the action, target platforms, and key capabilities, with no filler. The vague term 'optimize' is the one word that does not clearly earn its place.

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

Completeness2/5

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

For a five-parameter transformation tool with no annotations and no output schema, the description should state what is returned (formatted text) and how character-limit violations are handled. Neither is covered, and the enum/description platform mismatch adds ambiguity.

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 coverage is 100%, so the schema already documents all five parameters thoroughly and the baseline applies. The description adds nothing beyond restating platform and style concepts, and its platform list (twitter, linkedin, bluesky, threads, mastodon) omits facebook and instagram, which the enum actually accepts.

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 set (format, optimize, style) against a specific resource (social media posts) and names the target platforms plus two distinguishing capabilities (character checks, Unicode typography). It is clear what the tool is for, though it does not differentiate from nearest siblings like omni_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 Guidelines3/5

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

Usage is implied: call this when you have raw post text that needs platform-specific formatting. There is no explicit when-to-use or when-not-to-use guidance and no pointer to an alternative such as omni_split_thread for over-length content, so the agent must infer boundaries.

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