Skip to main content
Glama
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).

Reach everyone who engaged with a LinkedIn or X post

reach_post_engagers

LinkedIn profileUrl plus message explicitly follows that profile: check the latest 10 posts from the past 30 days every six hours and automatically enroll up to 500 new engagers per collection. Only use profileUrl when the customer requests recurring outreach. LinkedIn post URL plus message: PumpGTM creates a Play with its own approved sequence (note-less connection request, then your message), fetches every reactor and commenter in the background (up to 500), and enrolls all of them; call again with only playId for progress. X post URL (x.com/…/status/…) plus message, or plus an existing X sequenceId: creates a real X Play, its audience rules and collection source, and returns its Play link. X defaults to review before enrollment; select engagements when the customer wants only likes or replies. The customer adds selected people to the X sequence (or with add_to_sequence). followers=true instead of a post URL creates a new-followers X Play. A supplied Sequence keeps its status; a message creates an approved active Sequence. Existing shared sources retain their status, Sequence and collection progress. Report polling blockers and paused Sequences exactly as returned; do not promise polling or sending while blocked. Follower Plays can still receive incoming X follow events while fallback polling is blocked. Use manage_x_play to inspect/edit the returned X Play, including enabling autopilot only when the customer requests automatic enrollment. watchId alone checks source/Sequence progress. The X call itself never enrolls or sends.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asNoX only: which connected account's post or followers (@handle) when the workspace has several; default the first connected.
nameNo
playIdNo
messageNo
postUrlNo
watchIdNo
followersNoX only: collect the account's new followers for review instead of a post's engagers.
profileUrlNoLinkedIn only: explicitly follow this personal profile's latest posts and automatically enroll new reactors and commenters every six hours. Use with message instead of postUrl.
sequenceIdNoX posts only: an existing X DM sequence instead of a new one from message.
engagementsNoX posts only: liked for likes, replied for replies, both when the customer requests all engagers. Defaults to both.
workspaceIdNoA 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • addedInput schema / properties / profileUrl
      Added value: +{
      +  "description": "LinkedIn only: explicitly follow this personal profile's latest posts and automatically enroll new reactors and commenters every six hours. Use with message instead of postUrl.",
      +  "format": "uri",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations say non-readonly, non-destructive, non-idempotent; the description adds the 500-engager cap, six-hour polling, approval defaults, paused sequences, and that X calls never enroll. It notes polling blockers and fallback behavior, which is valuable context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single massive paragraph with no structure, run-on sentences, and extensive detail. It is not front-loaded; the agent must parse through many clauses to find key routing logic. This hurts readability and quick comprehension.

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?

Given the complexity (11 params, no output schema, multi-platform), the description covers the major behaviors, branching, and limitations well. Minor gaps remain regarding error handling or exact return shape, but it is largely complete.

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 55%, so the description must compensate. It explains profileUrl, message, postUrl, playId, watchId, followers, engagements, and sequenceId semantics well, though it doesn't clarify the optional 'name' or 'as' beyond what the schema already states.

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?

The description names a specific verb (reach) and resource (post engagers) and distinguishes between LinkedIn and X paths with detailed branching. It is clear what the tool does, though the density and lack of a concise opening sentence reduce immediate clarity.

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?

Explicit conditions are given for using profileUrl (recurring outreach only), for X engagements vs all, and for followers=true, with references to manage_x_play and watchId. However, it doesn't fully compare against add_to_sequence or other alternatives for enrolling contacts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources