Skip to main content
Glama

list_events

Read-onlyIdempotent

Retrieve the event stream for a discussion, including comments, polls, and reactions. Filter by event kind and page through results with limit and offset to trace reply trees or identify participants.

Instructions

Fetch the event stream for ONE discussion — new_comment, poll_created, stance_created, outcome_created, reaction, discussion_moved, etc. — with actor_id, kind, parent_id, created_at, and pointers to the underlying eventable record. Required: discussion_id. By default the connector paginates Loomio's v1/events endpoint up to a bounded cap and returns scope.complete; if you pass limit and/or offset, it returns exactly that one page. Optional kinds filters client-side after fetch. The response also embeds related comments, users, and polls arrays for in-place resolution. Use this to answer 'show me the reply tree for thread X', 'who participated in discussion Y', or as the building block for cross-discussion aggregations. Loomio's v1/events endpoint REQUIRES a discussion_id; there is no instance-wide, per-group, or per-user index. For user-centric questions across many discussions ('how active is X', 'compare members across groups'), use get_user_activity — do NOT loop list_events over every discussion yourself. get_user_activity does that fan-out server-side with concurrency control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
discussion_idYesID of the discussion whose event stream to fetch. Required — Loomio's v1/events endpoint silently returns empty without it.
limitNoPage size for a single-page fetch. Omit limit/offset to let the connector paginate the full discussion stream up to its bounded cap.
offsetNoPage offset (Loomio's `from` parameter). When supplied, list_events returns exactly that page instead of auto-paginating.
kindsNoOptional filter to only these event kinds (applied client-side after fetch — Loomio doesn't filter `kind` server-side). Common kinds: new_discussion, new_comment, comment_edited, poll_created, stance_created, outcome_created, discussion_moved, discussion_closed, reaction.
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds pagination details, client-side kind filtering, embedded arrays, and the required discussion_id constraint, all consistent with annotations.

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?

The description is well-structured, front-loaded with core purpose, and each sentence adds necessary information without redundancy.

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?

Despite no output schema, the description details the response shape (fields, embedded arrays) and covers behavioral constraints, pagination, and alternatives, fully preparing the agent.

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

Parameters5/5

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

Schema coverage is 100% with descriptions. The description adds further context: pagination behavior, that kinds filter client-side, and that limit/offset yield single pages, enhancing understanding 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?

The description clearly specifies that this tool fetches the event stream for exactly one discussion, lists specific event kinds, and contrasts with siblings by warning against looping over discussions for user-centric queries.

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 states when to use (reply tree, participant info) and when not to (user-centric questions), recommends alternative get_user_activity, and explains pagination behavior with limit/offset.

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