INDIVIDUAL MCP TOOL
gtm_list_approvals
Every drafted action that waits for the human — an invite note, a first message, a follow-up, a reply or a comment the planner wrote — with the draft, the 'why now', the lead, and a cockpit link.
LIVE ENDPOINT
https://agent.gtmotto.com/mcp
Connect to this endpoint to inspect the live schema for gtm_list_approvals and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests sending messages.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.gtmotto]
url = "https://agent.gtmotto.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"gtmotto": {
"type": "http",
"url": "https://agent.gtmotto.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: gtmotto
Remote MCP URL: https://agent.gtmotto.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"gtmotto": {
"url": "https://agent.gtmotto.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"gtmotto": {
"type": "http",
"url": "https://agent.gtmotto.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "gtmotto",
"transport": "streamable-http",
"url": "https://agent.gtmotto.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
gtm_whoami— Who this key belongs to, and what the workspace may do: org name, plan, subscription status, how many products and plays exist, and the LEAD METER (leads added this calendar month, the plan's cap, and what is left).gtm_list_plays— Every play in the workspace with enough context to route on: which product it sells, whether it is active or paused, whether a LinkedIn seat is actually connected (`seatConnected: false` means the play cannot act, whatever its status says), and how its leads are spread across the pipeline stages.gtm_show_play— ONE play in full — everything needed to judge it or copy it into a better one: goal and voice, the account's daily cap and working hours (shared by every play on the seat), the ICP facets, the five sourcing lanes with their config and last run, the autonomy ladder (which rungs run alone and which wait for a human), the LinkedIn seat, and today's used/cap for the seat plus this play's share.gtm_play_stats— The play's Stats screen: the pipeline (leads sourced → warmed → invited → new connections → conversations started) over four windows — all time, last 30 days, last 7 days, last 24 hours — each windowed count paired with the window before it as a percentage delta.gtm_linkedin_status— The play's LinkedIn seat and today's headroom against the LinkedIn limits.gtm_estimate_icp— How big an audience a CANDIDATE ICP would reach — '≈ N companies match' — before committing to it.gtm_create_play— Create a fully-configured play in one call: the product (an existing productId, or a websiteUrl which seeds one and kicks its research), the play itself, the ICP facets, which sourcing lanes are on, the autonomy ladder and the caps.gtm_sources_reference— THE REFERENCE for configuring sourcing lanes — read it before your first gtm_configure_source / gtm_set_source / gtm_run_source call.