Skip to main content
Glama

delimit_social_post

Post AI-generated social content to Twitter or Reddit automatically. Includes email approval flow for human review.

Instructions

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

When to use: when the AI drafts a social post, it MUST call this immediately (auto-trigger rule). Email approval flow handles human review. 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 - AUTO-TRIGGER RULE: When the AI drafts a social post, it MUST call this tool immediately. Never ask "want me to send this?" — just call the tool. The email-based approval flow handles human review.

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
NameRequiredDescriptionDefault
textNoTweet text. Leave empty to auto-generate.
categoryNoContent category for auto-generation.
platformNoSocial platform (twitter).twitter
accountNoTwitter handle (without @) to post from. Empty = default account.
quote_tweet_idNoTweet ID to quote (creates a quote tweet).
reply_to_idNoTweet ID to reply to (creates a reply).
draftNoIf True, save as draft for approval instead of posting immediately.
contextNoWHY this post should be made. Strategic reasoning shown in the approval email.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses side effects (queue for approval vs direct post), rate caps (2/hour, 24/day) with override env vars, sends approval email, and platform-specific tone rules. No annotations exist, so description carries full burden and delivers comprehensively.

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?

Well-structured with clear sections (When to use, Side effects, etc.) and front-loaded purpose. However, it repeats the auto-trigger rule twice and includes platform tone details that could be streamlined.

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?

With high parameter count, full schema coverage, and output schema, the description is exceptionally complete: covers side effects, rate caps, override mechanisms, email flow, platform tone rules, and auto-trigger logic.

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 covers 100% of parameters. Description adds context beyond schema for 'draft' (queues for approval), 'context' (strategic reasoning for email), and 'text' (auto-generation). Platform tone rules are separate from parameter semantics.

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 posts to social media (Twitter/Reddit), contrasts with siblings (delimit_social_generate, delimit_social_approve, delimit_social_history), and specifies the action 'post'.

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 states when to use (immediately after drafting), when not to use (use generate or history), and provides sibling contrast with actionable guidance for the AI agent.

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/delimit-ai/delimit-mcp-server'

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