Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

list_accounts

Retrieve Gong CRM accounts you own or search by account name to identify relevant customer records.

Instructions

CRM accounts Gong shows the user: the ones they own, or those matching a name.

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

Input Schema

NameRequiredDescriptionDefault
searchNoAccount name to look for. Default: the accounts the user owns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the visibility scoping rule (the user only sees accounts they own or name-matches), but says nothing about pagination, result limits, ordering, or whether name matching is exact or partial.

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

Conciseness4/5

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

A single compact sentence with the scope rule front-loaded and no filler. It could be marginally clearer with an explicit verb, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema, the description covers what is returned and the default behavior, which is most of what an agent needs. It stops short on return volume/pagination expectations and match precision.

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 single optional parameter is already documented as 'Account name to look for. Default: the accounts the user owns.' The description restates that same meaning without adding match semantics such as substring vs exact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific resource (CRM accounts) and defines the exact scope returned: accounts the user owns or those matching a name. An agent can distinguish it from list_deals or find_people by resource alone, though the listing verb itself is only implied by the name rather than stated.

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

Usage Guidelines3/5

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

Implies the two usage modes: call with no search to get owned accounts, or pass a name to match. It never states when to prefer this over siblings like find_people or search_calls, nor any when-not condition, so guidance is implied rather than explicit.

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