ShortsIntel

Pause or resume a tracker

set_tracker_state

Idempotent

Use when pausing or resuming one Tracker; a paused Tracker runs no cycles and is charged nothing. Not for a whole Collection: act_on_collection. To stop for good: delete_tracker. Price: Free. Find it as in get_tracker. Resuming restarts its daily cycles at the usual 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": {
      "state": "<state>"
    },
    "name": "set_tracker_state"
  }
}

Input Schema

Name	Required	Description
`kind`	No	If the target is tracked as several kinds.
`state`	Yes	paused stops the cycles; active resumes them.
`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.

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

Behavior4/5

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

Goes well beyond the annotations: a paused Tracker 'runs no cycles and is charged nothing', the action is free, and resuming restarts daily cycles 'at the usual price'. That billing/cycle consequence is the key non-obvious behavior of this mutation and is not derivable from readOnlyHint=false, idempotentHint=true, destructiveHint=false. It stops short of covering error cases (e.g. resuming an over-quota tracker) or what happens to in-flight cycle data.

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?

Very tight and front-loaded: the primary use case is sentence one, alternatives follow, cost last. The telegraphic fragment style ('Price: Free.', 'Find it as in get_tracker.') is efficient but slightly cryptic and relies on the reader knowing get_tracker.

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, the description covers the selection decision, the sibling alternatives, the cost implication of both states, and where to obtain the identifier. Nothing an agent needs in order to call it 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 description coverage is 100%, so the baseline is 3, but 'Find it as in get_tracker' adds cross-tool meaning for how target/platform/kind are resolved to a single tracker — a rule the schema only hints at piecewise ('wins over target'). This is genuine added semantics rather than restatement.

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 (pause/resume) and resource (one Tracker / tracker state), and explicitly separates itself from act_on_collection (collection-wide) and delete_tracker (permanent stop). An agent can pick this tool 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?

Gives explicit when-to-use (pausing or resuming one Tracker), an explicit when-not with the correct alternative (whole Collection → act_on_collection), and the permanent-stop alternative (delete_tracker). The pause-vs-delete distinction is exactly the ambiguity an agent would otherwise guess at.

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?