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

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_task

Create a task with a required title and optional due time, assignees, recurrence, and metadata.

Instructions

[Official API + UAT, v1.3.7] Create a new task. summary is required; due / members / etc. are optional.

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": {
      "summary": "<summary>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYesTask title
descriptionNoTask description (optional)
dueNoDue time (optional). {timestamp:"<unix-millis>", is_all_day?:true|false}
membersNoInitial members (optional). Each: {id:"<open_id>", role:"assignee"|"follower", type?:"user", name?:"..."}
repeat_ruleNoRecurrence (optional, RFC5545 RRULE)
extraNoFree-form extra metadata (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It only mentions required/optional parameters and a version tag; it does not disclose side effects, return values, authentication needs, or idempotency. This is notably thin for a mutation tool.

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 a single sentence that front-loads the core action and required parameter. The version bracket is minor noise but does not detract from overall efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and nested object parameters, the description is under-specified. It does not describe what the tool returns, any default behaviors, or contextual prerequisites, making it incomplete for an agent to invoke confidently.

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 description coverage is 100%, so the baseline is 3. The description adds only a restatement that summary is required and others optional, which does not deepen understanding beyond what the schema already provides.

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 'Create a new task,' a specific verb+resource that clearly distinguishes this tool from sibling task operations like update_task, delete_task, and complete_task. The action is unambiguous.

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 creating new tasks but provides no explicit when-to-use or when-not-to-use guidance. It does not reference alternatives, despite many sibling task tools being present.

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