CrunchJunkie

set_link_monitor

Switch a client's weekly spam check on or off. ON reads the client's recent history once (a few cents) and then checks its new linking domains every Monday, within ONE monthly cap for all the workspace's clients (capUsd: 1, 2, 5 or 10, in DataForSEO's USD; on the Rank Tracker budget at most 2x that): the preview states the cap, what it covers, the account it runs on and the one-time read; switching on again with another cap changes the cap, and confirms a check paused by an account-type change. OFF stops it and resolves its open Signal. Requires write actions (and, to switch on, "Allow actions that spend AI"). 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": {
      "clientId": "<clientId>",
      "on": "<on>"
    },
    "name": "set_link_monitor"
  }
}

Input Schema

Name	Required	Description
`on`	Yes	true switches the check on (or confirms / changes it), false switches it off.
`capUsd`	No	Switching on: the workspace's monthly cap in DataForSEO's USD. Default: the cap already set, else 2.
`domain`	No	Switching on: the domain to check. Default: the client's own.
`confirm`	No	Set true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
`clientId`	Yes	Client id (from list_clients).
`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.

AddedNov 6, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well past the annotations by disclosing real cost (a one-time read of a few cents), the workspace-wide monthly cap and its Rank Tracker budget ceiling, required write/spend permissions, and that OFF resolves the open Signal. It also documents the preview/confirm safety flow and previewToken validity (15 minutes, single use, exact arguments), which is exactly the extra context an agent needs before a paid mutation.

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 second sentence is a long run-on with stacked parentheticals (cap formats, Rank Tracker multiplier, account, one-time read) that is hard to parse in one pass. The content earns its place, but the structure could be broken into discrete statements.

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 a 6-parameter mutation with no output schema and only minimal annotations, the description covers cost, permissions, preview mechanics, cap scope and side effects. The residual gap is the exact shape of the preview response, though the description does summarize what the preview states.

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 100%, so the baseline is 3; the description earns more by explaining that capUsd is a workspace-wide monthly cap covering all clients, that defaults fall back to the existing cap then 2, and that previewToken comes from this tool's own preview. Only the domain default is left purely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: "Switch a client's weekly spam check on or off," and the ON branch clarifies it monitors new linking domains. That distinguishes it from read-oriented siblings like get_link_monitor and run_link_lookup, though it never names those siblings explicitly.

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?

States the when-to-use cases clearly (ON to start/change a cap, OFF to stop and resolve its open Signal, re-ON to confirm a paused check). What's missing is an explicit pointer to the read-side alternative (get_link_monitor) for pure status checks, so the agent must infer that routing.

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?