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

Suggest AI search questions

suggest_ai_search_questions

Suggest about 12 buyer questions and likely competitors from the company profile, homepage and latest website scan. One model call, about costs.suggestQuestionsAbout Energy, within today's daily limit. With confirmed=true it returns the suggested questions and competitors. Nothing is tracked until questions are added with add_ai_search_questions and competitors with update_ai_search_settings; the latest suggestions also appear in get_ai_search_overview settings. Without confirmed=true nothing runs and nothing is charged: it returns the Energy cost, the Energy left and today's AI search limit, with the call that runs it, or the money answer when Energy can't cover it. Tell the customer the cost, then call again with confirmed=true. If AI search is not on for this workspace yet, this turns it on (aiSearchTurnedOn in the result says what it starts with). Only for a connection created by a current owner or admin of this workspace.

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": "suggest_ai_search_questions"
  }
}

Input Schema

Name	Required	Description	Default
`confirmed`	No	false prices the step and changes nothing; true runs it and spends Energy. Send true only after the customer agrees to the price.
`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	Preview only: the exact call that runs the step once the customer agrees; null when it can't run now.
`energy`	Yes	What the step costs and the Energy left.
`message`	No	A plain summary of the price or of what started, to pass on to the customer.
`started`	No	false on the priced preview: nothing ran or was charged.
`questions`	No	Run: suggested buyer questions; track them with add_ai_search_questions.
`readyToRun`	No	Preview only: true when Energy and today's limit allow the step; then call next after the customer agrees.
`competitors`	No	Run: likely competitors (name and domains); track them with update_ai_search_settings.
`aiSearchTurnedOn`	No	Present only when this call turned AI search on: what it now runs with. Tell the customer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / confirmed / description

Previous value: -"false (default) prices the step and changes nothing; true runs it."New value: +"false prices the step and changes nothing; true runs it and spends Energy. Send true only after the customer agrees to the price."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "aiSearchTurnedOn": {
+      "description": "Present only when this call turned AI search on: what it now runs with. Tell the customer.",
+      "type": "string"
+    },
+    "competitors": {
+      "description": "Run: likely competitors (name and domains); track them with update_ai_search_settings.",
+      "items": {},
+      "type": "array"
+    },
+    "energy": {
+      "additionalProperties": {},
+      "description": "What the step costs and the Energy left.",
+      "properties": {
+        "cost": {
+          "description": "Preview: the step's Energy cost.",
+          "type": "number"
+        },
+        "costAbout": {
+          "description": "Run: about the Energy this step is charging.",
+          "type": "number"
+        },
+        "costAtMost": {
+          "description": "Run: the most Energy this step can charge.",
+          "type": "number"
+        },
+        "costIsMaximum": {
+          "description": "Preview: true when cost is a ceiling rather than an estimate.",
+          "type": "boolean"
+        },
+        "dailyLimitUsd": {
+          "description": "Preview: today's AI search limit in US dollars.",
+          "type": "number"
+        },
+        "nextStep": {
+          "description": "Preview when Energy is short: how the customer gets more.",
+          "type": "string"
+        },
+        "remaining": {
+          "description": "Energy the workspace has left (null when unreadable).",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "remainingBefore": {
+          "description": "Run: Energy the workspace had before the step.",
+          "type": "number"
+        },
+        "required": {
+          "description": "Preview when Energy is short: Energy the step needs.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "todayLimitRemaining": {
+          "description": "Preview: Energy today's AI search limit still allows.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "A plain summary of the price or of what started, to pass on to the customer.",
+      "type": "string"
+    },
+    "next": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "arguments": {
+              "additionalProperties": {},
+              "description": "The exact arguments to send, including confirmed=true.",
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "reason": {
+              "description": "Why and when to make the call.",
+              "type": "string"
+            },
+            "requiresConfirmation": {
+              "description": "True: call it only after the customer agrees to the price.",
+              "type": "boolean"
+            },
+            "tool": {
+              "description": "The tool to call to run the step.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "tool",
+            "arguments",
+            "reason",
+            "requiresConfirmation"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Preview only: the exact call that runs the step once the customer agrees; null when it can't run now."
+    },
+    "questions": {
+      "description": "Run: suggested buyer questions; track them with add_ai_search_questions.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "readyToRun": {
+      "description": "Preview only: true when Energy and today's limit allow the step; then call next after the customer agrees.",
+      "type": "boolean"
+    },
+    "started": {
+      "description": "false on the priced preview: nothing ran or was charged.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "energy"
+  ],
+  "type": "object"
+}

AddedNov 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), the description discloses what is actually mutated: nothing is tracked until separate add/update calls, the latest suggestions are visible in get_ai_search_overview, and the call can enable AI search if it is off (aiSearchTurnedOn). It also discloses the cost model and the daily-limit gating, which no annotation conveys.

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

Conciseness3/5

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

Core behavior is front-loaded and the confirm-then-run flow is clear, but the text is long and the cost sentences are garbled template artifacts ("about costs.suggestQuestionsAbout Energy", "the money answer", "the Energy left"). Repeated, unclear placeholders cost clarity even though little is strictly off-topic.

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?

For a tool with two phases, side effects, a paywall and an owner/admin restriction, the description covers the flow, side effects, and persistence boundaries well, and the output schema carries return shape. The remaining weakness is that the pricing/insufficient-Energy outcomes are described in mangled phrasing, leaving the exact failure payload slightly ambiguous.

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 schema already explains confirmed's pricing-versus-spending semantics and the workspaceId teammate-omission rule, so the baseline is 3. The description adds some framing by describing what each mode returns, but with an output schema present that is largely redundant rather than new meaning.

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?

"Suggest about 12 buyer questions and likely competitors from the company profile, homepage and latest website scan" states a specific verb, a concrete output (buyer questions + competitors), and the input sources. It also contrasts with add_ai_search_questions and update_ai_search_settings, which persist rather than suggest, so a reader can tell it apart from siblings without opening a schema.

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 names the when: call without confirmed to price, tell the customer the cost, then call again with confirmed=true. It names the when-not (nothing runs or is charged without confirmation), points to the persistence alternatives by name, and gives an eligibility boundary (only for a connection created by a current owner or admin).

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?