Edit opportunity
edit_opportunityWRITE$0.02 / callCORRECT one opportunity — a figure that was re-measured, a competitor that moved, or a decision not to work it. Free on every plan. 🔴 THIS IS NOT WHERE A WIN IS RECORDED. Whether the opportunity was taken is the verdict on the hypotheses pointing at this row (edit_hypothesis), and this table deliberately has no column for it: one fact with two owners is two answers within a week. What IS decided here is disposition — dropped for "the audience is real and the fit is not", with the reason in the owner's words, so the next run reading the same demand does not re-propose it. The same rule as add_opportunity: intent, current, competitor, potential, demand_note and drop_reason are the owner's; evidence and demand_source are the trace.
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, from list_opportunities.
The opportunity's handle.
—
—
—
—
—
—
—
—
One of: create, rewrite, expand, structure, authority, none.
—
—
—
One of: open, dropped.
—
—
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "edit_opportunity",
"arguments": {
"direction_key": "<direction_key>",
"key": "<key>",
"action": "create",
"disposition": "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_opportunity","arguments":{"direction_key":"<direction_key>","key":"<key>","action":"create","disposition":"open"}}}'