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

Save the confirmed workspace setup

save_workspace_setup

Destructive

Save the company profile and setup answers the customer confirmed, exactly as preview_workspace_setup reviewed them, with its reviewToken. Call it only after the customer confirms the summary. A changed payload or a workspace changed since the review is refused; preview again. Saving the company confirms it and starts a fresh set of setup audiences. Then read get_workspace view=playbook, propose one or two campaigns with audience, rationale and full messages, check each with check_campaign and save only what the customer approves. Contacts no one. Only a workspace owner or admin's connection may use it. Returns what was saved and the setup revision.

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": {
      "reviewToken": "<reviewToken>"
    },
    "name": "save_workspace_setup"
  }
}

Input Schema

Name	Required	Description
`answers`	No	The setup answers you drafted: proof, best customer, warm sources, audiences, signals and channels.
`company`	No	The company profile you drafted from what you know about the business: name, website, offer, buyers, audiences and proof the person confirmed.
`reviewToken`	Yes	The reviewToken preview_workspace_setup returned for this exact payload.
`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
`next`	No	The suggested next call, or null.
`saved`	Yes	true when the setup was saved.
`contacted`	No	Always false.
`answersSaved`	No	Whether the setup answers were saved.
`companySaved`	No	Whether the company profile was saved and confirmed.
`setupRevision`	No	The setup revision after saving; build_campaigns needs the plan's revision.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, it discloses refusal conditions, that saving starts a fresh set of setup audiences, that it contacts no one, and that only a workspace owner or admin connection may use it. These are concrete behavioral and authorization details that materially help an agent invoke it correctly.

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?

The description is dense but front-loaded: purpose first, then the confirmation precondition, refusal behavior, follow-on workflow, side effects, authorization, and return. Every sentence carries operational guidance without 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?

Given the mutation side effects, deep nested schema, annotations, and existing output schema, the description covers the essential missing context: confirmation prerequisite, token consistency, refusal handling, authorization, side effects, and next steps.

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 already 100%, so the baseline is 3. The description adds useful meaning about reviewToken validity: it must match the previewed payload exactly, and a changed payload or changed workspace will be refused, requiring another preview.

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 states a specific action: save the company profile and setup answers exactly as preview_workspace_setup reviewed them, using its reviewToken. It clearly distinguishes this from preview by saying it should only be called after customer confirmation, and it names the exact resource being saved.

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 gives explicit when-to-use guidance: only after the customer confirms the summary, and preview again if the payload or workspace changed. It also describes the follow-on workflow with get_workspace view=playbook, check_campaign, and saving only approved campaigns.

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?