StealAds

Start tracking

start_tracking

Idempotent

Turns on tracking for a competitor already saved under a brand, so StealAds collects that advertiser's new ads on a schedule. add_competitor with track: true saves and tracks a new competitor in one call. 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": "start_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.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly false, destructive false, idempotent true), and the description adds the behavior that matters: a preview-first cost flow that spends nothing without confirm, a required ceiling and idempotency key echoed back from the preview, 15-minute key validity, no double charge on repeat, and a free no-op if already tracked.

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 what the tool does, then the sibling alternative, then the paid flow, the free flow, and the already-tracked edge case — each sentence carries distinct information. The paid-flow sentence is dense, packing the preview/confirm contract into one clause, but no wording is filler.

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 a cost-confirmation gate, the description covers every branch an agent must handle: preview, confirmed execution, free execution, idempotent replay, and already-tracked. Return values are handled by the existing output schema, so nothing essential is missing.

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 baseline is 3, but the description adds real meaning by explaining how the four parameters interlock in sequence — the preview returns idempotency_key and max_credits, which must be sent back unchanged with confirm: true. It stops short of new syntax detail beyond what the schema already states for each field.

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 ('Turns on tracking for a competitor already saved under a brand') and the concrete effect ('StealAds collects that advertiser's new ads on a schedule'). It explicitly contrasts with the sibling add_competitor with track: true, so an agent can pick between the two 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: use add_competitor with track: true to save-and-track a new competitor in one call, use this tool for a competitor already saved. It also spells out the two-step condition (credits charged) versus the single-call condition (no credits), and the already-tracked no-op case.

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.