Skip to main content
Glama
loomiomcp
by soil-dev

update_discussion

DestructiveIdempotent

Edit a Loomio discussion by id or key, changing only the fields you supply, such as title, body, privacy, permissions, or recipients.

Instructions

Edit a discussion by id_or_key: 1 call. Pass only what changes: title, description (REPLACES the body: read it first, send the whole text), private, allow_* flags, recipients to add. Cannot move a thread or change its tags; a discarded thread cannot be edited.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id_or_key": "<id_or_key>"
    },
    "name": "update_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
privateNotrue = members only; must fit `discussion_privacy_options`.
id_or_keyYesDiscussion id or short key.
descriptionNoNew body; REPLACES the whole description.
allow_commentsNoWhether members may comment.
allow_reactionsNoWhether members may react.
recipient_emailsNoEmails to invite as readers; non-members become guests.
notify_recipientsNofalse = add recipients without emailing them.
recipient_messageNoNotification text; records a visible 'edited' item.
description_formatNoOmitted = the STORED format stays; send 'html' when the text is HTML.
recipient_audienceNo'group' = notify the whole group (needs announce permission).
recipient_user_idsNoUser ids to add as readers and notify.
polls_one_at_a_timeNotrue = one open poll at a time.
attachments_admin_onlyNoOnly admins may add attachments (Loomio 3.14+).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.0.19
    • removedInput schema / properties / allow_concurrent_polls
      Removed value: -{
      -  "description": "Allow several open polls at once.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / attachments_admin_only
      Added value: +{
      +  "description": "Only admins may add attachments (Loomio 3.14+).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / polls_one_at_a_time
      Added value: +{
      +  "description": "true = one open poll at a time.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / id_or_key / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[A-Za-z0-9_-]+$",
      -    "type": "string"
      -  },
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  }
      +]
  3. Addedv0.0.13

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true; the description adds genuinely non-obvious behavior on top: the body is fully replaced rather than appended (with the read-first workflow), recipient additions can trigger notifications and a visible 'edited' item, and certain operations are refused outright. It does not disclose return content or how partial failures behave, keeping it below 5.

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?

Terse and front-loaded: the identifier, the patch rule, the destructive body-replacement warning, then the exclusions. A few shorthand items ('1 call', '`allow_*` flags') are slightly cryptic but recoverable from the schema, and nothing is redundant.

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

Completeness4/5

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

For a 14-parameter mutation with no output schema, the description covers the highest-risk behaviors (body replacement, notification side effects, blocked operations) and leans on a well-documented schema for the rest. The one real gap is that it says nothing about what the call returns or whether the edited object is echoed back.

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 coverage is 93%, so the baseline is 3; the description earns above that by grouping the boolean knobs as 'allow_* flags', flagging recipients as add-only, and stressing the replace semantics with a concrete pre-read instruction. It still leaves several parameters (description_format, polls_one_at_a_time, attachments_admin_only, notify_recipients) to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Edit a discussion by `id_or_key`') and immediately states the patch-style scope ('Pass only what changes'), which is enough to tell it apart from create_discussion, delete_discussion and the update_comment/update_poll siblings by resource alone. It does not explicitly contrast with any sibling, so it stops short of a 5.

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?

Gives clear positive usage (send only changed fields) plus real exclusions: cannot move a thread, cannot change tags, a discarded thread cannot be edited. What is missing is routing — it never says which tool to use instead for tags or thread moves, so an agent knows what is impossible but not where to go.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.