Skip to main content

intent_category removed on next channel

Status: Removed on next — this tool no longer exists on the private next MCP channel. The public /api/mcp channel continues to serve intent_category until the promotion PR merges.

intent_category bundled two unrelated jobs behind one topic-first tool. Both are now covered by tools already live on next:

  • Topic → companies discovery ("which companies show intent for this topic?") → use search_companies with the intent.topics.ids filter.
  • Activity drill-down (comparison / pricing / research / evaluation signals) → use company_intent, which returns activities inline.

Migration Guide

intent_category callReplacement
{ topic_name } (find companies for a topic)list_intent_topics({ name }) to get the topic ID, then search_companies({ filters: { intent: { topics: { ids: [<id>], … } } } })
{ signal }, { products: [...] }, or { group_by: "company" } (activity search)company_intent — read the activities field group

Step-by-step for the intent mode

  1. Call list_intent_topics({ name: "cloud security" }) to get the topic's hex ID.
  2. Call search_companies({ filters: { intent: { topics: { ids: [<id>] } } } }) to find matching companies.

topic_name was fuzzy-matched server-side; the replacement path resolves the topic explicitly via list_intent_topics first — deterministic, no silent mismatch.

Step-by-step for the activity search mode

Call company_intent({ company_domain: "cisco.com", fields: ["activities"] }). The activities field group returns the same signal/event detail inline.

What stayed the same

The underlying HG + TrustRadius intent signals, signal strength (0–100), intent levels, buyer-journey stages, and context types are all still available — through the two tools above. list_intent_topics remains the topic-discovery entry point.

Changelog

2026-07-30 — Breaking: intent_category removed; superseded by search_companies + company_intent

Availability: this removal is live on the private next MCP channel for allow-listed orgs. The public /api/mcp contract still exposes intent_category and is unchanged until the promotion PR lands.

Why this changed: intent_category bundled two unrelated jobs behind one topic-first tool. Both are now covered by tools already live on next, so there is no longer a third overlapping intent tool to choose between. Removing it eliminates ambiguity for the LLM in tool selection.