Demodesk

Fetch one group with its visibility and recording access. Typical use case: verifying the settings of a group after creating or changing it.

groups_get

Read the personal settings of the authenticated user: the personal keyword list for transcription (custom vocabulary), which meetings the notetaker records, notification preferences, language and time zone. Typical use cases: checking the current keyword list before adding a term, e.g. after the user explains how a product or name is spelled, or checking why a meeting was or wasn't recorded.

users_get_my_settings

Fetch one recording by token with detailed metadata and computed stats. Typical use case: opening one call after a token is known or selected from list results (for example: "open this recording", "show details for token X"). Returns a single recording object including ownership, timing, and processing state.

recordings_get

Retrieve transcript content for a single recording, optionally translated via `lang`. Typical use case: reading, quoting, summarizing, or analyzing what was said in one call (for example: "show transcript", "translate transcript to de"). Returns transcript paragraphs/sentences (or plain text format when requested).

recordings_get_transcript

Retrieve transcripts for up to 100 recordings in one request. Typical use case: cross-call analysis over a known set of recording tokens (for example: "get transcripts for these 20 calls"). This endpoint performs retrieval only and does not create, update, or delete data. Returns per-recording transcript payloads with per-item status so partial failures remain inspectable.

recordings_batch_get_transcripts

List the Demodesk analytics SQL tables available to query with execute_analytics_sql. Use this only when you need to discover which Demodesk tables are available before writing SQL. For simple queries, where you can guess the tables, prefer get_analytics_sql_table_context over this one. Returns a big overview of the whole Demodesk schema, incl table names, short descriptions, and column names

list_analytics_sql_tables

List company groups visible to the authenticated user. Typical use case: resolving a group id by name before adding or removing a group member.

groups_list

List non-deleted scorecards linked to a recording. Typical use case: coaching evaluation, rubric results, or scoring details for a call (for example: "show scorecard", "how did this call score?"). Returns scorecard entries and associated scoring metadata for the recording token.

recordings_list_scorecards

List AI-generated summaries attached to a recording. Typical use case: recap notes, highlights, or summary variants for a specific call (for example: "show the summary", "what are the key takeaways?"). Returns summary records and metadata for the requested recording token.

recordings_list_summaries

Find meeting recordings visible to the authenticated Demodesk user. Typical use case: searching, filtering, or browsing calls (for example: "show last week's meetings", "find calls where I talked to Daniel"). Prefer dedicated people filters over internal ids: `host_eq`, `host_in`, `attendee_eq`, `attendee_in`. Person filter values support an email address or `me` (resolves to authenticated user). Examples: `filter[host_eq]=host@example.com`, `filter[host_eq]=me`, `filter[attendee_eq]=attendee@example.com`, `filter[attendee_eq]=me`, `filter[attendee_in][]=me&filter[attendee_in][]=champion@example.com`. To find calls with a company or account, filter by its attendees' email domain with `attendee_domain_eq` or `attendee_domain_in` instead of relying on meeting titles, which rarely contain the account name. Resolve the company name to its email domain(s) yourself (for example "Deutsche Bahn" -> `deutschebahn.com`), and pass every domain the company uses, since one account can span several regional or legal entities. Examples: `filter[attendee_domain_eq]=example.com`, `filter[attendee_domain_in][]=example.com&filter[attendee_domain_in][]=example.de`. Returns paginated recording metadata and cursor info; use returned ids/tokens in follow-up tools like getting the transcripts of the found meetings.

recordings_list

List active users visible to the authenticated user. Typical use case: selecting or resolving teammates by name/email before filtering recordings or assigning follow-up actions. It can also be used to confirm that users exist when given a specific email address.

users_list

