Skip to main content
Glama
Marketing Ops MCP

Marketing Ops MCP

build_campaign_url

Read-onlyIdempotent

Generate a normalized UTM campaign URL with source, medium, and campaign values while keeping unrelated query parameters intact.

Instructions

Build a normalized UTM URL while preserving unrelated parameters.

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": {
      "payload": "<payload>"
    },
    "name": "build_campaign_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one real behavioral trait — that unrelated query parameters on the input URL survive the operation — which is useful and non-obvious. It does not disclose what 'normalized' means (lowercasing, encoding, ordering) or how the replace_existing toggle changes handling of pre-existing UTM parameters.

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?

A single sentence with no filler and the key scope constraint front-loaded. It is efficient, though its brevity comes at the cost of the parameter and normalization details noted elsewhere.

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?

With a nested payload object containing five fields, zero schema descriptions, and no output schema, the description is thin relative to the tool's surface. It covers the core outcome and one preservation behavior, but leaves the replace_existing toggle and normalization rules undocumented, which are exactly the gaps an agent would hit when invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does not. It never mentions the required url/source/medium/campaign fields or the replace_existing flag, whose semantics (does it strip prior UTM params or overwrite them?) are the single most consequential thing an agent needs to know. Only the 'preserving unrelated parameters' clause indirectly touches on behavior the flag affects.

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 and resource ('Build a normalized UTM URL') and adds the scope qualifier 'while preserving unrelated parameters'. An agent immediately knows this constructs a tagged campaign URL. It does not explicitly differentiate from siblings, but the listed siblings (experiment/funnel/transaction tools) are unrelated, so differentiation is not really needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives. Usage is only inferable from the purpose statement itself. A short clause such as 'use before sharing links in campaigns' would have raised this.

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