---
title: Prompts, resources and widgets
description: The ready-made prompts, in-chat widgets (MCP Apps) and resources the Signal connector serves.
product: signal
section: mcp
order: 7
---

<!-- Generated content: copied from Signal's code-generated tool reference (docs/mcp/tool-reference.md). Regenerate this pack's copy rather than editing it by hand. -->

# Prompts, resources and widgets

## Prompts

Ready-made starting points a person picks in their assistant, which the assistant fills in and sends as the person's own message. A prompt carries no workspace data, and is offered only to a connection that can use every tool and change action it names.

<a id="prompt-morning-brief"></a>
### My Morning Brief

`morning_brief` · Offered to a connection with the Sales and Analytics areas.

Starts the person's Morning Brief: their work for today (what to do first, Actions due and overdue, Deals at risk, the call queue, Bookings) and what happened overnight, from Signal's own reads. A review only reads: it changes nothing in Signal.

**Tools it names:** `get_my_focus`, `get_marketing_digest`

| Argument | Required | Description |
|---|---|---|
| `focus` | no | What to look at most, such as Deals at risk or my call queue; left out, all of it (at most 200 characters) |

<a id="prompt-campaign-debrief"></a>
### Debrief a Campaign

`campaign_debrief` · Offered to a connection with the Marketing area.

Starts a debrief of one Marketing Campaign: its results as the Performance tab shows them, each Email's results, and the pipeline and revenue it influenced under each attribution model. A review only reads: it changes nothing in Signal.

**Tools it names:** `list_campaigns`, `get_marketing_performance`, `list_marketing_emails`, `get_attribution`

| Argument | Required | Description |
|---|---|---|
| `campaign` | no | The Campaign, by its name; left out, the Campaign that sent most recently (at most 200 characters) |

<a id="prompt-import-prospect-list"></a>
### Import a prospect list

`import_prospect_list` · Offered to a connection with the Data import area, View and make changes, and a role, plan and modules that allow import_records.

