Docsbook
Overview

Unlink work

MCPunlink_workWRITE$0.02 / call

DISCONNECT two pieces of work that were linked in error. Free on every plan. Only for a link that was WRONG — a hypothesis attached to the pull request that did not test it, an issue attached to the wrong goal. A link to work that finished is not stale: it is the record of what that work was for, and removing it is how a merged change becomes unmeasurable again. This answers WHAT, not what to do about it. If you have not already got the method from docsbook_expert, get it first: it names which readings answer this question, what to compare them against, and what would make the conclusion wrong. One call, changes nothing.

Arguments
workspace_idstringoptional

Workspace ID (optional when MCP endpoint is auto-scoped). Numeric workspace id — OR the project as the user names it: 'owner/repo', the repo name alone, the site's display name, its docs URL or custom domain. Text is resolved server-side; an ambiguous name returns the candidates instead of guessing, so pass what the user said rather than calling list_workspaces first.

from_kindstringrequired

What sort of record this end is. issue: A GitHub issue on this project's repository — the unit of work. Ref is its number. pull_request: A GitHub pull request — the change that tests something. Ref is its number. hypothesis: A row of list_hypotheses — the claim a change is meant to prove. Ref is its key. memory: A row of list_memory — a goal the work argues for, a question it waits on, a fact or rule it rests on. Ref is its key. One of: issue, pull_request, hypothesis, memory.

from_refstringrequired

The GitHub number or the row's key.

to_kindstringrequired

What sort of record this end is. issue: A GitHub issue on this project's repository — the unit of work. Ref is its number. pull_request: A GitHub pull request — the change that tests something. Ref is its number. hypothesis: A row of list_hypotheses — the claim a change is meant to prove. Ref is its key. memory: A row of list_memory — a goal the work argues for, a question it waits on, a fact or rule it rests on. Ref is its key. One of: issue, pull_request, hypothesis, memory.

to_refstringrequired

The GitHub number or the row's key.

Call it#

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "unlink_work",
    "arguments": {
      "from_kind": "issue",
      "from_ref": "<from_ref>",
      "to_kind": "issue",
      "to_ref": "<to_ref>"
    }
  }
}
curl -X POST 'https://docsbook.io/api/mcp/server' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"unlink_work","arguments":{"from_kind":"issue","from_ref":"<from_ref>","to_kind":"issue","to_ref":"<to_ref>"}}}'

Try it over REST#

The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.

Your workspace is resolved from the API key, so workspace_id is decided server-side here and anything you send for it is ignored.

POST/api/v1/tools/unlink_work
Authorization
Authorizationstringrequired

Your API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.

Body
argsobjectrequired

The arguments above, as one JSON object.

Request
curl -X POST 'https://docsbook.io/api/v1/tools/unlink_work' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"args":{"from_kind":"issue","from_ref":"<from_ref>","to_kind":"issue","to_ref":"<to_ref>"}}'

Was this page helpful?