Skip to main content
Glama

changes_since

Retrieve incremental changes to tasks and projects since the last sync using a sync token. Returns added and modified items, with optional deletion tracking.

Instructions

Incremental sync feed: return what changed since the last call. Call with no args to bootstrap (returns every task/project in added plus a syncToken); call again passing the previous syncToken to get only changes since then. Returns { reset, syncToken, tasks: { added, modified }, projects: { added, modified } }. modified entries are field-level deltas { id, changes } — only the fields that changed, not the whole record. reset=true means a full snapshot (first call, or the token expired/unknown — discard local state). Always use the returned syncToken for the next call; tokens live ~10 min and do not survive a server restart. Deletions are reported in removed only when you pass includeRemoved:true (it needs a full scan); otherwise they are not tracked. Read-only; no side effects. Example: changes_since({ syncToken: 'abc123' })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
syncTokenNoToken from a prior changes_since call. Omit to bootstrap a full snapshot.
includeRemovedNoReport deleted entity IDs in `removed`. Default false — detecting deletions needs a full enumeration, so this trades the cheap incremental path for completeness. Set true only when you must track deletions; otherwise reconcile periodically with task_list / project_list.
Behavior5/5

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

With no annotations, the description fully discloses read-only nature, token expiry (~10 min), reset flag meaning, delta format, and that deletions require a full scan.

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?

Dense information, front-loaded purpose, but slightly long; every sentence earns its place though.

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?

No output schema, but description fully specifies return structure (reset, syncToken, tasks/projects with added/modified/removed) and delta format.

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

Parameters5/5

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

Schema coverage is 100% but description adds context: syncToken for bootstrapping vs incremental, includeRemoved trade-off between performance and completeness.

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?

Clearly states it's an incremental sync feed for changes since last call, distinguishing it from list/search tools among 100+ siblings.

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?

Explicitly covers bootstrapping vs incremental use, token handling, and when to use includeRemoved vs reconcile with task_list/project_list for deletions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/torsday/omnifocus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server