lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

slack_list_channel_members

Read-onlyIdempotent

Retrieve the full member list of any Slack channel through the Lightbulb platform's governed connector, giving you quick visibility into channel participation under a project's authenticated authority.

Instructions

Slack connector operation list_channel_members (platform tool slack.list_channel_members).

Routes only through the exact project/account governed connector authority.

Args: arguments: JSON string of arguments for the connector operation. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Required and must be read; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema

Name	Required	Default
`effect`	Yes
`arguments`	No	{}
`project_id`	No
`project_ref`	No
`approval_ref`	No
`idempotency_key`	No
`connector_account_ref`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.1Sep 7, 2026

addedInput schema / properties / approval_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}

addedInput schema / properties / connector_account_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}

addedInput schema / properties / effect

Added value: +{
+  "const": "read",
+  "title": "Effect",
+  "type": "string"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}

addedInput schema / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}

addedInput schema / properties / project_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}

addedInput schema / required
```
Added value: +[
+  "effect"
+]
```

First observedv0.1.0Jun 25, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds some context by noting the exact governed authority routing and that 'effect: Required and must be read; Spring verifies it'. However, it does not describe what the operation returns, pagination behavior, or any side effects beyond what annotations convey, and the mention of approval_ref 'when resuming a write' is tangential for a read operation.

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?

The description is compact and structured: a short header, one routing sentence, and an enumerated Args list. The first line is somewhat redundant with the tool name, but the list format makes the parameter details easy to scan and the routing constraint is front-loaded. No unnecessary prose is present.

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

Completeness2/5

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

Although an output schema exists and annotations cover the safety profile, the description is incomplete for actually invoking this tool correctly. It fails to explain what 'list_channel_members' does semantically, how to populate the `arguments` JSON string with the target channel, or how this tool differs from related Slack list operations. The generic wrapper language makes it insufficiently complete for an agent to use confidently.

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

Parameters3/5

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

With 0% schema description coverage, the description compensates by providing one-line meanings for all seven parameters (e.g., project_id as 'Authenticated Project UUID', connector_account_ref as 'Project-bound connector account alias'). This is valuable, but the critical `arguments` parameter is only described as 'JSON string of arguments for the connector operation' without specifying what Slack-specific fields (such as channel) are needed. This leaves a meaningful gap in understanding how to correctly invoke the operation.

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

Purpose2/5

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

The description's first sentence restates the tool name: 'Slack connector operation `list_channel_members` (platform tool `slack.list_channel_members`)'. It never explicitly states that the operation lists the members of a Slack channel, which is the core purpose. The name is self-descriptive, but the description adds no verb+resource clarity beyond the name itself and does not differentiate from sibling tools like slack_list_channels or slack_list_users.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. The routing statement, 'Routes only through the exact project/account governed connector authority', describes a constraint, not a usage context. There is no mention of scenarios, prerequisites, or exclusions that would help an agent decide to invoke this tool over other Slack listing tools.

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

Deploy Server