census_trigger_syncTRIGGERS 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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The resource id (a numeric id, passed as a string). | |
| force_full_sync | No | Re-sync ALL rows instead of just changes since the last run. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, and the description confirms mutative behavior ('writes records into the connected destination SaaS tool'). It also adds parameter-level detail (force_full_sync). No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with key information front-loaded. Includes API endpoint for reference. No extraneous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a trigger operation with a destructive hint, the description adequately explains what the tool does, the effect (writes records), and the optional parameter. No output schema needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description only reiterates the schema's documentation for force_full_sync. No additional semantic value beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action ('TRIGGERS a sync run') and the resource ('sync id'), with additional context about kicking off a live data sync that writes records. It distinguishes from sibling tools like census_get_sync or census_list_syncs by focusing on triggering a run.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description explains parameter usage (force_full_sync) but does not provide guidance on when to use this tool versus alternatives (e.g., viewing runs). No explicit when-not-to-use or context for choosing this over other sync-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource type (destination, model, source, sync, sync run, segment, workspace) with clear get/list/trigger actions. No overlapping purposes; agents can easily distinguish which tool to use for a given operation.
All tools follow a consistent 'census_verb_noun' pattern (e.g., census_get_destination, census_list_syncs). The only action tool, census_trigger_sync, also fits the pattern. No mixing of casing or verb styles.
13 tools is appropriate for a data integration platform that manages multiple resource types (destinations, sources, models, syncs, etc.). It's slightly on the higher side but well-scoped for the domain.
The set covers get, list, and trigger operations, but lacks create, update, and delete for resources. While Census API may not expose mutating operations via MCP, the surface is incomplete for full lifecycle management.