Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_build_utm_url

Build a campaign tracking URL by adding source, medium, campaign, term, and content parameters to a destination link for accurate social post attribution.

Instructions

Build a clean campaign tracking URL with source, medium, campaign, term, and content parameters.

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>",
      "source": "<source>",
      "medium": "<medium>",
      "campaign": "<campaign>"
    },
    "name": "omni_build_utm_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoOptional search/ad keyword.
mediumYesCampaign medium (e.g. social_post, email, cpc).
sourceYesCampaign source (e.g. twitter, linkedin, newsletter).
contentNoOptional content variation identifier.
base_urlYesDestination base URL.
campaignYesCampaign name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

C2.9/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 behavioral burden. The word 'clean' hints that existing or malformed query parameters are normalized or stripped, but the description never states this explicitly, nor does it describe validation behavior, error conditions, or whether an existing query string on base_url is preserved.

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, and the resource is stated before the supporting parameter list. It is arguably too terse rather than too verbose, but every word 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?

For a six-parameter URL composition tool with full schema coverage and no output schema, the description covers what it does but not how it behaves at the edges (query-string merging, encoding, return format). It is adequate as a minimum viable definition, not complete.

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%, with each of the six parameters individually documented including examples for source and medium, so the schema does the heavy lifting. The description only restates the parameter list without adding format, encoding, or conflict-resolution semantics beyond the schema.

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 names a specific verb ('Build') and resource ('campaign tracking URL') and enumerates the tracking fields it composes, so the operation is immediately identifiable. It stops short of distinguishing itself from sibling tools like omni_generate_campaign_links or omni_vanity_redirect, which plausibly overlap with this purpose.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Given that omni_generate_campaign_links and omni_vanity_redirect sit in the same catalog and could be confused with building a tracking URL, the absence of routing guidance is a real gap.

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