Skip to main content
Glama

instagram_reel_cancel

Cancel a queued or running Reel job by job ID and wait for cleanup to complete, stopping unwanted processing and freeing the job slot.

Instructions

Cancel a queued or running Reel job and wait for cleanup.

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": {
      "job_id": "<job_id>"
    },
    "name": "instagram_reel_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=false, and destructive=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the call blocks until cleanup finishes ('wait for cleanup'), which an agent needs to know for timeouts. It says nothing about failure modes such as cancelling an already-finished job, which is a meaningful gap for a non-idempotent mutation.

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?

One front-loaded sentence with no filler; every clause carries information. It is arguably terse enough that the missing error and prerequisite context noted above would have fit without bloat.

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?

An output schema exists, so return values need no explanation, and the single parameter is simple. However, for a non-idempotent mutation the definition leaves out what happens when the job is already terminal, whether the call is retryable, and whether cancellation is reversible — all of which an agent would benefit from knowing before invoking it.

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 description coverage is 0% and the single parameter, job_id, is never mentioned in the description. 'Reel job' gives enough surrounding context that job_id is largely self-evident, so the gap is modest, but the description adds no meaning beyond the schema.

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?

The description states a specific verb and resource ('Cancel a queued or running Reel job'), and the 'queued or running' qualifier implicitly separates it from instagram_reel_start, instagram_reel_status, and instagram_reel_artifact. It never names a sibling tool or redirect, so it falls short of full sibling differentiation, but an agent can pick it out of the catalog confidently.

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?

Usage is only implied: the agent can infer it should call this on a job that is queued or running. There is no explicit guidance on what to do when a job has already completed or failed, and no mention of checking status first via instagram_reel_status before cancelling.

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