MCP Tools

All tools available on the MCP server, grouped by domain. Bold arguments are required. Every write tool also accepts dry_run and idempotency_key (see conventions).

A key only sees the tools whose scope it has. Scopes marked admin only (conversations:write, agents:run, agent_tools:execute) can only be granted by an account administrator.

Contacts

Tool	Scope	Kind	Arguments
contacts_search	contacts:read	read	query, email, phone, company, source, tag_ids, created_after, created_before, updated_after, updated_before, sort_by, sort_order, page, limit
contacts_get	contacts:read	read	contact_id
contacts_create	contacts:write	write	name, email, phone, company, title, location, linkedin_profile_url, source, custom_fields, tag_ids
contacts_update	contacts:write	write	contact_id, name, email, phone, company, title, location, linkedin_profile_url, custom_fields
contacts_add_tags	contacts:write	write	contact_id, tags, create_missing
contacts_remove_tags	contacts:write	write	contact_id, tags
contacts_add_note	contacts:write	write	contact_id, content

Opportunities

Tool	Scope	Kind	Arguments
opportunities_search	opportunities:read	read	query, pipeline_id, stage_id, owner_user_id, contact_id, campaign_id, company, created_after, created_before, updated_after, updated_before, sort_by, sort_order, page, limit
opportunities_get	opportunities:read	read	opportunity_id, include_history
opportunities_create	opportunities:write	write	contact_id, name, email, phone, company, title, pipeline_id, stage_id, value, score, notes, owner_user_id, sector_id, campaign_id, source, custom_fields, activate_agent_id, enroll_in_flow_id
opportunities_update	opportunities:write	write	opportunity_id, title, value, score, notes, owner_user_id, sector_id, expected_close_date, probability, custom_fields
opportunities_move_stage	opportunities:write	write	opportunity_id, stage_id, stage_name, pipeline_name, discard_reason_id, notes

Conversations (inbox)

Tool	Scope	Kind	Arguments
conversations_list	conversations:read	read	contact_id, opportunity_id, status, created_after, created_before, updated_after, updated_before, last_message_after, last_message_before, page, limit
conversations_get	conversations:read	read	conversation_id, messages_limit
conversations_send_message	conversations:write	write	conversation_id, content, pause_ai
conversations_add_note	conversations:write	write	conversation_id, content
conversations_take_control	conversations:write	write	conversation_id, reason

Reference data

Tool	Scope	Kind	Arguments
pipelines_list	pipelines:read	read	include_inactive
tags_list	tags:read	read
users_list	users:read	read	role, is_active

Reports

Tool	Scope	Kind	Arguments
reports_funnel	reports:read	read	pipeline_id, sector_id
reports_sales_summary	reports:read	read	pipeline_id, sector_id, owner_user_id, from, to

AI employees

Tool	Scope	Kind	Arguments
agents_list	agents:read	read	include_inactive
agents_chat_start	agents:run	write	agent_id, lead_simulation
agents_chat_send	agents:run	write	session_id, message, event
agents_chat_end	agents:run	write (destructive)	session_id
knowledge_search	knowledge:read	read	query, limit, type, agent_id, contact_id
agent_register_lead_source	agent_tools:execute	write	source, campaign, adset, creative, contact_id
agent_send_email	agent_tools:execute	write	subject, body, contact_id, agent_id
agent_transfer_to_human	conversations:write	write	reason, farewell_message, agent_id, conversation_id, contact_id
agent_schedule_meeting	agent_tools:execute	write	message_prefix, agent_id, conversation_id, contact_id
agent_check_availability	agent_tools:execute	read	skip_days, agent_id, conversation_id, contact_id
agent_book_meeting	agent_tools:execute	write	slot_id, title, agent_id, contact_id, conversation_id

Notes per tool

• contacts_search / opportunities_search — query is a free-text partial match (name, email, company / title, contact). Combine updated_after with sort_by=updated_at for incremental sync.
• contacts_create — needs name plus at least one of email, phone or linkedin_profile_url; a contact with the same email returns DUPLICATE_ERROR.
• contacts_update — custom_fields replaces the whole object; tags are managed with contacts_add_tags / contacts_remove_tags.
• contacts_add_tags — tag names, matched case-insensitively. Unknown names return TAG_NOT_FOUND unless create_missing: true (requires tags:write). Adding a tag fires the same automations as in the app (email flows, tracking).
• opportunities_create — pass contact_id to link an existing contact, or name/email/phone/company to find-or-create one (matched by email). Without pipeline_id/stage_id the deal lands in the first stage of the account default pipeline. Without owner_user_id the account round-robin assigns an owner; the pipeline entry AI agent is activated as in the app.
• opportunities_update — custom_fields are merged. Stage changes go through opportunities_move_stage.
• opportunities_move_stage — by stage_id, or by stage_name (the opportunity's own pipeline is preferred; add pipeline_name to disambiguate, else AMBIGUOUS). Records history, sets won/lost timestamps and refreshes the Kanban in real time.
• conversations_list — status is one of ai_active, manual, closed; use archived: true|false to filter archived conversations.
• conversations_send_message — text only; sends through the conversation channel (WhatsApp, LinkedIn, Instagram, email, webchat). By default it pauses the AI employee on that conversation (pause_ai); ai_paused in the result says whether it actually did, with pause_reason otherwise (e.g. already_manual, no_agent).
• conversations_take_control — status manual, AI paused, scheduled follow-ups cancelled, control_taken event recorded. Release control from the inbox.
• reports_* — same definitions as the in-app reports: active = not lost/discarded, won = active in a win stage.
• AI-employee tools are described on the AI employees page.

Resources

URI	Scope	Content
getraze://account	any connected key	Account id, name, type, enabled modules and the key's scopes
getraze://pipelines	pipelines:read	Pipelines with ordered stages
getraze://tags	tags:read	Tags with usage counts
getraze://users	users:read	Team members
getraze://sectors	sectors:read	Sectors (teams)
getraze://agents	agents:read	Flow-based AI employees
getraze://tool-catalog	agents:read	The native tools an AI employee can use, with JSON Schema

Prompts

Prompt	Arguments	What it does
qualify_lead	contact_id, pipeline_name	Reads the contact, its conversations and opportunities, then proposes tags and a stage move — without executing them
daily_pipeline_review	pipeline_id, owner_user_id	Funnel + last 7 days + stale open deals, with three suggested actions