ShortsIntel

Delete a tracker

delete_tracker

DestructiveIdempotent

Use when the Customer wants one Tracker gone for good: its cycles stop. Not for a break: set_tracker_state (paused). Not for leaving one Collection: remove_from_collection. Price: Free. Find it as in get_tracker. Its Change Reports stay readable; tracking the target again starts a new Tracker.

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

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 destructiveHint=true and idempotentHint=true, but the description adds consequences the annotations cannot express: cycles stop, Change Reports remain readable, and re-tracking the target creates a new Tracker. It also notes the operation is free, which is real operational context.

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 case, then exclusions, then cost, then consequences — a sensible ordering with no filler. The telegraphic fragments ('Price: Free.') are efficient but slightly clipped, keeping it just below a 5.

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 and annotations carry the safety profile, so the description only needs to cover intent and consequences — which it does, including what survives deletion and what happens on re-tracking. 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.

Parameters3/5

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

Schema description coverage is 100%, so the four parameters (kind, target, platform, tracker_id) are already fully documented, including the 'tracker_id wins over target' precedence. The description only adds the pointer 'Find it as in get_tracker', which is a mild identification hint rather than parameter-level detail, so the baseline 3 applies.

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 ('one Tracker gone for good') plus the concrete effect ('its cycles stop'), and explicitly distinguishes itself from set_tracker_state and remove_from_collection. An agent can identify the right 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 ('gone for good'), when-not-to-use with two named alternatives ('Not for a break: set_tracker_state (paused). Not for leaving one Collection: remove_from_collection'), and a cost note. Nothing 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?