Tracklution

Get container details

get_container

Read-only

Detail view of one container — reveals which event names are tracked and which connectors (Google Ads, Facebook, GA4, etc.) are active.

USE WHEN:

You need the exact event names to pass as event_name filter on get_report / list_events (don't guess names like "Purchase" — check here first).
You need the connector alias for get_report's connector= filter.
The user asks "what's set up on site X?" or "which integrations are live?".

Call list_containers first to find the trc_ ID. Returns no time-series or event data — pair with get_summary / get_report for that.

Input Schema

Name	Required	Description	Default
`server_name`	No	Server name (required when connected to multiple servers). Use list_containers to see available servers.
`container_id`	Yes	The container ID (starts with "trc_"). Use list_containers to find available IDs.

Output Schema

Name	Required	Description	Default
`container`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 20, 2026

changedOutput schema / properties / container / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / container / properties / client / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "id": {
-        "type": "string"
-      },
-      "name": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "name"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "name"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / container / properties / connectors / items / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / container / properties / event_names / items / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / container / properties / pii_restricted
```
Added value: +{
+  "type": "boolean"
+}
```

First observedSep 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that with the negative scope ("no time-series or event data") and the ordering prerequisite, though it says nothing about auth requirements or response shape.

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?

Front-loaded with the core purpose, then organized into scannable USE WHEN bullets with a closing scope note. Every sentence carries information; there is no filler.

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

Completeness5/5

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

With an output schema present, return values need no prose explanation, and the description still supplies the two things an agent actually needs — the list_containers prerequisite and how this tool pairs with get_summary/get_report. Nothing material is missing.

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 description coverage is 100%, so both parameters (server_name, container_id) are already fully documented with the trc_ prefix hint and the list_containers pointer. The description reinforces the container_id lookup but adds no syntax or format detail beyond the schema — baseline 3 is correct.

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?

"Detail view of one container" names a specific verb and resource, then specifies exactly what it reveals (tracked event names, active connectors) — information an agent can use to distinguish it from list_containers and get_report without opening a schema.

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

Usage Guidelines5/5

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

A dedicated USE WHEN block gives explicit triggers (need event names, need connector alias, user asks what's set up) and names the sibling tools each feeds into. It also flags the prerequisite (call list_containers first) and explicitly states what it does NOT return.

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

All Tracklution 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?