tealium-mcp-server
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_data_layerB | Validates a Tealium data layer object against schemas and best practices. Returns errors, warnings, and suggestions for improvement. |
| generate_documentationA | Generates documentation from a data layer structure or tracking specification. Outputs Markdown or JSON Schema format. |
| debug_data_layerB | Analyzes a data layer for common issues, missing variables, type mismatches, and provides recommendations. Perfect for troubleshooting tracking issues. |
| generate_codeA | Generates TypeScript or JavaScript code from a tracking specification or data layer. Includes type definitions, helper functions, and event tracking code. |
| parse_tracking_specA | Parses tracking specifications from CSV or JSON format (e.g., exported from Google Sheets or Excel). Normalizes the data into a structured format. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Standard Data Layer Schema | Basic schema for page, user, and event data |
| E-commerce Schema | Schema for product, cart, and transaction tracking |
| Hotel Industry Schema | Schema for hotel search, booking, and guest tracking |
| Basic Data Layer Template | Minimal data layer setup with page and user tracking |
| Hotel Booking Template | Complete hotel booking funnel data layer implementation |
| Tealium Best Practices | Best practices guide for Tealium data layer implementation |
TDQS
Scored across 5 tools
Most tools are distinct, but validate_data_layer and debug_data_layer have significant overlap: both analyze a data layer for errors and issues. The descriptions differ in focus (schemas/best practices vs. common issues/missing variables), but an agent could easily confuse which to use for troubleshooting.
All five tool names follow a consistent verb_noun snake_case pattern: validate_, generate_, debug_, parse_, generate_. The pattern is predictable and clearly conveys the action and target.
Five tools is well-scoped for a data layer/tracking specification utility server. Each tool covers a distinct phase (parse, validate, debug, generate docs, generate code) without unnecessary bloat.
The toolset covers a complete workflow: parse raw specs, validate/debug data layers, and generate documentation or code. Minor gaps exist, such as no tool to edit or transform an existing data layer definition directly, but the core lifecycle is well represented.