Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_generate_campaign_links

Generates synchronized UTM campaign tracking links across multiple social platforms at once, so campaign attribution stays consistent across channels.

Instructions

Generate synchronized UTM campaign tracking links across multiple social platforms simultaneously.

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": {
      "base_url": "<base_url>",
      "campaign": "<campaign>"
    },
    "name": "omni_generate_campaign_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNoOptional content identifier.
base_urlYesBase target URL.
campaignYesCampaign name.
platformsNoTarget platforms (e.g. twitter, linkedin, bluesky, threads, mastodon, newsletter).

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?

No annotations exist, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the one-line purpose. It does not say whether links are persisted or returned only, whether the call fans out to external platform APIs (and thus needs auth or is rate limited), what 'synchronized' means concretely, or how unsupported platform values are handled.

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 zero filler, and the multi-platform scope appears before anything else. It is efficient, though its brevity is arguably under-specification rather than disciplined concision.

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 4-parameter generation tool with no annotations and no output schema, the agent gets no information about the return shape (single list? per-platform map?) or what 'synchronized' guarantees. Against a crowded sibling set that includes omni_build_utm_url and omni_tag_post_links, the definition does too little to establish its niche.

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 all four parameters are already documented in the schema, and the description adds no format, default, or constraint details beyond them. The only implied semantics is that platforms accepts multiple values, which the schema's array type already conveys; baseline 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?

Uses a specific verb ('Generate') plus resource ('UTM campaign tracking links') and adds a distinguishing scope ('across multiple social platforms simultaneously'). This separates it from a single-URL builder like omni_build_utm_url, though that sibling is never named.

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 'across multiple social platforms simultaneously' implies the batch/multi-platform case, which is the closest thing to when-to-use guidance present. There is no explicit when-not guidance and no named alternative for generating a single UTM link or for tagging existing posts.

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