SmartTools

UTM link builder

utm_builder

Append encoded UTM campaign parameters to a URL, preserving any existing query and fragment. Runs on smart-tools.xyz.

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

Input Schema

Name	Required	Description
`url`	Yes	Base URL, e.g. https://example.com/landing
`term`	No	utm_term (optional)
`locale`	No	Language for the source_url link (default en)
`medium`	Yes	utm_medium, e.g. cpc
`source`	Yes	utm_source, e.g. google
`content`	No	utm_content (optional)
`campaign`	Yes	utm_campaign, e.g. spring_sale

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A3.7/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. It does disclose that parameters are encoded and that existing query/fragment are preserved, but it does not explain behavior for duplicate UTM params, invalid URLs, or the exact return format. This is partial but not comprehensive.

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?

The first sentence is clear and efficient. However, 'Runs on smart-tools.xyz' is unnecessary and does not aid tool selection or invocation, slightly reducing conciseness.

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 simple append-parameters tool, the description covers the key behavior (encoding, preserving query/fragment). No output schema or annotations exist, but the tool's low complexity means the description is mostly adequate, though edge cases like existing UTM parameters are not addressed.

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 parameters are already documented in the schema. The description adds minimal value beyond noting preservation of query/fragment, which relates to the 'url' parameter. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('append') and resource ('URL'), clearly stating it adds UTM campaign parameters. It also mentions preserving existing query and fragment, which distinguishes it from any sibling tools (all other tools are converters/calculators).

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 implied by the action of appending UTM parameters to a URL, but there is no explicit guidance on when to use this tool vs. alternatives or when not to use it. No exclusions or alternative tool mentions are provided.

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

All SmartTools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?