Skip to main content
Glama

Coline

List deleted tasks

list_deleted_tasks
Read-onlyIdempotent

Lists recently deleted tasks on a board, newest first, so one can be restored.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>"
    },
    "name": "list_deleted_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.

Output Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description does add useful behavior beyond them: newest-first ordering and a deleted-only scope. It leaves undefined how far back "recently" reaches and whether results are paginated or capped.

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?

A single sentence with zero filler, front-loading the verb, resource, and ordering before the purpose clause. Nothing needs trimming and nothing is buried.

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 value shape needn't be described. For a list tool with a limit parameter and a vague "recently" retention window, though, the description should say how far back the listing reaches and how limit/paging behaves; both are absent.

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 67%: workspace and taskboardId are documented in the schema, and "on a board" loosely maps to taskboardId, but the limit parameter has no explanation anywhere. The description adds no meaning about scoping, ordering interaction with limit, or default page size.

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 and resource ("Lists recently deleted tasks on a board") plus ordering ("newest first"), which is enough to distinguish it from list_tasks or filter_tasks by scope. However, it never explicitly contrasts itself with those siblings, so an agent must infer the deleted-only scope is the differentiator.

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?

The trailing clause "so one can be restored" implies the use case (find a deleted task prior to restore), which is a genuine contextual cue. It offers no explicit when-not guidance, no named alternative for listing live tasks, and no prerequisites such as required permissions for viewing deleted items.

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