GTM Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GTM_MCP_MAX_USD | No | Daily spend cap (in USD) for the guarded `run_prospect_research` tool. | 2 |
| GTM_MCP_MAX_RUNS | No | Daily cap on the number of research runs the guarded `run_prospect_research` tool may start. | 5 |
| GTM_AGENT_OUTPUT_DIR | Yes | Path to the agent's output folder that the server reads (profiles, prospect briefs, signals, lists, runs.jsonl). Passed via `claude mcp add gtm-agent -e GTM_AGENT_OUTPUT_DIR=<agent>/output`. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsA | List every client that has a profile, with the date of its last profile run. |
| get_profileB | A client's ICP (industries, size, geographies, buyer titles, qualifiers, disqualifiers), competitors and the buying signals to watch. client: domain or slug, e.g. gong.io. |
| list_runsA | Past agent runs, newest first: status, judge score, retries, force-approved, cost. Filters: company (domain), job (research, list_building, signals, copywriting), since (ISO date, e.g. 2026-10-01). |
| run_costsB | Total and grouped spend from the run history. group_by: job, company or day. since: ISO date. |
| get_prospect_briefB | One prospect's research brief: summary, recent news, tech hints, 0-10 fit score with reasoning, and sourced cold-email openers. |
| rank_prospectsB | All researched prospects ranked by the agent's fit score, with tiers A (8-10), B (5-7), C (0-4). |
| get_signalsB | Latest buying-signal sweep for a client's prospect list: alerts with source URL and date, and which signals were tracked. |
| get_list_summaryB | A client's latest prospect list: company count, funnel and companies. Company-level only, never contact details. |
| run_prospect_researchA | Start a new prospect research run (spends OpenAI and web search credits). Without confirm it only returns a preview: what will run, estimated cost, today's usage. Pass confirm=true only after the user agrees. Daily run and dollar caps apply. client: the client domain or slug whose ICP the prospect is scored against, e.g. gong.io. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target clearly distinct resources (clients, profiles, runs, costs, signals, prospects). Minor overlap exists between get_list_summary and rank_prospects (both surface the prospect list) and between get_profile (client ICP) and get_prospect_brief (single prospect), but descriptions differentiate them adequately.
Names follow a mostly predictable verb_noun pattern (list_clients, get_profile, list_runs, get_signals, get_list_summary, rank_prospects, run_prospect_research). 'run_costs' is the one deviation, where 'run' acts as a noun and reads oddly next to the verbs.
Nine tools is well-scoped for a GTM agent workflow, covering clients, prospects, signals, runs and costs without redundancy. Each tool earns its place.
Read coverage is broad, but the surface is nearly read-only: only run_prospect_research is an action tool. There is no way to create/update a client, edit an ICP profile, or manage prospect lists, leaving notable lifecycle gaps.