Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

find_people

Look up company users, teams, or external people by the start of a name or email. Use returned company user IDs as participantIds when searching Gong calls.

Instructions

Look up company users, teams and external people by the start of a name or email; company users' ids are for search_calls' participantIds.

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": {
      "text": "<text>"
    },
    "name": "find_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe start of a name or email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the important behavioral detail that matching is prefix-based ('start of'), not substring or fuzzy, but says nothing about result caps, pagination, scope restrictions across company vs external people, or authentication requirements.

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?

One tight sentence with the resource and matching rule front-loaded and the downstream consumer appended as a semicolon clause. No filler, nothing repeated from the schema.

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 one-parameter lookup with no output schema, the description covers what it finds, how it matches, and why you would call it. The remaining gap is what a result contains and how many come back, which matters slightly given no output schema is supplied.

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?

The single parameter is fully documented in the schema at 100% coverage, so the baseline is 3. The description reinforces the prefix-matching semantics of 'text' but adds no format rules, length limits, or examples beyond what the schema already states.

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 (look up) and three concrete resources (company users, teams, external people), plus the matching rule (start of a name or email). It also ties the output to a sibling by noting company user ids feed search_calls' participantIds, which no other sibling in the list does.

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?

Usage is clear from context: call this when you need to resolve a person or obtain participantIds for search_calls. It does not state exclusions or whether broader lookups (full-name substring, listing all users) belong elsewhere, so it stops short of full when/when-not guidance.

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