Skip to main content
Glama

Census MCP by usefulapi

Trigger sync

census_trigger_sync
Destructive

TRIGGERS a sync run for the given sync id — this KICKS OFF a live data sync that writes records into the connected destination SaaS tool. Set force_full_sync=true to re-sync all rows instead of just changes. Census: POST /syncs/{id}/trigger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe resource id (a numeric id, passed as a string).
force_full_syncNoRe-sync ALL rows instead of just changes since the last run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.