AdCopilot

GTM: enable built-in variable (staged, never published)

gtm_enable_built_in_variable

Idempotent

Enable a built-in variable in the managed AdCopilot workspace (staged, never published; enable-only: disabling is a delete and is intentionally not exposed).

The first write to a container adds a draft workspace named AdCopilot
if it has none. AdCopilot has no Tag Manager publish permission, so
nothing reaches the website until a person publishes that workspace
in Tag Manager.

Tools revision: d80f65c0.

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": {
      "container": "<container>",
      "type": "<type>"
    },
    "name": "gtm_enable_built_in_variable"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes
`container`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations it discloses non-obvious side effects: the first write to a container creates a draft workspace named AdCopilot, changes are staged and never published, and the service has no publish permission so nothing reaches the live site until a human publishes. This is exactly the behavioral context an agent needs before invoking a write tool.

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

Conciseness4/5

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

The leading sentence front-loads the action and scope, followed by the staging caveat; there is little waste. The trailing 'Tools revision: d80f65c0.' line is irrelevant metadata that dilutes an otherwise tight description.

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

Completeness3/5

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

Return values need not be explained because an output schema exists, and the mutation's side effects and publication semantics are well covered. However, for a two-parameter write tool with zero schema descriptions, the total absence of parameter guidance leaves a real completeness gap.

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

Parameters2/5

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

Schema description coverage is 0% for both required parameters, and the description never explains them. It never says what 'type' accepts (built-in variable names/types) or what form 'container' takes, so an agent must guess the identifier format for a write call.

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?

States a specific verb and resource ('Enable a built-in variable') plus its location ('managed AdCopilot workspace'), and qualifies the operation as 'enable-only'. This cleanly separates it from gtm_create_variable, gtm_update_variable, and gtm_list_built_in_variables among the siblings.

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?

Explicitly frames the operation as enable-only and explains why the inverse path is absent ('disabling is a delete and is intentionally not exposed'), which routes an agent away from attempting a disable. It does not name a sibling to use for checking which built-in variables are already enabled, so the alternative-selection guidance is clear but not fully spelled out.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?