Skip to main content
Glama

create_discussion

Create a new discussion thread in a Loomio group by specifying a title and group ID. Set the body, visibility, and notification recipients as needed.

Instructions

Create a new Loomio discussion (thread) in a group. Required: title, group_id. The private field is auto-resolved from the group's discussion_privacy_options when omitted (matches Loomio's web UI default — public_only → false, anything else → true); pass it explicitly to override. Optional description + description_format ('md' / 'html') set the body. Notification recipients can be specified via recipient_audience: 'group' (notify all members), recipient_user_ids (explicit user ids), or recipient_emails (invite new people), optionally with a recipient_message. Caller must be allowed to start discussions in the group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDiscussion title (required).
group_idYesID of the Loomio group to create the discussion in (required).
descriptionNoOptional discussion body.
description_formatNoFormat of `description`. Defaults to Loomio's group default when omitted.
privateNoVisibility: true = group members only, false = publicly visible. Loomio's validator enforces this against the group's `discussion_privacy_options`: `public_only` requires `private: false`, `private_only` requires `private: true`, `public_or_private` allows either. When omitted, the connector reads the group's setting and chooses the value Loomio's web UI would pick: `false` for `public_only`, `true` otherwise (matching `Group#discussion_private_default`). Pass an explicit value to override.
recipient_audienceNoAudience selector for notification recipients. 'group' = notify whole group.
recipient_user_idsNoExplicit list of user IDs to notify.
recipient_emailsNoExplicit list of email addresses to notify.
recipient_messageNoOptional custom message to include in notifications.
Behavior5/5

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

Description adds detail beyond annotations: auto-resolution of private field, notification options, permission requirements. Annotations indicate write operation (readOnlyHint=false) and side effects (openWorldHint=true), which description aligns with and expands upon.

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 with no redundant information. First sentence states primary purpose. All sentences add value, covering required fields, auto-resolution, optional fields, and permission requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description does not mention return value (likely the created discussion object). Lacks information on error handling or validation outcomes. Missing this factor despite good input coverage.

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 all 9 parameters with descriptions (100% coverage). Description adds behavioral context (e.g., private auto-resolution logic, recipient usage) that enhances schema, making semantic understanding richer.

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 verb 'Create', resource 'Loomio discussion (thread)', and context 'in a group'. Differentiates from siblings like create_comment, create_poll by focusing on discussion creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Specifies required fields (title, group_id), optional fields, and auto-resolution behavior for private. Mentions caller permission requirement. Does not explicitly list alternatives, but context is clear.

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/soil-dev/loomiomcp'

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