Skip to main content
Glama
Sign In

Google Tag Manager MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Google Tag Manager Prompts

prompts_menu
Read-only

Browse the Google Tag Manager prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "prompts_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
is_customNo
prompt_idNo
prompt_typeNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, and the description is consistent with a safe catalog-browsing operation. It adds useful behavioral context by distinguishing public/system prompts from workspace prompts and indicating that is_custom plus workspace_id are needed for workspace prompt details, though it does not mention pagination or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded, uses a compact numbered list, and gives only the routing information needed for the two request modes. There is no wasted language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists, the description need not explain return values, and it adequately covers the two request pathways. The main remaining gap is that prompt_type values and some parameter interactions are not fully described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description does substantial work: it maps request='menu' to listing and optional workspace_id/prompt_type, and request='prompt_details' to prompt_id plus is_custom=True and workspace_id for workspace prompts. It still leaves prompt_type's permitted values and some nuances of is_custom underspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Browse the Google Tag Manager prompt catalog,' and then distinguishes two concrete operations, listing prompts and fetching prompt details. This is enough to separate the tool from generic siblings like execute_action and query_data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The numbered modes give clear usage context for request='menu' versus request='prompt_details', including which parameters apply to each mode. It does not explicitly say when to prefer this catalog over sibling tools, but the usage pattern is clear enough for an agent to select it correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Google Tag Manager MCP by InsightfulPipe toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources