Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Pause tracking

pause_tracking
Idempotent

Turns off scheduled scans for a tracked competitor and returns tracking: false. Ads already collected are not deleted. The current paid month is not refunded and a scan that is already running is not cancelled. resume_tracking turns tracking back on.

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": "pause_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitor_idYesCompetitor id from list_competitors.

Output Schema

NameRequiredDescriptionDefault
replayedNoreplayed value in this response.
trackingNoWhether tracking is enabled after this operation.
cost_creditsNoCredits quoted or charged by this operation.
competitor_idNoReference for the selected rival.
original_reservation_creditsNooriginal reservation credits value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=false, idempotentHint=true), it discloses the exact side effects that matter: collected ads remain, the paid month is not refunded, and an in-flight scan keeps running. That is precisely the billing and in-flight-work context annotations cannot convey, and it is consistent with idempotent, non-destructive hints.

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?

Four short sentences, each conveying a distinct and non-redundant fact, with the primary action front-loaded and the caveats following. Nothing is padded or repeated from the name or schema.

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 one-parameter mutation with an output schema and full annotation coverage, the description covers the action, its limits, the billing consequence, and the inverse tool. An agent has everything needed to call it correctly and predict the result.

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?

There is a single required parameter with 100% schema description coverage ('Competitor id from list_competitors'), so the schema already carries the semantics. The description adds no further parameter detail, which is acceptable at this schema coverage but is only baseline value.

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 states a precise verb and resource ('Turns off scheduled scans for a tracked competitor') and even names the observable effect ('returns tracking: false'), which makes it immediately distinguishable from siblings like resume_tracking and get_tracking_status.

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 explicitly names resume_tracking as the inverse operation and states what pausing does not affect, giving a clear context for choosing this tool. It does not spell out when to prefer get_tracking_status or when pausing is inappropriate, so it stops short of full when/when-not guidance.

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

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