Influence

Get Listmonk lists

listmonkListsGet

Read-onlyIdempotent

List available subscriber lists. Requires an owned active account and current provider availability. Follow nextCursor until done, keeping the same connection and search fields.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cursor`	No	nextCursor from the previous page of this exact tool and input
`connectionId`	Yes	Owned connectionId returned by accountList

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "ok": {
-        "const": true,
-        "type": "boolean"
-      },
-      "output": {
-        "additionalProperties": false,
-        "properties": {
-          "output": {
-            "additionalProperties": false,
-            "properties": {
-              "done": {
-                "$ref": "#/$defs/__schema0"
-              },
-              "items": {
-                "$ref": "#/$defs/__schema1"
-              },
-              "nextCursor": {
-                "$ref": "#/$defs/__schema3"
-              }
-            },
-            "required": [
-              "done",
-              "items"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "output"
-        ],
-        "type": "object"
-      },
-      "toolName": {
-        "const": "listmonkListsGet",
-        "type": "string"
-      }
-    },
-    "required": [
-      "ok",
-      "output",
-      "toolName"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "enum": [
-              "INVALID_INPUT",
-              "FORBIDDEN",
-              "NOT_FOUND",
-              "CONFLICT",
-              "FEATURE_DISABLED",
-              "CONFIRMATION_REQUIRED",
-              "CONFIRMATION_INVALID",
-              "UPSTREAM_FAILED",
-              "NEEDS_REVIEW",
-              "INTERNAL"
-            ],
-            "type": "string"
-          },
-          "message": {
-            "maxLength": 2048,
-            "minLength": 1,
-            "type": "string"
-          },
-          "retryable": {
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "code",
-          "message",
-          "retryable"
-        ],
-        "type": "object"
-      },
-      "ok": {
-        "const": false,
-        "type": "boolean"
-      },
-      "toolName": {
-        "const": "listmonkListsGet",
-        "type": "string"
-      }
-    },
-    "required": [
-      "error",
-      "ok",
-      "toolName"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "ok": {
+        "const": true,
+        "type": "boolean"
+      },
+      "output": {
+        "additionalProperties": false,
+        "properties": {
+          "output": {
+            "additionalProperties": false,
+            "properties": {
+              "done": {
+                "$ref": "#/$defs/__schema0"
+              },
+              "items": {
+                "$ref": "#/$defs/__schema1"
+              },
+              "nextCursor": {
+                "$ref": "#/$defs/__schema3"
+              }
+            },
+            "required": [
+              "done",
+              "items"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "output"
+        ],
+        "type": "object"
+      },
+      "toolName": {
+        "const": "listmonkListsGet",
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "output",
+      "toolName"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "code": {
+            "enum": [
+              "AI_SCHEDULING_LIMIT_REACHED",
+              "AI_SCHEDULING_UNAVAILABLE",
+              "INVALID_INPUT",
+              "FORBIDDEN",
+              "NOT_FOUND",
+              "CONFLICT",
+              "FEATURE_DISABLED",
+              "CONFIRMATION_REQUIRED",
+              "CONFIRMATION_INVALID",
+              "UPSTREAM_FAILED",
+              "NEEDS_REVIEW",
+              "INTERNAL"
+            ],
+            "type": "string"
+          },
+          "message": {
+            "maxLength": 2048,
+            "minLength": 1,
+            "type": "string"
+          },
+          "retryable": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "code",
+          "message",
+          "retryable"
+        ],
+        "type": "object"
+      },
+      "ok": {
+        "const": false,
+        "type": "boolean"
+      },
+      "toolName": {
+        "const": "listmonkListsGet",
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "ok",
+      "toolName"
+    ],
+    "type": "object"
+  }
+]

First observedOct 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context: an account/provider availability gate that can make the call fail, plus the requirement to stay on the same connection while paging. This goes meaningfully beyond what the annotations state.

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?

Three short sentences, zero padding, with the core purpose and pagination protocol front-loaded before the prerequisites. Nothing here is filler.

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?

Preconditions, pagination, and cursor-stability are all covered, and an output schema exists so return values need not be described. The only blemish is the reference to "search fields" despite no search parameter in the schema, which could momentarily mislead an agent constructing the call.

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?

Schema coverage is 100%, so both parameters are already documented; the schema itself says cursor must come from a previous page of this exact tool and input. The description's "keeping the same connection and search fields" largely restates that, with the extra wrinkle that no search parameter actually exists in 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?

Specific verb+resource ("List available subscriber lists") with a clear scope, and the name identifies Listmonk. It does not differentiate from the sibling listmonkTemplateList or other *List tools, so an agent must infer the distinction.

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

Usage Guidelines3/5

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

It states preconditions (owned active account, provider availability) and a pagination protocol (follow nextCursor until done), which is genuinely useful usage guidance. However, it never says when to prefer this over alternatives such as listmonkTemplateList or when not to call it, so routing is left implicit.

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

All Influence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?