CrunchJunkie

remove_tracking_prompt

Destructive

Stop tracking an AI-visibility prompt. Mode deactivate (default) pauses it: no future scans (it also leaves a scan that is queued or running) and every stored answer is kept; update_tracking_prompt (active: true) or Resume on the app's Prompts tab resumes it. Mode delete removes it permanently and cannot be undone: every answer stored for it is deleted with it. Views that count individual answers are recalculated without them for past periods too, and the daily totals stored for past days (the headline visibility in get_ai_visibility_metrics and get_visibility_trend) are rebuilt for the days it was measured on. Both modes write an internal timeline note. Requires MCP write actions; without confirm:true it returns a preview.

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": {
      "promptId": "<promptId>"
    },
    "name": "remove_tracking_prompt"
  }
}

Input Schema

Name	Required	Description
`mode`	No	deactivate (default): pause scanning, keep every stored answer. delete: permanent — removes the prompt AND every answer stored for it; views that count individual answers change for past periods too.
`confirm`	No	Set true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
`promptId`	Yes	Prompt id (from list_prompts).
`previewToken`	No	With confirm:true: the previewToken from this tool's preview (valid 15 minutes, once, for exactly the previewed arguments).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedOct 19, 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 destructiveHint=true annotation by naming exactly what is destroyed (every stored answer for the prompt) versus preserved in deactivate mode, and by disclosing downstream recomputation of answer-level views and stored daily totals used by get_ai_visibility_metrics and get_visibility_trend, plus an internal timeline note. It stops short of stating whether the deletion is scoped per workspace or how long the timeline note is retained, keeping it at a 4 rather than a 5.

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-loads the action and the mode distinction, then layers consequences; every sentence carries operational weight. It is a dense single paragraph, though, and the recomputation clause packs several facts into one long sentence that could be split for faster scanning.

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 destructive 4-parameter tool with no output schema, it covers preconditions (MCP write actions), the preview-without-confirm return behavior, both mode outcomes, resumption paths, and system-wide side effects. An agent has everything needed to call it correctly or to warn a user first.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond it: deactivate also drops a queued or running scan, and delete rebuilds the stored daily totals for past days the prompt was measured on — neither is captured in the schema's mode enum text. The confirm/previewToken flow is restated from the schema rather than extended.

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 ('Stop tracking an AI-visibility prompt') and immediately splits the two behaviors into named modes. It names the sibling tool that reverses the safe mode (update_tracking_prompt with active: true) and the app UI path, so it is distinguishable from add_tracking_prompt and update_tracking_prompt without opening either 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 routes the agent: deactivate is the default non-destructive pause, delete is the permanent path, and resumption goes through update_tracking_prompt or the Prompts tab Resume control. It also names the precondition (requires MCP write actions) and the preview step before applying.

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

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