Starts importing a list (a spreadsheet, a file in the chat or another app's export) into Signal as prospect contacts, Prospect Companies or Accounts, as the CSV import does. Each part is previewed, and the person confirms it before anything is imported.

**Tools it names:** `list_change_actions`, `preview_change`, `apply_change`

**Change actions it names:** [`import_records`](change-actions.md#change-import-records)

| Argument | Required | Description |
|---|---|---|
| `source` | yes | Where the list is: a spreadsheet or file in this chat, or another app (at most 200 characters) |
| `kind` | no | What the rows are: prospect contacts (the default), Prospect Companies or Accounts (at most 200 characters) |

<a id="prompt-weekly-pipeline-review"></a>
### Review the week's pipeline

`weekly_pipeline_review` · Offered to a connection with the Sales area.

Starts a review of the pipeline over the last week, or a stretch the person names: open Deals by stage, those closing soon or past their close date, Deals won and lost, and overdue Actions. A review only reads: it changes nothing in Signal.

**Tools it names:** `get_pipeline_summary`, `list_deals`, `list_actions`

| Argument | Required | Description |
|---|---|---|
| `period` | no | The stretch to look back over, such as this week; left out, the last 7 days (at most 200 characters) |
| `focus` | no | A pipeline, a stage or a teammate to look at most; left out, the whole pipeline (at most 200 characters) |

<a id="prompt-attribution-review"></a>
### Review what drives pipeline

`attribution_review` · Offered to a connection with the Marketing area.

Starts a review of which Campaigns really drive pipeline and revenue, under each of Signal's attribution models, with the model, basis, window and evidence behind every figure. A review only reads: it changes nothing in Signal.

**Tools it names:** `list_campaigns`, `get_attribution`

| Argument | Required | Description |
|---|---|---|
| `range` | no | The window to look at, such as the last quarter; left out, Signal's default (at most 200 characters) |
| `campaigns` | no | Campaigns to look at most, by name; left out, every Campaign (at most 200 characters) |

<a id="prompt-channel-performance"></a>
### How our channels performed

`channel_performance` · Offered to a connection with the Marketing and Analytics areas.

Starts a review of channel performance: website analytics by channel, Signal's own website tracking and Campaign Emails, side by side and each labeled with its source. A review only reads: it changes nothing in Signal.

**Tools it names:** `list_connected_apps`, `preview_chart`, `get_website_activity`, `list_marketing_emails`

| Argument | Required | Description |
|---|---|---|
| `range` | no | The window to look at, such as last month; left out, the last 30 days (at most 200 characters) |

<a id="prompt-bill-call-offs"></a>
### Bill my call-offs

`bill_call_offs` · Offered to a connection with the Sales area, View and make changes, and a role, plan and modules that allow record_call_off_invoice.

Starts billing Property call-offs that are ready to bill: each invoice is created through the person's accounting app's own connector, after checking it has none for that call-off yet, and its number is recorded in Signal, previewed and confirmed.

**Tools it names:** `list_call_offs`, `preview_change`, `apply_change`

**Change actions it names:** [`record_call_off_invoice`](change-actions.md#change-record-call-off-invoice)

| Argument | Required | Description |
|---|---|---|
| `call_offs` | no | Which call-offs: a developer, a development or call-off references; left out, every one ready to bill (at most 200 characters) |

<a id="prompt-build-workflow"></a>
### Build a workflow

`build_workflow` · Offered to a connection with the Sales area, View and make changes, and a role, plan and modules that allow create_workflow, fill_workflow_setting and turn_on_workflow.

Starts building a workflow from what the person says should happen and when: drafted from the triggers and actions Signal has today, completed with the person's answers, and turned on only if they confirm. Every change is previewed first.

**Tools it names:** `list_workflow_building_blocks`, `list_workflows`, `get_workflow`, `preview_change`, `apply_change`

**Change actions it names:** [`create_workflow`](change-actions.md#change-create-workflow), [`fill_workflow_setting`](change-actions.md#change-fill-workflow-setting), [`turn_on_workflow`](change-actions.md#change-turn-on-workflow)

| Argument | Required | Description |
|---|---|---|
| `goal` | yes | What should happen and when, in your own words (at most 600 characters) |

<a id="prompt-fill-my-call-queue"></a>
### Fill my call queue

`fill_my_call_queue` · Offered to a connection with the Sales area, View and make changes, and a role, plan and modules that allow create_call_list and add_to_call_queue.

Starts filling the person's call queue for today from Hot prospects, a Segment, a search or Deals at risk, skipping anyone already waiting. Who will be added is previewed, and the person confirms it before anyone is added.

**Tools it names:** `list_call_queue`, `get_my_focus`, `preview_change`, `apply_change`

**Change actions it names:** [`create_call_list`](change-actions.md#change-create-call-list), [`add_to_call_queue`](change-actions.md#change-add-to-call-queue)

| Argument | Required | Description |
|---|---|---|
| `from` | no | Who to call: Hot prospects, a Segment by name, a search or Deals at risk; left out, suggest from today's focus (at most 200 characters) |

## Widgets

Interactive views drawn by hosts that support MCP Apps, each linked from the tools whose answers it draws. A widget is the same page for everyone and reaches no network; what it draws arrives in its tool's answer.

MCP Apps protocol version: `2026-01-26`.

| Widget | What it draws | Tools | Resource |
|---|---|---|---|
| <a id="widget-chart"></a>Signal chart (`chart`) | Draws a chart (preview_chart), a live Google Analytics report (run_ga4_report) or a dashboard's tiles (get_dashboard, Traffic & Channels included) in Signal's own colors, words and number formats. | `preview_chart`, `run_ga4_report`, `get_dashboard` | `ui://signal/chart.html` |
| <a id="widget-attribution"></a>Signal attribution (`attribution`) | Draws get_attribution's answer: a Campaign's credit under every model, a Deal's journey and credits, or the Model comparison. | `get_attribution` | `ui://signal/attribution.html` |
| <a id="widget-campaign-card"></a>Signal Marketing results (`campaign_card`) | Draws get_marketing_performance's answer: a Campaign's figures, an Email's results, a Form's submissions or a Sequence's counts. | `get_marketing_performance` | `ui://signal/campaign_card.html` |
| <a id="widget-focus-board"></a>Signal focus for today (`focus_board`) | Draws get_my_focus's answer: today's Actions, each with Mark done and Reschedule as the connection allows, and the rest of the day. | `get_my_focus` | `ui://signal/focus_board.html` |
| <a id="widget-email-preview"></a>Signal Email preview (`email_preview`) | Draws get_marketing_item's preview of a Marketing Email, sanitized, in a sandboxed frame, with Send me a test as the connection allows. | `get_marketing_item` | `ui://signal/email_preview.html` |
| <a id="widget-change-card"></a>Signal change (`change_card`) | Draws preview_change's card with Confirm, the receipt with Undo when it's allowed, and an import's rows to leave out. | `preview_change` | `ui://signal/change_card.html` |
| <a id="widget-pipeline-board"></a>Signal pipeline (`pipeline_board`) | Draws list_deals' answer as a board: the Deals by stage, each with Move to… as the connection allows. | `list_deals` | `ui://signal/pipeline_board.html` |
| <a id="widget-website-companies"></a>Signal website visits (`website_companies`) | Draws get_website_activity's answer: the companies and people that visited your website, your sites, the overview or one record's visits, with Add as a Prospect Company as the connection allows. | `get_website_activity` | `ui://signal/website_companies.html` |
| <a id="widget-record-card"></a>Signal record (`record_card`) | Draws fetch's answer: a record's facts and what hangs off it, with Add a note as the connection allows, or a change's status. | `fetch` | `ui://signal/record_card.html` |

## Resources

What an assistant can read beside the conversation, each through the same checks as the tool it mirrors.

| Resource | What it holds | Served to |
|---|---|---|
| <a id="resource-glossary"></a>Signal's glossary (`signal://glossary`) | Signal's words (Deals, Accounts, prospect contacts, Actions, Segments, Sequences, Signal Score, call-offs and more), each with a one-line meaning. | Every connection |
| <a id="resource-attribution-models"></a>Attribution models (`signal://attribution-models`) | How Signal splits a Deal's credit between Campaigns: the six models, the pipeline and revenue bases, the lookback window and the time-decay half-life. | Every connection |
| <a id="resource-change-actions"></a>Change actions (`signal://change-actions`) | The changes this connection can preview in its default workspace, as list_change_actions lists them: each one's name, what it does, its area and its required fields. | Connections with View and make changes |
| <a id="resource-metric-catalog"></a>Metric catalog (`signal://workspaces/{workspace_id}/metrics`) | The KPI catalog the workspace's plan offers, as list_metrics gives it: each metric's key, name, unit, group, per_person and what it measures. | Connections with the Analytics area |
| <a id="resource-pipelines"></a>Pipelines and stages (`signal://workspaces/{workspace_id}/pipelines`) | The workspace's Deal pipelines, as list_pipelines gives them: each pipeline's id, name, whether it is the default, and its stages in order. | Connections with the Sales area |
| <a id="resource-brand-kit"></a>Brand Kit (`signal://workspaces/{workspace_id}/brand-kit`) | The workspace's Brand Kit, as get_marketing_item gives it for brand_kit: brand and button colors, the palette, body and heading fonts, and the logo. | Connections with the Marketing area |
| <a id="resource-segment-fields"></a>Segment fields (`signal://workspaces/{workspace_id}/segment-fields`) | The fields a workspace Segment's rules can use, for prospect contacts and for Contacts at Accounts: type, operators and choices. | Connections with the Marketing area |
| <a id="resource-workflow-options"></a>Workflow options (`signal://workspaces/{workspace_id}/workflow-options`) | The choices a workflow step's setting takes, as fill_workflow_setting checks them: stages with their pipeline, pipelines, teammates, Lists and Sequences, each by id. | Connections with the Sales area |
