SyncBooster

Get calendar

syncbooster_get_calendar

Read-only

Reads scheduled, published and imported external posts in a brand date window of at most 92 days, sorted by display_date; is_example marks the sample post SyncBooster made for the brand. Returns up to 200 items and has no cursor: when truncated is true, call again with from set to next_from, which is inclusive, so drop items whose id you already have.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_id": "<brand_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "syncbooster_get_calendar"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	End of the window as an ISO datetime with offset.
`from`	Yes	Start of the calendar window as an ISO datetime with offset.
`brand_id`	Yes	Brand id from syncbooster_list_brands.
`statuses`	No
`platforms`	No	Platform publish_key values from syncbooster_list_brands.
`channel_ids`	No	Limit to these channel ids from syncbooster_list_brands.

Output Schema

Name	Required	Description	Default
`items`	Yes
`next_from`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses a 92-day maximum window, sorting by display_date, a 200-item limit, the absence of a cursor, the meaning of truncated/next_from, and inclusive pagination with duplicate handling. It also explains that is_example marks the brand sample post.

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

Conciseness5/5

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

The description is two dense, front-loaded sentences with no wasted wording. It covers purpose, ordering, sample marker, item limit, and pagination mechanics in a compact structure.

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 the output schema exists, the description need not explain return values. It supplies the critical operational details an agent needs: window cap, ordering, truncation behavior, next_from usage, and duplicate avoidance.

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

Parameters4/5

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

Schema coverage is high at 83%, so the schema already documents most parameters. The description adds meaningful semantics beyond the schema: the from/to window is capped at 92 days, and from is inclusive when using next_from for pagination. It does not further explain optional statuses/platforms/channel_ids filters beyond what the schema provides.

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?

The description states a specific verb and resource: reading scheduled, published, and imported external posts for a brand within a date window, sorted by display_date. This clearly distinguishes it from single-post siblings like syncbooster_get_post and general listing tools like syncbooster_list_posts.

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

Usage Guidelines4/5

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

It gives clear pagination guidance: when truncated is true, call again with from set to next_from and drop duplicate ids. However, it does not explicitly compare this tool to alternatives such as list_posts or get_post, so sibling selection is implied rather than stated.

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

All SyncBooster tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?