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

Stop tracking an AI search question

remove_ai_search_question

DestructiveIdempotent

Stop tracking one question. Its past answers are kept but no longer count in the figures. No Energy. Returns removed and the questionId. Only for a connection created by a current owner or admin of this workspace.

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": {
      "questionId": "<questionId>"
    },
    "name": "remove_ai_search_question"
  }
}

Input Schema

Name	Required	Description	Default
`questionId`	Yes	A tracked question's questionId, from get_ai_search_overview questions or add_ai_search_questions.
`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	Default
`removed`	Yes	True when the question is no longer tracked.
`questionId`	Yes	The question removed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / questionId / description

Previous value: -"A tracked question's questionId."New value: +"A tracked question's questionId, from get_ai_search_overview questions or add_ai_search_questions."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "questionId": {
+      "description": "The question removed.",
+      "type": "string"
+    },
+    "removed": {
+      "description": "True when the question is no longer tracked.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "removed",
+    "questionId"
+  ],
+  "type": "object"
+}

AddedNov 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, which already mark it destructive and idempotent, the description explains the important consequence that past answers are kept but no longer counted. It also states there is no Energy cost, gives the permission requirement, and mentions returned fields.

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 short and front-loaded: it starts with the action, then effect, cost, return, and eligibility. Every sentence contributes useful information, and the fragment "No Energy" is efficient in context.

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 mutation tool with an output schema, rich annotations, and fully described parameters, the description covers the key behavioral facts: data retention, metric impact, energy cost, permissions, and return shape. Nothing material is missing.

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%, and the schema already explains that questionId comes from overview or add operations and that workspaceId is omitted for the caller's own workspace. The description adds only the general framing that exactly one question is affected, with no additional parameter-level guidance.

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 and resource: "Stop tracking one question." It distinguishes the operation from adding questions and getting overview data by specifying that it affects exactly one tracked question and that its past answers remain but stop counting.

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

Usage Guidelines4/5

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

The description gives clear context for when to use it (stop tracking one question) and an eligibility restriction (only for a connection created by a current owner or admin). It does not explicitly name alternatives or when-not-to-use cases, so it is strong but not fully complete on usage routing.

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?