CryptoAd Network

End an ad

archive_ad

DestructiveIdempotent

Ends an ad for good (Banner, Native, Paid Visits). What it has not spent returns to the balance. It cannot be started again.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "archive_ad"
  }
}

Input Schema

Name	Required	Description	Default
`ad_id`	Yes	The id of an ad of this account.
`api_key`	No	The API key of the account (can_live_...). Optional when this MCP connection sends it as the Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real substance beyond them: unspent budget returns to the account balance and the ad is permanently unstartable. It does not say what happens to historical stats or whether ending an already-ended ad errors, which is the remaining gap.

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?

Three short sentences, zero filler, with the core action and its permanence front-loaded before the financial consequence. Every sentence carries distinct information.

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 two-parameter destructive tool with an output schema absent, the description covers the essential consequences (permanent end, budget refund). Only a note on the response or behavior on already-archived ads would make it complete.

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 coverage is 100%, so ad_id and api_key are already fully documented in the input schema. The description adds no extra meaning about parameter format or constraints, 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 ("Ends an ad") and pins down scope with the supported ad types (Banner, Native, Paid Visits). The phrases "for good" and "cannot be started again" distinguish it from the reversible pause_ad/resume_ad siblings without needing their schemas.

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?

The irreversibility clause gives a clear condition for use: only when the ad should never run again. It stops short of naming pause_ad as the alternative for temporary stops, so the guidance is strong but implicit rather than explicit.

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

All CryptoAd Network 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?