Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_generate_hooks

Generate hooks, headlines, and opening lines from a topic using proven copywriting frameworks to help social posts capture attention and increase engagement.

Instructions

Generate high-converting viral hooks, headlines, and opening lines based on proven copywriting frameworks.

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": {
      "topic": "<topic>"
    },
    "name": "omni_generate_hooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of hook variations to generate.
nicheNoTarget audience niche (e.g. tech, saas, creator, ai, finance).tech
topicYesThe topic, product, or central theme.
frameworkNoCopywriting framework: contrarian, question, number_list, curiosity_gap, transformation, how_to, negative_bias, secret_mistake, story_lead, or all.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It reveals almost nothing beyond the one-line purpose: no indication of output shape (list of strings? numbered?), whether generation is costly/rate-limited, or whether results are deterministic across calls.

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 wasted clauses. The adjective stack 'high-converting viral' is mildly promotional but does convey the intended output style, so it earns its place.

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?

An adequate but thin definition for a four-parameter generative tool. Since there is no output schema, the description should have sketched the return value (e.g., N hook strings) rather than leaving the response shape entirely unstated.

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 topic, niche, count, and framework are already fully documented in the input schema, including the framework values. The description adds no syntax, defaults, or interaction guidance beyond that baseline.

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+resource: generate hooks, headlines, and opening lines, plus the mechanism (copywriting frameworks). No sibling tool produces creative copy, so the resource alone differentiates it, though the description never says so explicitly.

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 only implied by the phrasing 'viral hooks' for social copy; there is no statement of when to pick this over alternatives such as omni_format_post or omni_split_thread. No exclusions or prerequisites are given.

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