Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_vanity_redirect

Generate a standalone zero-dependency HTML vanity redirect page with Open Graph and Twitter Card tags for rich link previews and configurable redirect delay.

Instructions

Generate a standalone zero-dependency HTML vanity redirect page with Open Graph and Twitter Card tags.

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": {
      "target_url": "<target_url>",
      "title": "<title>"
    },
    "name": "omni_vanity_redirect"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesPage title for browser tab and OG preview.
delay_msNoClient redirect delay in milliseconds.
og_imageNoOG image URL for rich link preview card.
target_urlYesDestination redirect URL.
og_descriptionNoOG card description preview text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and 'standalone zero-dependency' does usefully characterize the produced artifact as self-contained HTML. However, it never states whether the tool writes a file or returns markup, nor whether the redirect fires client-side (a key trait given the delay_ms parameter), leaving the side-effect profile ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the defining artifact and its key capability (OG/Twitter tags) are stated first. Nothing could be removed without losing information.

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 five-parameter generator with no annotations and no output schema, the description omits important context: the return form (HTML string vs. written file), how delay_ms affects behavior, and any environment constraints. The rich schema compensates for parameter-level gaps, but the output and side-effect story remains incomplete.

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 five parameters (title, target_url, og_image, og_description, delay_ms) are already well documented in the schema. The description adds no extra meaning about their interplay, 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?

The description names a specific verb ('Generate') and a specific artifact ('standalone zero-dependency HTML vanity redirect page with Open Graph and Twitter Card tags'), which is clearly distinct from sibling tools like omni_build_utm_url and omni_sanitize_url. It stops short of explicitly contrasting with any sibling, but the resource is specific enough that an agent can identify the tool's job immediately.

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: the agent can infer this is for producing redirect pages, but there is no statement of when to choose it over alternatives (e.g., link-building tools in the sibling list) or any prerequisites. No exclusions or decision criteria are given.

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