PumpGTM

This connector has been deprecated

Duplicate listing. The official PumpGTM connector is https://glama.ai/mcp/connectors/com.pumpgtm/mcp (same server, https://mcp.pumpgtm.com/mcp).

Preview moving leads to another sequence

preview_move_leads

Read-onlyIdempotent

Read eligibility for moving up to 500 existing people to one sequence in this workspace. Only untouched outreach across LinkedIn, email and X qualifies; inspect every excluded reason. Queued on one channel is not proof the other channels are untouched. Preserves lead identities, original Play attribution and bound senders. Preview does not pause, move, approve or send. Use move_leads only for the customer's requested selection and destination. Returns eligibleCount, blockedCount and a per-person result with eligibility, reason and message.

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": {
      "leadIds": "<leadIds>",
      "sequenceId": "<sequenceId>"
    },
    "name": "preview_move_leads"
  }
}

Input Schema

Name	Required	Description
`leadIds`	Yes	IDs of the existing people to move, from list_leads. Each is checked separately.
`sequenceId`	Yes	Destination sequence ID, from list_sequences. It keeps its own approval and start status.
`workspaceId`	No	A teammate's workspace you may manage: an active workspace ID from list_team_workspaces. Omit for your own workspace. Supply on every call for a teammate.

Output Schema

Name	Required	Description
`results`	Yes	One entry per requested person.
`sequenceId`	Yes	Destination sequence ID.
`blockedCount`	Yes	How many people cannot move; inspect each reason.
`eligibleCount`	Yes	How many people can move now.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

addedInput schema / properties / leadIds / description

Added value: +"IDs of the existing people to move, from list_leads. Each is checked separately."

addedInput schema / properties / sequenceId / description

Added value: +"Destination sequence ID, from list_sequences. It keeps its own approval and start status."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "blockedCount": {
+      "description": "How many people cannot move; inspect each reason.",
+      "type": "number"
+    },
+    "eligibleCount": {
+      "description": "How many people can move now.",
+      "type": "number"
+    },
+    "results": {
+      "description": "One entry per requested person.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "eligible": {
+            "description": "true when this person can move to the destination.",
+            "type": "boolean"
+          },
+          "leadId": {
+            "description": "The person's lead ID.",
+            "type": "string"
+          },
+          "message": {
+            "description": "Plain-language explanation to show the customer.",
+            "type": "string"
+          },
+          "person": {
+            "description": "The person's name, or null when unknown.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reason": {
+            "description": "Why the person is blocked (or a safety note), or null. Codes such as outreach_started or contact_stopped.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sourceSequenceId": {
+            "description": "Sequence the person was in, or null.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "leadId",
+          "person",
+          "sourceSequenceId",
+          "reason",
+          "message",
+          "eligible"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sequenceId": {
+      "description": "Destination sequence ID.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "sequenceId",
+    "eligibleCount",
+    "blockedCount",
+    "results"
+  ],
+  "type": "object"
+}

AddedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), the description discloses crucial eligibility rules: only untouched outreach across LinkedIn, email and X qualifies, and queued on one channel is not proof the others are untouched. It also clarifies preservation guarantees (identities, Play attribution, bound senders) and explicitly states what the preview does NOT do (pause, move, approve, send), which is rich behavioral context.

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 front-loaded and dense with useful information, but it includes a redundant explanation of return fields (eligibleCount, blockedCount, per-person result) when an output schema exists. Most sentences earn their place, though the phrasing around 'queued on one channel' is slightly indirect.

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?

Given the complex eligibility rules, mutation-adjacent nature, and existing output schema, the description provides all the context an agent needs: what qualifies, what is preserved, what is not performed, and how it relates to move_leads. Nothing critical is missing.

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 description coverage is 100%, so the schema already documents leadIds, sequenceId, and workspaceId thoroughly. The description adds only the 'up to 500' limit, which duplicates the schema's maxItems constraint, and otherwise does not add per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Read eligibility for moving up to 500 existing people to one sequence in this workspace.' This clearly distinguishes it from the mutation sibling move_leads and tells an agent exactly what the tool does.

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?

It explicitly routes the agent: 'Use move_leads only for the customer's requested selection and destination,' implying preview should be used when evaluating eligibility. It also says 'inspect every excluded reason,' which is actionable guidance. The only gap is that it doesn't explicitly say 'call this before move_leads,' leaving the sequencing slightly inferred.

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

All PumpGTM 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?