Influence

List Whop companies

whopCompanyList

Read-onlyIdempotent

List available publishing companies. 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": "whopCompanyList",
-        "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": "whopCompanyList",
-        "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": "whopCompanyList",
+        "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": "whopCompanyList",
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "ok",
+      "toolName"
+    ],
+    "type": "object"
+  }
+]

First observedOct 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/not-open-world, so the burden is low; the description still adds real value by stating prerequisites (owned active account, provider availability) and pagination behavior ('Follow nextCursor until done, keeping the same connection and search fields'). It does not cover rate limits or empty-result behavior, hence a 4 rather than 5.

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, front-loaded with the purpose, then prerequisites, then the pagination instruction. No filler or redundancy.

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?

An output schema exists so return values need no explanation, and the description covers purpose, prereqs, and pagination. For a simple two-parameter list tool this is largely complete, with only the absence of any 'when not to use' note as a minor gap.

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 100% so the baseline is 3, and the description adds genuinely useful pagination semantics: keep the same connection and search fields while advancing nextCursor. This reinforces the cursor/connectionId contract beyond the schema's terse field descriptions.

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?

States a specific verb and resource ('List available publishing companies'), letting an agent distinguish it from siblings like whopExperienceList without opening any schema. The phrasing is precise about the resource type being listed.

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?

Gives prerequisites ('Requires an owned active account and current provider availability') but does not say when to prefer this over alternatives or when it should not be used. Usage is implied by the listing purpose and the account prerequisite rather than stated as routing guidance.

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?