LLPROBeta

Home / Businesses / URL UTM Parameter Check

URL UTM Parameter Check

Check a campaign link's UTM parameters: missing source, medium or campaign, mixed-case values, spaces, typos and tags placed after the #, with a signed record.

Testing

What it does
Check a campaign link's UTM parameters: missing source, medium or campaign, mixed-case values, spaces, typos and tags placed after the #, with a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call url_utm_check at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

URL UTM Parameter Check is for agents that write newsletters, social posts and ads for a business and must check every campaign link before it is sent, so that traffic is grouped correctly in analytics. Check the UTM tracking parameters on a campaign link before it goes out. Send the full link (http or https). Get back every utm_ parameter found, and a list of findings: a missing or empty utm_source, utm_medium or utm_campaign, upper-case letters in a value (analytics reports treat 'Email' and 'email' as two different values), spaces (a raw space, or a space written as %20 or +), a parameter name that is not lower case, a repeated parameter, a utm_ name that is not a standard one (a likely typo), and UTM parameters placed after the # sign. Each finding says which parameter and what to change. Nothing is fetched: the link is only read. It is one of the Team communication department tools LLPRO builds for the work agents do across business software (Mailchimp, HubSpot, Google Analytics, Slack, Microsoft Teams). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that write newsletters, social posts and ads for a business and must check every campaign link before it is sent, so that traffic is grouped correctly in analytics.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not open the link, follow redirects or check that the page exists (a redirect can drop the UTM parameters; test that with the live link). Does not know your naming convention, so it does not judge whether 'cpc' or 'paid-search' is the right medium or whether a campaign name is a good one. Does not check utm_id, utm_term or utm_content (they are optional). Other tools (Adobe, Matomo, a CRM) may read UTM parameters differently from Google Analytics. Not legal, tax or financial advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "url_utm_check", "arguments": {"url": "https://example.com/page?utm_source=newsletter&utm_medium=email&utm_campaign=spring-sale"}}}

For agents

Tool url_utm_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:2wey2bljcurqlds4y5v5jpi34u): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): pcuyZgRVsr8fgIVxp++VnbuJYqQ3DJAokOzIJyjlDAo=

For agents that search MCP registries for utm parameters, campaign link check, utm_source utm_medium utm_campaign tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card