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).

List leads

list_leads

Read-onlyIdempotent

This workspace's leads with LinkedIn and sequence progress. stage is cumulative (reached this milestone or beyond); stageExact is the current position only. Count is exact even when the page is limited. Pass leadId to read one lead in full. To undo a removal whose ID was not saved, search with query without activity/stage filters, identify the correct person and sequence, then pass their removal.id to undo_remove_leads. removal is null when no current Undo event is available; do not add a replacement lead. A returned ID still requires Undo's normal safety checks.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Zero-based page for personalFiles.
`limit`	No
`query`	No
`stage`	No
`leadId`	No
`sinceDays`	No
`bookedOnly`	No
`sequenceId`	No
`stageExact`	No
`strategyId`	No
`engagedOnly`	No
`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.
`personalFiles`	No	With sequenceId: which file each person has for that sequence's per-person file step (for example their personalised video), 25 people a page: file name and size, and state waiting (no file yet), ready (attached, not sent), sent, or closed (not needed). query narrows by name, email, company or handle; waitingForInput=true lists only people still missing a file. Use it when the customer wants to check who got which file; appUrl opens the same table in the app, where each video can be watched.
`waitingForInput`	No	Only people the engine is holding because a LinkedIn message, email, X DM or Instagram DM step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists channel, waitingFor keys (waitingForFiles names the ones that are a file for that person) and waitingSince.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / waitingForInput / description

Previous value: -"Only people the engine is holding because a LinkedIn message, email or X DM step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists channel, waitingFor keys (waitingForFiles names the ones that are a file for that person) and waitingSince."New value: +"Only people the engine is holding because a LinkedIn message, email, X DM or Instagram DM step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists channel, waitingFor keys (waitingForFiles names the ones that are a file for that person) and waitingSince."

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / page

Added value: +{
+  "description": "Zero-based page for personalFiles.",
+  "maximum": 400,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / personalFiles

Added value: +{
+  "description": "With sequenceId: which file each person has for that sequence's per-person file step (for example their personalised video), 25 people a page: file name and size, and state waiting (no file yet), ready (attached, not sent), sent, or closed (not needed). query narrows by name, email, company or handle; waitingForInput=true lists only people still missing a file. Use it when the customer wants to check who got which file; appUrl opens the same table in the app, where each video can be watched.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / waitingForInput / description

Previous value: -"Only people the engine is holding because a LinkedIn message, email or X DM step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists channel, waitingFor keys and waitingSince."New value: +"Only people the engine is holding because a LinkedIn message, email or X DM step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists channel, waitingFor keys (waitingForFiles names the ones that are a file for that person) and waitingSince."

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / waitingForInput / description

Previous value: -"Only people the engine is holding because a message step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists waitingFor keys and waitingSince."New value: +"Only people the engine is holding because a LinkedIn message, email or X DM step needs a value from the customer (see leads_waiting_for_input in get_workspace). Each returned lead lists channel, waitingFor keys and waitingSince."

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"Team owner only: an active workspace ID from list_team_workspaces. Omit for your own workspace. Supply on every call for a teammate."New value: +"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."

First observedOct 1, 2026

TDQS

Score is being calculated.

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?