gtm.devdocs
find companies

ICP to search filters API

plan_targeting

1 credit / call

Turn a plain-language targeting description (ICP, persona, market) into canonical, ready-to-use filters — the recommended FIRST call when you are unsure of exact vocabulary. Returns company filters (for search_companies / size_tam) — including funding graph (stage, amount, date range, investors) and detected tech stack when the description names them — a best-effort `total` for those filters, people filters (for find_people), a concept_query (for concept_search when meaning matters more than filters), a filters-vs-semantic strategy recommendation, and suggested next tool calls. Funding/tech/investor language is always routed to exact filters, never treated as a vibe for semantic search. Resolution runs against the graph's real vocabularies, so returned values always match what the search tools accept.

Get an API key 1,000 free live credits · no card

Parameters

paramtypedescription
description requiredstringPlain-language targeting, e.g. "VP+ finance leaders at mid-market US SaaS companies that feel API-first".
targetstring: companies | people | bothWhat the plan is for. Default "both".

Call it from your agent (MCP)

Connect once and plan_targeting appears in your agent’s toolbox next to every other gtm.dev tool. Claude Code:

claude mcp add --transport http gtm https://mcp.gtm.dev \
  --header "Authorization: Bearer YOUR_API_KEY"

Under the hood, the client sends:

curl -X POST https://mcp.gtm.dev \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"plan_targeting","arguments":{"description":"VP+ finance leaders at mid-market US SaaS companies that feel API-first"}}}'

other clients (cursor, claude desktop, openai agents sdk, langchain): mcp setup

Call it over REST

curl -X POST https://api.gtm.dev/v1/tools/plan_targeting \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"description":"VP+ finance leaders at mid-market US SaaS companies that feel API-first"}'

Errors (401, 402, 429, 400) are listed in the REST reference. Calls that error are not billed — see pricing.

Related tools