Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_telegram_action_queue_cancel

Cancels all still-queued actions in a local Telegram action queue after explicit confirmation, leaving already sent or failed actions unchanged.

Instructions

Cancel all still-queued actions in one local Telegram action queue. Requires confirm=true; already sent or failed actions are not changed.

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": {
      "queue_id": "<queue_id>",
      "confirm": "<confirm>"
    },
    "name": "ads_telegram_action_queue_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesExplicitly confirm cancelling the queued actions
queue_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and meaningfully discloses that this is a bulk cancellation affecting only still-queued actions, that confirmation is required, and that sent/failed actions are unaffected. It could go further by stating whether cancellation is irreversible or what the result looks like.

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?

Two short sentences, front-loaded with the operation and followed by the confirmation requirement and scope constraint. There is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter cancellation tool, the description covers the main behavioral constraints and mutation scope. However, without annotations or an output schema, it leaves queue_id semantics and the result of the operation underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: confirm is documented in both schema and description, but queue_id has no description anywhere and the description does not compensate by explaining where it comes from or what it identifies.

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 specific verb and resource: cancel all still-queued actions in one local Telegram action queue. The scope ('still-queued', 'one local queue') and exclusion of sent/failed actions clearly distinguish this from list/process/create siblings.

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 for cancelling queued actions and states the confirm=true prerequisite. It also gives an exclusion by noting that already sent or failed actions are not changed, though it does not explicitly name an alternative sibling such as queue_process.

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

Deploy Server

Other Tools