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

Create a Buying intent X Play

create_x_play

Create a Buying intent Play from one signal: people who follow several competitors, engage with competitors' posts, ask X or LinkedIn for a tool like the customer's, complain about a competitor, or ask on Reddit (signal explains each and the fields it needs). When the customer has not named competitors, suggest a few from the company profile and confirm before creating. Phrases are short buyer words, never the company's own marketing terms; criteria says who fits in one sentence. The Play collects people once a day, even before X is connected, and lists them for review; it never enrolls or messages anyone by itself. sequenceId attaches an existing sequence; message instead creates an approved active X DM sequence named after the Play. For Plays on the account's own posts or followers use reach_post_engagers. Returns the new Play with its review link and what happens next.

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": {
      "name": "<name>",
      "signal": "<signal>"
    },
    "name": "create_x_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe Play's name, e.g. "Founders who follow our competitors".
signalYesWhich buying signal the Play watches. competitor_followers: people following several competitor X accounts (competitors, minShared). competitor_post_engagers: people replying to, quoting or reposting the competitors' recent X posts (competitors, postsPerCompetitor). asks: people asking X and/or LinkedIn for a tool like the customer's (phrases, networks). complaints: people unhappy with a competitor on X and/or LinkedIn (phrases, competitors for X, competitorNames for LinkedIn). reddit: Reddit threads asking for what the customer sells, with a reply drafted for review (phrases, subreddits).
messageNoThe first X DM; creates an approved active X DM sequence named after the Play. Use instead of sequenceId.
phrasesNoasks, complaints, reddit: short search phrases in the words a buyer would write, e.g. "best bank for a startup" or "account frozen", never the company's own marketing terms.
criteriaNoWho fits, in one sentence, e.g. "Founders or finance leads at early-stage US startups". Found people are checked against it; omit to keep everyone the signal finds.
networksNoasks, complaints: where to search; omitted means X only.
minSharedNocompetitor_followers: how many of the competitors a person must follow to count; omitted means 3, capped at the number of competitors.
sequenceIdNoAn existing sequence from list_sequences to attach (X lane, or LinkedIn lane). Omit to attach none for now.
subredditsNoreddit: subreddits to prefer, as r/name or name. Threads elsewhere on Reddit still count; omit to search all of Reddit.
competitorsNoCompetitor X accounts as @handle, handle or x.com profile link: at least two for competitor_followers, at least one for competitor_post_engagers, optional for complaints (anchors the X search).
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.
competitorNamesNocomplaints on LinkedIn: competitor company names as written ("Mercury"), since LinkedIn posts name companies, not X handles.
postsPerCompetitorNocompetitor_post_engagers: how many of each competitor's newest posts are read every day; omitted means 5.

Output Schema

NameRequiredDescriptionDefault
playYesThe Play after this call.
changedYesWhether this call changed anything.
nextStepYesWhat happens next, in words to tell the customer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare creation, non-read-only, non-idempotent, open-world, and non-destructive. The description adds meaningful behavior beyond that: daily collection even before X is connected, no automatic enrollment or messaging, review-link output, and that message creates an approved active X DM sequence. It doesn't address duplicate-creation behavior despite idempotentHint=false, which keeps it below a 5.

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 with purpose and packed with useful routing and behavioral detail. It is dense and somewhat run-on, but nearly every clause carries actionable information rather than repetition.

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?

With an output schema, full parameter documentation, and annotations already present, the description adds the remaining decision context an agent needs: signal choice, competitor confirmation, sequence attachment, daily collection behavior, and the sibling alternative. Nothing material is missing for correct invocation.

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 the schema already documents all 13 parameters in detail. The description reinforces a few semantics, such as phrases being short buyer words rather than marketing terms and criteria being one sentence, but most of that is already in the schema 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?

The description opens with a specific verb and resource ("Create a Buying intent Play") and immediately scopes the five signal types that define the Play. It explicitly distinguishes itself from reach_post_engagers by naming that sibling for Plays on the account's own posts or followers.

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

Usage Guidelines5/5

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

It states when to use this tool versus reach_post_engagers, when to suggest competitors from the company profile and confirm first, and when to use sequenceId versus message. These are explicit routing and prerequisite conditions rather than implied usage.

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