Skip to main content
Glama

AI Visibility Monitor

visibility_manage
Destructive

Manage the workspace's AI-visibility monitor: list the tracked prompts scans ask every engine, add/edit/remove prompts, set the scan cadence, and choose which AI engines are tracked. Reads of scan RESULTS live in ai_citations action scan_results. Running a FRESH scan is not available over MCP; point the user at the dashboard. Config changes apply directly (no staging) but are plan-capped, and cadence and engines are spend levers - 'daily' multiplies recurring scan cost ~7x, each added engine adds its per-question cost; both need the user's explicit ask. Already scoped to the connected workspace and its site; no domain or site parameter is needed. Cost: all actions are FREE config changes; each ACTIVE prompt raises the recurring scan cost when scans run, cadence 'daily' is ~7x weekly spend, and each tracked engine adds its per-question cost - disclose before setting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoupdate: new prompt wording.
resetNoset_engines: true tracks the default engines.
actionYesWhich operation to run. list (tracked prompts + plan allowance + cadence); add (track a new buyer question (plan-capped)); update (rename / pin / (de)activate a prompt); remove (delete a prompt permanently (confirm with the user)); set_cadence (weekly / daily / manual - daily is ~7x spend, explicit user ask only); set_engines (choose tracked AI engines (full list) or reset to defaults - each engine adds scan cost, quote it first).
activeNoupdate: false pauses scanning (keeps history), true re-activates (re-checks the plan cap).
pinnedNoupdate: pin the prompt.
promptNoadd: the buyer question to track, in the customer voice.
cadenceNoset_cadence: how often scans run. 'daily' ~7x weekly spend.
enginesNoset_engines: the FULL list of engine ids to track (see list for ids and per-engine cost).
promptIdNoupdate/remove: the prompt id from list.
languageCodeNoLocale language code, e.g. "en".
locationCodeNoLocale location code (default: primary monitor).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / user_intent
      Removed value: -{
      -  "description": "Optional: one short sentence describing what the user is ultimately trying to achieve with this request. Used by SEOmatic to tailor answers and improve the product; never required.",
      -  "maxLength": 300,
      -  "type": "string"
      -}
  2. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which operation to run. list (tracked prompts + plan allowance + cadence); add (track a new buyer question (plan-capped)); update (rename / pin / (de)activate a prompt); remove (delete a prompt permanently (confirm with the user)); set_cadence (weekly / daily / manual - daily is ~7x spend, explicit user ask only)."New value: +"Which operation to run. list (tracked prompts + plan allowance + cadence); add (track a new buyer question (plan-capped)); update (rename / pin / (de)activate a prompt); remove (delete a prompt permanently (confirm with the user)); set_cadence (weekly / daily / manual - daily is ~7x spend, explicit user ask only); set_engines (choose tracked AI engines (full list) or reset to defaults - each engine adds scan cost, quote it first)."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "add",
      -  "update",
      -  "remove",
      -  "set_cadence"
      -]New value: +[
      +  "list",
      +  "add",
      +  "update",
      +  "remove",
      +  "set_cadence",
      +  "set_engines"
      +]
    • addedInput schema / properties / engines
      Added value: +{
      +  "description": "set_engines: the FULL list of engine ids to track (see list for ids and per-engine cost).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / reset
      Added value: +{
      +  "description": "set_engines: true tracks the default engines.",
      +  "type": "boolean"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which operation to run. add (track a new buyer question (plan-capped)); update (rename / pin / (de)activate a prompt); remove (delete a prompt permanently (confirm with the user)); set_cadence (weekly / daily / manual - daily is ~7x spend, explicit user ask only)."New value: +"Which operation to run. list (tracked prompts + plan allowance + cadence); add (track a new buyer question (plan-capped)); update (rename / pin / (de)activate a prompt); remove (delete a prompt permanently (confirm with the user)); set_cadence (weekly / daily / manual - daily is ~7x spend, explicit user ask only)."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add",
      -  "update",
      -  "remove",
      -  "set_cadence"
      -]New value: +[
      +  "list",
      +  "add",
      +  "update",
      +  "remove",
      +  "set_cadence"
      +]
  4. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.