jptb-google-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JPTB_CONNECTION_ID | Yes | Connection ID from 'Connect Google' in the JP Agent Tracking Bridge admin | |
| JPTB_SESSION_TOKEN | Yes | Session token from 'Start Tagging' in the JP Agent Tracking Bridge admin |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gtm_list_accountsC | List GTM accounts accessible to the connected Google user. |
| gtm_list_containersC | List containers in a GTM account. |
| gtm_get_containerB | Get a single GTM container's details. |
| gtm_list_workspacesB | List workspaces in a GTM container. |
| gtm_list_tagsA | List tags in a GTM workspace (inspect-first; do not touch unrelated tags). |
| gtm_list_triggersC | List triggers in a GTM workspace. |
| gtm_list_variablesC | List variables in a GTM workspace. |
| gtm_list_versionsA | List version headers (published + drafts) of a GTM container. |
| gtm_get_versionB | Get a single GTM container version's full content. |
| gtm_resolveA | Resolve a GTM container publicId (e.g. GTM-XXXX) to account_id/container_id/workspace_id. Defaults to the customer's configured container. |
| gtm_create_tagB | Create a GTM tag (full tag object). Use predictable JPTB naming; reuse/update an equivalent existing JPTB tag instead of duplicating. |
| gtm_update_tagC | Update an existing GTM tag by id. |
| gtm_create_triggerB | Create a GTM trigger (full trigger object). |
| gtm_update_triggerB | Update an existing GTM trigger by id. |
| gtm_create_variableC | Create a GTM variable (full variable object). |
| gtm_update_variableC | Update an existing GTM variable by id. |
| gtm_create_versionA | Create a GTM container version from a workspace (does NOT publish). |
| gtm_publish_versionB | Publish a prepared GTM version to live. PRIVILEGED: only call after explicit user approval. |
| ga4_list_accountsA | List GA4 account/property summaries accessible to the connected Google user. |
| ga4_get_propertyA | Get a GA4 property's details (by numeric property id, not measurement id). |
| ga4_list_data_streamsC | List data streams for a GA4 property. |
| ga4_run_realtime_reportA | Run a GA4 realtime report (read-only). report = {dimensions:[{name}], metrics:[{name}], ...}. IMPORTANT: realtime has minutes-scale ingestion latency. An empty result is NOT proof an event was dropped. Wait at least 5 minutes after the last event and/or calibrate with a unique direct /g/collect canary hit before concluding. See docs/GA4-LATENCY.md. |
| ga4_run_reportA | Run a GA4 standard report (read-only). report = {dateRanges:[{startDate,endDate}], dimensions, metrics, ...}. |
| ga4_resolveA | Resolve a GA4 measurement id (e.g. G-XXXX) to numeric property_id + stream. Defaults to the customer's configured measurement id. |
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 24 tools
Each tool is scoped by a clear product prefix (gtm_/ga4_) and a specific resource/action, so tags, triggers, variables, versions, and GA4 reporting tools are all easily distinguishable. The two resolve tools are also cleanly separated by domain. There is no meaningful overlap between tools.
Tools overwhelmingly follow a product_verb_noun pattern in snake_case, such as gtm_list_tags, gtm_update_trigger, and ga4_run_report. The only minor deviation is gtm_resolve and ga4_resolve, which omit an explicit noun object, though they are still consistent with each other and easy to understand.
24 tools is above the typical 3-15 sweet spot and feels slightly heavy, but the count is justified by covering two distinct Google products with multiple subresources. Each tool has a specific purpose, so the set is not bloated or redundant.
The GTM toolset covers the core tag/trigger/variable workflow through create, update, version, and publish, and the GA4 toolset covers property lookup and reporting. Minor gaps exist, such as no delete operations for GTM resources and no individual get for tags/triggers/variables, but these can generally be worked around with list operations.