AWSYS Links

Cancel Import

cancel_import

DestructiveIdempotent

Cancel an in-flight import job. The orchestrator checks for cancellation between Bitly groups; any short codes already written remain. Returns the job in its final status. Idempotent — calling on an already-terminal job is a no-op.

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

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The jobId to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint), it discloses the cancellation granularity (checked between Bitly groups), the resulting partial state (short codes already written remain), and the return value (job in final status). This is exactly the kind of operational detail an agent cannot infer from the annotation flags.

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, the action and scope front-loaded, and each subsequent sentence adds a distinct fact (partial-write behavior, return value, idempotency). No filler or repetition of the title.

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 no output schema, the description covers what is destroyed, what survives, what is returned, and how repeat calls behave. Nothing material an agent needs before invoking it is missing.

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?

The single job_id parameter is fully described in the schema (100% coverage), and the description adds no additional meaning about its format or where to obtain it. Baseline 3 applies since the schema carries the load.

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 opens with a specific verb and resource ('Cancel an in-flight import job') and the 'in-flight' qualifier scopes it precisely, distinguishing it from get_import_status and other sibling tools without needing the schema.

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 makes clear this is for jobs that are still running and explains that calls against terminal jobs are a no-op, which implicitly tells the agent to check status first. It stops short of explicitly naming get_import_status as the alternative for that check.

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

All AWSYS Links 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?