Skip to main content
Glama

Ad Spec Guard

build_utm

Read-only

Assemble a campaign URL with consistent UTM tagging, normalise the values so they do not split into duplicate rows in analytics, and report every correction made and every risk found. Also flags a source or medium that departs from the conventional value for the platform, which silently breaks channel grouping.

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": "build_utm"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoOptional keyword or audience term.
mediumYesTraffic medium, for example 'cpc' or 'paid_social'.
sourceYesTraffic source, for example 'google' or 'facebook'.
contentNoOptional creative or variant identifier.
base_urlYesLanding page URL, with or without an existing query string.
campaignYesCampaign name.
platformNoOptional platform key, used to check source and medium against the conventional values.
conventionNoNaming convention applied to every value.lowercase_underscore

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description goes beyond them by disclosing that values are normalized to avoid duplicate analytics rows, that corrections and risks are reported, and that non-conventional source/medium values are flagged. What remains unsaid is the shape of the returned report, though the prose at least signals that a report accompanies the URL.

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 action is front-loaded in the first clause and there is little padding. The second sentence is a fragment ("Also flags a source or medium...") with a trailing relative clause, which is slightly awkward but still compact and information-dense.

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 an 8-parameter, fully documented read-only tool with annotations, the description covers construction, normalization, flagging, and reporting. Without an output schema it would help to state what is actually returned (URL string plus correction/risk list), which is the one 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 coverage is 100%, so every parameter including platform and convention is already documented in the schema. The description reinforces the intent of normalization and the platform-vs-convention check but adds no syntax, defaults, or edge cases beyond that. Baseline 3 fits when the schema carries the parameter detail.

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?

"Assemble a campaign URL" is a specific verb plus resource, and the description adds the normalization and reporting behaviors that define the tool's scope. It does not explicitly contrast itself with the sibling validate_utm, leaving the build-vs-check boundary to be inferred from the verb.

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: use this when constructing a new tagged URL rather than inspecting an existing one. There are no explicit when-not conditions, prerequisites, or named alternatives, so an agent must infer the split with validate_utm.

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.