delimit

Official

Overview Schema Source Related Servers Discussions Admin

Delimit Social Post

delimit_social_post

Publish authorized social posts to Twitter or Reddit, or create drafts for approval when immediate posting isn't authorized.

Instructions

Post to social media (Twitter / Reddit) (Pro).

When to use: after the user explicitly authorizes the external post in the current session, or when draft=True is used to prepare a review artifact that cannot publish by itself. When NOT to use: just to generate (use delimit_social_generate) or to inspect history (delimit_social_history).

Sibling contrast: delimit_social_generate is draft-only; delimit_social_approve manages the queue; this is the actual post path.

Side effects: when draft=True, queues for delimit_social_approve. Otherwise posts via the social backend. Subject to rate cap: 2 original posts per hour, 24 per day (founder-approved 2026-04-30). Override via DELIMIT_HOURLY_TWEETS / DELIMIT_DAILY_TWEETS env. Sends approval email with the registry_draft_id for inbox-daemon matching.

IMPORTANT - EXTERNAL ACTION BOUNDARY: draft=False can publish externally. Do not invoke that path without explicit current-session authorization or an applicable operator policy already supplied to the session. A draft/approval queue is not itself authorization to publish.

Categories: tip, changelog, insight, engagement. Leave text empty to auto-generate from templates. Every post provides value - tips, insights, governance wisdom. Rate cap: 2 original posts per hour, 24 per day (founder-approved 2026-04-30). Override via DELIMIT_HOURLY_TWEETS / DELIMIT_DAILY_TWEETS.

IMPORTANT - Platform tone rules (these are DIFFERENT per platform):

Twitter: confident technical brand. Direct, professional, ALWAYS POSITIVE. Celebrate wins and progress. Never complain or air gaps publicly. No em dashes or en dashes. Default to insight-first with no CTA unless source-grounded.
Reddit: helpful builder voice. Grounded, concise, never salesy. Default to no Delimit mention unless directly necessary and source-grounded. NO bullet points/lists/bold/em dashes. 2-3 sentences max.
LinkedIn: professional hook + insight + CTA

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	No	Tweet text. Leave empty to auto-generate.
`draft`	No	If True, save as draft for approval instead of posting immediately.
`account`	No	Twitter handle (without @) to post from. Empty = default account.
`context`	No	WHY this post should be made. Strategic reasoning shown in the approval email.
`category`	No	Content category for auto-generation.
`platform`	No	Social platform (twitter).	twitter
`reply_to_id`	No	Tweet ID to reply to (creates a reply).
`quote_tweet_id`	No	Tweet ID to quote (creates a quote tweet).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv4.5.5May 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint:false and destructiveHint:false annotations, the description discloses external publishing side effects, draft queueing behavior, rate caps, approval-email side effects, and an explicit authorization boundary for draft=False. This is exactly the behavioral context needed for an externally mutating tool.

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

Conciseness3/5

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

The description is well-sectioned and front-loaded, but it repeats the rate-cap sentence verbatim and includes filler like 'Every post provides value - tips, insights, governance wisdom.' Some sentences do not earn their place.

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?

For a high-complexity, externally mutating tool, the description covers authorization, drafts, side effects, rate limits, exclusions, and platform tone. It loses a point because the Reddit/LinkedIn references conflict with the schema's 'twitter' platform description and redundant sections add noise.

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 meaningful guidance on leaving text empty to auto-generate, category choices, and per-platform tone rules. However, there is a minor mismatch: the schema's platform field says '(twitter)' while the description also discusses Reddit and LinkedIn.

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 and resource ('Post to social media (Twitter / Reddit)') and explicitly positions itself as 'the actual post path' versus siblings like delimit_social_generate and delimit_social_approve. This makes the tool's role unambiguous.

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?

The description contains explicit 'When to use' and 'When NOT to use' sections, names the exact alternative tools, and clarifies the draft/approval queue relationship. An agent receives direct routing instructions for choosing this tool over its siblings.

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

Deploy Server