Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

list_deals

Retrieve the deals or opportunities visible to you in Gong, or filter to a single account by ID to review that account's pipeline.

Instructions

Deals (opportunities) Gong shows the user, or one account's.

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_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdNoOnly this account's deals: its id from list_accounts. Default: the user's deals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. "Gong shows the user" hints that results are permission-scoped to the caller's visibility, which is genuinely useful, but nothing states that this is a read-only operation, how many deals are returned, whether results are paginated or truncated, or what a deal record contains.

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

Conciseness3/5

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

There is zero padding, but the single sentence is a fragment that is arguably under-specified rather than concise. It is front-loaded and readable, yet one more clause about scope or return behavior would have cost nothing and removed ambiguity.

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

Completeness2/5

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

For a simple one-optional-parameter read tool with no output schema and no annotations, an agent still lacks the essentials: how results are ordered or limited, whether the call is safe to repeat, and what fields come back. The description is not wrong, just insufficient for confident invocation.

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 accountId parameter is already documented with its source (list_accounts) and its default. The description's phrase "or one account's" corroborates that scoping but adds no syntax, format, or behavioral detail beyond the schema, so the baseline 3 applies.

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

Purpose3/5

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

"Deals (opportunities) Gong shows the user, or one account's" identifies the resource and disambiguates the CRM synonym (deals = opportunities), but the verb 'list' is only implied by the tool name and the sentence is a noun fragment. It conveys scope better than a bare restatement, but it does not read as a clean verb+resource statement.

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

Usage Guidelines2/5

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

The only usage signal is the default behavior implied by the schema (user's deals vs. one account's deals). There is no explicit when-to-use guidance, no mention of related tools such as list_accounts for obtaining an accountId, and no indication of what to do when the user wants deals across multiple accounts.

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