Skip to main content
Glama

UTM Link Builder API - tag many URLs with campaign parameters

utm_builder
Read-onlyIdempotent

Add utm_source, utm_medium, utm_campaign (and term/content) to one or many URLs, keeping existing parameters, clean lower-case values. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/utm-builder.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "https://example.com/offer",
      "medium": "email",
      "source": "newsletter",
      "campaign": "Black Friday 2026"
    },
    "name": "utm_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoutm_term (optional)
urlsYesURLs, one per line
mediumYesutm_medium, e.g. email
sourceYesutm_source, e.g. newsletter
contentNoutm_content (optional)
campaignYesutm_campaign
lowercaseNoLower case with _ for spaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, open-world), the description discloses server-side execution, immediate deletion of inputs, no storage, a 25 calls/day per-IP free limit, and $0.001/call via x402 — meaningful operational and cost context an agent cannot get from the schema. The gap is that it never says what comes back (tagged URL list vs. errors), and there is no output schema to cover that.

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?

Three dense sentences: capability and scope first, then privacy/execution, then pricing. Every clause carries load — the x402 URL is needed to actually use the paid tier — and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter, stateless transform with annotations covering safety and no output schema, the definition supplies the operational facts that matter most (cost, rate limit, data handling). It stops short on return shape and on any cap for the number of URLs per request, which leaves a small but real 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 the schema already documents all seven parameters including the optional term/content and the lowercase default. The description adds only marginal semantics — 'keeping existing parameters' and 'clean lower-case values' — which lightly reinforces the lowercase flag but gives no format or multi-URL delimiter detail beyond the schema's 'one per line'.

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 opens with a concrete verb and resource: 'Add utm_source, utm_medium, utm_campaign ... to one or many URLs,' and adds scope details (preserves existing parameters, lower-cases values). No sibling in the catalog does UTM tagging, so there is nothing to disambiguate against, but the operation and its batch nature are unmistakable.

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 context is implied by 'one or many URLs' and the free-vs-paid tiering, so an agent can tell this is a stateless batch transformation. There is no explicit when-to-use/when-not guidance and no named alternative for cases like single-URL tagging or existing-UTM replacement, which is acceptable given no close sibling exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources