Skip to main content
Glama
Sign In

Mark

by com.use-mark.app
OverviewDiscussionsAdmin

Update Posting Slots

update_posting_slots
Idempotent

Adds or removes a channel's posting slots. A slot is a weekday, 1 (Monday) through 7 (Sunday), and a count: how many posts that channel makes that day, 1 to 5 (default 1). A slot has no time: the day's first post goes at the channel's posting time (set with update_channel_settings postingTime, default 09:00 in the workspace timezone), each further post 3 hours later, and a post placed after its time goes out at the next minute. Adding a weekday the channel already has sets that slot's count. Related: list_channels, get_calendar, update_channel_settings.

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": {
      "channel": "<channel>"
    },
    "name": "update_posting_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoSlots to add, or weekdays whose count to set.
removeNoExisting slot ids to remove, from get_calendar.
channelYesChannel id, e.g. linkedin.

Output Schema

NameRequiredDescriptionDefault
addedYes
slotsYes
appUrlYes
errorsYes
removedYes
postingTimeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
-  "instagram",
-  "facebook",
-  "youtube",
-  "pinterest",
-  "tiktok",
-  "x",
-  "linkedin",
-  "linkedin_article",
-  "blog",
-  "faq",
-  "competitor_page",
-  "landing_page",
-  "email",
-  "meta_ads",
-  "google_ads"
-]New value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "pinterest",
+  "tiktok",
+  "x",
+  "linkedin",
+  "linkedin_article",
+  "blog",
+  "faq",
+  "competitor_page",
+  "meta_ads",
+  "google_ads"
+]
  2. Changed11 schema fields changed
    • changedInput schema / properties / add / description
      Previous value: -"Slots to add."New value: +"Slots to add, or weekdays whose count to set."
    • addedInput schema / properties / add / items / properties / count
      Added value: +{
+  "description": "Posts that day, 1 to 5. Defaults to 1.",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / add / items / properties / time
      Removed value: -{
-  "description": "Time of day in 24-hour HH:MM.",
-  "pattern": "^\\d{2}:\\d{2}$",
-  "type": "string"
-}
    • changedInput schema / properties / add / items / required
      Previous value: -[
-  "weekday",
-  "time"
-]New value: +[
+  "weekday"
+]
    • addedOutput schema / properties / postingTime
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / slots / items / properties / count
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / slots / items / properties / marketName
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / slots / items / properties / nextOpen
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedOutput schema / properties / slots / items / properties / time
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / slots / items / required
      Previous value: -[
-  "channel",
-  "id",
-  "time",
-  "weekday"
-]New value: +[
+  "channel",
+  "count",
+  "id",
+  "marketName",
+  "nextOpen",
+  "weekday"
+]
    • changedOutput schema / required
      Previous value: -[
-  "added",
-  "appUrl",
-  "errors",
-  "removed",
-  "slots"
-]New value: +[
+  "added",
+  "appUrl",
+  "errors",
+  "postingTime",
+  "removed",
+  "slots"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
-  "instagram",
-  "facebook",
-  "youtube",
-  "pinterest",
-  "tiktok",
-  "x",
-  "linkedin",
-  "blog",
-  "faq",
-  "competitor_page",
-  "landing_page",
-  "email",
-  "meta_ads",
-  "google_ads"
-]New value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "pinterest",
+  "tiktok",
+  "x",
+  "linkedin",
+  "linkedin_article",
+  "blog",
+  "faq",
+  "competitor_page",
+  "landing_page",
+  "email",
+  "meta_ads",
+  "google_ads"
+]
  4. Changed1 schema field changed
    • changedOutput schema / properties / slots / items / properties / time / type
      Previous value: -"number"New value: +"string"
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare it non-read-only, idempotent, and non-destructive. The description adds useful behavior beyond annotations: adding an existing weekday sets its count, the first post uses the channel posting time, later posts are three hours apart, and late posts go out at the next minute. It does not state how removing a slot affects already-scheduled posts, leaving one behavioral gap.

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 purpose is front-loaded in the first sentence, and the remaining sentences compactly define slot semantics, timing behavior, and related tools. Every sentence earns its place without fluff.

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

Completeness4/5

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

With annotations and an output schema already present, the description covers slot semantics, scheduling timing, idempotent set behavior, and related tools. It leaves the removal side effect on existing scheduled posts unstated, so it is strong but not fully complete.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by mapping weekdays 1-7 to Monday-Sunday, explaining count as posts per day, and clarifying that adding an existing weekday sets that slot's count.

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 opens with a specific verb-resource pair, 'Adds or removes a channel's posting slots,' and immediately defines what a slot is. It clearly distinguishes this recurring weekly-slot configuration from channel posting time settings by pointing to update_channel_settings.

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 names related tools (list_channels, get_calendar, update_channel_settings) and explains that removal IDs come from get_calendar, giving clear context for use. However, it never explicitly states when to choose this over alternatives like post-level rescheduling or when not to use it.

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

All Mark toolsInspect
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