Skip to main content
The public catalog contains 50 tools before scope and workspace filtering. Use tools/list to discover the tools and argument schemas your connection can actually use. Tool names retain watchlist and organization where those are part of the public contract. In the app, these correspond to tracked profiles and your workspace.

​
Workspace and connection

​
Leads and accounts

​
Discovery

​
Targeting

​
Tracked profiles

​
Content and analytics

​
Integrations and synchronization

​
Audience and post qualification

​
Confirm actions

Select the workspace, target, and action before making a write request.
  • traxy_start_agent_run and traxy_qualify_linkedin_post require confirmLeadUsage: true after the user agrees that new qualified people may consume pipeline capacity.
  • traxy_apply_lead_action supports snooze, done, good, bad, and client. The done action needs confirmDone: true.
  • Contact enrichment needs an explicit request. Email and phone follow the workspace’s entitlements and do not consume pipeline capacity.
  • ICP and Signal Brief updates replace supplied arrays and leave omitted fields unchanged. Inspect the current configuration before sending replacements.
  • Webhook-style destination tools support Webhook, Clay, n8n, and Zapier. Queuing delivery is not proof that the receiver accepted it.
The former confirmCreditSpend argument is not accepted. Sending it returns validation_failed; use only the current schema. The capacity tool replaces the former Agent budget-status tool. Manage campaigns, senders, and sequences in the app; those actions are not in this public MCP catalog. See workspace selection and error handling when building a client.