Skip to main content
Glama
Sign In
feishu-user-plugin

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_task

Permanently remove a task from Feishu using its unique GUID. Ideal for cleaning up completed or unwanted tasks.

Instructions

[Official API + UAT, v1.3.7] Permanently delete a task.

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": {
      "task_guid": "<task_guid>"
    },
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_guidYesTask GUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It states 'permanently' which indicates irreversibility, a key behavioral trait. However, it does not mention auth requirements, side effects on related data, or what happens to associated task members/progress.

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?

The description is a single concise sentence that is front-loaded with the action 'Permanently delete a task'. The prefix '[Official API + UAT, v1.3.7]' is low-value noise but does not significantly detract from clarity.

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?

For a simple 1-parameter destructive operation, the description covers the core action but lacks context on how to retrieve the task GUID, what 'permanently' implies for related data, and any prerequisites or side effects. It is minimally adequate but leaves gaps.

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% with a single parameter task_guid described as 'Task GUID'. The description adds no extra meaning beyond the schema, such as how to obtain the GUID or its format, so the baseline of 3 applies.

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 'Permanently delete a task' with a specific verb (delete) and resource (task). The use of 'permanently' adds important specificity and distinguishes it from related actions like complete_task or update_task.

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 description implies usage for deleting a task but provides no explicit guidance on when to use this tool versus alternatives such as complete_task (non-destructive status change) or other delete tools. It lacks any exclusions or alternative mentions.

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