ShortsIntel

Get a tracker

get_tracker

Read-onlyIdempotent

Use when you need one Tracker's kind, platform, target, state and analysis switch, and with a focus its latest in-focus sample. Not for what changed: get_changes. Not for starting one: track (an untracked target here is not_found). Price: Free. Find it by tracker_id, or by platform + target as track takes them. With a focus, off-focus videos are hidden and counted in off_focus_count (a creator Tracker returns recent_videos); include_off_focus=true shows every verdict.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tracker"
  }
}

Input Schema

Name	Required	Description
`kind`	No	If the target is tracked as several kinds.
`target`	No	Creator handle (@ optional), or an Advertiser's id or URL.
`platform`	No	With target. Needed unless kind=advertiser (meta or none).
`tracker_id`	No	Tracker id; wins over target.
`include_off_focus`	No	With a Focus: true returns every sampled Video with its verdict and reason, off-focus ones included.

Output Schema

Name	Required	Description
`sample`	No	Only on a Tracker with a Focus: its latest Sample through the Focus.
`tracker`	No
`recent_videos`	No	Only on a Creator Tracker with a Focus: its newest Videos through the Focus.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "tiktok",
-  "instagram",
-  "youtube",
-  "facebook",
-  "meta"
-]New value: +[
+  "tiktok",
+  "instagram",
+  "youtube",
+  "facebook",
+  "meta",
+  "google"
+]

changedInput schema / properties / target / description

Previous value: -"Creator handle (@ optional), or an Advertiser's Page id or URL."New value: +"Creator handle (@ optional), or an Advertiser's id or URL."

Changed5 schema fields changedNov 8, 2026

changedInput schema / properties / include_off_focus / description

Previous value: -"A Tracker with a Focus: true returns every sampled Video with its focus verdict and reason, off-focus ones included."New value: +"With a Focus: true returns every sampled Video with its verdict and reason, off-focus ones included."

changedInput schema / properties / kind / description

Previous value: -"Only if the target is tracked as several kinds."New value: +"If the target is tracked as several kinds."

changedInput schema / properties / platform / description

Previous value: -"With target, finds the Tracker. Needed unless kind=advertiser (an Advertiser takes meta or none)."New value: +"With target. Needed unless kind=advertiser (meta or none)."

changedInput schema / properties / target / description

Previous value: -"Creator handle (@ optional), or an Advertiser's Facebook Page id or URL."New value: +"Creator handle (@ optional), or an Advertiser's Page id or URL."

changedInput schema / properties / tracker_id / description

Previous value: -"The Tracker's id. Wins over platform and target."New value: +"Tracker id; wins over target."

Changed5 schema fields changedNov 5, 2026

changedInput schema / properties / kind / description

Previous value: -"Only when the same target is tracked as more than one kind."New value: +"Only if the target is tracked as several kinds."

changedInput schema / properties / platform / description

Previous value: -"With target, finds the Tracker. Needed unless kind=advertiser: for an Advertiser pass meta, or omit it and set kind=advertiser."New value: +"With target, finds the Tracker. Needed unless kind=advertiser (an Advertiser takes meta or none)."

changedInput schema / properties / target / description

Previous value: -"Creator handle (with or without @), or an Advertiser's Facebook Page id or Page URL."New value: +"Creator handle (@ optional), or an Advertiser's Facebook Page id or URL."

changedOutput schema / properties / tracker / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / tracker / properties
```
Removed value: -{}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "recent_videos": {
+      "$ref": "#/properties/tracker",
+      "description": "Only on a Creator Tracker with a Focus: its newest Videos through the Focus."
+    },
+    "sample": {
+      "$ref": "#/properties/tracker",
+      "description": "Only on a Tracker with a Focus: its latest Sample through the Focus."
+    },
+    "tracker": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds non-obvious behavior: focus hides off-focus videos and reports them via off_focus_count, a creator Tracker returns recent_videos, and the call is free of credit cost. It stops short of describing pagination or sample-size limits, so it is strong but not exhaustive.

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?

Front-loaded with the 'Use when' clause, then exclusions, then cost, then mechanics – good ordering with no filler. The telegraphic fragments ('with a focus', 'as track takes them') save space but require a careful read.

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?

An output schema exists, so return-value detail is unnecessary; the description instead supplies what the schema cannot – lookup paths, focus-filtering behavior, cost, and routing to siblings. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: two lookup paths (tracker_id vs platform+target, the latter mirroring track), the precedence of tracker_id, and the fact that include_off_focus changes both returned verdicts and the off_focus_count tally. The kind parameter's disambiguation role is only lightly covered.

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 and enumerates what is returned (kind, platform, target, state, analysis switch, latest in-focus sample), which lets an agent distinguish it from get_changes and track without opening any 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?

Explicitly names the two adjacent alternatives and the condition that rules them out: 'Not for what changed: get_changes' and 'Not for starting one: track', plus the note that an untracked target here yields not_found. That is genuine when/when-not guidance rather than implied context.

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

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