Skip to main content
Glama
max-paulus

gong-mcp

by max-paulus

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
getv2callsbyidC

Retrieve a single call

postv2callsextensiveC

Filtered call list with rich payload

postv2callstranscriptC

Download transcripts

getv2usersB

List Gong users (100-row pages)

getv2dataprivacydataforemailaddressD

Activities for an email address (GDPR helper)

getv2askanythinggeneratebriefD

Generate account/deal brief

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.4/5.0

Scored across 6 tools

Disambiguation4/5

The tools have distinct purposes: generating briefs, retrieving calls, GDPR activities, listing users, filtering calls, and downloading transcripts. There is some potential overlap between getv2callsbyid and postv2callsextensive (both involve call data), but their descriptions clarify that one retrieves a single call while the other filters lists, reducing confusion.

Naming Consistency2/5

The naming is inconsistent, mixing HTTP methods (get, post) with descriptive suffixes in a non-uniform pattern. For example, getv2askanythinggeneratebrief includes an action verb 'generate' in the name, while others like getv2users do not. This lack of a clear, predictable naming convention makes the set harder to navigate.

Tool Count4/5

With 6 tools, the count is reasonable for a Gong CRM integration server. It covers key areas like calls, users, and data privacy without being overwhelming. However, it feels slightly thin for comprehensive CRM operations, such as missing update or delete functionalities.

Completeness3/5

The toolset covers core read operations for calls, users, and GDPR activities, but lacks obvious CRUD completeness. There are no tools for creating, updating, or deleting resources, which are essential for full CRM workflows. This creates gaps that agents might struggle with for comprehensive task handling.

Maintenance

ActivityInactive
ResponsivenessNo issues