Manage Demodesk custom API integration objects. Supports the actions: Get, Create. API integration objects define external APIs available in Demodesk, including name, base_url, optional prompt/instructions, and permission rules (allowed HTTP methods + URL patterns). Before creating an integration, validate the target API base URL and docs using a web tool available in your MCP client (for example a web fetch/browse tool), then verify with a test request. The base_url should be the API root (for example https://api.example.com). Permission url_patterns must be relative paths (for example /v1/users/*), not full URLs. API keys and signing secrets must still be configured manually by the user in Demodesk UI.

manage_api_integrations

This tool operates on Demodesk agent objects in the authenticated user's workspace. Manage agents. Supports the actions: Get, Create, Update, Delete, Run. Agents are automated tasks that can be triggered by time schedules, events, or external webhooks. Use the Run action to execute an agent immediately, regardless of its trigger type or enabled status. Use the Get action without an agent_id to list agents as a compact overview: name, trigger type, owner, collaborators, your role, last run and a short excerpt of the prompt. Use the Get action with an agent_id to read a single agent in full, including its complete prompt, condition, trigger params, its 10 most recent executions and, for webhook-triggered agents, the webhook_token and endpoint. For webhook-triggered agents, use the webhook_token returned by Get with an agent_id, Create or Update (the list does not include it) to trigger it via: POST https://demodesk.com/webhook/agents/trigger with header `X-Agent-Token` set to the webhook_token or query parameter `token`, e.g. POST https://demodesk.com/webhook/agents/trigger?token=<webhook_token>. The request body should be JSON and can contain additional context data to pass to the agent.

manage_agents

This tool operates on Demodesk battlecard objects in the authenticated user's workspace. Manage battlecards: decks of cards reps open during meetings, e.g. for objection handling, competitors or troubleshooting. Supports Get, Create, Update, and Delete actions. Get retrieves one deck with its full cards by deck_id. Without deck_id it lists the decks the user can read, optionally filtered by name, with only card ids and titles. Create makes a new deck; owner decides whether it is a company deck shared with the whole team (only admins and managers) or a personal deck. Update renames a deck and adds, changes or removes cards. To keep a deck current, list the decks, Get the right one by deck_id and update its existing cards by id instead of creating a new deck or duplicate cards. Existing cards are patched by id with only the fields to change, e.g. {"id": 21, "text": "<p>New guidance</p>"}; omitted fields keep their value. To remove an existing card, pass its id with destroy: true. Delete removes a whole deck with all its cards by deck_id; only use it when the user asks to delete the deck. Card text is HTML as shown in the battlecard editor, e.g. "<p>Intro</p><ul><li><p>Point</p></li></ul>".

manage_battlecards

This tool operates on Demodesk Deal insight automation mapping objects in the authenticated user's workspace. Manage the deal insight automation configuration — the mappings (rules) that decide which deal insight prompt is applied to a meeting. The first matching rule determines which prompt will be used. The rules are sorted by position in ascending order. Supports the actions: Get, CreateMapping, UpdateMapping, DeleteMapping, UpdateConfiguration. The CreateMapping/UpdateMapping/DeleteMapping actions each operate on a single mapping (rule). Get returns the company's deal insight automation configuration, including all automation mappings. Make sure to use dedicated tools to map entities' IDs to human-readable names. CreateMapping adds a single new mapping referencing an existing prompt (by mapping.prompt_id and mapping.prompt_type) with a mapping.condition that selects when the prompt applies. The condition may be a natural language description (e.g. "only for external meetings") or a JSONLogic object. UpdateMapping changes a single existing mapping (by mapping_id) with one or more of the mapping attributes: condition, prompt (prompt_id and prompt_type together), position, and the messaging destination attributes. Only the provided attributes are changed. Both CreateMapping and UpdateMapping accept messaging destination attributes (mapping.slack_destinations, mapping.teams_destinations) to configure the alerts posted when the rule matches; see those parameters for their merge semantics. DeleteMapping removes a single mapping by its ID. UpdateConfiguration changes the automation-wide settings (not a single mapping) via the configuration object: deal_insight_language_kind, deal_insight_language_code. Only the provided attributes are changed. NOTE: When there are rules with same positions, the old positions' positions are shifted automatically. No need to manually update positions if there might be a collision.

manage_deal_insight_automation

This tool operates on Demodesk Follow-up email automation mapping objects in the authenticated user's workspace. Manage the follow-up email automation configuration — the mappings (rules) that decide which prompt is applied to a meeting. The first matching rule determines which prompt will be used. The rules are sorted by position in ascending order. Supports the actions: Get, CreateMapping, UpdateMapping, DeleteMapping, UpdateConfiguration. The CreateMapping/UpdateMapping/DeleteMapping actions each operate on a single mapping (rule). Get returns the company's follow-up email automation configuration, including all automation mappings and the fallback mapping. Make sure to use dedicated tools to map entities' IDs to human-readable names. CreateMapping adds a single new mapping referencing an existing prompt (by mapping.prompt_id and mapping.prompt_type) with a mapping.condition that selects when the prompt applies. The condition may be a natural language description (e.g. "only for external meetings") or a JSONLogic object. UpdateMapping changes a single existing mapping (by mapping_id) with one or more of the mapping attributes: condition, prompt (prompt_id and prompt_type together), position. Only the provided attributes are changed. DeleteMapping removes a single mapping by its ID. The fallback mapping cannot be deleted. UpdateConfiguration changes the automation-wide settings (not a single mapping) via the configuration object: language_kind, language_code, fallback_enabled, and fallback_follow_up_email_automation_mapping_id. Only the provided attributes are changed. NOTE: When there are rules with same positions, the old positions' positions are shifted automatically. No need to manually update positions if there might be a collision.

manage_follow_up_email_automation

This tool operates on Demodesk meeting type objects in the authenticated user's workspace. Manage the messages of a meeting type: which emails and calendar invites it sends, their copy, and its reminders. Supports Get and Update for one meeting type at a time; use search_meeting_types to find meeting type ids. Always Get the meeting type first, then Update it. Switches: - send_email_invite: default of the "send email invite" option when a host schedules a meeting. - send_email_invite_from_booker: send the scheduling email invite from the booker instead of the host. - send_calendar_invite: default of the "send calendar invite" option when a host schedules a meeting. - send_appointment_invite: send the confirmation email to guests who book via the booking page. - send_link_booking_calendar_invite: send a calendar invite to guests who book via the booking page. - send_reminders: send the reminders of this meeting type. - show_follow_up_email: offer the follow-up email to the host after the meeting. Templates, each with its own copy: - invite: email sent when a host schedules a meeting (subject, body). - appointment: confirmation email for guests booking via the booking page (subject, body). - calendar_invite: calendar event when a host schedules a meeting (title, description, location). - link_booking_calendar_invite: calendar event for guests booking via the booking page (title, description, location). - in_meeting_invite: email for inviting people during a meeting (subject, body). - follow_up_email: follow-up email after the meeting (subject, body). Each template is written on its own; changing one never changes another, even when two are identical. If the user wants the same change in two identical templates, update both. Bodies are HTML. Personalization fields appear as {{slug}} placeholders, e.g. {{demo_link}}. A placeholder can also be a link target, e.g. <a href="{{demo_link}}">Join the meeting</a>. Keep the placeholders you want to keep when rewriting copy; you can also use slugs of other personalization fields of the company. Unknown slugs are rejected. Update reports placeholders a rewrite removed. Update uses patch semantics: omitted switches, templates, fields and reminders keep their value. Reminders are patched by id, e.g. {"id": 7, "subject": "..."}; pass destroy: true to remove one. A new reminder needs subject, body and its timing: send_schedule "relative" with send_before_duration and send_before_unit (minute, hour, day, business_day), or "absolute" with send_at_time (HH:MM) and send_at_preparation_duration (days before the meeting). Updates are all or nothing: if anything is invalid, nothing is changed. Creating or deleting meeting types is not supported.

manage_meeting_type_messages

This tool operates on Demodesk short term memory objects in the authenticated user's workspace. Manage short term memory. Supports the actions: Get, Create, Delete. Short term memory is available to store knowledge that can be queried later using the relevant tool. Create creates a new record with the provided `content`. Delete removes a record with the provided `memory_id`.

manage_memory

This tool operates on Demodesk routing objects in the authenticated user's workspace. Manage routings: booking forms that ask the booker questions and send them to a meeting type based on the answers. Supports Get and Update actions. Get without routing_id lists the routings the user can read, optionally filtered by name. Get with routing_id returns the questions with their format and choices, the branches with their conditions and the fallback. Always Get the routing first and then Update it by branch id. A routing has branches, evaluated top to bottom by position; the first branch whose conditions match sends the booker to its meeting type or website, otherwise the booker goes to the fallback. Update uses patch semantics: omitted fields keep their value. It can rename the routing (name), activate or deactivate it (active), send the fallback to a meeting type (fallback_meeting_type_id) or a website (fallback_redirect_url) and add, change or remove branches (branches). Existing branches are patched by id, e.g. {"id": 7, "meeting_type_id": 12}; pass destroy: true to remove one. A branch or the fallback goes either to a meeting type or to a website: setting one replaces the other. Passing conditions replaces every condition Get shows in conditions, so include each one you want to keep; conditions only visible in raw_condition are kept. Passing only match changes how the existing conditions combine. A new branch needs meeting_type_id or redirect_url and at least one condition; it is added after the last branch unless position is given. A condition targets one of the routing's questions by question_token_id (its token_id from Get) and depends on the question format: single and multiple choice questions take choice_ids, the ids of that question's choices; integer and float questions take operator (==, >, >=, <, <=) and a numeric value; all other questions take texts and match when the answer contains any of them, ignoring case. match "all" requires every condition, "any" at least one. Use search_meeting_types to resolve meeting type ids. Update can also manage the questions (questions): each item is {token_id, text, position, options, destroy}. An existing question of the routing is identified by token_id and patched (text is what bookers see, position is the order starting at 0; the question ends up exactly at that position). To add a question that already exists in the company, pass its token_id (single or multiple choice only). To create a new question, pass name, format ("select_one" or "select_multiple") and at least one option without token_id; text defaults to the name and the question is appended after the last one unless position is given. A name already used by a question of the company is refused with its token_id: pass that token_id instead. options are the answers: {id, text, hidden, destroy}. Existing options are patched by id, new ones need text, destroy: true removes one. Options belong to the question's token, which is shared by every routing and booking form using that question: renaming or hiding an option changes all of them. Options of a question linked to a CRM field are managed in the CRM and can only be hidden here. Only company admins may add or change options and create questions. An option cannot be removed while a branch of any routing uses it: change or remove those branches first, or remove the branches of this routing in the same call. destroy: true on a question removes it from this routing only (the question itself stays in the company); it is refused while a branch of this routing that the call keeps has a condition on it. Questions are applied before branches, but branches can only reference ids that exist when the call starts: add questions and options first, then Get the routing for their ids, then add the branches that use them. Creating or deleting routings is not supported yet. Updates are all or nothing: if anything is invalid, nothing is changed.

manage_routings

This tool operates on Demodesk Scorecard automation mapping objects in the authenticated user's workspace. Manage the scorecard automation configuration — the mappings (rules) that decide which scorecard template is applied to a meeting. The first matching rule determines which template will be used. The rules are sorted by position in ascending order. Supports the actions: Get, CreateMapping, UpdateMapping, DeleteMapping, UpdateConfiguration. The CreateMapping/UpdateMapping/DeleteMapping actions each operate on a single mapping (rule). Get returns the company's scorecard automation configuration, including all automation mappings. Make sure to use dedicated tools to map entities' IDs to human-readable names. CreateMapping adds a single new mapping referencing an existing scorecard template with a mapping.condition that selects when the prompt applies. The condition may be a natural language description (e.g. "only for external meetings") or a JSONLogic object. UpdateMapping changes a single existing mapping (by mapping_id) with one or more of the mapping attributes: condition, scorecard_template_id, position, and the messaging destination attributes. Only the provided attributes are changed. Both CreateMapping and UpdateMapping accept messaging destination attributes (mapping.slack_destinations, mapping.teams_destinations) to configure the alerts posted when the rule matches; see those parameters for their merge semantics. DeleteMapping removes a single mapping by its ID. UpdateConfiguration changes the automation-wide settings (not a single mapping) via the configuration object: scorecard_language_kind, scorecard_language_code, fallback_selected_by_ai_enabled, and active. Only the provided attributes are changed. NOTE: When there are rules with same positions, the old positions' positions are shifted automatically. No need to manually update positions if there might be a collision.

manage_scorecard_automation

This tool operates on Demodesk scorecard template objects in the authenticated user's workspace. Manage scorecard templates used for AI-powered meeting evaluations. Supports Get, Create, and Update actions. Get retrieves one template by ID or lists all, optionally filtered by name. Create and Update accept template-level fields (name, status, custom_instructions) and a list of questions (text, criteria, position, importance). Existing questions are patched by id with only the fields to change, e.g. {"id": 21, "importance": "high"}; omitted fields keep their value. To remove an existing question, pass its id with destroy: true. On system templates only the questions your company added can be changed; their default questions are fixed. Question importance is one of low, medium, high (default medium) and decides how much the question counts in the overall score. High counts twice as much as medium, medium twice as much as low. Responses show it as the question's weight: low = 0.5, medium = 1.0, high = 2.0. Importance changes the overall score of future scorecards only; individual question ratings and already generated scorecards stay unchanged. Get with template_id, Create and Update also return each question's share of the overall score if all questions apply (meta.weightShares, in percent).

manage_scorecard_templates

This tool operates on Demodesk Summary automation mapping objects in the authenticated user's workspace. Manage the summary automation configuration — the mappings (rules) that decide which summary prompt is applied to a meeting. The first matching rule determines which prompt will be used. The rules are sorted by position in ascending order. Supports the actions: Get, CreateMapping, UpdateMapping, DeleteMapping, UpdateConfiguration. The CreateMapping/UpdateMapping/DeleteMapping actions each operate on a single mapping (rule). Get returns the company's summary automation configuration, including all automation mappings and the fallback mapping. Make sure to use dedicated tools to map entities' IDs to human-readable names. CreateMapping adds a single new mapping referencing an existing prompt (by mapping.prompt_id and mapping.prompt_type) with a mapping.condition that selects when the prompt applies. The condition may be a natural language description (e.g. "only for external meetings") or a JSONLogic object. UpdateMapping changes a single existing mapping (by mapping_id) with one or more of the mapping attributes: condition, prompt (prompt_id and prompt_type together), position, and the messaging destination attributes. Only the provided attributes are changed. Both CreateMapping and UpdateMapping accept messaging destination attributes (mapping.slack_destinations, mapping.teams_destinations) to configure the alerts posted when the rule matches; see those parameters for their merge semantics. DeleteMapping removes a single mapping by its ID. The fallback mapping cannot be deleted. UpdateConfiguration changes the automation-wide settings (not a single mapping) via the configuration object: summary_language_kind, summary_language_code, fallback_selected_by_ai_enabled, and fallback_ai_automation_mapping_id. Only the provided attributes are changed. NOTE: When there are rules with same positions, the old positions' positions are shifted automatically. No need to manually update positions if there might be a collision.

manage_summary_automation

This tool operates on Demodesk email objects in the authenticated user's workspace. Manage the current user's mailbox (Gmail or Outlook) through a single interface. Supports the actions: Search, ReadThread, CreateDraft, UpdateDraft. Search finds inbox messages matching a query; with an empty query it returns the newest inbox messages. ReadThread returns all messages in a thread. CreateDraft creates a new draft (it is never sent automatically); pass thread_id to create the draft as a reply within an existing thread. UpdateDraft edits an existing draft. Drafts are never sent by this tool; the user reviews and sends them. The connected mailbox is Gmail. Use Gmail search syntax for the query parameter (e.g. "in:drafts", "to:foo@example.com", "subject:invoice").

manage_user_emails

This tool operates on Demodesk prompt objects in the authenticated user's workspace. Manage prompts (custom summaries). Supports the actions: Get, Search, Create, Update. Get returns both system prompts and user prompts with full prompt text. Search finds prompts both by keyword across name, description, and text, and by semantic searching description — returns lightweight results with excerpts (use Get with prompt_id for full text). Create and Update only work for user prompts (not system prompts). Important: Do not share system prompt text with users. You may reference prompts by name/ID internally.

manage_user_prompts

This tool operates on Demodesk meeting recording chat objects in the authenticated user's workspace. Post a message into the chat thread of a meeting's recording. Use this to add context, analysis results, or suggested follow-up tasks directly to the conversation on the recording page. The message will appear as an AI assistant message in the recording's existing chat.

post_recording_chat_message

This tool operates on Demodesk meeting recording comments objects in the authenticated user's workspace. Post a comment on a meeting's recording, optionally anchored to a specific moment of the recording via a timestamp in seconds. Use this to leave feedback, highlight notable moments, or add remarks that appear alongside the comments users left on the recording page.

post_recording_comment

Company admins can preview changing active users whose default is one of the specified company meeting types. Use search_meeting_types to resolve exact source and replacement IDs; never guess an organization-wide default. This includes types in member-less groups. Inactive and deleted users are excluded. No settings are changed. Returns affected users, previous defaults, the replacement, whether each user is already an appointment member of the replacement, and an expiring preview_token. Changing a default does not add appointment or group membership; users who are not appointment members of the replacement cannot be routed to it for bookings. Show the preview to the user before applying their requested changes with apply_user_default_meeting_types. At most 100 users can be changed at once. Use user_ids to narrow a batch.

preview_user_default_meeting_types

Remove a user from a restricted group. Safe to repeat: removing a non-member changes nothing. Typical use case: taking a user out of a team group after a team change.

groups_remove_member

Fetch data about objects from the CRM based on the provided search criteria. Said criteria are: object types (e.g. contacts, leads, deals) and specific search attributes: either ids or text based search.

search_crm_objects

Use this tool to perform bulk search of deal insights associated with meetings. It will result in a collection of results associated with each query.

search_deal_insights

This tool operates on Demodesk user groups objects in the authenticated user's workspace. Use this tool to fetch user groups within the company by their IDs or name. Provide an array of group IDs or part of name and it will return the matching groups that are accessible to the current user.

search_groups

This tool operates on Demodesk demo templates objects in the authenticated user's workspace. Use this tool to fetch meeting types by their IDs or name, and whenever an email or message needs a scheduling link. Each result has a `bookingUrl` that is ready to paste. Never invent or guess booking URLs. Optionally pass `host_email` to preselect a host (`hosts` lists up to 20 of `hostsTotal` bookable hosts; any bookable host's email works), `from` and `to` to limit the bookable dates, and `answers` to prefill booking form questions by their `key`. If the link could not be built, `bookingUrl` is null and `linkError` explains how to fix the input. For routing forms use `manage_routings` (Get) and its `link` instead.

