Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Trigger Analytics Sync

trigger_analytics_sync
Idempotent

Refresh analytics for all connected accounts now by requesting a background sync of the last 7 days; use it after publishing or when analytics look stale.

Instructions

Ask AdaptlyPost to refresh analytics now instead of waiting for the scheduled sync: every connected account is queued and the last 7 days are re-read. Use it when the user just published and wants numbers, or when get_analytics_overview shows an old lastSyncedAt. Allowed once per workspace every 15 minutes, and a YouTube channel read in the last 12 hours is skipped; inside the cooldown, or when no connected account has analytics, it returns queued: false with cooldownSecondsRemaining rather than an error, so do not retry in a loop. The sync runs in the background: poll get_analytics_sync_status until syncInProgress is false, then read the metrics again. Takes only the optional workspaceId and changes no content.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trigger_analytics_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with queued (true when a sync was started), message, and cooldownSecondsRemaining (seconds until the next allowed sync, null when queued).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the 15-minute-per-workspace throttle, the 12-hour YouTube skip, and the non-error failure mode (queued: false with cooldownSecondsRemaining) when inside cooldown or when no account has analytics. It also explains that the work is asynchronous and runs in the background, which the annotations (openWorldHint, idempotentHint) do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and scope, and nearly every sentence carries operational value (throttle, skip rule, failure shape, polling flow). It is dense and close to a single run-on block, which slightly hurts scanability, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a mutation-adjacent async trigger with an output schema and annotations, the description covers everything an agent needs: what is queued, what window is re-read, the rate limit, the non-error cooldown response, and the follow-up polling tool. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single workspaceId parameter is already fully documented in the schema, so the description's 'takes only the optional workspaceId' adds no new semantics. It does implicitly confirm the scope is workspace-wide, but that is a minor increment; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('refresh analytics now instead of waiting for the scheduled sync') and immediately scopes the effect: every connected account is queued and the last 7 days are re-read. It is clearly distinguishable from get_analytics_overview and get_analytics_sync_status, which it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete triggering conditions (user just published and wants numbers; get_analytics_overview shows an old lastSyncedAt) and an explicit anti-pattern ('do not retry in a loop'). It also tells the agent what to do instead after triggering: poll get_analytics_sync_status until syncInProgress is false, then re-read metrics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools