Skip to main content
Glama
519,423 tools. Updated 2026-09-06 07:28

"Google Tag Manager" matching MCP tools:

  • Read and write Google Tag Manager objects: accounts, containers, workspaces, tags, triggers, variables. Create versions and publish with real write actions.
    Apache 2.0
  • Lists all Google Tag Manager accounts accessible to the authorized user, returning account IDs, paths, and names. Use this entry point to obtain the accountId required by every other tool.
    MIT
  • Create a tag, trigger, or variable in a Google Tag Manager workspace by providing the resource JSON with name and type, plus optional parameters and trigger IDs for tags. Returns the created resource with its assigned ID and fingerprint.
    MIT
  • Execute raw Google Tag Manager API v2 calls for any endpoint, managing authentication, rate limits, and retries automatically, so you can perform actions unavailable in dedicated tools.
    MIT
    Destructive
  • List all Google Tag Manager accounts accessible to you, with an optional filter to include Google Tag accounts.
    Apache 2.0

Matching MCP Servers

Matching MCP Connectors

  • List all workspaces in a Google Tag Manager container to get workspace IDs, including the default workspace, required for every tag, trigger, and variable operation.
    MIT
  • Delete a Google Tag Manager tag, trigger, or variable by API path. Provide the path exactly as returned in the resource's path field; success returns an empty response.
    MIT
    Destructive
  • List Google Tag Manager entities one hierarchy level at a time, returning concise summaries with paths to drill down or fetch full details.
    MIT
  • Retrieve all Google Tag Manager accounts accessible via the service account, returning their IDs, names, and paths. Use this to identify available accounts and obtain their identifiers for subsequent management tasks.
    MIT
  • Retrieve a specific Google Tag Manager account by its ID to access account details like name, path, and sharing settings, enabling quick verification or management of account configuration.
    MIT
  • Retrieve all containers in a Google Tag Manager account by providing the account ID. Use this to view and manage your GTM containers.
    Apache 2.0
  • Scan a page's HTML to find analytics and advertising tracking tags such as GA4, Google Tag Manager, Meta Pixel, and consent platforms, reporting each tag's ID and location.
    MIT
  • Save Google OAuth client ID and client secret to authenticate with Search Console, Indexing, Analytics, and Tag Manager APIs.
    MIT
  • Create a Google Tag Manager tag with predictable JPTB naming, reusing an existing equivalent tag to prevent duplicates.
    MIT
  • Create tracking pixels for conversions and microconversions to measure marketing performance in Google Tag Manager. Specify event types like sales or newsletter signups with optional monetary values.
    MIT
  • Lists all tags within a specified Google Tag Manager workspace using account, container, and workspace IDs.
    MIT
  • Manage Google Tag Manager tags by getting, listing, creating, updating, or deleting them within a specified account, container, and workspace.
    Apache 2.0