ShortsIntel

Switch tracker analysis on or off

set_tracker_intelligence

Idempotent

Use when switching analysis of new videos or Ads on or off for one Tracker, from its next cycle. Not for a whole Collection: act_on_collection. Not for which videos count: set_tracker_focus. Price: Free. Find it as in get_tracker. The switch is free; on, it spends Credits: +20 credits per new video or Ad analysed, on top of the cycle price.

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": {
      "intelligence": "<intelligence>"
    },
    "name": "set_tracker_intelligence"
  }
}

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.
`intelligence`	Yes	true switches analysis on (spends Credits), false off.

Output Schema

Name	Required	Description	Default
`tracker`	No

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."

Changed4 schema fields changedNov 8, 2026

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": {
+    "tracker": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare a non-read-only, idempotent, non-destructive local mutation, and the description adds context they cannot carry: the change takes effect from the next cycle, the switch action itself is free, and enabling it spends +20 credits per new video or Ad analysed on top of the cycle price. That cost and timing disclosure is exactly the kind of behavioral detail an agent needs before committing.

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?

Roughly four short sentences, front-loaded with the when-to-use and exclusions before cost details. The telegraphed fragment style ('Price: Free.', 'Find it as in get_tracker.') is terse but the pieces are slightly scattered rather than flowing, which costs a point.

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?

For a 5-parameter mutation with an output schema and full annotations, the description covers the remaining burden: selection guidance, alternatives, effective timing, and credit cost. An agent has everything needed to decide and call correctly.

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 100% and the schema already explains the intelligence flag, enum values, and tracker_id precedence, so the description need not repeat it. The one addition is 'Find it as in get_tracker', which helps the agent source target/kind identifiers but is thin guidance. Baseline 3 is appropriate given the schema does the heavy lifting.

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 concrete verb and resource ('switching analysis of new videos or Ads on or off for one Tracker') plus the timing scope ('from its next cycle'). It names the siblings it is not (act_on_collection, set_tracker_focus), so an agent can separate it from those tools 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?

Explicit when-to-use clause opens the description, followed by two explicit when-not clauses that each route to a named alternative. Nothing about selecting this tool versus act_on_collection or set_tracker_focus is left to inference.

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?