Skip to main content
Glama

Campaign link builder

toolfound_campaign_links
Read-onlyIdempotent

Create one deterministic UTM link while retaining unrelated query parameters and the page anchor. Returns an evidence-bounded result and the canonical web tool URL.

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

Input Schema

NameRequiredDescriptionDefault
mediumYesThe channel type (utm_medium), such as email, social, referral or cpc.
sourceYesWhere the traffic comes from (utm_source), such as the newsletter, site or platform name.
contentNoOptional label (utm_content) that tells apart variants within one campaign, such as which button or placement.
campaignYesThe campaign or launch name (utm_campaign) used to group results in analytics, for example october_launch.
websiteUrlYesDestination page that visitors should land on. Existing query parameters and any #anchor are kept in the result.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / campaign / description
      Added value: +"The campaign or launch name (utm_campaign) used to group results in analytics, for example october_launch."
    • addedInput schema / properties / content / description
      Added value: +"Optional label (utm_content) that tells apart variants within one campaign, such as which button or placement."
    • addedInput schema / properties / medium / description
      Added value: +"The channel type (utm_medium), such as email, social, referral or cpc."
    • addedInput schema / properties / source / description
      Added value: +"Where the traffic comes from (utm_source), such as the newsletter, site or platform name."
    • addedInput schema / properties / websiteUrl / description
      Added value: +"Destination page that visitors should land on. Existing query parameters and any #anchor are kept in the result."
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: existing query parameters and the #anchor survive the operation, and the result is 'evidence-bounded' with a canonical web tool URL returned. It says nothing about error behavior for malformed or non-URI inputs, which is the remaining gap.

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?

Two compact sentences with the action front-loaded and the preservation guarantee second; nothing is redundant. The phrase 'evidence-bounded result' is slightly opaque but costs little space.

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?

With an output schema present, return values need not be explained here, and the description's mention of the canonical URL return is a useful pointer. For a five-parameter, non-destructive link builder this is nearly complete, though it omits any note on validation failures or what 'deterministic' implies for repeated identical inputs.

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 every parameter including websiteUrl, source, medium, campaign and content is already documented with examples. The description adds only the preservation rule for existing query strings and anchors, which the websiteUrl schema property already states. Baseline 3 applies when the schema does the heavy lifting.

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 ('Create one deterministic UTM link') plus its key preservation behavior ('retaining unrelated query parameters and the page anchor'), which is far more specific than the title's 'Campaign link builder'. It does not explicitly distinguish itself from the nearby cleaner sibling, so the agent must infer that this tool appends UTM parameters while the cleaner presumably strips them.

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 naming of alternatives such as toolfound_campaign_url_cleaner, and no statement of prerequisites like a valid destination URL. The intended scenario (tagging a campaign link) is only weakly implied by the word 'campaign' in the parameters.

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