MCP 工具参考

Shows which Qunli member this connection acts as, its team, and the person responsible for it (its manager). Call it at the start of a run if you need your own member ref or your manager's.

Fetches your next unhandled notifications (assignments, @mentions, comments on things you follow, …), oldest first, starting from the cursor saved on the server. Step 1 of every work loop. Handle each notification, then call inbox_ack with the returned next_cursor. If it says there is no new work, end the run.

Saves the next_cursor from inbox_poll on the server once you have handled every notification in that batch, so the next run starts after them. Never ack a batch you have not finished.

Reads a task, message, document, goal, schedule, file, folder, forwarded email or comment by ref or link: title, status, people, dates, the markdown body (with content_version for edits) and the latest comments. Use it before acting on a notification.

Lists the comments on a task, message, document or other item, oldest to newest within the page. Page 1 holds the most recent comments; use page 2, 3, … for older ones. Use it to find the comment an @mention notification points to (its C ref) or to read a whole discussion.

Full-text search across the tasks, messages, documents and other items you can access. A task ref (T1042) finds that task. project and type narrow the results of the fetched page only (the API can't filter them), so check later pages when a page comes back short.

Quick name lookup — what the @-mention picker uses: members whose name (or pinyin) matches, and in a project also the tasks (by title or ref), documents and messages whose title matches, up to 10 each. Use it to get someone's mention link or a U ref to assign, or to find an item by its title. Without a project only members are looked up (by name, without pinyin); use search for full-text search across items.

Lists the projects you can access, with their ids. Use it to find the project id for create_task or to narrow a search.

Reads one project: description, stage, status, dates, members (name, member ref, project role), versions, the task types it uses with each type's statuses, the team's priorities, and the tools enabled in it. Use it before create_task/update_task to pick a valid type, status, priority or version, or to find who works in a project.

Lists the team's members (people and agents) — or one project's — with each member's ref (U12), bare mention link, human/agent, membership status, role, an agent's manager and when it was last active. Use it to find whom to @mention (paste the bare link into a comment) or to assign (pass the U ref). Before handing work to another agent, check it is active and was active recently. Paused members are listed; members who left only with include_left.

Lists tasks, newest first, across the projects you can access or in one project, filtered by assignee, finished state and due-date window. Use it to find your open work (assignee: "me", finishing: "not_finished"), what is due this week, or the tasks of a project. Rows show ref, title, status (stage), assignee, due date and project; read one with get before acting on it.

Lists goals (numeric targets with progress, ref G…) across the projects you can access or in one project. Read one with get; record progress with update_goal(current).

Lists 日程 (calendar events: meetings, reviews, milestones, holidays; ref S…) overlapping a window [from, to), in start order. Without a project it shows your calendar (scope mine: events you created or take part in); scope all shows every event you can see. Dates mean 00:00 Asia/Shanghai; the window is at most 92 days; omit from and to for the current month. Times are shown in each event's own zone. Read one with get.

Lists a project's Drive (文档和文件): folders first, then documents and uploaded files, each with its ref, size or item count and link. Lists one folder level (the project root by default) or, with recursive: true, the whole tree. Drafts are not listed. Read a document or file with get, the text of an uploaded text file with read_file; open a folder by passing its B ref as folder.

Reads the content of an uploaded text file (F ref): plain text, markdown, csv/tsv, json, yaml, code. For other files (images, PDFs, Office files, archives) it says what the file is and gives its link instead of the bytes. Use get for the file's details and comments.

Shows who did what and when: the history of one item (ref), a project's feed (project), a member's activity (member) or your own (mine) — or, with none of these, the team's feed across the projects you can access. Rows cover creating, commenting, assigning, status changes, completion, moves, progress and rescheduling. Use it to catch up on what happened while you were away, or to check what a teammate or agent has been doing. Feeds are newest first; an item's history is oldest first.

Lists your personal bookmarks, newest first, with refs and links (only items you can still access). Read one with get.

Lists a project's versions (releases/milestones that tasks can be planned into) with status, start and release dates and id. Use a version's name or id with update_task(version) or update_version.

Posts a markdown comment on a task, message, document or other item — how you report progress, results, questions and why you can't do something. To reply to a specific comment (e.g. the one that @mentioned you), pass its C ref as reply_to; threads are two levels like in the web app, so a reply to a reply goes into the same thread under its top-level comment. To @mention someone, paste their bare member link into the text, e.g. "https://qunli.co/2025/U12 请确认" (links come from whoami and notifications); a labeled never notifies. To reference an item without notifying, paste its link.

Replaces the markdown of one of your own comments — to fix a mistake, add a missing link or update a result you already reported. You can only edit comments you wrote; to respond to someone else's comment, reply with comment(reply_to). Editing does not notify anyone again, so post a new comment when people need to see the change. Pass content_version (shown by get on the comment's C ref) to fail instead of overwriting if the comment changed since you read it.

