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

Edit an X Play's audience or sequence

edit_x_play
Destructive

Change an X Play's name, audience rules, buying signal fields or attached sequence, exactly as the customer asked. Read the Play with list_x_plays first and pass its revision as expectedRevision; fields you leave out stay unchanged and the sender stays fixed. Signal fields (competitors, phrases and the rest) apply only to a Buying intent Play and replace its sources. A Play that enrolls automatically may route future people differently after an audience or sequence change. It never pauses, resumes or turns automatic enrollment on or off (set_x_play_status does that), connects accounts or sends anything. Returns the Play after the change.

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": {
      "playId": "<playId>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "edit_x_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA new name for the Play.
planNoAudience rules to change; each omitted rule stays as it is.
playIdYesThe X Play's ID, from list_x_plays.
signalNoWhich 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).
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.
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.
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.
expectedRevisionYesThe Play's current revision from list_x_plays; a stale revision is refused so a concurrent change is never overwritten.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the destructiveHint/openWorldHint annotations, the description discloses patch semantics (omitted fields unchanged, sender fixed), that signal fields replace rather than merge sources, that signal fields only apply to Buying intent Plays, that automatic enrollment may route future people differently, and that stale revisions are refused. It does not explain what exactly the destructiveHint risk covers (e.g. audience replacement consequences for enrolled people), leaving a small gap.

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?

Front-loaded with the action, then the revision protocol, then the semantic caveats, then the return value. Every sentence carries decision-relevant information despite the length forced by 13 parameters.

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?

For a 13-parameter, nested-object mutation with an output schema, the description covers the mutation contract, the concurrency guard, scoping side effects, and the boundary against a sibling tool. Nothing an agent needs to call it safely is missing.

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 baseline is 3, but the description adds real meaning the schema does not: omission means "keep as is", and signal fields replace the Play's sources rather than augment them, which changes how an agent should populate competitor/phrase arrays.

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?

"Change an X Play's name, audience rules, buying signal fields or attached sequence" names a specific verb and enumerates the mutable surface, which distinguishes it cleanly from set_x_play_status and create_x_play.

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?

Explicit prerequisite workflow: read with list_x_plays first and pass its revision as expectedRevision. It also names the excluded operations and the alternative tool ("It never pauses, resumes or turns automatic enrollment on or off (set_x_play_status does that)").

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