Skip to main content
Glama
Sign In
Open Tracked MCP

Open Tracked MCP

Official
by OpenTracked-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

open_tracked_power_ups

List enabled power-ups in an Open Tracked container or toggle one by key (geo_headers, user_agent_info, user_id, custom_loader, cookie_keeper).

Instructions

Power-Ups of a container: 'list' which are on, or 'toggle' one (key such as geo_headers (visitor location), user_agent_info (device info), user_id, custom_loader, cookie_keeper).

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": {
      "action": "<action>",
      "containerId": "<containerId>"
    },
    "name": "open_tracked_power_ups"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
actionYes
containerIdYesThe Open Tracked container id (the number in its address).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Toggle' is a mutation, but the description never says whether the change is immediate and reversible, what state a toggled-off Power-Up leaves behind, or whether elevated permissions are needed. It only adds the vocabulary of the keys, not the consequences of flipping them.

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?

A single sentence that front-loads the resource and then enumerates the two actions, with no filler. The parenthetical key list is dense but each example carries meaning, so nothing is wasted.

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

Completeness2/5

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

For a mutation-capable, three-parameter tool with no annotations and no output schema, the description leaves too much open: what 'list' returns (names? enabled flags?), whether key is conditionally required, and what a successful toggle produces. An agent could call it, but not confidently predict the result.

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

Parameters3/5

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

Schema coverage is only 33%: containerId is documented in the schema, but the description partially compensates by glossing the action enum and giving concrete key examples with meanings (geo_headers = visitor location, user_agent_info = device info). The key parameter remains ambiguous, though — the description does not say whether key is mandatory for 'toggle' or ignored for 'list', which is the main usability question.

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

Purpose4/5

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

States a specific resource (Power-Ups of a container) and the two operations it supports ('list' which are on, 'toggle' one), so an agent can tell it manipulates container add-ons rather than containers or domains. It is clear on its own but never contrasts itself with siblings like open_tracked_containers or open_tracked_gtm_pack.

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

Usage Guidelines3/5

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

The two enum values are effectively explained in-line ('list' which are on vs 'toggle' one), which implies the selection rule. However, there is no guidance on prerequisites (permissions, plan tier), when not to use it, or which sibling to reach for instead.

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

Deploy Server

Other Tools