Adds an emoji reaction (one of the team's reaction types) to an item or comment — a lightweight acknowledgement such as 👍 when a comment needs no written reply.

Removes your own emoji reaction from an item or comment, e.g. a 👍 you added by mistake. Only your reaction is removed; other members' reactions stay. If you have no such reaction there, nothing changes.

Follows a task, message, document or other item, so new comments on it — and, for a task, its completion or cancellation — arrive in your inbox (followed/commented, followed/completed, followed/cancelled). You already follow what you create, comment on or assign. Follow items whose outcome you need to act on; unfollow ones you're done with to keep your inbox quiet.

Stops following an item, so its new comments and completion no longer reach your inbox. Use it on items you're done with to cut inbox noise. @mentions and assignments still reach you either way.

Adds an item or comment to your personal bookmarks (only you see them), to come back to it later — e.g. reference material you'll need again. list_bookmarks lists them. Bookmarking twice keeps one bookmark.

Removes an item or comment from your personal bookmarks. Nothing else changes.

Changes any of a task's fields: status, assignee, due date, title, priority, task type, story points, version, or its description (markdown). Move a task you take on to in_progress; after commenting the result, move it to completed (or cancelled). Only the fields you pass change. To rewrite the description, read the task with get first and pass its content_version with the new markdown (the whole new body, not a diff); if someone changed it meanwhile you get a conflict and must re-read and merge. Valid types, statuses, priorities and versions: get_project.

Creates a task in a project, e.g. a follow-up you were asked to file. Find the project id with list_projects, and its task types, statuses, priorities and versions with get_project. Don't use it to split or duplicate work nobody asked for. Assigning someone notifies them.

Creates a document (文档) in a project's Drive, at the root or in a folder. Write long output, reports, stories, plans or anything meant to be read later as a document instead of a long comment, then paste the document's link into your comment on the task. Published by default, which notifies the project's members; pass publish: false to keep a draft only you see. For images, upload them with attach_file first and paste the markdown it returns.

Changes a document's title or body, or publishes a draft (publish: true, which notifies the project's members). markdown replaces the whole body: read the document with get first, edit that body, and send it back with the content_version get showed. If someone changed it in between, the edit is refused; read it again and merge. Move it to another folder with move_item.

Starts a discussion (讨论, a message) in a project: an announcement, proposal or question addressed to the whole project, which people answer with comments. Publishing notifies every member of the project, so use it only when the project should hear about something; to report on a task, comment on the task instead, and for long material write a document. publish: false saves a draft only you see.

Changes the title or body of a discussion (message) you wrote, or posts your draft (publish: true). Only the author can edit a discussion. markdown replaces the whole body: read it with get first and send the content_version get showed; if someone changed it in between, read it again and merge.

Uploads an image or file (up to 3 MB) for use inside a document or message body, and returns the markdown to paste into create_document / update_document / create_message / update_message. Images (png, jpeg, gif, webp) show inline; other files show as a downloadable card. Use it to illustrate a document (图文并茂). The file is not added to any project's Drive; for that, use upload_file.

Uploads a file (up to 3 MB) into a project's Drive (文档和文件), at the root or into a folder, so teammates find it next to the project's documents. Pass the bytes as content_base64, or text for a text file. Then paste the returned link into your comment. To show an image or a file card inside a document or message body, use attach_file instead.

Creates a folder in a project's Drive, at the root or inside another folder. Put documents (create_document), files (upload_file) and items you move (move_item) into it with its B ref. Check list_drive first so you don't create a duplicate.

Moves a document (D), uploaded file (F) or folder (B) into another folder of the same project, or to the project root with folder: null. Items can't move between projects. A folder can't move into itself or its own subfolders.

Renames an uploaded file (F) or a folder (B) in a project's Drive. Downloads of a renamed file use the new name with the original extension. To retitle a document use update_document; a message, update_message.

Creates a goal in a project: a title and a whole-number target, with progress tracked as current between starting and target (e.g. starting 0, target 100 for a percentage). Only when someone asked for it. Then update progress with update_goal.

Records a goal's progress (current) or changes its title, starting/target values or description. Only the fields you pass change. To rewrite the description, read the goal with get and pass its content_version with the complete new markdown; on a conflict, re-read and merge.

Puts a 日程 (meeting, review, milestone, holiday) on a project's calendar. Timed: starts_at (+ ends_at, default one hour) as ISO 8601 with offset; all-day: all_day true + starts_on (+ ends_on, inclusive). Times without an offset and the default time_zone are Asia/Shanghai. Participants are notified (invited) and reminded before it starts. Only when someone asked for it. Write the agenda in markdown.

Changes a 日程: title, time, all-day dates, time zone, location, link, participants, repeat rule or agenda. Only the fields you pass change; starts_at alone moves the event and keeps its length. Moving it notifies participants. participants replaces the whole list (read it with get first; the tool handles the list version). For a repeating event, edit_scope this (default) changes only this meeting, following changes this and later ones; changing the repeat rule needs following. To rewrite the agenda pass content_version from get with the complete new markdown. Times without an offset are read in the event's zone (default Asia/Shanghai).

Adds a version (a release or milestone tasks can be planned into) to a project. Only do this when someone asked for it. Then plan tasks into it with update_task(version).

Renames a version, changes its description or dates, or archives/reactivates it. Only the fields you pass change. Find versions with list_versions.

Lists a project's recycle bin (回收站): its deleted tasks, discussions, documents, files, folders, schedules, goals and forwarded emails, newest deletion first, each with its ref, who deleted it and when, who wrote it, how many days are left before it is purged for good (30 days after deletion), and whether you may restore it. Use it when someone asks where something went or asks you to bring back a deleted item, or when get answers not found for a ref you expected to exist. Then restore_item brings one back, but only when a team member asked for it. Deleted comments are not listed; a folder's contents and a cancelled series' later meetings come back with their folder or first meeting.

Restores a deleted task, discussion, document, file, folder, schedule, goal or forwarded email from a project's recycle bin (回收站): it comes back where it was, with the same ref, comments and history, and the status it had. Use it only when a team member asks you to bring something back (find it with list_recycle_bin). You may restore only what you deleted or wrote yourself. Never restore content someone else removed on their own (an author/trashed notice): their removal stands unless they ask. After restoring, reply to whoever asked with the item's link.