Skip to main content
Glama

update_pulse_item

Idempotent

Change one Pulse item's state. Every action changes the queue for the WHOLE workspace — an item belongs to the workspace, not to whoever called the tool, so dismissing a recommendation hides it from every member and records who decided that. acknowledge closes an attention item as seen, with no reason and no note — it is the only hand-close an automatic item accepts. resolve closes with a resolutionCode and is refused for an automatic item. Both need the permission for the item's source (manage_broadcasts for a broadcast, manage_automation for a flow, sequence or operation), and a critical item that is not manual by policy can be closed only by an owner or admin (a workspace key counts as owner); resolve on such an item also needs a note. Closing a card does not fix its cause, and it hides the problem: an item closed by hand is NOT raised again for 14 days, even while its detector still observes the condition. Only an anomaly the platform closed itself (resolutionCode source_condition_cleared) reopens at once when the condition returns. A dismissed recommendation returns by itself after the same cooldown. Does not apply a recommendation's proposed change — that is a dashboard action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoFree-text note stored with a `resolve`. Required when resolving a critical item that is not `manual` by policy. Ignored by `acknowledge`, which stores no note.
actionYesacknowledge: close an attention item as seen (the only hand-close an `automatic` item accepts). resolve: close it with a reason (refused for an `automatic` item). dismiss/restore: hide or unhide a recommendation for the workspace. snooze: hide it from the workspace queue until a time.
itemIdYesRequired. Pulse item id, as returned by list_pulse_items.
reasonNoOptional reason recorded with a `dismiss`, so a teammate can see why it was waved off.
snoozeUntilNoRequired for `snooze`. ISO 8601 timestamp in the future, e.g. "2026-09-15T09:00:00Z".
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.
resolutionCodeNoRequired for `resolve`. reviewed = looked at it, no_action_needed = not a real problem, fixed_elsewhere = handled outside the platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"acknowledge: close it as seen. resolve: close it with a reason. dismiss/restore: hide or unhide a recommendation for the workspace. snooze: hide it from the workspace queue until a time."New value: +"acknowledge: close an attention item as seen (the only hand-close an `automatic` item accepts). resolve: close it with a reason (refused for an `automatic` item). dismiss/restore: hide or unhide a recommendation for the workspace. snooze: hide it from the workspace queue until a time."
    • changedInput schema / properties / note / description
      Previous value: -"Free-text note stored with a `resolve`. Required when overriding a critical item."New value: +"Free-text note stored with a `resolve`. Required when resolving a critical item that is not `manual` by policy. Ignored by `acknowledge`, which stores no note."
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.