set_recommendation_status

set_recommendation_status MCP tool: mark a recommendation or plan step as done, excluded, or back to do. Done logs the action in the project's journal so its effect is measured.

Updated 2026-10-15

set_recommendation_status records what was done with a recommendation or a plan step: done, excluded, or back to do. It writes exactly what the dashboard's "Done", "Exclude" and "Restore" buttons write, so the hub, the plans and the journal stay in sync whoever acts.

When to use

Call it once an agent, or the user, has carried out an action from list_recommendations or get_recommendation: listed on a directory, asked a ranking to add the brand, published or fixed a page. Marking it done is what makes its effect measurable: the plan then compares the share of answers citing the brand before and since that day.

Exclude an action that does not fit the business (a directory outside your trade, a ranking you will never be in). It disappears from every plan and from the hub, and can be put back with status: "todo".

Input

Field	Type	Default	Description
`projectId`	string (CUID)	required	Project to update.
`id`	string	required	A row or step `id` from `list_recommendations` / `get_recommendation`, a site plan item `id` from list_priority_pages (`page:…` or `fix:…`), or a content plan mission `id` from list_content_plan (`content:…`, `page:…`, `fix:…`, `source:…`). A mission marked done or excluded leaves the plan.
`status`	enum	required	`done`, `excluded`, `todo` (puts a done or excluded item back).
`title`	string	-	Required for `done` and `excluded`: what was done, shown in the journal and the Done tab. 200 characters max.
`date`	string (YYYY-MM-DD)	today	Day the action was done, `done` only. Can be backdated.

Response

{ "success": true, "id": "source:g2.com", "status": "done" }

Errors: title_required when done or excluded comes without a title.

Behavior

Shared sources. A source is one action for the whole project. Marking source:g2.com done checks it in every prompt plan and every local zone plan that lists G2.
Journal. done creates an entry in the project's action log, tagged as logged by an AI agent, at date. It shows on the dashboard performance chart and in reports, like create_action_log. Do not log the same action twice.
Back to do. todo removes the decision. The journal entry stays: the action did happen.
Automatic steps. The create and optimize page steps tick themselves when the generated page is published. Use this tool on them only to exclude them.
Roles. Write tool: the customer role is refused.

Tips and patterns

Write title the way a person would read it in a monthly report: "Listed on G2", "Asked Flint to add us to their AI visibility ranking".
Backdate date when logging actions done before the agent ran, so the before and after comparison starts on the right day.
After a batch of actions, call list_recommendations again: the next best actions move up.

Related tools

list_recommendations: the actions and their ids
get_recommendation: the steps of a plan and their measured effect
create_action_log: log an action that is not a recommendation