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

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_tasks

List tasks for the current user with optional filters for completion status (completed, pending, or all) and task type (personal or all) to narrow results.

Instructions

[Official API + UAT, v1.3.7] List the current user's tasks. Filter by completion or type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
completedNotrue → only completed; false → only pending; omit → all
typeNoFilter by task type (optional). E.g. "all" / "personal".
page_sizeNoItems per page (default Feishu default)
page_tokenNoPagination token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only list operation via 'List', which is safe. However, it does not disclose pagination behavior, default page size, or any potential limits, which are relevant given page_size and page_token parameters.

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 very concise, with the main purpose front-loaded. The prefix '[Official API + UAT, v1.3.7]' is extra clutter that does not aid the agent, slightly reducing the score from a perfect 5.

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 simple list tool with good schema coverage, the description covers the essential functionality: listing current user's tasks with filters. It could mention pagination or that it returns a list of tasks, but the schema already handles parameter details. The absence of an output schema means the description could clarify return format, but it's not a major gap.

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 input schema already describes all four parameters with 100% coverage. The description only restates 'Filter by completion or type', which adds no new meaning beyond what the schema provides. It does not explain page_size or page_token behavior, so the baseline score of 3 is appropriate.

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 'List the current user's tasks' with a specific verb and resource. It also mentions filtering by completion or type, and the plural 'tasks' distinguishes it from sibling tools like get_task, create_task, etc.

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 gives clear context by specifying 'current user's tasks' and filter options, implying when to use it. However, it does not explicitly mention alternatives or when not to use it, such as pointing to get_task for a single task or complete_task for updates.

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