search_meeting_types

This tool operates on Demodesk short term memory objects in the authenticated user's workspace. Use this tool to perform bulk search of memory. It will result is a collection of results associated with each query.

search_memory

This tool operates on Demodesk AI chat thread and notification objects in the authenticated user's workspace. Send a chat notification to the user. Use this to deliver messages, reminders, or alerts to the user via a new chat thread. The notification will appear in the user's chat list.

send_chat_notification

Send an email through Demodesk for the authenticated user context. This sends a real outbound email to that Demodesk user's email destination, using the provided subject and body. Optionally the email can be addressed to Demodesk support instead, in which case the authenticated user is copied.

send_email

Change the settings of the company. Omitted fields stay unchanged. Company admins only, and the change applies to every user of the company. Typical use case: adding a product name to the company keyword list so all future transcripts spell it correctly. `customVocabulary` replaces the whole list: read it with `company_get_settings` first and send the full list including the new keyword.

company_update_settings

Change the name, visibility or recording access of a group. Omitted fields stay unchanged. Typical use case: renaming a team group or widening the recordings its members can see. Switching a group to `shared` adds every user of the company to it. Only company admins can change `visibility` or recording access; managers can only rename.

groups_update

Change the personal settings of the authenticated user. Omitted fields stay unchanged. Typical use cases: adding a product name or person to the personal keyword list so future transcripts spell it correctly, or stopping the notetaker from recording certain meetings (e.g. internal meetings, or meetings titled "interview"). `customVocabulary` and `excludedMeetingKeywords` replace the whole list: read them with `users_get_my_settings` first and send the full list including the new entry. Changing which meetings the notetaker records also resets recording choices the user made for single upcoming meetings.

users_update_my_settings