Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_analyze_engagement

Analyze post text to score viral readiness and engagement potential, check readability and sentiment, and get actionable optimization tips for a target platform.

Instructions

Analyze text for engagement potential, viral readiness score (0-100), readability metrics, sentiment, structure, and actionable optimization tips.

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

Input Schema

NameRequiredDescriptionDefault
textYesPost text to analyze.
platformNoTarget platform for contextual scoring.twitter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the substance of the result (a 0-100 viral score, readability metrics, sentiment, structure, tips), which is meaningful given there is no output schema, but it says nothing about whether the call is purely read-only, whether it is deterministic, whether it costs quota, or how long it takes.

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 dense sentence with the core action front-loaded and the output inventory following. No filler, though the comma-separated output list is slightly dense to parse in one pass.

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?

For a two-parameter analysis tool with no output schema, enumerating the returned artifacts is the right move and largely compensates for the missing schema. However, the 'platform' parameter's accepted values and its effect on scoring are left unexplained, leaving a gap an agent would hit on first use.

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 both 'text' and 'platform' are already documented in the schema. The description adds no meaning beyond that — it does not say what platforms are valid or how platform changes the scoring — so the baseline of 3 applies.

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?

States a specific verb ('Analyze') and resource ('text') and enumerates the outputs produced: engagement potential, viral readiness score (0-100), readability, sentiment, structure, and optimization tips. It is clearly distinguishable from formatting/generation siblings like omni_format_post or omni_generate_hooks, though it never names or contrasts with them explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are referenced. An agent can infer this is for evaluating drafted post text before publishing, but nothing in the description states that precondition or tells it what to do instead for related tasks.

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