Skip to main content
Glama

Cancel Submission Tool

cancel-submission-tool
DestructiveIdempotent

Cancel a scheduled, queued or in-flight video submission on any platform — TikTok, Instagram or YouTube. The running pipeline stops driving the phone between steps; a not-yet-started job no-ops.

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": {
      "submission_id": "<submission_id>"
    },
    "name": "cancel-submission-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYesID of the submission to cancel, on any platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavior: cancellation is cooperative ('the running pipeline stops driving the phone between steps') rather than an immediate kill, and it describes the no-op outcome for un-started jobs. It still doesn't say what is returned or what happens if the submission already finished.

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 sentences, no filler, with scope and applicable states front-loaded and the edge-case behavior (no-op) placed second. Nothing is redundant with the title.

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 single-parameter mutation tool with no output schema and full annotation coverage, the description covers scope, states, and the graceful-stop semantics. The remaining gap is outcome reporting: it doesn't indicate what the caller learns when the cancel succeeds, fails, or targets an already-completed submission.

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% for the single submission_id parameter, so the schema already carries the documentation burden. The description only adds that the ID is platform-agnostic ('on any platform'), which is marginally useful but not a real semantics extension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('cancel') against a specific resource ('video submission') and enumerates the applicable states (scheduled, queued, in-flight) plus the cross-platform scope. The sibling set contains delete-submission-tool, and the description never distinguishes cancel from delete, so an agent must still infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clarifies which submission states this applies to and that a not-yet-started job no-ops, which implicitly guides usage. It gives no explicit when-to-use-vs-alternative guidance, particularly relative to delete-submission-tool, which is the sibling most likely to be confused with this one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources