Skip to main content
Glama

create_okr_progress_record

Add a progress note to an OKR objective or key result with optional percentage and status updates.

Instructions

[Official API + UAT, v1.3.7] Add a progress note to an OKR objective or key result. Feishu requires source_title, source_url, and a block-structured content; this tool exposes a simple content_text and auto-wraps it into the single-paragraph block format. Pass richer content directly if you need lists / mentions / docs links / images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_idYesID of the OKR objective or key result. Get from get_okrs response (`objective_list[].id` or `objective_list[].kr_list[].id`).
target_typeYes1 = objective, 2 = key result. Pick based on which level target_id refers to.
content_textNoPlain-text progress note. Auto-wrapped into the Feishu block format. Use `content` instead for rich text.
contentNoOptional: full Feishu block structure ({blocks:[...]}). If provided, overrides content_text.
source_titleNoSource label (default "Progress update"). Shown next to the note in the OKR UI.
source_urlNoSource URL (default https://feishu.cn/). Feishu requires a URL even for plain notes.
source_url_pcNoOptional PC-specific source URL.
source_url_mobileNoOptional mobile-specific source URL.
progress_percentNoOptional progress percent (0-100) to bump alongside the note.
progress_statusNoOptional status code (Feishu enum: 1=on track, 2=at risk, 3=blocked, etc).
user_id_typeNoType of user IDs in mentioned_user_list etc. (default open_id)
Behavior4/5

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

With no annotations, the description reveals Feishu API constraints (required fields, auto-wrapping) and notes that a URL is mandatory. No destructive behavior mentioned; appropriate for a create operation.

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?

Two efficient sentences: first states purpose, second explains key API nuance and simplification. Front-loaded and no extraneous text.

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?

Covers main behavior and critical parameters well. Optional parameters like `progress_percent` are left to schema, which is acceptable given schema coverage. Lacks output description but no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%; description adds value by explaining auto-wrapping, override behavior, and purpose/sourcing of key parameters beyond schema definitions.

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?

Description clearly states the action ('Add a progress note'), the resource ('OKR objective or key result'), and distinguishes from sibling tools like list/delete versions. Includes API version info.

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?

Provides explicit guidance on when to use simple `content_text` vs rich `content`, and defaults for `source_title` and `source_url`. However, lacks explicit when-not-to-use or alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EthanQC/feishu-user-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server