MCP tool reference

Tempo exposes self-describing MCP tools for deal context, CRM work, and permitted configuration. Your client reads each tool’s current input schema when it connects. Tempo also checks some inputs when a tool runs, such as the occurred_at format. This page is the catalog. Deal reads cover every visible deal in your organization. For an organization admin, the signal tools also cover deals that other tools hide. Personal data, write actions, and admin tools still follow your role and deal ownership. The tools you see also depend on the toolsets in your connection URL and what is enabled for your organization. You may see fewer tools than this page lists. Some reads return fewer rows than their requested page size. While a result returns has_more: true or a non-null next_cursor, follow its next_cursor or next_skip before treating the list as complete. Access in the tables below is Read for tools that change nothing, and Write for tools that create, change, or remove something in Tempo or your CRM. Requires names any gate beyond a signed-in Tempo account.

Core

Always included in every connection.

Tool	Access	Purpose and key parameters	Requires
`get_session_context`	Read	Who is signed in: user, organization, role, timezone, `active_toolsets`, `connected_sources`, and `crm_objects_supported`. Pass `include_entrypoints=true` to get the navigation map of recommended tool routes.	—

Workspace

Tool	Access	Purpose and key parameters	Requires
`list_deals`	Read	Find visible CRM Opportunities by `name`, `scope`, or `owner`, with paging and `sort_by`. `include_fields` adds field values; `include_touches` and `no_buyer_touch_since` add last-touch evidence. For a historical touch check, pass `as_of` as an ISO 8601 instant with an offset. It limits touch dates, not current CRM fields, and cannot be combined with `include_touches`.	—
`get_deal_state`	Read	Current Tempo deal state for `deal_ids`, 25 per page: brief, next step, and cited sources. Follow `next_cursor` for more. Request IDs listed in `deferred_deal_ids` again; `next_cursor` does not cover them. Optional `dimensions`, `include_citations`, and `include_history`. For CRM field values, use `get_deal_fields`.	—
`list_meetings`	Read	Meetings from your calendar, for one `deal_id`, or for an account’s deal-linked meetings by `account_id`. Follow `next_skip` while `has_more` is true.	—

Read dimension history

get_deal_state dimension summaries show current claims by default. To compare earlier revisions, pass include_history: true for exactly one deal and at least one dimensions value. Earlier revisions appear with their dates and statuses. A history request for more than one deal or without dimensions returns invalid_input. With include_citations: true, citations support the revisions shown. Some dimensions generated before history was available return no citations and null for observation_count and artifact_count. Treat null as unknown, not zero. When a summary is cut short, its text_cursor reads the whole summary. Keep include_history and every other input unchanged when you continue with cursor or text_cursor.

CRM

Tool	Access	Purpose and key parameters	Requires
`list_deal_updates`	Read	CRM field updates Tempo proposed from evidence. Filter by `deal_id`, `status` (`pending`, `approved`, `rejected`), `since`, `field_ids`, `deal_state`, `stages`, and more. Defaults to pending updates on open, non-renewal deals touched in the last 30 days.	—
`list_fields`	Read	Field catalog for `account`, `contact`, or `opportunity`. CRM-synced fields plus Tempo-managed fields (`include_managed`). Pass up to 50 `field_ids` for full definitions and update policy.	—
`get_deal_fields`	Read	Current field values for one deal: a curated set by default, a `query` to narrow, or `include_all_fields`.	—
`manage_fields`	Write	Approve, reject, revert, create, edit, or revise CRM update proposals. `create` lands as pending unless you pass `approve=true`. It also manages Tempo-owned field definitions.	Organization admin for organization-wide definition changes
`list_crm_objects`	Read	List `account`, `contact`, or `opportunity` rows. Contacts can be filtered by `opportunity_id`.	—
`create_crm_object`	Write	Create an account, contact, or opportunity in the connected CRM. The record is created without a review step.	—

Context

