PumpGTM MCP server

Plan setup campaigns

plan_campaigns

Read-onlyIdempotent

List the standard campaigns PumpGTM would build from the saved setup answers, with each one's channels, what it needs and whether it is already built. Use it when the customer has little business context to draft campaigns from; offer the one or two that fit best and build only the ones they pick with build_campaigns, passing setupRevision as expectedRevision. Read-only: saves nothing. Only a workspace owner or admin's connection may use it. Returns companyConfirmed, setupRevision, channels and campaigns, with a reason when there are none yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_campaigns"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`reason`	No	Why there are no campaigns yet.
`channels`	Yes	Channels the person chose.
`campaigns`	Yes	Campaigns PumpGTM can build.
`setupRevision`	Yes	Pass as expectedRevision to build_campaigns.
`companyConfirmed`	Yes	Whether the company profile is confirmed; campaigns build only after it is.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only: saves nothing' is largely redundant. What the description adds beyond the structured fields is meaningful: an authorization constraint ('Only a workspace owner or admin's connection may use it') and the response shape including the empty-state 'reason', neither of which annotations convey.

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?

Front-loaded with the purpose and value, then chaining guidance, then constraints and returns – a sensible priority order. Minor waste in 'Read-only: saves nothing', which repeats the annotation, and the return-value sentence is somewhat redundant given an output schema exists.

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 zero-required-parameter read tool with full annotation coverage and an output schema, the description covers everything an agent needs: when to call it, how to hand off to build_campaigns, the permission prerequisite, and the empty-result behavior. No material gaps remain.

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 description coverage is 100% and the single workspaceId parameter is fully documented in the schema with its default behavior for omission. The description does not mention workspaceId at all; it references setupRevision only as a return value consumed by build_campaigns. Baseline 3 applies since the schema carries the parameter burden.

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?

States a specific verb and resource ('List the standard campaigns PumpGTM would build from the saved setup answers') and enumerates what each item contains: channels, requirements, and built status. It is clearly distinct from build_campaigns, which the description names as the follow-on action.

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?

Explicitly names the triggering situation ('when the customer has little business context to draft campaigns from'), the recommended interaction (offer one or two that fit best), and the exact alternative plus argument mapping ('build only the ones they pick with build_campaigns, passing setupRevision as expectedRevision').

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

All PumpGTM MCP server 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.