ClickTrail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_click_id_schemaB | Return the canonical click ID allowlist and lifecycle schema. |
| generate_nextjs_integrationC | Generate a consent-gated Next.js attribution integration. |
| generate_shopify_integrationC | Generate a consent-gated Shopify Web Pixel and order webhook attribution integration. |
| validate_attribution_pipelineC | Validate declared attribution lifecycle stages and consent. |
| diagnose_missing_click_idsC | Diagnose common click ID loss boundaries. |
| calculate_click_id_coverageC | Calculate capture, persistence, and attachment coverage. |
| reconcile_conversionsC | Reconcile CRM conversions against destination conversion records. |
| send_conversionB | Build a destination-neutral conversion payload without network side effects. |
| send_qualified_leadB | Build a qualified lead conversion payload without network side effects. |
| send_saleB | Build a sale conversion payload without network side effects. |
| check_conversion_statusC | Explain how to verify a conversion without querying a provider. |
| inspect_projectC | Inspect a caller-provided project snapshot for attribution capabilities. |
| detect_attribution_gapsC | Find unproven or missing attribution lifecycle stages. |
| plan_installationC | Create a framework-specific, evidence-aware installation plan. |
| simulate_ad_clickC | Simulate a synthetic click-to-account attribution journey locally. |
| verify_captureC | Verify that a click ID was captured intact after consent. |
| verify_form_attachmentC | Verify that attribution was copied into form fields. |
| verify_crm_attachmentC | Verify that attribution reached a CRM/account record. |
| verify_conversion_deliveryB | Classify provider delivery from an explicit receipt or return unknown. |
| attribution_healthC | Score the seven attribution lifecycle stages without inventing runtime proof. |
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 20 tools
Multiple tools overlap in diagnostic and validation purposes: validate_attribution_pipeline, diagnose_missing_click_ids, calculate_click_id_coverage, detect_attribution_gaps, and attribution_health all assess attribution health from slightly different angles, making selection ambiguous. The three send_* tools also differ only by payload type, adding further confusion.
Nearly all tools follow a consistent verb_noun snake_case pattern (capture_, generate_, send_, verify_, etc.), which aids predictability. The lone exception is 'attribution_health', which breaks the pattern with a noun_noun construction, causing a minor inconsistency.
With 20 tools, the server sits in the heavy range (16-25). The domain is broad, but many diagnostic and sending tools could be merged into fewer general-purpose tools without losing capability, making the count feel somewhat excessive.
The tool set covers the core attribution lifecycle: schema, integration generation, capture verification, conversion payload construction, delivery verification, diagnosis, and reconciliation. Minor gaps like a generic integration generator or direct conversion mutation exist but are workable for most agent workflows.