Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_sanitize_url

Removes surveillance and ad network click IDs like fbclid and gclid from URLs, with an option to retain clean UTM tags.

Instructions

Strip surveillance and ad network click IDs (fbclid, gclid, msclkid, twclid, etc.) from a URL.

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": {
      "url": "<url>"
    },
    "name": "omni_sanitize_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget URL to cleanse.
keep_utmNoWhether to retain clean marketing UTM tags.

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 supplied, the description carries the full burden, and it does disclose what is removed (click IDs) versus retained (UTM tags, governed by keep_utm). It is silent on whether non-tracking parameters are preserved, whether it is a pure local transformation or performs network work, and how invalid URLs 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.

Conciseness5/5

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

A single front-loaded sentence with the action first and the concrete parameter examples immediately after. Every clause earns its place and there is no filler.

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 simple two-parameter utility this is close, but with no output schema the definition never states that the result is a cleaned URL string (versus an object or a change list) nor what happens on malformed input. One more sentence on the return shape would close the remaining gap.

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 parameters are already documented ('Target URL to cleanse' and the keep_utm default of true). The description adds only the concept of which IDs count as tracking, which is useful framing but does not extend either parameter's 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?

States a specific verb ('strip') and resource ('surveillance and ad network click IDs') and enumerates concrete examples (fbclid, gclid, msclkid, twclid), so the agent knows precisely what transformation happens. It does not explicitly contrast itself with the related omni_build_utm_url, leaving the UTM boundary to be inferred from the keep_utm parameter.

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 tool is for cleaning tracking parameters off a URL, presumably before sharing or republishing. There is no statement of when to prefer this over omni_build_utm_url or omni_generate_campaign_links, and no when-not guidance or prerequisites.

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