Skip to main content
Glama
Sign In
queue-inspector-mcp

queue-inspector-mcp

by Yusufihsangorgel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete job

delete_job
Destructive

Permanently remove a job from a queue by its ID. Only inactive jobs can be deleted.

Instructions

Permanently delete a job from a queue. Active jobs cannot be deleted. Faithfully replicates the backend's own delete (asynq Inspector.DeleteTask, bullmq Job.remove).

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": "<queue>",
      "id": "<id>"
    },
    "name": "delete_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob or task id.
queueYesQueue name, as reported by list_queues.
backendNoWhich backend owns the queue. Optional when the queue name is unique across backends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description adds context beyond the destructiveHint annotation, stating the deletion is permanent and cannot delete active jobs. It also mentions replicating backend behavior, which is useful for understanding side effects.

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?

The description is extremely concise with two sentences, front-loading the main action and constraints. No superfluous 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 delete operation, the description covers key constraints and backend fidelity. It lacks information about the return value or error behavior, but the context is sufficient for a simple tool.

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 the schema already describes all parameters. The description does not add additional semantics beyond what is in the schema.

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 clearly states the action 'permanently delete' and the resource 'job from a queue'. It distinguishes from siblings like get_job, list_jobs, retry_job by specifying deletion and noting that active jobs cannot be deleted.

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 description explicitly says 'Active jobs cannot be deleted', providing a clear when-not condition. However, it does not explicitly guide when to use this tool over alternatives like retry_job or list_jobs.

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