Skip to main content
Glama

delimit_content_publish

Manually trigger the next queued tweet or YouTube video on demand, bypassing the autonomous content loop.

Instructions

Manually trigger a content publish (tweet or YouTube video) (Pro).

When to use: to fire off the next queued tweet or video on demand, bypassing the autonomous content loop. When NOT to use: to inspect the queue (use delimit_content_schedule) or modify it (delimit_content_queue).

Sibling contrast: delimit_content_schedule reads; delimit_content_queue mutates queue; this performs a single publish step.

Side effects: writes to the social/YouTube backends — for tweet, posts the next queued tweet; for youtube, generates and uploads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_typeNo"tweet" (default) to post next queued tweet, or "youtube" to generate + upload the next video.tweet

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses side effects: writes to backends, posts tweet, generates/upload video. This informs the agent of mutating behavior.

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?

Concise, well-structured with labeled sections. Every sentence adds value. Front-loaded with main purpose.

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?

For a simple tool with one parameter and an output schema, the description covers purpose, usage, side effects, and sibling relationships. Complete enough for correct selection and invocation.

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

Parameters3/5

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

Schema coverage is 100% and the description adds no additional parameter meaning beyond what the schema already provides. Baseline 3 applies.

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 the action ('manually trigger a content publish') and resource ('tweet or YouTube video'). Distinguishes from siblings by naming delimit_content_schedule and delimit_content_queue.

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?

Explicit 'When to use' and 'When NOT to use' sections, plus sibling contrast listing specific alternatives. Guidance is direct and actionable.

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