Skip to main content
Glama

socialclaw

by io.github.ndesv21

apply_schedule

Create a publishing run from a schedule document. Posts are scheduled or published through connected accounts. Send an idempotencyKey so retries do not create duplicate runs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scheduleYesSocialClaw schedule document. Minimal shape: { timezone, posts: [{ account, name, description, publish_at, media_link? }] }. Campaign documents use { timezone, campaigns: [...] }. Per-post provider settings go in settings, e.g. TikTok inbox mode: settings: { tiktokPostMode: "draft" } sends the media to TikTok's inbox notification flow instead of publishing, and the creator finishes the post inside the TikTok app.
idempotencyKeyNoStable key to deduplicate retries.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / schedule / description
      Previous value: -"SocialClaw schedule document. Minimal shape: { timezone, posts: [{ account, name, description, publish_at, media_link? }] }. Campaign documents use { timezone, campaigns: [...] }. Per-post provider settings go in settings, e.g. TikTok drafts: settings: { tiktokPostMode: \"draft\" } uploads the media to the account's TikTok drafts (inbox) instead of publishing, and the creator finishes the post inside the TikTok app."New value: +"SocialClaw schedule document. Minimal shape: { timezone, posts: [{ account, name, description, publish_at, media_link? }] }. Campaign documents use { timezone, campaigns: [...] }. Per-post provider settings go in settings, e.g. TikTok inbox mode: settings: { tiktokPostMode: \"draft\" } sends the media to TikTok's inbox notification flow instead of publishing, and the creator finishes the post inside the TikTok app."
  2. Changed1 schema field changed
    • changedInput schema / properties / schedule / description
      Previous value: -"SocialClaw schedule document. Minimal shape: { timezone, posts: [{ account, name, description, publish_at, media_link? }] }. Campaign documents use { timezone, campaigns: [...] }."New value: +"SocialClaw schedule document. Minimal shape: { timezone, posts: [{ account, name, description, publish_at, media_link? }] }. Campaign documents use { timezone, campaigns: [...] }. Per-post provider settings go in settings, e.g. TikTok drafts: settings: { tiktokPostMode: \"draft\" } uploads the media to the account's TikTok drafts (inbox) instead of publishing, and the creator finishes the post inside the TikTok app."
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It discloses that posts are 'scheduled or published through connected accounts' and that idempotencyKey prevents duplicate runs on retries. However, it does not mention side effects, error behavior, or what exactly constitutes a 'publishing run' in terms of irreversible actions.

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 sentences, front-loaded with the primary purpose, and every sentence adds useful information. No fluff or repetition of schema details.

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

Completeness3/5

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

With no output schema, the description should cover return values or how to monitor success; it does not. It covers the core purpose, connected-account behavior, and idempotency, but for a mutation tool with potential multi-step publishing, more detail about what happens after the call would improve completeness.

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 100%, so the baseline is 3. The description adds value by explaining the practical purpose of idempotencyKey ('so retries do not create duplicate runs') beyond the schema's 'Stable key to deduplicate retries,' and the schedule parameter is already well-documented in the schema.

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 clearly states the tool's action and resource: 'Create a publishing run from a schedule document.' It distinguishes from siblings like publish_draft (single draft) and validate_schedule (validation only) by focusing on batch/schedule-driven publishing.

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

Usage Guidelines3/5

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

Usage is implied: if you have a schedule document, apply_schedule is the tool to use. The idempotencyKey note gives retry-related guidance, but there is no explicit comparison to alternatives or when-not-to-use conditions, unlike the calibration example that named a sibling tool.

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

All socialclaw toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but a few are close: delete_instagram_comment vs hide_instagram_comment overlap (though one is preferred), and get_analytics overlaps with Instagram-specific analytics tools. Overall, the boundaries are generally clear, with only minor potential confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., list_accounts, connect_account, upload_asset, cancel_post). There are no deviations in style or grammar, making the naming highly predictable.

Tool Count2/5

With 31 tools, this exceeds the 25-tool threshold for 'too many'. While the broad multi-provider social media domain justifies some breadth, the sheer number makes the surface heavy and potentially overwhelming, pushing the score down.

Completeness4/5

The tool set covers core workflows well: account connection, scheduling/publishing, post management, analytics, Instagram-specific engagement (comments, messages), asset upload, and workspace health/usage. Minor gaps include no explicit disconnect_account or delete_post, but these are edge cases; the domain is largely covered.

Resources