delete_knowledge_entry
Take back something the Copilot was taught — the entry, its passages and its file go together, at once.
Remove a Knowledge entry. The entry, its passages and, for an uploaded document, its file go in one step, so the Copilot stops answering from it the moment this returns: no member is answered from it in the inbox, the project bot or the portal chat, and no inbox suggestion is drafted from it. Emits knowledge.deleted with the entry as it was, never its text.
Nothing is recoverable
Deleting is not archiving: the words are gone with the passages. To stop members being answered
from an entry while keeping it for the team, change its audience to team with
update_knowledge_entry instead.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.
Arguments
project_id*stringUUID of the project the entry belongs to.
knowledge_entry_id*stringUUID of the entry to remove, from `list_knowledge_entries`.
What it returns
{ "data": { "id": "3b7e4d2a-9c1f-4a6b-8d5e-2f7c9a1b3e4d", "deleted": true }}A second call with the same id is RESOURCE_NOT_FOUND: the entry no longer exists to delete.
How it fails
RESOURCE_NOT_FOUNDproject_id names a project the token cannot see, or knowledge_entry_id is unknown, belongs to another project, or was already deleted.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-knowledge:delete, or its owner's role on the project's team may not remove Knowledge.
How is this guide?
Last updated on