Configure mentions
MCP
configure_mentionsWRITE$0.00003 / call
Features
Use get_mentions to read what the checks found.
Input5
Your API key, for the REST call. Sent from your browser straight to the API — never to Docsbook, never stored.
Workspace ID (optional when MCP endpoint is auto-scoped to a workspace). 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.
Which engine this arms: ai_overview (Google's AI answer), google or bing (the results page). One of:
ai_overview, google, bing.Whether the daily check runs. Queries are kept either way.
The queries to check, up to 5. Replaces the saved list.
5-field UTC cron for the check. Defaults to a daily early-morning slot.
Output8
ai_overview | google | bing.
As STORED — trimmed, de-duplicated and capped at 5.
null
null
null
null
Limitations
- Choose what the mention checks watch on one engine: turn the daily check on or off, and set the queries (up to 5) — the exact words a reader would type or ask.
- Queries a workspace does NOT rank for are the point: those are the ones Search Console can never report on.
Example input
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "configure_mentions",
"arguments": {
"surface": "ai_overview"
}
}
}Example output
{
"surface": "<surface>",
"enabled": true,
"queries": [],
"cronExpression": "<cronExpression>",
"lastRunAt": "<lastRunAt>",
"lastStatus": "<lastStatus>",
"lastDetail": "<lastDetail>",
"note": "<note>"
}