utm-helper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UTM_SPEC_SOURCE_URL | No | Raw base URL of the Git spec source. The server appends file names (e.g. GUIDE.md), so it must serve raw file contents. A trailing / is added if omitted. | https://raw.githubusercontent.com/ArcadeAI/utm-helper-mcp/main/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| UtmServer_GetGuidelinesA | Return the authoritative UTM tagging guide. Fetches |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool name is specific and unambiguous.
Single tool ensures perfect naming consistency; the PascalCase prefix 'UtmServer_' is clear and consistent.
A single tool that only returns guidelines is far too minimal for a UTM helper server. The domain typically requires at least URL generation and validation tools.
The tool surface is severely incomplete; it only provides guidelines but lacks any operational UTM tools such as creation, parsing, or validation.