create_board
ChatGPTCreates a structured Kanban-style board only when the user explicitly asks to create/build/make a board. Call this tool ONLY for clear, direct commands such as: 'create a board', 'make a board for this', 'set up a board', 'add as a board to my ideaboard', or equivalent explicit intent. Do NOT call this tool during normal discussion, planning, or brainstorming unless the user clearly requests board creation. You must generate the COMPLETE board structure using all relevant conversation context. Do not ask follow-up questions. Infer missing details when reasonable. The board must reflect content planning and work management in a Kanban-style flow (e.g., ideas -> planning -> execution -> review or similar logical stages). Generate: - A clear, concise board title (2-6 words). - Well-structured column titles (3-5 words each, representing workflow stages). - Cards that capture tasks, decisions, content ideas, and next steps based on the conversation. If sufficient detail exists, ALWAYS include cards. Only create an empty board if the user explicitly asks for no cards. Each card should be actionable and specific, not vague. Prefer clarity over abstraction. Card descriptions MUST: - Be rich HTML (never plain text). - Use proper structure (<p>, <ul>/<ol>, <li><p>...</p></li>, <strong>, headings where useful). - Adapt depth based on complexity (simple tasks -> short, complex tasks -> detailed). Card Quality Rules: - Titles should be clear and outcome-focused (5-8 words). - Avoid duplicate or overlapping cards. - Group related work logically within the same column. - Balance between too many small cards vs. overly large cards. Priority must be one of: low, medium, high (default: medium). Use high priority for critical path or blocking tasks.
create_card
ChatGPTCreates one high-quality idea or task card only when the user explicitly asks to create/save/add a card. Call this tool ONLY for clear, direct commands such as: 'create a card', 'add this as a card', 'save this idea', 'add to ideaboard', 'save this in my ideaboard' or equivalent explicit intent. Do NOT call this tool during normal discussion, brainstorming, Q&A, comparisons, or clarifications unless the user clearly requests card creation. You must generate the COMPLETE card using all relevant conversation context. Do not ask follow-up questions. Infer missing details when reasonable. The card should align with content planning or work management use cases (idea capture, tasks, execution steps, or decisions). Generate a strong, specific, outcome-focused title (5–8 words). Avoid vague titles. Description Generation Rules: - Adapt description depth dynamically based on conversation context and user intent. - Internally classify context as: 'brief', 'moderate', or 'detailed', and match output depth accordingly. - If the user requests a short/simple output → keep it concise. - If context is limited → produce a short, focused summary. - If context includes detailed discussion, research, or multiple messages → produce a structured, well-organized description with key points and insights. - Always prioritize clarity, structure, and usefulness over length. Description MUST: - Be rich HTML (never plain text) - Use valid structure: <p>, <ul>/<ol>, <li><p>...</p></li>, <strong>, and headings when appropriate - Use semantic hierarchy: one <h1> (optional for short content), <h2> for sections, <h3> only for nested subsections - Avoid unnecessary verbosity or excessive headings in simple cards Card Quality Rules: - Ensure the card is actionable, clear, and directly usable in a workflow - Avoid duplicating information or including irrelevant context - Structure content for quick scanning and execution (not long paragraphs only) Priority must be one of: low, medium, high (default: medium). Use high priority for urgent or critical tasks.
create_content_planner_posts
ChatGPTWrite tool: creates new content planner posts in draft status for the selected channels. Content supports text and one or multiple images, videos or animations. Use channel IDs from list_automation_channels. Integrators should require explicit user confirmation before invoking this tool.
list_automation_channels
ChatGPTFetches a list of available channels that can be used to create content planner posts.
