CrunchJunkie

add_tracking_prompt

Add AI-visibility tracking prompts for a client — queries to monitor across AI engines (e.g. "best CRM for startups"): one with text, or a set with prompts (up to 50) under one preview and one confirmation; how many is the user's choice (suggest_prompts without count gives the advice). A prompt the project already tracks in that market is skipped (a paused one is named), and a trial workspace keeps its active-prompt allowance; the preview lists what will be added and what is left out. Requires MCP write actions; without confirm:true it returns a preview.

Input Schema

Name	Required	Description
`tags`	No	Tags for the prompt (with text), e.g. ["stage: consideration", "intent: free crm"]. Up to 25, 40 chars each.
`text`	No	One prompt/query to track. Or pass prompts for several.
`market`	No	The market the prompt is scanned in, as a locale ("de-DE", "en-US", or a language alone such as "de"). It is one of the project's markets (list_prompts lists them under markets; add_market adds one). Omit for the project's own market. Write the prompt in that market's language.
`confirm`	No	Set true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
`prompts`	No	Several prompts at once (up to 50), each with its own optional category and tags (e.g. the tags suggest_prompts returned). All go to the same market.
`category`	No	Prompt category (with text). Passed = the person's choice, kept as given and never re-filed automatically. Omitted = discovery, except that a prompt naming the brand or one of its aliases is filed as brand (the result's note says so; discovery files a general question).
`clientId`	Yes	Client id (from list_clients). The client needs an AI-visibility project.
`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.

Changed3 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
```
- removedInput schema / properties / prompts / items / additionalProperties
```
Removed value: -false
```

Changed5 schema fields changedOct 23, 2026

changedInput schema / properties / category / description

Previous value: -"Prompt category. Passed = the person's choice, kept as given and never re-filed automatically. Omitted = discovery, except that a prompt naming the brand or one of its aliases is filed as brand (the result's note says so; discovery files a general question)."New value: +"Prompt category (with text). Passed = the person's choice, kept as given and never re-filed automatically. Omitted = discovery, except that a prompt naming the brand or one of its aliases is filed as brand (the result's note says so; discovery files a general question)."

addedInput schema / properties / prompts

Added value: +{
+  "description": "Several prompts at once (up to 50), each with its own optional category and tags (e.g. the tags suggest_prompts returned). All go to the same market.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "category": {
+        "enum": [
+          "discovery",
+          "brand",
+          "competitor",
+          "shopping"
+        ],
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 25,
+        "type": "array"
+      },
+      "text": {
+        "maxLength": 2000,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Tags for the prompt (with text), e.g. [\"stage: consideration\", \"intent: free crm\"]. Up to 25, 40 chars each.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 25,
+  "type": "array"
+}

changedInput schema / properties / text / description

Previous value: -"The prompt/query to track."New value: +"One prompt/query to track. Or pass prompts for several."

changedInput schema / required

Previous value: -[
-  "clientId",
-  "text"
-]New value: +[
+  "clientId"
+]

Changed3 schema fields changedOct 22, 2026

changedInput schema / properties / category / description

Previous value: -"Prompt category. Passed = the person's choice, kept as given and never re-filed automatically. Omitted = discovery, except that a prompt naming the brand or one of its aliases is filed as brand (the result's note says so; pass discovery if it is a general question)."New value: +"Prompt category. Passed = the person's choice, kept as given and never re-filed automatically. Omitted = discovery, except that a prompt naming the brand or one of its aliases is filed as brand (the result's note says so; discovery files a general question)."

changedInput schema / properties / clientId / description

Previous value: -"Client id (from list_clients). The client must have an AI-visibility project."New value: +"Client id (from list_clients). The client needs an AI-visibility project."

changedInput schema / properties / market / description

Previous value: -"The market the prompt is scanned in, as a locale (\"de-DE\", \"en-US\", or a language alone such as \"de\"). It must be one of the project's markets (list_prompts lists them under markets; add_market adds one). Omit for the project's own market. Write the prompt in that market's language."New value: +"The market the prompt is scanned in, as a locale (\"de-DE\", \"en-US\", or a language alone such as \"de\"). It is one of the project's markets (list_prompts lists them under markets; add_market adds one). Omit for the project's own market. Write the prompt in that market's language."

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds substantial behavior: the preview/confirm two-step, previewToken validity (15 minutes, single use, bound to previewed arguments), duplicate skipping with named paused prompts, and trial workspace allowance limits. This is well beyond what the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the remainder is one sprawling sentence stitched with em-dashes and nested parentheticals ('...one preview and one confirmation; how many is the user's choice (suggest_prompts without count gives the advice)...'), which is dense and hard to parse in a single pass.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no output schema, the description covers the critical call mechanics (preview token, confirm gating, duplicate handling, trial limits). Only minor gaps remain, such as the exact success response shape, which the preview mechanism largely addresses.

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 schema already documents every parameter, including the category defaulting rule and market locale guidance. The description adds marginal value, mainly reiterating the text-vs-prompts choice and the 50-prompt cap already present in the schema, 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: 'Add AI-visibility tracking prompts for a client — queries to monitor across AI engines', with a concrete example query. It implicitly distinguishes itself from suggest_prompts (advice) and update_tracking_prompt (edit existing) so an agent can route correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the two input modes (single text vs. a prompts set), points to suggest_prompts for deciding how many, and states the confirm:true gating for preview vs. apply. It does not explicitly say when to prefer update_tracking_prompt over this tool, but the usage context is otherwise clear.

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?