Edit direction
edit_directionWRITE$0.02 / callJUDGE a direction with the target reading, move its review date, or correct it. Free on every plan. 🔴 CLOSING ONE IS A SEPARATE SENTENCE FROM JUDGING THE CHANGES UNDER IT. status: "reached" says the docs now show up for this audience by what target predicted; a set of confirmed hypotheses does not say that on its own and never has. The reverse is the row this store exists to be able to write: every claim confirmed, the target still short — which means the opportunities addressed a smaller share of the audience than anybody thought, and the next direction is about the rest of it. result is what the re-check showed, written FOR THE OWNER: 'now on Google's first page for 2 of the 5 searches; the AI answer still names a competitor for the other 3'. The figures with their call ids go in method. abandoned is legitimate and needs the same honesty: say in result what changed about the audience or the market. 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.
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.
The direction's handle, from list_opportunities.
Written for the owner.
The goal it serves — the standing goal, a branch, or one of the owner's own. Checked against that list.
Written for the owner.
Technical.
Technical.
Technical.
Written for the owner.
Technical.
—
—
—
reached only when the TARGET reading says so — not when the changes under it were confirmed. One of: open, reached, abandoned.
What the re-check showed, in the owner's words. The baseline-and-reading pair with its call ids goes in method.
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "edit_direction",
"arguments": {
"key": "<key>",
"status": "open"
}
}
}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":"edit_direction","arguments":{"key":"<key>","status":"open"}}}'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.
/api/v1/tools/edit_directionYour 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.
The arguments above, as one JSON object.
curl -X POST 'https://docsbook.io/api/v1/tools/edit_direction' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"args":{"key":"<key>","status":"open"}}'