Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

delimit_social_target

Scans X, Reddit, HN, Dev.to, and GitHub to discover posts where your venture can engage. Automatically drafts replies or creates ledger items for strategic targets.

Instructions

Discover engagement opportunities across platforms (Pro).

When to use: to find posts on X, Reddit, HN, Dev.to, GitHub where a Delimit venture can engage. Run inside a /loop for continuous discovery. When NOT to use: to fetch one X tweet (use delimit_x_fetch) or drafts (delimit_social_generate).

Sibling contrast: delimit_social_target_config configures which platforms to scan; delimit_x_fetch is single-tweet; this is the multi-platform scanner.

Side effects: read-only network scans by default. With draft_replies=True, calls delimit_social_post(draft=True) for "reply" targets. With create_ledger=True, calls delimit_ledger_add for "strategic" targets. Deduplicates across runs.

IMPORTANT - TOOL CHAINING RULE: After scanning, the AI MUST immediately process results:

  1. For "reply" targets: draft a reply via delimit_social_post or delimit_notify

  2. For "strategic" targets: create a ledger item via delimit_ledger_add

  3. For "both": do both Never just return targets and stop. Always chain to the next action.

Scans X, Reddit (RapidAPI), HN, Dev.to, GitHub for posts where ventures can engage. NamePros flagged as manual_check_needed (no API).

Run in a /loop for continuous discovery. Deduplicates across runs. Targets are classified as: reply (social engagement), strategic (ledger item), or both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo"scan" to discover targets, "list" to show recent, "stats" to show counts.scan
platformsNoComma-separated platforms to scan (x, hn, devto, reddit, github, namepros).x,hn,devto,reddit,github
venturesNoComma-separated ventures to scan for. Empty = all.
keywordsNoExtra keywords to search for beyond venture topics.
limitNoMax targets per platform.
draft_repliesNoIf True, auto-draft social posts for "reply" targets.
create_ledgerNoIf True, create ledger items for "strategic" targets.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Discloses side effects: read-only by default, conditional calls to other tools when flags are set, and deduplication across runs. Also details tool chaining requirements. While no annotations exist, this provides sufficient behavioral insight for agent decision-making.

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 sections for purpose, usage, contrast, side effects, and chaining rules. Minor repetition of '/loop' guidance, but overall efficient and front-loaded with key purpose and usage guidelines.

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?

Covers all essential aspects: purpose, when to use/not, sibling differentiation, side effects, required follow-up actions, and output classification. Given the complexity (7 parameters, output schema exists), the description leaves no significant gaps for an agent to invoke it correctly.

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?

With 100% schema coverage, the description still adds value by explaining target classification (reply, strategic, both) and how parameters like draft_replies and create_ledger trigger side effects. Context about platform enumeration and NamePros limitations is helpful beyond 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?

Clearly states the tool discovers engagement opportunities across platforms (Pro). It distinguishes itself from siblings delimit_social_target_config and delimit_x_fetch by specifying it is a multi-platform scanner, while the former configures platforms and the latter fetches single tweets.

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 provides when to use (to find posts for engagement, run in /loop) and when NOT to use (for single tweet or drafts, with named alternatives). The 'Sibling contrast' section further clarifies differentiation.

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