PumpGTM MCP server

Link company contact

add_company_contact

Add a person to an existing CRM company's contacts, optionally linked to the same person's existing PumpGTM lead in this workspace. Use it when the customer names a stakeholder on an account. Never guess a lead match from a company name; link only an exact person from list_leads. Does not create or enroll outreach leads. Requires the CRM feature. Returns the saved contact.

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": {
      "id": "<id>",
      "company_id": "<company_id>",
      "name": "<name>",
      "email": "<email>",
      "role": "<role>",
      "lead_id": "<lead_id>"
    },
    "name": "add_company_contact"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	New UUID you generate for this contact.
`name`	Yes	Contact's full name.
`role`	Yes	Contact's job title or role in the deal (for example Champion, CFO), or null.
`email`	Yes	Contact's work email when the customer supplied it, or null. Never guess an address.
`lead_id`	Yes	ID of the same person's existing PumpGTM lead (from list_leads) to link them, or null. Only link an exact person match, never a guess from the company name.
`company_id`	Yes	ID of the existing CRM company this person works at, from get_pipeline, get_company or save_company.
`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
`id`	Yes	Contact ID.
`name`	Yes	Contact's name.
`role`	No	Role or title, or null.
`email`	No	Email, or null.
`lead_id`	No	Linked PumpGTM lead ID, or null.
`company_id`	Yes	Company this contact works at.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 10, 2026

addedInput schema / properties / company_id / description

Added value: +"ID of the existing CRM company this person works at, from get_pipeline, get_company or save_company."

addedInput schema / properties / email / description

Added value: +"Contact's work email when the customer supplied it, or null. Never guess an address."

addedInput schema / properties / id / description

Added value: +"New UUID you generate for this contact."

addedInput schema / properties / lead_id / description

Added value: +"ID of the same person's existing PumpGTM lead (from list_leads) to link them, or null. Only link an exact person match, never a guess from the company name."

addedInput schema / properties / name / description
```
Added value: +"Contact's full name."
```

addedInput schema / properties / role / description

Added value: +"Contact's job title or role in the deal (for example Champion, CFO), or null."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "description": "The saved contact.",
+  "properties": {
+    "company_id": {
+      "description": "Company this contact works at.",
+      "type": "string"
+    },
+    "email": {
+      "description": "Email, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Contact ID.",
+      "type": "string"
+    },
+    "lead_id": {
+      "description": "Linked PumpGTM lead ID, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Contact's name.",
+      "type": "string"
+    },
+    "role": {
+      "description": "Role or title, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "company_id",
+    "name"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / email / anyOf

Previous value: -[
-  {
-    "format": "email",
-    "maxLength": 254,
-    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "email",
+    "maxLength": 254,
+    "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"Team owner only: an active workspace ID from list_team_workspaces. Omit for your own workspace. Supply on every call for a teammate."New value: +"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."

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Team owner only: an active workspace ID from list_team_workspaces. Omit for your own workspace. Supply on every call for a teammate.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

First observedOct 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=false, so the mutation profile is known. The description adds value beyond those fields: a feature-availability prerequisite, the scope boundary that it does not create or enroll outreach leads, and the fact that it returns the saved contact. It does not address the non-idempotent behavior (caller-supplied UUID, duplicate risk), which keeps it below a 5.

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?

Four short sentences, front-loaded with the action and scope, followed by usage condition, constraint, and return. No filler or redundancy; every sentence contributes a distinct rule.

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 non-destructive mutation with seven parameters and an output schema, the description covers the prerequisite, the sibling boundary, the matching rule, and that a saved contact is returned. Nothing an agent needs to invoke it correctly 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 description coverage is 100% and each parameter already carries guidance, including 'Only link an exact person match, never a guess from the company name' for lead_id. The description largely restates that constraint rather than adding new semantics, so it sits at the baseline for a fully documented schema.

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 ('Add a person to an existing CRM company's contacts') with the optional lead-link qualifier, then explicitly negates a nearby sibling behavior ('Does not create or enroll outreach leads'). An agent can distinguish this from add_leads or save_company 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?

Gives a concrete trigger ('Use it when the customer names a stakeholder on an account'), an explicit prohibition ('Never guess a lead match from a company name'), the correct source tool for a valid argument ('link only an exact person from list_leads'), and a hard prerequisite ('Requires the CRM feature'). When-to-use, when-not-to, and alternative sourcing are all covered.

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.