Skip to main content
Glama

UTM campaign link

bpj_campaign_utm_link
Read-onlyIdempotent

Set campaign, medium and source tags while preserving other query parameters and anchors.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
mediumYes
sourceYes
campaignYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior — existing query parameters and anchors are preserved — but is silent on what happens to an already-present utm_* parameter (overwrite vs. duplicate), on URL encoding, and on how a malformed or relative URL is handled.

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 well-formed sentence with no filler, and the preservation guarantee is placed where it matters. It is efficient, though the brevity comes at the cost of the missing detail noted elsewhere.

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

Completeness2/5

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

With no output schema and no schema descriptions, the definition should explain the four required inputs and the return value (presumably the rewritten URL). It never states what is returned or how the url input must be formed, leaving an agent to guess at call correctness for a 4-required-parameter tool.

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% across four required parameters, so the description must carry the burden, yet it only restates the parameter names (campaign, medium, source) and omits the most important one, url. It adds no meaning about the expected URL form (absolute vs. relative, maxLength 1800) or value constraints on the 160-character tag fields.

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 states a specific action (set campaign/medium/source tags) against an implied resource (a URL's query string), which aligns with the tool name and title 'UTM campaign link'. It is clear what the tool produces, though it never uses the word 'URL' directly, relying on 'other query parameters and anchors' to imply it.

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 explicit guidance on when to reach for this tool versus the many other bpj_* link utilities (canonical checks, label checks, relative-link resolution). The use case is inferable from the name and effect, but nothing states prerequisites, when-not-to-use, or which sibling to pick instead.

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.