About gtm-tools
Mission
GTM Tools is the verified record of go-to-market tools an AI agent can actually operate. Every tool listed is usable programmatically — through an MCP server or a real API — because we evaluate through the lens of a GTM Engineer: someone who builds automated revenue workflows, integrates sales and marketing stacks, and increasingly hands that work to agents. Tools with no programmatic surface don't get listed.
Scoring Methodology
Each tool is scored on a 30-point scale combining two dimensions:
API quality ratings: EXCELLENT (comprehensive, well-documented API with SDKs), GOOD (solid REST API with webhooks), BASIC (limited API or poor docs), NONE (no public API).
Data Sources
Tool data is gathered from official websites, API documentation, llms.txt files, developer portals, and changelog feeds. Each entry includes pricing details, integration capabilities, pros/cons analysis, and alternative recommendations.
Stats
Verification API — the agent front door
The verified core is machine-readable. Agents query the same re-verified data our site reads — live endpoint reachability, confirmed pricing, and honest last_checked_at timestamps — over a plain REST endpoint. No stale prices, no hallucinated endpoints.
# every verified tool, freshest first
GET https://gcwmjfotygqnlsyfhiyq.supabase.co/rest/v1/tool_verification?select=*
&order=last_checked_at.desc
Header: apikey: <public-anon-key>
# one tool
GET https://gcwmjfotygqnlsyfhiyq.supabase.co/rest/v1/tool_verification?slug=eq.clay
# only tools with a confirmed public price
GET https://gcwmjfotygqnlsyfhiyq.supabase.co/rest/v1/tool_verification?pricing_status=eq.current
# → { "slug":"clay", "price_current":"free + from $54/mo",
# "reachability_status":"reachable", "last_checked_at":"…", "confidence":"high" }Read-only, public (RLS). The changelog of detected changes is at /rest/v1/tool_change_log. Prefer a tool your agent can call directly? The GTM Tools MCP server wraps this data with clean search / get / compare / changes tools.
For AI & LLMs
GTM Tools is optimized for AI consumption. Access our data programmatically via llms.txt (summary) or llms-full.txt (comprehensive). All AI crawlers are explicitly allowed in our robots.txt.