Tool	Access	Purpose and key parameters	Requires
`search_observations`	Read	Ranked, cited observation rows with no synthesis. Search by `query` or `observation_ids`, across `deal_ids` or all visible deals, with `per_deal_limit` and cursor paging. Fast; an empty result is not proof of absence.	—
`search_deal_context`	Read	Search one deal, a `deal_ids` set, or all visible deals. By default returns cited evidence with short per-deal briefs. Set `detail=evidence` for evidence only, or `detail=summary` for a prose answer with citations. `budget_mode` defaults to `auto`: a search over one deal starts at `instant`, and other searches start at `medium` (Balanced) and may continue at `high`. Pass `instant`, `medium`, or `high` to set the effort yourself.	—
`get_search_deal_context_result`	Read	Read a search `run_id`, its coverage, and later answer or evidence pages. Use its cursors or detail markers to continue without starting a new search.	—
`aggregate_observations`	Read	Count recorded competitor observations across visible deals or selected `deal_ids`, with optional dates. Follow `next_cursor` for the rest.	—
`search_deals`	Read	Find visible deals in a situation. Describe it with a `deal_id`, a `query` in words, `theme_ids`, or a `signal_id`; pass `deal_id` with `query` to say what to compare on. By default (`when=now`) it compares open deals as they stand today, or on `as_of`. Set `when=any` to search every week of every deal, won and lost included. Each match lists its matched week, shared themes, the themes discussed next, and its CRM lifecycle, stage, and close date as last entered in the CRM. `outcome` keeps only won, lost, open, or closed deals; won, lost, and closed search every week. `include_evidence=true` adds up to three cited observations from the 14 days ending each match’s matched week. `rerank=true` has a model rate the best matches: with `query` it improves their order, and from a deal alone it picks each match’s week instead. It adds a few seconds at most and does not apply to `theme_ids` or `signal_id`. Matches are leads; confirm with `search_observations` or `get_deal_state` before naming deals.	Themes available for your organization
`search_playbook`	Read	Search approved Playbook guidance: process, methodology, policy, and competitive content.	—
`search_themes`	Read	Browse or search recurring Themes across the organization. `level` is `themes` or `topics`; filter by window (`days`, `from`/`to`), `sources`, `types`, `families`, `statuses`, `topic_id`, or `deal_id`. This tool and `get_theme` can return `computed_at`, the UTC time when counts were computed.	Themes available for your organization
`get_theme`	Read	One theme or topic by `id`, with `include` sections such as `definition`, `examples`, `related`, `timeline`, `observations`, `deals`, `accounts`, and `artifacts`.	Themes available for your organization
`list_theme_accounts`	Read	Accounts where one theme appeared, with the evidence. Follow `next_cursor` for more.	—
`list_live_signals`	Read	Live signals and their IDs, tags, and recorded activity.	—
`list_signal_accounts`	Read	Accounts where selected live signals recorded observations.	—
`list_account_signals`	Read	Live signals recorded on a named account or a seller’s accounts.	—
`list_signal_deals`	Read	Deals where selected live signals recorded observations.	—
`list_deal_signals`	Read	Live signals recorded on named deals.	—
`list_signal_observations`	Read	Cited observations behind a signal’s activity on an account or deal.	—
`list_artifacts`	Read	Artifact metadata for a `deal_id`, an `account_id`, `deal_ids`, or all visible deals, with type, source, and date filters. Follow `next_cursor` for more. `contains` scans stored source text for exact wording and returns a coverage receipt.	—
`get_artifact`	Read	Paged raw content of one deal artifact or approved Playbook artifact. Set `artifact_scope=playbook` for Playbook content; use `content_offset`, `query`, or a line span to read more.	—
`write_artifact`	Write	Save content to a deal as an artifact. `kind` is `chat`, `mcp` (requires an HTTP or HTTPS `mcp_origin_url`), `file` (base64), or `brain_dump` (base64 audio). `occurred_at` requires an ISO 8601 timestamp with UTC (`Z`) or a numeric UTC offset. Writing content that already exists on the same deal returns the existing artifact instead of creating a duplicate. For `mcp` content, new content at a source URL already on the deal updates that artifact. If that new content already belongs to a different artifact on the deal, Tempo returns a conflict. Tempo can extract observations that inform CRM updates.	—
`manage_artifacts`	Write	`retract` one `artifact_id`, which removes its observations and any pending CRM proposals derived from them, or `reprocess_failed` artifacts.	—

Build

Included with the build toolset or the all preset. In the Tempo app, turn on Include Skills and Build tools to add it.

Skills

Tool	Access	Purpose and key parameters	Requires
`list_skills`	Read	Browse visible Skills, filtered by `status` or `search`, or inspect one with `view=detail`.	—
`use_skill`	Write	Load a published Skill’s instructions by `skill_id`, or by `scope` and `skill_key`, and record the activation.	—
`manage_skills`	Write	Create, update, publish, or delete Skills. Each action is permission-checked for that Skill.	Permission on the Skill; organization Skills are managed by admins

Playbook sources and context sources

Tool	Access	Purpose and key parameters	Requires
`list_playbook_sources`	Read	Playbook artifacts with processing and approval status, `revision`, allowed actions, and linked Notion roots.	—
`manage_playbook_sources`	Write	Create, replace, update, approve, reprocess, or delete Playbook sources; link or unlink Notion roots.	Organization admin
`list_context_sources`	Read	Inspect linkable sources for a deal with one `view`: `granola_meetings`, `notion_pages`, `notion_links`, `slack_channels`, or `opportunity_contacts`.	—
`manage_context_sources`	Write	`link`, `unlink`, or `set_capture_mode` for a `source_type` of `meeting`, `notion_page`, `slack_channel`, `contact_email`, or `email_domain` on a deal. Never connects a provider or handles credentials.	—

manage_playbook_sources is not registered for members who are not organization admins, so it does not appear in their tool list. Context source tools decide which already-connected evidence belongs to a deal. Provider connections stay in Settings → Connections.

Prompts

Published Skills you can see are registered as MCP prompts, named by each Skill’s execution name. There is no fixed get_started prompt; it was removed when Skills became the way to start a workflow. Use get_session_context with include_entrypoints=true for a navigation map instead.

Tools that are no longer available

Canvas, Automation, action item, Gmail draft, tone profile, next-action, profile, and setup tools were removed from the MCP server. search_deal_states was replaced by search_deals. A client that still lists them is using a cached catalog; reconnect to refresh it. Action items remain available over the REST API.

Use the live schema

Tool descriptions summarize purpose, not every parameter or response field. Use the schema your MCP client receives as the contract for the connected environment.

Organization membership, teams, integration connections, provider mappings, API keys, and organization settings remain web-app administration tasks.

​Core

​Workspace

​Read dimension history

​CRM

​Context

​Build

​Skills

​Playbook sources and context sources

​Prompts

​Tools that are no longer available

​Use the live schema

Core

Workspace

Read dimension history

CRM

Context

Build

Skills

Playbook sources and context sources

Prompts

Tools that are no longer available

Use the live schema