StealAds

Resume tracking

resume_tracking

Idempotent

Turns tracking back on for a saved competitor whose tracking was paused; otherwise the same as start_tracking. When tracking would charge credits it takes two steps: without confirm it returns a cost preview (idempotency_key, max_credits) and changes nothing; the same call with confirm: true and those two values starts tracking. Tracking that costs no credits starts on the first call. A competitor that is already tracked returns tracking: true at no cost.

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": {
      "competitor_id": "<competitor_id>"
    },
    "name": "resume_tracking"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	true starts the paid work shown in the cost preview. Absent or false returns that preview and spends nothing when credits would be charged; an action that costs no credits runs on this call.
`max_credits`	No	max_credits from the cost preview, sent unchanged with confirm: true as the approved credit ceiling. A higher current price needs a new preview.
`competitor_id`	Yes	Competitor id from list_competitors.
`idempotency_key`	No	idempotency_key from the cost preview, needed with confirm: true and valid for 15 minutes. A repeat with the same key returns the first result without a second charge.

Output Schema

Name	Required	Description
`replayed`	No	replayed value in this response.
`tracking`	No	Whether tracking is enabled after this operation.
`billing_url`	No	billing url value in this response.
`max_credits`	No	Explicit credit ceiling to echo after the user approves this quote.
`cost_credits`	No	Credits quoted or charged by this operation.
`what_happens`	No	Plain explanation of the proposed work, confirmation steps and quote expiry.
`competitor_id`	No	Reference for the selected rival.
`enough_credits`	No	enough credits value in this response.
`balance_credits`	No	balance credits value in this response.
`idempotency_key`	No	Key binding confirmation to this preview and preventing duplicate work.
`confirmation_required`	No	True for a cost preview awaiting explicit approval.
`original_reservation_credits`	No	original reservation credits value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026

changedInput schema / properties / competitor_id / description

Previous value: -"Competitor reference from list_competitors (e.g. the returned competitor id)."New value: +"Competitor id from list_competitors."

changedInput schema / properties / confirm / description

Previous value: -"Set to true to spend the credits shown in the preview. Leave it out to see the cost first."New value: +"true starts the paid work shown in the cost preview. Absent or false returns that preview and spends nothing when credits would be charged; an action that costs no credits runs on this call."

changedInput schema / properties / idempotency_key / description

Previous value: -"The idempotency_key from the preview. Required with confirm: true. Repeating a confirmed call with the same key returns the first result and does not spend again."New value: +"idempotency_key from the cost preview, needed with confirm: true and valid for 15 minutes. A repeat with the same key returns the first result without a second charge."

changedInput schema / properties / max_credits / description

Previous value: -"The explicit credit ceiling you approve. For paid confirmation, echo max_credits from the preview unchanged. A higher current price requires a new preview and approval."New value: +"max_credits from the cost preview, sent unchanged with confirm: true as the approved credit ceiling. A higher current price needs a new preview."

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: paid tracking uses a preview-then-confirm flow, confirm without the preview values changes nothing, repeated idempotency keys avoid double charges, and no-cost tracking starts immediately. This is consistent with idempotentHint and the non-read-only annotation.

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

Conciseness5/5

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

The description front-loads the purpose, then explains the conditional credit flow in a compact sequence. Every sentence carries actionable meaning, and there is no redundant restatement of the schema or annotations.

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 mutation tool with an output schema, the description covers the important operational details: paused-competitor scope, paid versus free behavior, cost preview requirements, idempotency, and the already-tracked result. The structured fields handle the remaining parameter and return-value details.

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, but the description adds cross-parameter workflow meaning: confirm, max_credits, and idempotency_key must be used together after a cost preview. It does not fully re-explain every field, but it clarifies how the fields interact during the paid two-step flow.

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?

The description uses a specific verb and resource: it turns tracking back on for a saved competitor whose tracking was paused. It also distinguishes this from start_tracking by saying it otherwise behaves the same, giving an agent a clear routing signal.

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?

It clearly indicates use when a saved competitor's tracking is paused and notes that already-tracked competitors return tracking: true at no cost. It does not explicitly say to use start_tracking instead when the competitor is not paused, but the sibling reference gives strong implied guidance.

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

All StealAds 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.