memory_record_ctr_feedback
Record click-through rate feedback when a search result is shown to the user, used by the re-ranker to refine ranking over time.
Instructions
Record click-through rate feedback for a search result.
G4 fix (2026-06-22): memory_record_ctr_feedback (this tool)
and memory_reinforce (mcp_memory.py) record two different
signals on purpose — they are not interchangeable.
memory_record_ctr_feedbackrecords the implicit signal: "the user saw this result in the response." Writes a row toctr_feedbackwith action=returned/clicked/etc. The search re-ranker reads this table to adjust ranking over time. Use this when a search result is delivered to the user, regardless of whether the user does anything with it.memory_reinforcerecords the explicit signal: "the user judged this memory useful (or not)." Updatessuccess_scoreand recomputesfitness_score. Use this when a user acts on a memory — e.g. cites it in a lesson, marks a decision as right, or undoes a save because the memory was wrong. Skippingmemory_reinforceon every "user saw it" event would over-credit the success score.
In short: record_ctr_feedback = "delivered to user",
reinforce = "user acted on it positively". Call both when
a user follows up on a search hit. Call only
record_ctr_feedback when the user just sees the result.
Call only reinforce when the success/failure signal comes
from outside the search path (e.g. a downstream agent confirms
the memory was correct).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| action | No | returned | |
| source | No | ||
| query_id | Yes | ||
| returned_at | No | ||
| ranking_params | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |