13
],
14
"toolCount": 63,
15
"triggerCount": 2,
16
- "version": "20260828_00",
16
+ "version": "20260903_00",
17
"tools": [
18
{
19
"slug": "GMAIL_ADD_LABEL_TO_EMAIL",
535
],
536
"toolCount": 893,
537
"triggerCount": 20,
538
- "version": "20260831_00",
538
+ "version": "20260902_00",
539
"tools": [
540
{
541
"slug": "GITHUB_ABORT_REPOSITORY_MIGRATION",
5170
],
5171
"toolCount": 49,
5172
"triggerCount": 7,
5173
- "version": "20260826_00",
5173
+ "version": "20260902_00",
5174
"tools": [
5175
{
5176
"slug": "GOOGLECALENDAR_ACL_DELETE",
5934
],
5935
"toolCount": 53,
5936
"triggerCount": 16,
5937
- "version": "20260826_00",
5937
+ "version": "20260902_00",
5938
"tools": [
5939
{
5940
"slug": "GOOGLESHEETS_ADD_SHEET",
8072
],
8073
"toolCount": 305,
8074
"triggerCount": 5,
8075
- "version": "20260901_00",
8075
+ "version": "20260903_00",
8076
"tools": [
8077
{
8078
"slug": "OUTLOOK_ACCEPT_EVENT",
10312
],
10313
"toolCount": 90,
10314
"triggerCount": 7,
10315
- "version": "20260826_00",
10315
+ "version": "20260902_00",
10316
"tools": [
10317
{
10318
"slug": "GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE",
12540
],
12541
"toolCount": 47,
12542
"triggerCount": 12,
12543
- "version": "20260819_00",
12543
+ "version": "20260908_00",
12544
"tools": [
12545
{
12546
"slug": "LINEAR_ARCHIVE_ISSUE",
12619
},
12620
{
12621
"slug": "LINEAR_GET_ATTACHMENT",
12622
- "name": "Download issue attachments",
12623
- "description": "Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension."
12622
+ "name": "Download issue files",
12623
+ "description": "Downloads a Linear Attachment record or a private upload embedded in issue/comment Markdown; `file_name` must include the correct extension."
12624
},
12625
{
12626
"slug": "LINEAR_GET_COMMENT",
12645
{
12646
"slug": "LINEAR_GET_LINEAR_ISSUE",
12647
"name": "Get Linear issue",
12648
- "description": "Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes for comment IDs), subscribers, and due date. Does not include parent, milestone, cycle, or relation graphs—use LINEAR_RUN_QUERY_OR_MUTATION for those. Optional fields (labels, project, state, assignee, cycle) may be null; guard against null when accessing nested properties. Returns null or 'Entity not found' for invalid IDs, cross-workspace IDs, or restricted teams. Rate limit: ~60 req/min; HTTP 429 on excess—apply exponential backoff and respect Retry-After headers."
12648
+ "description": "Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes for comment IDs), subscribers, and due date. Embedded screenshots are uploads.linear.app URLs in description/comment Markdown, not Attachment records; download them with LINEAR_GET_ATTACHMENT's upload_url input. Does not include parent, milestone, cycle, or relation graphs—use LINEAR_RUN_QUERY_OR_MUTATION for those. Optional fields (labels, project, state, assignee, cycle) may be null; guard against null when accessing nested properties. Returns null or 'Entity not found' for invalid IDs, cross-workspace IDs, or restricted teams. Rate limit: ~60 req/min; HTTP 429 on excess—apply exponential backoff and respect Retry-After headers."
12649
},
12650
{
12651
"slug": "LINEAR_GET_LINEAR_PROJECT",
12929
],
12930
"toolCount": 26,
12931
"triggerCount": 6,
12932
- "version": "20260828_00",
12932
+ "version": "20260902_00",
12933
"tools": [
12934
{
12935
"slug": "AIRTABLE_CREATE_BASE",
13521
"OAUTH2"
13522
],
13523
"toolCount": 102,
13524
- "triggerCount": 3,
13525
- "version": "20260828_00",
13524
+ "triggerCount": 17,
13525
+ "version": "20260908_00",
13526
"tools": [
13527
{
13528
"slug": "JIRA_ADD_ATTACHMENT",
14037
],
14038
"triggers": [
14039
{
14040
- "slug": "JIRA_NEW_ISSUE_TRIGGER",
14041
- "name": "New Issue",
14042
- "description": "Fires when a new issue is created in the Jira project you configure.\n\nOnly issues created in that project produce an event."
14040
+ "slug": "JIRA_COMMENT_CREATED",
14041
+ "name": "Comment Created",
14042
+ "description": "Triggers when a comment is posted on a Jira issue. Can deliver comments\non issues the connected account cannot open in Jira itself."
14043
+ },
14044
+ {
14045
+ "slug": "JIRA_COMMENT_DELETED",
14046
+ "name": "Comment Deleted",
14047
+ "description": "Triggers when a comment is deleted from a Jira issue. The deleted\ncomment's text still arrives. Can deliver comments on issues the connected\naccount cannot open in Jira itself."
14048
+ },
14049
+ {
14050
+ "slug": "JIRA_COMMENT_UPDATED",
14051
+ "name": "Comment Updated",
14052
+ "description": "Triggers when an existing comment on a Jira issue is edited. The payload\ncarries the comment as it now reads, not what it said before. Can deliver\ncomments on issues the connected account cannot open in Jira itself."
14053
+ },
14054
+ {
14055
+ "slug": "JIRA_ISSUE_CREATED",
14056
+ "name": "Issue Created",
14057
+ "description": "Triggers when an issue is created in Jira, including a sub-task. Can\ndeliver issues the connected account cannot open in Jira itself."
14058
+ },
14059
+ {
14060
+ "slug": "JIRA_ISSUE_DELETED",
14061
+ "name": "Issue Deleted",
14062
+ "description": "Triggers when an issue is deleted from Jira. The deleted issue's full\nfield set still arrives, so the filters below apply to it as usual. Can\ndeliver issues the connected account cannot open in Jira itself."
14063
+ },
14064
+ {
14065
+ "slug": "JIRA_ISSUE_UPDATED",
14066
+ "name": "Issue Updated",
14067
+ "description": "Triggers when a field on an existing issue changes — its status, assignee,\nor anything else on the issue. One edit can change several fields and arrives\nas one event; creating a sub-task also updates its parent. Commenting does not\nfire it. Can deliver issues the connected account cannot open in Jira itself."
14068
+ },
14069
+ {
14070
+ "slug": "JIRA_SPRINT_CLOSED",
14071
+ "name": "Sprint Closed",
14072
+ "description": "Triggers when a sprint is completed and moves into the closed state."
14073
+ },
14074
+ {
14075
+ "slug": "JIRA_SPRINT_CREATED",
14076
+ "name": "Sprint Created",
14077
+ "description": "Triggers when a sprint is created on a Jira board. Creating a sprint does\nnot start it — watch Sprint Started for that."
14078
+ },
14079
+ {
14080
+ "slug": "JIRA_SPRINT_STARTED",
14081
+ "name": "Sprint Started",
14082
+ "description": "Triggers when a sprint moves into the active state."
14083
},
14084
{
14045
- "slug": "JIRA_NEW_PROJECT_TRIGGER",
14046
- "name": "New Project",
14047
- "description": "Triggered when a new project is added in Jira"
14085
+ "slug": "JIRA_SPRINT_UPDATED",
14086
+ "name": "Sprint Updated",
14087
+ "description": "Triggers when a sprint's name, goal, dates or state changes. Starting a\nsprint also fires this when the same call changed another field; closing one\ndoes not."
14088
},
14089
{
14050
- "slug": "JIRA_UPDATED_ISSUE_TRIGGER",
14051
- "name": "Updated Issue",
14052
- "description": "Fires when an existing issue is changed in the Jira project you configure —\nfor example its status, assignee, or any other field on the issue is\nupdated. Only issues in that project produce an event.\n\nIt does not fire on comment activity: adding, editing, or deleting a\ncomment on an issue will not produce an event from this trigger."
14090
+ "slug": "JIRA_VERSION_CREATED",
14091
+ "name": "Version Created",
14092
+ "description": "Triggers when a project version is created in Jira."
14093
+ },
14094
+ {
14095
+ "slug": "JIRA_VERSION_DELETED",
14096
+ "name": "Version Deleted",
14097
+ "description": "Triggers when a project version is deleted outright. A version that\ndisappeared because it was merged into another one fires Version Merged\ninstead."
14098
+ },
14099
+ {
14100
+ "slug": "JIRA_VERSION_MERGED",
14101
+ "name": "Version Merged",
14102
+ "description": "Triggers when a project version is merged into another one, carrying both\nthe version that went away and the one that survived."
14103
+ },
14104
+ {
14105
+ "slug": "JIRA_VERSION_MOVED",
14106
+ "name": "Version Moved",
14107
+ "description": "Triggers when a project version is reordered within its project's release\nlist."
14108
+ },
14109
+ {
14110
+ "slug": "JIRA_VERSION_RELEASED",
14111
+ "name": "Version Released",
14112
+ "description": "Triggers when a project version is marked released."
14113
+ },
14114
+ {
14115
+ "slug": "JIRA_VERSION_UNRELEASED",
14116
+ "name": "Version Unreleased",
14117
+ "description": "Triggers when a released project version is put back to unreleased."
14118
+ },
14119
+ {
14120
+ "slug": "JIRA_VERSION_UPDATED",
14121
+ "name": "Version Updated",
14122
+ "description": "Triggers when a project version's name, description or dates change.\nReleasing and un-releasing a version each fire this as well, alongside\nVersion Released and Version Unreleased."
14123
}
14124
],
14125
"authConfigDetails": [
14281
],
14282
"toolCount": 30,
14283
"triggerCount": 0,
14214
- "version": "20260826_00",
14284
+ "version": "20260903_00",
14285
"tools": [
14286
{
14287
"slug": "FIRECRAWL_AGENT_CANCEL",
18538
],
18539
"toolCount": 110,
18540
"triggerCount": 0,
18471
- "version": "20260826_00",
18541
+ "version": "20260903_00",
18542
"tools": [
18543
{
18544
"slug": "BITBUCKET_APPROVE_PULL_REQUEST",
19928
],
19929
"toolCount": 22,
19930
"triggerCount": 0,
19861
- "version": "20260618_00",
19931
+ "version": "20260903_00",
19932
"tools": [
19933
{
19934
"slug": "COMPOSIO_SEARCH_AMAZON",
23291
],
23292
"toolCount": 17,
23293
"triggerCount": 0,
23224
- "version": "20260828_00",
23294
+ "version": "20260903_00",
23295
"tools": [
23296
{
23297
"slug": "SNOWFLAKE_CANCEL_STATEMENT_EXECUTION",
24373
],
24374
"toolCount": 173,
24375
"triggerCount": 0,
24306
- "version": "20260831_00",
24376
+ "version": "20260903_00",
24377
"tools": [
24378
{
24379
"slug": "MICROSOFT_TEAMS_ADD_CHAT_MEMBER",
28979
],
28980
"toolCount": 83,
28981
"triggerCount": 9,
28912
- "version": "20260828_00",
28982
+ "version": "20260903_00",
28983
"tools": [
28984
{
28985
"slug": "ONE_DRIVE_ADD_WORKBOOK_WORKSHEET",
33882
"OAUTH1"
33883
],
33884
"toolCount": 329,
33815
- "triggerCount": 5,
33816
- "version": "20260812_00",
33885
+ "triggerCount": 20,
33886
+ "version": "20260908_00",
33887
"tools": [
33888
{
33889
"slug": "TRELLO_ADD_BOARDS",
35533
],
35534
"triggers": [
35535
{
35466
- "slug": "TRELLO_ARCHIVED_CARD_TRIGGER",
35467
- "name": "Card Archived Trigger",
35468
- "description": "Triggered when a card is archived in the specified board"
35536
+ "slug": "TRELLO_ATTACHMENT_ADDED_TO_CARD",
35537
+ "name": "Attachment Added To Card",
35538
+ "description": "Triggers when a file or link is attached to a card."
35539
+ },
35540
+ {
35541
+ "slug": "TRELLO_ATTACHMENT_REMOVED_FROM_CARD",
35542
+ "name": "Attachment Removed From Card",
35543
+ "description": "Triggers when an attachment is removed from a card. Trello drops the\nattachment's URL from this event."
35544
+ },
35545
+ {
35546
+ "slug": "TRELLO_BOARD_ADDED_TO_WORKSPACE",
35547
+ "name": "Board Added To Workspace",
35548
+ "description": "Triggers when a board enters the watched Workspace — the Trello equivalent\nof a new project starting. Covers both a board created inside the Workspace\nand an existing board moved into it."
35549
+ },
35550
+ {
35551
+ "slug": "TRELLO_BOARD_LABEL_CREATED",
35552
+ "name": "Board Label Created",
35553
+ "description": "Triggers when a label is added to the board's label set. Applying an\nexisting label to a card is TRELLO_LABEL_ADDED_TO_CARD."
35554
+ },
35555
+ {
35556
+ "slug": "TRELLO_BOARD_LABEL_DELETED",
35557
+ "name": "Board Label Deleted",
35558
+ "description": "Triggers when a label is deleted from the board's label set. Trello drops\nthe label's text and colour from this event."
35559
+ },
35560
+ {
35561
+ "slug": "TRELLO_BOARD_LABEL_UPDATED",
35562
+ "name": "Board Label Updated",
35563
+ "description": "Triggers when a board label changes. `old` carries the previous value of the\nfield that changed."
35564
+ },
35565
+ {
35566
+ "slug": "TRELLO_BOARD_MEMBER_ROLE_CHANGED",
35567
+ "name": "Board Member Role Changed",
35568
+ "description": "Triggers when a board member is promoted to admin or demoted to a normal\nmember. `role` says which they hold now. Changes to and from Trello's\nobserver role are not covered."
35569
+ },
35570
+ {
35571
+ "slug": "TRELLO_BOARD_REMOVED_FROM_WORKSPACE",
35572
+ "name": "Board Removed From Workspace",
35573
+ "description": "Triggers when a board leaves the watched Workspace."
35574
+ },
35575
+ {
35576
+ "slug": "TRELLO_BOARD_UPDATED",
35577
+ "name": "Board Updated",
35578
+ "description": "Triggers when the watched board is renamed, its description changes, it is\nclosed or reopened, or one of its preferences changes — commenting,\nself-join, voting or card covers. `old` carries the previous value of the\none field that changed. Board visibility changes emit no Trello event, so\nthis never fires for a board becoming public or private."
35579
+ },
35580
+ {
35581
+ "slug": "TRELLO_CARD_COPIED",
35582
+ "name": "Card Copied",
35583
+ "description": "Triggers when a card is duplicated onto the watched board. The copy is the\ncard in the payload; `source_card` is the one it came from."
35584
+ },
35585
+ {
35586
+ "slug": "TRELLO_CARD_CREATED",
35587
+ "name": "Card Created",
35588
+ "description": "Triggers when a new card is typed onto the watched board. A card that\narrives by being copied, converted from a checklist item, or moved in from\nanother board has its own trigger."
35589
+ },
35590
+ {
35591
+ "slug": "TRELLO_CARD_CREATED_FROM_CHECKLIST_ITEM",
35592
+ "name": "Card Created From Checklist Item",
35593
+ "description": "Triggers when a checklist item is promoted into a card of its own — a\nsub-task becoming tracked work."
35594
+ },
35595
+ {
35596
+ "slug": "TRELLO_CARD_DELETED",
35597
+ "name": "Card Deleted",
35598
+ "description": "Triggers when a card is permanently deleted from the watched board. Trello\ndrops the card's title from this event, so only its ids are available."
35599
+ },
35600
+ {
35601
+ "slug": "TRELLO_CARD_MOVED_BETWEEN_LISTS",
35602
+ "name": "Card Moved Between Lists",
35603
+ "description": "Triggers when a card moves from one list to another on the watched board —\nthe hook for stage-change automations such as 'when a card reaches Done,\nclose the linked issue'. Moving a card within its own list changes only its\nposition and emits nothing."
35604
+ },
35605
+ {
35606
+ "slug": "TRELLO_CARD_MOVED_IN_FROM_ANOTHER_BOARD",
35607
+ "name": "Card Moved In From Another Board",
35608
+ "description": "Triggers when a card is moved onto the watched board from a different one —\na triage board handing work to a sprint board, say."
35609
},
35610
{
35471
- "slug": "TRELLO_NEW_ACTIVITY_TRIGGER",
35472
- "name": "New Activity Trigger",
35473
- "description": "Triggered when there is activity in Trello."
35611
+ "slug": "TRELLO_CARD_MOVED_OUT_TO_ANOTHER_BOARD",
35612
+ "name": "Card Moved Out To Another Board",
35613
+ "description": "Triggers when a card leaves the watched board for a different one."
35614
},
35615
{
35476
- "slug": "TRELLO_NEW_BOARD_TRIGGER",
35477
- "name": "New Board Trigger",
35478
- "description": "Triggered when a board is created in the specified workspace"
35616
+ "slug": "TRELLO_CARD_UPDATED",
35617
+ "name": "Card Updated",
35618
+ "description": "Triggers when a card's title, description, due date, start date, completion\ncheckbox or archived state changes. `old` carries the previous value of the\none field that changed and `card` carries the new one. Moving a card to a\ndifferent list is TRELLO_CARD_MOVED_BETWEEN_LISTS instead."
35619
},
35620
{
35481
- "slug": "TRELLO_NEW_CARD_TRIGGER",
35482
- "name": "New Card Trigger",
35483
- "description": "Triggered when a card is created in the specified board"
35621
+ "slug": "TRELLO_CARD_VOTE_CHANGED",
35622
+ "name": "Card Vote Changed",
35623
+ "description": "Triggers when a vote is cast on or withdrawn from a card — `voted` says\nwhich. Voting has to be enabled on the board for this to be possible."
35624
},
35625
{
35486
- "slug": "TRELLO_UPDATED_CARD_TRIGGER",
35487
- "name": "Card Updated Trigger",
35488
- "description": "Triggered when a specific card is updated"
35626
+ "slug": "TRELLO_CHECKLIST_ADDED_TO_CARD",
35627
+ "name": "Checklist Added To Card",
35628
+ "description": "Triggers when a checklist is attached to a card."
35629
+ },
35630
+ {
35631
+ "slug": "TRELLO_CHECKLIST_ITEM_ADDED",
35632
+ "name": "Checklist Item Added",
35633
+ "description": "Triggers when an item is added to a checklist."
35634
}
35635
],
35636
"authConfigDetails": [
40907
"OAUTH2"
40908
],
40909
"toolCount": 432,
40765
- "triggerCount": 7,
40766
- "version": "20260831_00",
40910
+ "triggerCount": 20,
40911
+ "version": "20260902_00",
40912
"tools": [
40913
{
40914
"slug": "STRIPE_ACCEPT_QUOTE",
43073
],
43074
"triggers": [
43075
{
42931
- "slug": "STRIPE_CHARGE_FAILED_TRIGGER",
42932
- "name": "Charge Failed Trigger",
42933
- "description": "Triggered when a direct charge fails in Stripe's legacy Charges API"
43076
+ "slug": "STRIPE_CHARGE_CAPTURED",
43077
+ "name": "Charge Captured",
43078
+ "description": "Occurs whenever a previously uncaptured charge is captured."
43079
+ },
43080
+ {
43081
+ "slug": "STRIPE_CHARGE_DISPUTE_CLOSED",
43082
+ "name": "Charge Dispute Closed",
43083
+ "description": "Occurs when a dispute is closed and the dispute status changes to `lost`, `warning_closed`, or `won`."
43084
+ },
43085
+ {
43086
+ "slug": "STRIPE_CHARGE_DISPUTE_CREATED",
43087
+ "name": "Charge Dispute Created",
43088
+ "description": "Occurs whenever a customer disputes a charge with their bank."
43089
+ },
43090
+ {
43091
+ "slug": "STRIPE_CHARGE_DISPUTE_UPDATED",
43092
+ "name": "Charge Dispute Updated",
43093
+ "description": "Occurs when the dispute is updated (usually with evidence)."
43094
+ },
43095
+ {
43096
+ "slug": "STRIPE_CHARGE_FAILED",
43097
+ "name": "Charge Failed",
43098
+ "description": "Occurs whenever a failed charge attempt occurs."
43099
+ },
43100
+ {
43101
+ "slug": "STRIPE_CHARGE_REFUNDED",
43102
+ "name": "Charge Refunded",
43103
+ "description": "Occurs whenever a charge is refunded, including partial refunds. Listen to `refund.created` for information about the refund."
43104
+ },
43105
+ {
43106
+ "slug": "STRIPE_CHARGE_REFUND_UPDATED",
43107
+ "name": "Charge Refund Updated",
43108
+ "description": "Occurs whenever a refund is updated on selected payment methods. For updates on all refunds, listen to `refund.updated` instead."
43109
+ },
43110
+ {
43111
+ "slug": "STRIPE_CHARGE_SUCCEEDED",
43112
+ "name": "Charge Succeeded",
43113
+ "description": "Occurs whenever a charge is successful."
43114
+ },
43115
+ {
43116
+ "slug": "STRIPE_CHECKOUT_SESSION_ASYNC_PAYMENT_FAILED",
43117
+ "name": "Checkout Session Async Payment Failed",
43118
+ "description": "Occurs when a payment intent using a delayed payment method fails."
43119
+ },
43120
+ {
43121
+ "slug": "STRIPE_CHECKOUT_SESSION_ASYNC_PAYMENT_SUCCEEDED",
43122
+ "name": "Checkout Session Async Payment Succeeded",
43123
+ "description": "Occurs when a payment intent using a delayed payment method finally succeeds."
43124
+ },
43125
+ {
43126
+ "slug": "STRIPE_CHECKOUT_SESSION_COMPLETED",
43127
+ "name": "Checkout Session Completed",
43128
+ "description": "Occurs when a Checkout Session has been successfully completed."
43129
+ },
43130
+ {
43131
+ "slug": "STRIPE_CHECKOUT_SESSION_EXPIRED",
43132
+ "name": "Checkout Session Expired",
43133
+ "description": "Occurs when a Checkout Session is expired."
43134
+ },
43135
+ {
43136
+ "slug": "STRIPE_CUSTOMER_CREATED",
43137
+ "name": "Customer Created",
43138
+ "description": "Occurs whenever a new customer is created."
43139
+ },
43140
+ {
43141
+ "slug": "STRIPE_CUSTOMER_DELETED",
43142
+ "name": "Customer Deleted",
43143
+ "description": "Occurs whenever a customer is deleted."
43144
},
43145
{
42936
- "slug": "STRIPE_CHECKOUT_SESSION_COMPLETED_TRIGGER",
42937
- "name": "Checkout Session Completed Trigger",
42938
- "description": "Triggered when a checkout session is completed in Stripe"
43146
+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_CREATED",
43147
+ "name": "Customer Subscription Created",
43148
+ "description": "Occurs whenever a customer is signed up for a new plan."
43149
},
43150
{
42941
- "slug": "STRIPE_INVOICE_PAYMENT_SUCCEEDED_TRIGGER",
42942
- "name": "Invoice Payment Succeeded Trigger",
42943
- "description": "Triggered when an invoice payment is successful in Stripe"
43151
+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_DELETED",
43152
+ "name": "Customer Subscription Deleted",
43153
+ "description": "Occurs whenever a customer's subscription ends."
43154
},
43155
{
42946
- "slug": "STRIPE_PAYMENT_FAILED_TRIGGER",
42947
- "name": "Payment Intent Failed Trigger",
42948
- "description": "Triggered when a payment intent fails in Stripe"
43156
+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_TRIAL_WILL_END",
43157
+ "name": "Customer Subscription Trial Will End",
43158
+ "description": "Occurs three days before a subscription's trial period is scheduled to end, or immediately when a trial is ended early (for example, with `trial_end=now` or when a Customer Portal plan change ends a trial). If a trial is shortened so that fewer than three days remain, this event can fire immediately, including during the same transaction that collects payment. Before sending payment-reminder communications from this webhook, check the subscription status and latest invoice to determine whether payment has already been collected."
43159
},
43160
{
42951
- "slug": "STRIPE_PRODUCT_CREATED_TRIGGER",
42952
- "name": "Product Created Trigger",
42953
- "description": "Triggered when a product is created in Stripe"
43161
+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_UPDATED",
43162
+ "name": "Customer Subscription Updated",
43163
+ "description": "Occurs whenever a subscription changes (e.g., switching from one plan to another, or changing the status from trial to active)."
43164
},
43165
{
42956
- "slug": "STRIPE_SUBSCRIPTION_ADDED_TRIGGER",
42957
- "name": "Subscription Added Trigger",
42958
- "description": "Triggered when a subscription is added in Stripe"
43166
+ "slug": "STRIPE_CUSTOMER_UPDATED",
43167
+ "name": "Customer Updated",
43168
+ "description": "Occurs whenever any property of a customer changes."
43169
},
43170
{
42961
- "slug": "STRIPE_SUBSCRIPTION_DELETED_TRIGGER",
42962
- "name": "Subscription Deleted Trigger",
42963
- "description": "Triggered when a subscription is deleted in Stripe"
43171
+ "slug": "STRIPE_INVOICE_CREATED",
43172
+ "name": "Invoice Created",
43173
+ "description": "Occurs whenever a new invoice is created. To learn how webhooks can be used with this event, and how they can affect it, see Using Webhooks with Subscriptions."
43174
}
43175
],
43176
"authConfigDetails": [
47432
],
47433
"toolCount": 177,
47434
"triggerCount": 0,
47225
- "version": "20260819_00",
47435
+ "version": "20260903_00",
47436
"tools": [
47437
{
47438
"slug": "DROPBOX_ACTIVATE_TEAM_FOLDER",
49139
],
49140
"toolCount": 69,
49141
"triggerCount": 20,
48932
- "version": "20260828_00",
49142
+ "version": "20260903_00",
49143
"tools": [
49144
{
49145
"slug": "CONFLUENCE_ADD_CONTENT_LABEL",
60725
],
60726
"toolCount": 452,
60727
"triggerCount": 2,
60518
- "version": "20260828_00",
60728
+ "version": "20260903_00",
60729
"tools": [
60730
{
60731
"slug": "ZENDESK_APPLY_ZENDESK_MACRO",
63290
"OAUTH2",
63291
"API_KEY"
63292
],
63083
- "toolCount": 53,
63293
+ "toolCount": 56,
63294
"triggerCount": 0,
63085
- "version": "20260826_00",
63295
+ "version": "20260902_00",
63296
"tools": [
63297
{
63298
"slug": "METAADS_CREATE_AD",
63349
"name": "Get Page Accounts",
63350
"description": "Tool to retrieve permanent page access tokens for accounts managed by the user. Use when you need to get pages the user manages along with access tokens for each page."
63351
},
63352
+ {
63353
+ "slug": "METAADS_GET_PIXEL_EVENT_STATS",
63354
+ "name": "Get Pixel Event Stats",
63355
+ "description": "Read recent Pixel event-count and processing statistics, optionally restricted to server events and one event name, to verify aggregate ingestion."
63356
+ },
63357
{
63358
"slug": "METAADS_GET_USER",
63359
"name": "Get User",
63364
"name": "Get Video",
63365
"description": "DEPRECATED: Use METAADS_GET_OBJECT instead. Tool to retrieve video information from Meta's Graph API by video ID. Use when you need to get video details such as the source URL for playback/download, permalink URL to view on Facebook, or other video metadata like title, description, length, and thumbnails."
63366
},
63367
+ {
63368
+ "slug": "METAADS_LIST_AD_ACCOUNT_PIXELS",
63369
+ "name": "List Ad Account Pixels",
63370
+ "description": "List the Pixels and consolidated datasets associated with an ad account so a usable data-source ID can be selected for Conversions API events."
63371
+ },
63372
{
63373
"slug": "METAADS_LIST_AD_CREATIVES",
63374
"name": "List Ad Creatives",
63554
"name": "Read Ad Sets",
63555
"description": "Retrieve ad sets from a Meta ad account using the Marketing API. Returns information about the ad sets including their status, targeting, and other properties."
63556
},
63557
+ {
63558
+ "slug": "METAADS_SEND_CONVERSION_EVENTS",
63559
+ "name": "Send Conversion Events",
63560
+ "description": "Irreversibly submit 1-1,000 validated server conversion events to a Meta Pixel or dataset. A test_event_code routes events to Test Events but does not prevent targeting or measurement side effects; production submission requires explicit confirmation."
63561
+ },
63562
{
63563
"slug": "METAADS_UPDATE_AD_CREATIVE",
63564
"name": "Update Ad Creative",
63774
"composioManagedAuthSchemes": [
63775
"OAUTH2"
63776
],
63552
- "toolCount": 467,
63777
+ "toolCount": 473,
63778
"triggerCount": 20,
63554
- "version": "20260828_00",
63779
+ "version": "20260903_00",
63780
"tools": [
63781
{
63782
"slug": "GOOGLESUPER_ACL_DELETE",
64063
"name": "Create a new calendar",
64064
"description": "Creates a new secondary Google Calendar with the specified title and optional settings. Use this action when you need to create a new calendar for organizing events separately from the primary calendar. The authenticated user becomes the owner of the newly created calendar. Optional parameters include description, location, and timezone."
64065
},
64066
+ {
64067
+ "slug": "GOOGLESUPER_CREATE_CALLOUT_ASSET",
64068
+ "name": "Create Callout Asset",
64069
+ "description": "Create an immutable account asset containing a validated callout. Associate the returned resource using Mutate Customer Assets with field_type CALLOUT. Cleanup removes that association; Google does not allow deleting the asset."
64070
+ },
64071
{
64072
"slug": "GOOGLESUPER_CREATE_CHART",
64073
"name": "Create Chart in Google Sheets",
64718
"name": "Get contacts",
64719
"description": "Fetches contacts (connections) for the authenticated Google account, allowing selection of specific data fields and pagination. Only covers saved contacts and 'Other Contacts'; email-header-only senders are out of scope. Contact records may have sparse data — handle missing fields gracefully. People API shares a per-user QPS quota; HTTP 429 requires exponential backoff (1s, 2s, 4s)."
64720
},
64721
+ {
64722
+ "slug": "GOOGLESUPER_GET_CONVERSION_ACTION_TAG_SNIPPETS",
64723
+ "name": "Get Conversion Action Tag Snippets",
64724
+ "description": "Retrieve provider-generated website or call conversion tag snippets after creating a conversion action. Markup is returned exactly as Google provides it."
64725
+ },
64726
{
64727
"slug": "GOOGLESUPER_GET_CURRENT_DATE_TIME",
64728
"name": "Get current date and time",
64913
"name": "Get Revision",
64914
"description": "Tool to get a specific revision's metadata (name, modifiedTime, keepForever, etc.) by revision ID. Returns metadata only — not file content. Use a separate download tool to retrieve file content or restore a revision."
64915
},
64916
+ {
64917
+ "slug": "GOOGLESUPER_GET_RMF_REPORT",
64918
+ "name": "Get Required Google Ads Report",
64919
+ "description": "Run a prominent, bounded Google Ads report template for Customer, Campaign, Ad, Keyword, Search Term, Dynamic Search Ads Search Term, or Bidding Strategy. Official required columns are always selected; dates default to LAST_30_DAYS."
64920
+ },
64921
{
64922
"slug": "GOOGLESUPER_GET_ROUTE",
64923
"name": "Get Route",
65061
{
65062
"slug": "GOOGLESUPER_LIST_ACCESSIBLE_CUSTOMERS",
65063
"name": "List Accessible Customers",
64824
- "description": "List Google Ads customer resource names directly accessible to the authenticated user. Use this to discover available customer IDs or populate an account picker. For MCC child account names, status, and direct hierarchy, use List Sub Accounts."
65064
+ "description": "List Google Ads customer resource names directly accessible to the authenticated OAuth user. Google determines the complete result from the OAuth credentials and ignores customer_id and login-customer-id; this action does not filter the response. For MCC child account names, status, and direct hierarchy, use List Sub Accounts."
65065
},
65066
{
65067
"slug": "GOOGLESUPER_LIST_ACCESS_PROPOSALS",
65511
{
65512
"slug": "GOOGLESUPER_MUTATE_ASSETS",
65513
"name": "Mutate Assets",
65274
- "description": "Create or update Google Ads assets such as sitelinks, callouts, structured snippets, text assets, lead forms, promotions, calls, price assets, and media assets. Google Ads AssetService does not expose remove via mutate."
65514
+ "description": "Create or update supported Google Ads assets such as sitelinks, structured snippets, text assets, lead forms, promotions, calls, price assets, and media assets. Use Create Callout Asset for validated immutable callouts. Google Ads does not allow removing assets; cleanup removes their resource associations."
65515
},
65516
{
65517
"slug": "GOOGLESUPER_MUTATE_BIDDING_STRATEGIES",
65518
"name": "Mutate Bidding Strategies",
65279
- "description": "Create, update, or remove portfolio bidding strategies such as Target CPA, Target ROAS, Target Spend, Maximize Conversions, Maximize Conversion Value, Target Impression Share, and Enhanced CPC."
65519
+ "description": "Create, update, or remove portfolio bidding strategies such as Target CPA, Target ROAS, Target Spend, Maximize Conversions, Maximize Conversion Value, and Target Impression Share."
65520
},
65521
{
65522
"slug": "GOOGLESUPER_MUTATE_CAMPAIGN_ASSETS",
65543
"name": "Mutate Campaigns",
65544
"description": "Create, update, or remove Google Ads campaigns in batch. Supports multiple operations (create, update, remove) in a single request. Use when managing campaign lifecycle, applying bulk changes, or automating campaign management workflows. This action is irreversible for remove operations — deleted campaigns cannot be recovered. Plan accordingly and consider using validate_only=true to test changes before applying them."
65545
},
65546
+ {
65547
+ "slug": "GOOGLESUPER_MUTATE_CAMPAIGNS_V2",
65548
+ "name": "Mutate Campaigns V2",
65549
+ "description": "Create, update, or remove Google Ads campaigns in batch. Supports multiple operations (create, update, remove) in a single request. Use when managing campaign lifecycle, applying bulk changes, or automating campaign management workflows. This action is irreversible for remove operations — deleted campaigns cannot be recovered. Plan accordingly and consider using validate_only=true to test changes before applying them."
65550
+ },
65551
{
65552
"slug": "GOOGLESUPER_MUTATE_CONDITIONAL_FORMAT_RULES",
65553
"name": "Mutate conditional format rules",
65558
"name": "Mutate Conversion Actions",
65559
"description": "Create, update, or remove Google Ads conversion actions for conversion tracking configuration. This manages Google Ads conversion action resources; installing website/app tags remains outside this action."
65560
},
65561
+ {
65562
+ "slug": "GOOGLESUPER_MUTATE_CUSTOMER_ASSETS",
65563
+ "name": "Mutate Customer Assets",
65564
+ "description": "Create or remove customer-level asset associations. Removal irreversibly removes the current association; recreate it to restore the link. Use this after creating assets to attach callouts, sitelinks, snippets, and other asset types across a Google Ads customer account."
65565
+ },
65566
{
65567
"slug": "GOOGLESUPER_MUTATE_LABELS",
65568
"name": "Mutate Labels",
65569
"description": "Create, update, or remove Google Ads labels. Pair this with campaign label mutations to organize campaigns and support filtering."
65570
},
65571
+ {
65572
+ "slug": "GOOGLESUPER_MUTATE_PORTFOLIO_BIDDING_STRATEGIES",
65573
+ "name": "Mutate Portfolio Bidding Strategies",
65574
+ "description": "Create, edit, or remove typed Target CPA and Target ROAS portfolio strategies. Attach with Mutate Campaigns, read with Get Required Google Ads Report, and transition all campaigns before removal. Budget alignment is not exposed because Google requires the bidding strategy and campaign budget to be changed atomically with GoogleAdsService.Mutate, while this action uses the resource-specific mutate endpoint. currency_code can be set on create only for manager-account strategies."
65575
+ },
65576
{
65577
"slug": "GOOGLESUPER_NEARBY_SEARCH",
65578
"name": "Nearby search",
65766
{
65767
"slug": "GOOGLESUPER_SEARCH_STREAM_GAQL",
65768
"name": "Search Stream GAQL",
65514
- "description": "Execute a Google Ads Query Language (GAQL) query and stream all results in a single response. This method is more efficient than paginated search for bulk data retrieval of campaigns, ad groups, and performance metrics (clicks, impressions, cost). Use this action when you need the entire result set without pagination. Results are returned as a single response containing all matching rows."
65769
+ "description": "Execute a Google Ads Query Language (GAQL) query and aggregate every streamed response batch in order. For very large reports, select only needed fields and use WHERE and LIMIT because action responses are returned inline and are not automatically offloaded."
65770
},
65771
{
65772
"slug": "GOOGLESUPER_SEND_DRAFT",
66666
],
66667
"toolCount": 16,
66668
"triggerCount": 0,
66414
- "version": "20260615_00",
66669
+ "version": "20260908_00",
66670
"tools": [
66671
{
66672
"slug": "TYPEFULLY_CREATE_DRAFT",
67392
],
67393
"toolCount": 105,
67394
"triggerCount": 11,
67140
- "version": "20260826_00",
67395
+ "version": "20260903_00",
67396
"tools": [
67397
{
67398
"slug": "ZOOM_ADD_A_MEETING_REGISTRANT",
69520
"composioManagedAuthSchemes": [
69521
"OAUTH2"
69522
],
69268
- "toolCount": 22,
69523
+ "toolCount": 28,
69524
"triggerCount": 0,
69270
- "version": "20260721_00",
69525
+ "version": "20260902_00",
69526
"tools": [
69527
{
69528
"slug": "GOOGLEADS_ADD_OR_REMOVE_TO_CUSTOMER_LIST",
69529
"name": "Add or remove to customer list",
69530
"description": "Adds or removes contacts from a Google Ads customer list (UserList/audience/remarketing list), not a Google Ads customer account. Note: It takes 6 to 12 hours for changes to be reflected in the customer list. Email addresses must comply with Google Ads policies and applicable privacy/consent laws."
69531
},
69532
+ {
69533
+ "slug": "GOOGLEADS_CREATE_CALLOUT_ASSET",
69534
+ "name": "Create Callout Asset",
69535
+ "description": "Create an immutable account asset containing a validated callout. Associate the returned resource using Mutate Customer Assets with field_type CALLOUT. Cleanup removes that association; Google does not allow deleting the asset."
69536
+ },
69537
{
69538
"slug": "GOOGLEADS_CREATE_CUSTOMER_LIST",
69539
"name": "Create customer list",
69549
"name": "Get campaign by name",
69550
"description": "Queries Google Ads via SQL to retrieve a campaign by its exact name. Requires an active Google Ads connection with valid customer_id and appropriate OAuth scopes."
69551
},
69552
+ {
69553
+ "slug": "GOOGLEADS_GET_CONVERSION_ACTION_TAG_SNIPPETS",
69554
+ "name": "Get Conversion Action Tag Snippets",
69555
+ "description": "Retrieve provider-generated website or call conversion tag snippets after creating a conversion action. Markup is returned exactly as Google provides it."
69556
+ },
69557
{
69558
"slug": "GOOGLEADS_GET_CUSTOMER_LISTS",
69559
"name": "Get customer lists",
69560
"description": "GetCustomerLists Tool lists all customer lists (audience/remarketing lists) in Google Ads. These are user segments for targeting, not Google Ads accounts — list IDs are distinct from account IDs. When multiple lists share similar names, review all returned results before selecting one for downstream operations."
69561
},
69562
+ {
69563
+ "slug": "GOOGLEADS_GET_RMF_REPORT",
69564
+ "name": "Get Required Google Ads Report",
69565
+ "description": "Run a prominent, bounded Google Ads report template for Customer, Campaign, Ad, Keyword, Search Term, Dynamic Search Ads Search Term, or Bidding Strategy. Official required columns are always selected; dates default to LAST_30_DAYS."
69566
+ },
69567
{
69568
"slug": "GOOGLEADS_LIST_ACCESSIBLE_CUSTOMERS",
69569
"name": "List Accessible Customers",
69300
- "description": "List Google Ads customer resource names directly accessible to the authenticated user. Use this to discover available customer IDs or populate an account picker. For MCC child account names, status, and direct hierarchy, use List Sub Accounts."
69570
+ "description": "List Google Ads customer resource names directly accessible to the authenticated OAuth user. Google determines the complete result from the OAuth credentials and ignores customer_id and login-customer-id; this action does not filter the response. For MCC child account names, status, and direct hierarchy, use List Sub Accounts."
69571
},
69572
{
69573
"slug": "GOOGLEADS_LIST_SUB_ACCOUNTS",
69602
{
69603
"slug": "GOOGLEADS_MUTATE_ASSETS",
69604
"name": "Mutate Assets",
69335
- "description": "Create or update Google Ads assets such as sitelinks, callouts, structured snippets, text assets, lead forms, promotions, calls, price assets, and media assets. Google Ads AssetService does not expose remove via mutate."
69605
+ "description": "Create or update supported Google Ads assets such as sitelinks, structured snippets, text assets, lead forms, promotions, calls, price assets, and media assets. Use Create Callout Asset for validated immutable callouts. Google Ads does not allow removing assets; cleanup removes their resource associations."
69606
},
69607
{
69608
"slug": "GOOGLEADS_MUTATE_BIDDING_STRATEGIES",
69609
"name": "Mutate Bidding Strategies",
69340
- "description": "Create, update, or remove portfolio bidding strategies such as Target CPA, Target ROAS, Target Spend, Maximize Conversions, Maximize Conversion Value, Target Impression Share, and Enhanced CPC."
69610
+ "description": "Create, update, or remove portfolio bidding strategies such as Target CPA, Target ROAS, Target Spend, Maximize Conversions, Maximize Conversion Value, and Target Impression Share."
69611
},
69612
{
69613
"slug": "GOOGLEADS_MUTATE_CAMPAIGN_ASSETS",
69634
"name": "Mutate Campaigns",
69635
"description": "Create, update, or remove Google Ads campaigns in batch. Supports multiple operations (create, update, remove) in a single request. Use when managing campaign lifecycle, applying bulk changes, or automating campaign management workflows. This action is irreversible for remove operations — deleted campaigns cannot be recovered. Plan accordingly and consider using validate_only=true to test changes before applying them."
69636
},
69637
+ {
69638
+ "slug": "GOOGLEADS_MUTATE_CAMPAIGNS_V2",
69639
+ "name": "Mutate Campaigns V2",
69640
+ "description": "Create, update, or remove Google Ads campaigns in batch. Supports multiple operations (create, update, remove) in a single request. Use when managing campaign lifecycle, applying bulk changes, or automating campaign management workflows. This action is irreversible for remove operations — deleted campaigns cannot be recovered. Plan accordingly and consider using validate_only=true to test changes before applying them."
69641
+ },
69642
{
69643
"slug": "GOOGLEADS_MUTATE_CONVERSION_ACTIONS",
69644
"name": "Mutate Conversion Actions",
69645
"description": "Create, update, or remove Google Ads conversion actions for conversion tracking configuration. This manages Google Ads conversion action resources; installing website/app tags remains outside this action."
69646
},
69647
+ {
69648
+ "slug": "GOOGLEADS_MUTATE_CUSTOMER_ASSETS",
69649
+ "name": "Mutate Customer Assets",
69650
+ "description": "Create or remove customer-level asset associations. Removal irreversibly removes the current association; recreate it to restore the link. Use this after creating assets to attach callouts, sitelinks, snippets, and other asset types across a Google Ads customer account."
69651
+ },
69652
{
69653
"slug": "GOOGLEADS_MUTATE_LABELS",
69654
"name": "Mutate Labels",
69655
"description": "Create, update, or remove Google Ads labels. Pair this with campaign label mutations to organize campaigns and support filtering."
69656
},
69657
+ {
69658
+ "slug": "GOOGLEADS_MUTATE_PORTFOLIO_BIDDING_STRATEGIES",
69659
+ "name": "Mutate Portfolio Bidding Strategies",
69660
+ "description": "Create, edit, or remove typed Target CPA and Target ROAS portfolio strategies. Attach with Mutate Campaigns, read with Get Required Google Ads Report, and transition all campaigns before removal. Budget alignment is not exposed because Google requires the bidding strategy and campaign budget to be changed atomically with GoogleAdsService.Mutate, while this action uses the resource-specific mutate endpoint. currency_code can be set on create only for manager-account strategies."
69661
+ },
69662
{
69663
"slug": "GOOGLEADS_SEARCH_STREAM_GAQL",
69664
"name": "Search Stream GAQL",
69380
- "description": "Execute a Google Ads Query Language (GAQL) query and stream all results in a single response. This method is more efficient than paginated search for bulk data retrieval of campaigns, ad groups, and performance metrics (clicks, impressions, cost). Use this action when you need the entire result set without pagination. Results are returned as a single response containing all matching rows."
69665
+ "description": "Execute a Google Ads Query Language (GAQL) query and aggregate every streamed response batch in order. For very large reports, select only needed fields and use WHERE and LIMIT because action responses are returned inline and are not automatically offloaded."
69666
}
69667
],
69668
"triggers": [],
69749
],
69750
"toolCount": 368,
69751
"triggerCount": 0,
69467
- "version": "20260730_00",
69752
+ "version": "20260903_00",
69753
"tools": [
69754
{
69755
"slug": "PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGER",
72960
],
72961
"toolCount": 98,
72962
"triggerCount": 0,
72678
- "version": "20260831_00",
72963
+ "version": "20260908_00",
72964
"tools": [
72965
{
72966
"slug": "SHARE_POINT_ADD_ATTACHMENT_TO_LIST_ITEM",
79972
],
79973
"toolCount": 58,
79974
"triggerCount": 0,
79690
- "version": "20260819_00",
79975
+ "version": "20260903_00",
79976
"tools": [
79977
{
79978
"slug": "ZOHO_INVENTORY_ADD_CREDIT_NOTE_COMMENT",
80347
"composioManagedAuthSchemes": [
80348
"OAUTH2"
80349
],
80065
- "toolCount": 43,
80350
+ "toolCount": 44,
80351
"triggerCount": 0,
80067
- "version": "20260721_00",
80352
+ "version": "20260902_00",
80353
"tools": [
80354
{
80355
"slug": "FACEBOOK_ASSIGN_PAGE_TASK",
80361
"name": "Create Comment",
80362
"description": "Creates a comment on a Facebook post or replies to an existing comment."
80363
},
80364
+ {
80365
+ "slug": "FACEBOOK_CREATE_MULTI_PHOTO_POST",
80366
+ "name": "Create Multi-Photo Post",
80367
+ "description": "Publish one Facebook Page feed post containing one or more photos from public URLs. The action first uploads every photo with published=false, then creates one /feed post with those photo IDs as attached_media. If any upload fails, the feed post is not created; earlier uploads can remain unpublished on Facebook temporarily. This action publishes immediately and does not add photos to an existing album."
80368
+ },
80369
{
80370
"slug": "FACEBOOK_CREATE_PHOTO_ALBUM",
80371
"name": "Create Photo Album",
80564
{
80565
"slug": "FACEBOOK_UPLOAD_PHOTOS_BATCH",
80566
"name": "Upload Photos Batch",
80277
- "description": "Uploads multiple photo files in batch to a Facebook Page or Album. Uses Facebook's batch API for efficient multi-photo upload. Maximum 50 photos per batch."
80567
+ "description": "Uploads up to 50 independent photos to a Facebook Page or Album using the Graph batch API. With published=true, each page photo may create its own feed story; this action does not create one post containing all photos. Use FACEBOOK_CREATE_MULTI_PHOTO_POST for one multi-photo feed post."
80568
},
80569
{
80570
"slug": "FACEBOOK_UPLOAD_VIDEO",
81208
],
81209
"toolCount": 48,
81210
"triggerCount": 0,
80921
- "version": "20260826_00",
81211
+ "version": "20260903_00",
81212
"tools": [
81213
{
81214
"slug": "CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST",
81215
"name": "Access user specific brand templates list",
80926
- "description": "Lists brand templates available to the user (Canva Enterprise only). This endpoint retrieves all brand templates the user has access to. Brand templates are pre-designed layouts with variable data fields that can be populated programmatically using the autofill API. Returns template metadata including IDs, names, and dataset schemas."
81216
+ "description": "Lists brand templates available to users on plans with brand-template access, such as Canva Pro, Canva Teams, or Canva Enterprise. Returns one page of template metadata, including IDs and titles. Follow the response's continuation token to retrieve additional pages. Dataset definitions are available from CANVA_RETRIEVE_BRAND_TEMPLATE_DATASET_DEFINITION."
81217
},
81218
{
81219
"slug": "CANVA_CREATE_ASSET_UPLOAD_JOB",
81220
"name": "Create Asset Upload Job",
80931
- "description": "Uploads an asset file to the user's Canva content library. This endpoint initiates an asynchronous upload job for images, videos, audio files, PDFs, or fonts. Returns a job ID to track the upload progress. Once complete, the asset can be used in designs, referenced by its asset ID, and managed through other asset endpoints. IMPORTANT: This is an async operation. Use CANVA_FETCH_ASSET_UPLOAD_JOB_STATUS to poll the job status until it reaches 'success' or 'failed' status."
81221
+ "description": "Uploads an asset file to the user's Canva content library. This endpoint initiates an asynchronous upload job for images or videos. Returns a job ID to track the upload progress. Once complete, the asset can be used in designs, referenced by its asset ID, and managed through other asset endpoints. IMPORTANT: This is an async operation. Use CANVA_FETCH_ASSET_UPLOAD_JOB_STATUS to poll the job status until it reaches 'success' or 'failed' status."
81222
},
81223
{
81224
"slug": "CANVA_CREATE_CANVA_DESIGN_EXPORT_JOB",
81228
{
81229
"slug": "CANVA_CREATE_CANVA_DESIGN_WITH_OPTIONAL_ASSET",
81230
"name": "Create canva design with optional asset (Deprecated)",
80941
- "description": "DEPRECATED: Use CANVA_POST_DESIGNS instead. Creates a new Canva design with specified dimensions or from an asset. This endpoint creates a design using either a preset type (doc, presentation, whiteboard), custom dimensions, or by importing an image asset. Returns the design ID, URLs for editing and viewing, owner info, and metadata. The design can be immediately accessed and edited."
81231
+ "description": "DEPRECATED: Use CANVA_POST_DESIGNS instead. Creates a new Canva design with specified dimensions or from an asset. This endpoint creates a design using either a preset type (doc, email, presentation, whiteboard), custom dimensions, or by importing an image asset. Returns the design ID, URLs for editing and viewing, owner info, and metadata. The design can be immediately accessed and edited."
81232
},
81233
{
81234
"slug": "CANVA_CREATE_COMMENT_REPLY_IN_DESIGN",
80945
- "name": "Create comment reply in design",
80946
- "description": "This preview API allows replying to comments within a design on Canva, with a limit of 100 replies per comment. Users should note potential unannounced changes, and that preview APIs are not eligible for public integrations."
81235
+ "name": "Create comment reply in design (Deprecated)",
81236
+ "description": "DEPRECATED: Use CANVA_POST_DESIGNS_DESIGNID_COMMENTS_THREADID_REPLIES instead. This preview API allows replying to comments within a design on Canva, with a limit of 100 replies per comment. Users should note potential unannounced changes, and that preview APIs are not eligible for public integrations."
81237
},
81238
{
81239
"slug": "CANVA_CREATE_DESIGN_COMMENT_IN_PREVIEW_API",
80950
- "name": "Create design comment in preview api",
80951
- "description": "Creates a new comment thread on a Canva design. This preview API allows adding text comments to designs for collaboration and feedback. Returns the created comment with ID, author info, and timestamp. Comments can be replied to using the comment reply endpoint."
81240
+ "name": "Create design comment in preview api (Deprecated)",
81241
+ "description": "DEPRECATED: Use CANVA_POST_DESIGNS_DESIGNID_COMMENTS instead. Creates a new comment thread on a Canva design using Canva's deprecated Create comment API. This preview API allows adding text comments to designs for collaboration and feedback. Returns the created comment with ID, author info, and timestamp. Comments can be replied to using the comment reply endpoint."
81242
},
81243
{
81244
"slug": "CANVA_CREATE_DESIGN_IMPORT_JOB",
81268
{
81269
"slug": "CANVA_FETCH_ASSET_UPLOAD_JOB_STATUS",
81270
"name": "Fetch asset upload job status",
80981
- "description": "Polls for asset upload job completion status. Use this after CANVA_CREATE_ASSET_UPLOAD_JOB to check the upload progress. Repeatedly call this endpoint until a 'success' or 'failed' status is received to get the final asset ID and metadata. IMPORTANT: This tool is ONLY for direct file upload jobs (CANVA_CREATE_ASSET_UPLOAD_JOB). Do NOT use this for URL import jobs created by CANVA_CREATE_URL_ASSET_UPLOAD_JOB - those use a different API endpoint. Use CANVA_GET_URL_ASSET_UPLOADS_JOBID to poll URL import job status."
81271
+ "description": "Polls for asset upload job completion status. Use this after CANVA_CREATE_ASSET_UPLOAD_JOB to check the upload progress. Repeatedly call this endpoint until a 'success' or 'failed' status is received to get the final asset ID and metadata. IMPORTANT: This tool is ONLY for direct file upload jobs (CANVA_CREATE_ASSET_UPLOAD_JOB). Do NOT use this for URL import jobs created by CANVA_CREATE_URL_ASSET_UPLOAD_JOB - those use a different API endpoint. Use CANVA_GET_URL_ASSET_UPLOADS_JOBID to poll URL asset upload job status."
81272
},
81273
{
81274
"slug": "CANVA_FETCH_CANVA_CONNECT_SIGNING_PUBLIC_KEYS",
81278
{
81279
"slug": "CANVA_FETCH_CURRENT_USER_DETAILS",
81280
"name": "Fetch current user details",
80991
- "description": "Returns the User ID, Team ID, and display name of the user account associated with the provided access token."
81281
+ "description": "Returns the User ID and Team ID associated with the provided access token. Use CANVA_RETRIEVE_USER_PROFILE_DATA to retrieve the user's display name."
81282
},
81283
{
81284
"slug": "CANVA_FETCH_DESIGN_METADATA_AND_ACCESS_INFORMATION",
81288
{
81289
"slug": "CANVA_GET_DESIGN_COMMENT_REPLIES",
81290
"name": "Get design comment thread replies",
81001
- "description": "Retrieves a list of replies for a comment or suggestion thread on a design. Use when you need to view all replies in a specific thread."
81291
+ "description": "Retrieves a page of replies for a comment or suggestion thread on a design. Returns up to limit replies (default 50, maximum 100); follow the continuation token to retrieve the rest. This is a preview API. Public integrations that use it cannot pass Canva's review process."
81292
},
81293
{
81294
"slug": "CANVA_GET_DESIGN_COMMENT_REPLY",
81295
"name": "Get specific design comment reply",
81006
- "description": "Retrieves a specific reply to a comment or suggestion thread on a design. Use when you need to view details of a particular reply."
81296
+ "description": "Retrieves a specific reply to a comment or suggestion thread on a design. Use when you need to view details of a particular reply. This is a preview API. Public integrations that use it cannot pass Canva's review process."
81297
},
81298
{
81299
"slug": "CANVA_GET_DESIGN_EXPORT_JOB_RESULT",
81300
"name": "Get design export job result",
81011
- "description": "Polls for design export job completion status. Use this after CANVA_CREATE_CANVA_DESIGN_EXPORT_JOB to check the export progress. Call this endpoint repeatedly until the job is complete to receive download links for the exported design pages. Download URLs expire after 30 days."
81301
+ "description": "Polls for design export job completion status. Use this after CANVA_CREATE_CANVA_DESIGN_EXPORT_JOB to check the export progress. Call this endpoint repeatedly until the job is complete to receive download links for the exported design pages. Download URLs expire after 24 hours."
81302
},
81303
{
81304
"slug": "CANVA_GET_DESIGNS_DESIGNID_COMMENTS_THREADID",
81305
"name": "Get designs designid comments threadid",
81016
- "description": "Retrieves metadata for a comment or suggestion thread on a design. Use when you need to get details about a specific thread including content, author, timestamps, and status."
81306
+ "description": "Retrieves metadata for a comment or suggestion thread on a design. Use when you need to get details about a specific thread including content, author, timestamps, and status. This is a preview API. Public integrations that use it cannot pass Canva's review process."
81307
},
81308
{
81309
"slug": "CANVA_GET_DESIGNS_DESIGNID_EXPORT_FORMATS",
81310
"name": "Get design export formats",
81021
- "description": "Lists available file formats for exporting a design. Use this to check which export formats (PDF, JPG, PNG, SVG, PPTX, GIF, MP4) are supported for a specific design."
81311
+ "description": "Lists available file formats for exporting a design. Use this to check which export formats (PDF, JPG, PNG, SVG, PPTX, GIF, MP4, HTML bundle, standalone HTML, and CSV) are supported for a specific design."
81312
},
81313
{
81314
"slug": "CANVA_GET_URL_ASSET_UPLOADS_JOBID",
81328
{
81329
"slug": "CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB",
81330
"name": "Initiate canva design autofill job",
81041
- "description": "Upcoming brand template ID updates require migration within 6 months. Canva Enterprise users can auto-fill designs using various data types, including experimental chart data. Monitor jobs with specific API."
81331
+ "description": "Creates an asynchronous autofill job from a brand template or existing design, or updates an existing design in place. Canva Enterprise users are eligible; paid-plan users can use a limited development trial. Poll the returned job ID with CANVA_RETRIEVE_DESIGN_AUTOFILL_JOB_STATUS."
81332
},
81333
{
81334
"slug": "CANVA_LIST_DESIGN_PAGES_WITH_PAGINATION",
81338
{
81339
"slug": "CANVA_LIST_FOLDER_ITEMS_BY_TYPE_WITH_SORTING",
81340
"name": "List folder items by type with sorting",
81051
- "description": "Lists the items in a folder, including each item's `type`. Folders can contain: - Other folders. - Designs, such as Instagram posts, Presentations, and Documents ([Canva Docs](https://www.canva.com/create/documents/)). - Image assets."
81341
+ "description": "Lists folder items, including folders, designs, image assets, and brand templates. Brand templates are returned only when explicitly requested in `item_types` and the user's plan supports them. Video assets are currently not returned."
81342
},
81343
{
81344
"slug": "CANVA_LIST_USER_DESIGNS",
81353
{
81354
"slug": "CANVA_POST_DESIGNS",
81355
"name": "Create new Canva design",
81066
- "description": "Creates a new Canva design with preset type or custom dimensions. Use when creating new designs for docs, presentations, whiteboards, or with specific pixel dimensions. Optionally insert an image asset into the design. Returns design ID, edit/view URLs, and metadata."
81356
+ "description": "Creates a Canva design with a preset type, custom dimensions, an existing design, or a brand template. Copying designs and using brand templates are Canva preview features. Optionally insert an image asset when using a preset or custom type. Returns design ID, edit/view URLs, and metadata."
81357
},
81358
{
81359
"slug": "CANVA_POST_DESIGNS_DESIGNID_COMMENTS",
81360
"name": "Post designs designid comments",
81071
- "description": "Creates a comment thread on a Canva design. Use when you need to add feedback or collaboration comments to a specific design. Rate limited to 100 requests per minute per user."
81361
+ "description": "Creates a comment thread on a Canva design. Use when you need to add feedback or collaboration comments to a specific design. Rate limited to 100 requests per minute per user. This is a preview API. Public integrations that use it cannot pass Canva's review process."
81362
},
81363
{
81364
"slug": "CANVA_POST_DESIGNS_DESIGNID_COMMENTS_THREADID_REPLIES",
81365
"name": "Create reply to comment thread",
81076
- "description": "Tool to create a reply to a comment or suggestion thread on a Canva design. Use when you need to respond to existing comments or suggestions. Maximum 100 replies per thread allowed."
81366
+ "description": "Tool to create a reply to a comment or suggestion thread on a Canva design. Use when you need to respond to existing comments or suggestions. Maximum 100 replies per thread allowed. This is a preview API. Public integrations that use it cannot pass Canva's review process."
81367
},
81368
{
81369
"slug": "CANVA_POST_EXPORTS",
81370
"name": "Start design export job",
81081
- "description": "Starts a new asynchronous job to export a Canva design file. Use when exporting designs to various formats (PDF, JPG, PNG, GIF, PPTX, MP4). Returns a job ID that can be used to poll for completion status and download URLs. IMPORTANT: Format compatibility varies by design type. Before exporting, use the CANVA_GET_DESIGNS_DESIGNID_EXPORT_FORMATS action to check which formats are supported for the specific design. Attempting to export in an unsupported format will result in a 400 error (e.g., 'png export not supported for this design type')."
81371
+ "description": "Starts a new asynchronous job to export a Canva design file. Use when exporting designs to various formats (PDF, JPG, PNG, GIF, PPTX, MP4, CSV, and HTML). Returns a job ID that can be used to poll for completion status and download URLs. IMPORTANT: Format compatibility varies by design type. Before exporting, use the CANVA_GET_DESIGNS_DESIGNID_EXPORT_FORMATS action to check which formats are supported for the specific design. Attempting to export in an unsupported format will result in a 400 error (e.g., 'png export not supported for this design type')."
81372
},
81373
{
81374
"slug": "CANVA_POST_FOLDERS",
81398
{
81399
"slug": "CANVA_RETRIEVE_BRAND_TEMPLATE_DATASET_DEFINITION",
81400
"name": "Retrieve brand template dataset definition",
81111
- "description": "Canva's brand template IDs will change later this year, including a 6-month integration migration. API access requires Enterprise membership, providing autofill for images, text, and charts, although chart data could change during preview."
81401
+ "description": "Gets the dataset definition for a brand template. Available to users on plans with brand-template access, such as Canva Pro, Canva Teams, or Canva Enterprise. Data fields can contain images, text, and charts; chart data is a preview feature."
81402
},
81403
{
81404
"slug": "CANVA_RETRIEVE_CANVA_ENTERPRISE_BRAND_TEMPLATE_METADATA",
81115
- "name": "Retrieve canva enterprise brand template metadata",
81116
- "description": "Upcoming update will change brand template IDs; integrations must migrate within 6 months. API use requires Canva Enterprise membership."
81405
+ "name": "Retrieve brand template metadata",
81406
+ "description": "Retrieves metadata for a brand template. Available to users on plans with brand-template access, such as Canva Pro, Canva Teams, or Canva Enterprise."
81407
},
81408
{
81409
"slug": "CANVA_RETRIEVE_DESIGN_AUTOFILL_JOB_STATUS",
81410
"name": "Retrieve design autofill job status",
81121
- "description": "API users with Canva Enterprise membership can retrieve design autofill job results, potentially requiring multiple requests until a `success` or `failed` status is received."
81411
+ "description": "Retrieves a design autofill job result. Canva Enterprise users are eligible, while paid-plan users can use a limited development trial. Poll until the status is `success` or `failed`."
81412
},
81413
{
81414
"slug": "CANVA_RETRIEVE_DESIGN_IMPORT_JOB_STATUS",
81433
{
81434
"slug": "CANVA_REVOKE_OAUTH_TOKENS",
81435
"name": "Revoke oauth tokens",
81146
- "description": "Revoke a refresh token to end its lineage and user consent, requiring re-authentication. Authenticate using either basic access with Base64-encoded credentials or body parameters with client ID and secret."
81436
+ "description": "Revoke an access token or refresh token. Revoking a refresh token also revokes its lineage and user consent, requiring re-authentication. Authenticate using either basic access with Base64-encoded credentials or body parameters with client ID and secret."
81437
},
81438
{
81439
"slug": "CANVA_UPDATE_ASSET_S_NAME_AND_TAGS_BY_ID",
81491
"type": "string",
81492
"description": "Scopes to request from the user, comma separated",
81493
"required": false,
81204
- "default": "app:read,app:write,asset:read,asset:write,brandtemplate:content:read,brandtemplate:meta:read,comment:read,comment:write,design:content:read,design:content:write,design:meta:read,design:permission:read,design:permission:write,folder:read,folder:write,folder:permission:read,folder:permission:write,profile:read"
81494
+ "default": "asset:read,asset:write,brandtemplate:content:read,brandtemplate:meta:read,comment:read,comment:write,design:content:read,design:content:write,design:meta:read,folder:read,folder:write,folder:permission:write,profile:read"
81495
}
81496
]
81497
},
82606
],
82607
"toolCount": 41,
82608
"triggerCount": 0,
82319
- "version": "20260721_00",
82609
+ "version": "20260902_00",
82610
"tools": [
82611
{
82612
"slug": "TIMELY_CREATE_CLIENT",
109652
],
109653
"toolCount": 137,
109654
"triggerCount": 0,
109365
- "version": "20260819_00",
109655
+ "version": "20260903_00",
109656
"tools": [
109657
{
109658
"slug": "ZOHO_INVOICE_ADD_CREDITNOTE_TO_INVOICES",
110415
],
110416
"toolCount": 121,
110417
"triggerCount": 0,
110128
- "version": "20260721_00",
110418
+ "version": "20260903_00",
110419
"tools": [
110420
{
110421
"slug": "STACK_EXCHANGE_CREATE_FILTER",
111327
]
111328
},
111329
{
111040
- "slug": "datadog",
111041
- "name": "Datadog",
111042
- "logo": "https://logos.composio.dev/api/datadog",
111043
- "description": "Datadog offers monitoring, observability, and security for cloud-scale applications, unifying metrics, logs, and traces to help teams detect issues and optimize performance",
111044
- "category": "server monitoring",
111330
+ "slug": "twitch",
111331
+ "name": "Twitch",
111332
+ "logo": "https://logos.composio.dev/api/twitch",
111333
+ "description": "Twitch is a live streaming platform popular with gamers, creators, and communities, offering real-time interaction and monetization through subscriptions and donations",
111334
+ "category": "video & audio",
111335
"authSchemes": [
111336
"OAUTH2",
111047
- "API_KEY",
111048
- "BEARER_TOKEN"
111337
+ "S2S_OAUTH2",
111338
+ "NO_AUTH"
111339
],
111050
- "toolCount": 65,
111340
+ "composioManagedAuthSchemes": [
111341
+ "OAUTH2"
111342
+ ],
111343
+ "toolCount": 149,
111344
"triggerCount": 0,
111052
- "version": "20260826_00",
111345
+ "version": "20260908_00",
111346
"tools": [
111347
{
111055
- "slug": "DATADOG_AGGREGATE_LOGS",
111056
- "name": "Aggregate logs",
111057
- "description": "Aggregate Datadog logs without downloading raw events. Use for counts, unique values, percentiles, numeric statistics, grouped breakdowns, and values over time. Use DATADOG_SEARCH_LOGS only when individual log messages are required."
111348
+ "slug": "TWITCH_ADD_BLOCKED_TERM",
111349
+ "name": "Add Blocked Term",
111350
+ "description": "Adds a word or phrase to the broadcaster’s list of blocked terms."
111351
},
111352
{
111060
- "slug": "DATADOG_CREATE_DASHBOARD",
111061
- "name": "Create Dashboard",
111062
- "description": "Create a dashboard in Datadog. Dashboards provide customizable visualizations for monitoring your infrastructure, applications, and business metrics in a unified view."
111353
+ "slug": "TWITCH_ADD_CHANNEL_MODERATOR",
111354
+ "name": "Add Channel Moderator",
111355
+ "description": "Adds a moderator to the broadcaster’s chat room."
111356
},
111357
{
111065
- "slug": "DATADOG_CREATE_DOWNTIME",
111066
- "name": "Create downtime",
111067
- "description": "Creates a new downtime in Datadog to suppress alerts during maintenance windows or planned outages. Useful for preventing false alarms during deployments or maintenance."
111358
+ "slug": "TWITCH_ADD_CHANNEL_VIP",
111359
+ "name": "Add Channel VIP",
111360
+ "description": "Adds the specified user as a VIP in the broadcaster’s channel."
111361
},
111362
{
111070
- "slug": "DATADOG_CREATE_ESCALATION_POLICY",
111071
- "name": "Create On-Call escalation policy",
111072
- "description": "Creates a Datadog On-Call escalation policy."
111363
+ "slug": "TWITCH_ADD_SUSPICIOUS_STATUS_TO_CHAT_USER",
111364
+ "name": "Add Suspicious Status to Chat User",
111365
+ "description": "Adds a suspicious user status to a chatter on the broadcaster’s channel."
111366
},
111367
{
111075
- "slug": "DATADOG_CREATE_EVENT",
111076
- "name": "Create event",
111077
- "description": "Creates a new event in Datadog. Events are useful for tracking deployments, outages, configuration changes, and other important occurrences."
111368
+ "slug": "TWITCH_ASSIGN_GUEST_STAR_SLOT",
111369
+ "name": "Assign Guest Star Slot",
111370
+ "description": "BETA Allows a previously invited user to be assigned a slot within the active Guest Star session."
111371
},
111372
{
111080
- "slug": "DATADOG_CREATE_MONITOR",
111081
- "name": "Create monitor",
111082
- "description": "Creates a new Datadog monitor to track metrics, logs, or other data sources with configurable alerting thresholds and notifications."
111373
+ "slug": "TWITCH_BAN_USER",
111374
+ "name": "Ban User",
111375
+ "description": "Bans a user from participating in a broadcaster’s chat room or puts them in a timeout."
111376
},
111377
{
111085
- "slug": "DATADOG_CREATE_NOTIFICATION_CHANNEL",
111086
- "name": "Create On-Call notification channel",
111087
- "description": "Creates an On-Call notification channel for a Datadog user."
111378
+ "slug": "TWITCH_BLOCK_USER",
111379
+ "name": "Block User",
111380
+ "description": "Blocks the specified user from interacting with or having contact with the broadcaster."
111381
},
111382
{
111090
- "slug": "DATADOG_CREATE_NOTIFICATION_RULE",
111091
- "name": "Create On-Call notification rule",
111092
- "description": "Creates an On-Call notification rule for a Datadog user."
111383
+ "slug": "TWITCH_CANCEL_A_RAID",
111384
+ "name": "Cancel a raid",
111385
+ "description": "Cancel a pending raid."
111386
},
111387
{
111095
- "slug": "DATADOG_CREATE_SCHEDULE",
111096
- "name": "Create On-Call schedule",
111097
- "description": "Creates a Datadog On-Call schedule."
111388
+ "slug": "TWITCH_CHECK_AUTOMOD_STATUS",
111389
+ "name": "Check AutoMod Status",
111390
+ "description": "Checks whether AutoMod would flag the specified message for review."
111391
},
111392
{
111100
- "slug": "DATADOG_CREATE_SLO",
111101
- "name": "Create SLO",
111102
- "description": "Create a Service Level Objective (SLO) in Datadog. SLOs help you define and track reliability targets for your services, enabling data-driven decisions about service quality and reliability investments."
111393
+ "slug": "TWITCH_CHECK_USER_SUBSCRIPTION",
111394
+ "name": "Check User Subscription",
111395
+ "description": "Checks whether the user subscribes to the broadcaster’s channel."
111396
},
111397
{
111105
- "slug": "DATADOG_CREATE_SYNTHETIC_API_TEST",
111106
- "name": "Create Synthetic API Test",
111107
- "description": "Create a synthetic API test in Datadog. Creates a new synthetic API test that continuously monitors API endpoints from multiple locations worldwide. Useful for proactive monitoring of API uptime, performance, and functionality."
111398
+ "slug": "TWITCH_CREATE_CHANNEL_STREAM_SCHEDULE_SEGMENT",
111399
+ "name": "Create Channel Stream Schedule Segment",
111400
+ "description": "Adds a single or recurring broadcast to the broadcaster’s streaming schedule."
111401
},
111402
{
111110
- "slug": "DATADOG_CREATE_WEBHOOK",
111111
- "name": "Create Webhook",
111112
- "description": "Create a webhook in Datadog. Registers a named destination endpoint; each monitor must explicitly reference the webhook by name in its message or notification settings for alerts to be delivered."
111403
+ "slug": "TWITCH_CREATE_CLIP",
111404
+ "name": "Request Clip Creation",
111405
+ "description": "Starts Twitch's asynchronous clip-creation process for a live stream. A 202 response is acceptance, not completed creation. Use GET_CLIPS with the returned ID to verify; if it is still absent after 60 seconds, Twitch says to assume creation failed."
111406
},
111407
{
111115
- "slug": "DATADOG_DELETE_DASHBOARD",
111116
- "name": "Delete Dashboard",
111117
- "description": "Delete a dashboard in Datadog. Permanently removes a dashboard from your organization. This action cannot be undone. Use with caution."
111408
+ "slug": "TWITCH_CREATE_CLIP_FROM_VOD",
111409
+ "name": "Request Clip Creation From VOD",
111410
+ "description": "Starts Twitch's asynchronous clip-creation process from a VOD. A 202 response is acceptance, not completed creation. Use GET_CLIPS with the returned ID to verify completion."
111411
},
111412
{
111120
- "slug": "DATADOG_DELETE_ESCALATION_POLICY",
111121
- "name": "Delete On-Call escalation policy",
111122
- "description": "Deletes a Datadog On-Call escalation policy by ID. This action cannot be undone."
111413
+ "slug": "TWITCH_CREATE_CONDUITS",
111414
+ "name": "Create Conduits",
111415
+ "description": "Creates a new conduit."
111416
},
111417
{
111125
- "slug": "DATADOG_DELETE_MONITOR",
111126
- "name": "Delete monitor",
111127
- "description": "Deletes a Datadog monitor permanently. Use with caution as this action cannot be undone."
111418
+ "slug": "TWITCH_CREATE_CUSTOM_REWARDS",
111419
+ "name": "Create Custom Rewards",
111420
+ "description": "Creates a Custom Reward in the broadcaster’s channel."
111421
},
111422
{
111130
- "slug": "DATADOG_DELETE_NOTIFICATION_CHANNEL",
111131
- "name": "Delete On-Call notification channel",
111132
- "description": "Deletes an On-Call notification channel for a Datadog user. This action cannot be undone."
111423
+ "slug": "TWITCH_CREATE_EVENTSUB_SUBSCRIPTION",
111424
+ "name": "Create EventSub Subscription",
111425
+ "description": "Creates an EventSub subscription with a transport-specific body. This endpoint has no universal OAuth scope: WebSocket requires a user-token OAuth connection carrying the subscription type's scope; webhook and conduit require an app-token S2S OAuth connection whose client ID has any required prior user grant. Execution metadata does not expose token family, so select the matching connection before calling; Twitch rejects a mismatch with 401. Check the subscription-type documentation for its condition fields and scope."
111426
},
111427
{
111135
- "slug": "DATADOG_DELETE_NOTIFICATION_RULE",
111136
- "name": "Delete On-Call notification rule",
111137
- "description": "Deletes an On-Call notification rule for a Datadog user. This action cannot be undone."
111428
+ "slug": "TWITCH_CREATE_EXTENSION_SECRET",
111429
+ "name": "Create Extension Secret",
111430
+ "description": "Creates an Extension shared secret with a grace delay; Twitch returns both the prior overlapping secret and the new one. All secret content is redacted from tool output to prevent credential leakage. This action cannot install the one-time new secret into the connected EBS credential, so subsequent EBS calls keep using the existing credential and may fail after its overlap expires; rotate the EBS credential through a secure channel before then."
111431
},
111432
{
111140
- "slug": "DATADOG_DELETE_SCHEDULE",
111141
- "name": "Delete On-Call schedule",
111142
- "description": "Deletes a Datadog On-Call schedule by ID. This action cannot be undone."
111433
+ "slug": "TWITCH_CREATE_GUEST_STAR_SESSION",
111434
+ "name": "Create Guest Star Session",
111435
+ "description": "BETA Programmatically creates a Guest Star session on behalf of the broadcaster."
111436
},
111437
{
111145
- "slug": "DATADOG_GET_DASHBOARD",
111146
- "name": "Get Dashboard",
111147
- "description": "Get a specific dashboard from Datadog. Retrieves detailed information about a dashboard including its widgets, layout, template variables, and metadata."
111438
+ "slug": "TWITCH_CREATE_POLL",
111439
+ "name": "Create Poll",
111440
+ "description": "Creates a poll that viewers in the broadcaster’s channel can vote on."
111441
},
111442
{
111150
- "slug": "DATADOG_GET_ESCALATION_POLICY",
111151
- "name": "Get On-Call escalation policy",
111152
- "description": "Retrieves a Datadog On-Call escalation policy by ID."
111443
+ "slug": "TWITCH_CREATE_PREDICTION",
111444
+ "name": "Create Prediction",
111445
+ "description": "Create a Channel Points Prediction."
111446
},
111447
{
111155
- "slug": "DATADOG_GET_MONITOR",
111156
- "name": "Get monitor",
111157
- "description": "Retrieves detailed information about a specific Datadog monitor, including its current state, configuration, and any active downtimes."
111448
+ "slug": "TWITCH_CREATE_STREAM_MARKER",
111449
+ "name": "Create Stream Marker",
111450
+ "description": "Adds a marker to a live stream."
111451
},
111452
{
111160
- "slug": "DATADOG_GET_NOTIFICATION_CHANNEL",
111161
- "name": "Get On-Call notification channel",
111162
- "description": "Retrieves an On-Call notification channel for a user by ID."
111453
+ "slug": "TWITCH_DELETE_CHANNEL_STREAM_SCHEDULE_SEGMENT",
111454
+ "name": "Delete Channel Stream Schedule Segment",
111455
+ "description": "Deletes a broadcast from the broadcaster’s streaming schedule."
111456
},
111457
{
111165
- "slug": "DATADOG_GET_NOTIFICATION_RULE",
111166
- "name": "Get On-Call notification rule",
111167
- "description": "Retrieves an On-Call notification rule for a user by ID."
111458
+ "slug": "TWITCH_DELETE_CHAT_MESSAGES",
111459
+ "name": "Delete Chat Messages",
111460
+ "description": "Removes a single chat message or all chat messages from the broadcaster’s chat room."
111461
},
111462
{
111170
- "slug": "DATADOG_GET_SCHEDULE",
111171
- "name": "Get On-Call schedule",
111172
- "description": "Retrieves a Datadog On-Call schedule by ID."
111463
+ "slug": "TWITCH_DELETE_CONDUIT",
111464
+ "name": "Delete Conduit",
111465
+ "description": "Deletes a specified conduit."
111466
},
111467
{
111175
- "slug": "DATADOG_GET_SCHEDULED_ON_CALL_USER",
111176
- "name": "Get scheduled on-call user",
111177
- "description": "Gets the currently scheduled on-call user for a Datadog On-Call schedule."
111468
+ "slug": "TWITCH_DELETE_CUSTOM_REWARD",
111469
+ "name": "Delete Custom Reward",
111470
+ "description": "Deletes a custom reward that the broadcaster created."
111471
},
111472
{
111180
- "slug": "DATADOG_GET_SERVICE_DEPENDENCIES",
111181
- "name": "Get Service Dependencies",
111182
- "description": "Get service dependency mapping from Datadog APM. This action retrieves the dependency graph for a specific service, showing both upstream services (that call this service) and downstream services (that this service calls). It's essential for: - Understanding the blast radius of service failures - Identifying critical dependencies during incidents - Analyzing service communication patterns - Planning architectural changes - Monitoring service health in context The dependency information includes call rates, error rates, and latency metrics to help assess the health of service relationships. Requires APM instrumentation on the target service; uninstrumented services return empty or incomplete dependency data."
111473
+ "slug": "TWITCH_DELETE_EVENTSUB_SUBSCRIPTION",
111474
+ "name": "Delete EventSub Subscription",
111475
+ "description": "Deletes an EventSub subscription."
111476
},
111477
{
111185
- "slug": "DATADOG_GET_SYNTHETICS_LOCATIONS",
111186
- "name": "Get Synthetics Locations",
111187
- "description": "Tool to retrieve all available public and private locations for Synthetic tests in Datadog. Use when you need a list of location identifiers for creating or managing synthetic tests."
111478
+ "slug": "TWITCH_DELETE_GUEST_STAR_INVITE",
111479
+ "name": "Delete Guest Star Invite",
111480
+ "description": "BETA Revokes a previously sent invite for a Guest Star session."
111481
},
111482
{
111190
- "slug": "DATADOG_GET_TAGS",
111191
- "name": "Get host tags",
111192
- "description": "Retrieves all tags associated with a specific host in Datadog. Useful for understanding host metadata and organizing infrastructure."
111483
+ "slug": "TWITCH_DELETE_GUEST_STAR_SLOT",
111484
+ "name": "Delete Guest Star Slot",
111485
+ "description": "BETA Allows a caller to remove a slot assignment from a user participating in an active Guest Star session."
111486
},
111487
{
111195
- "slug": "DATADOG_GET_TEAM_ON_CALL_USERS",
111196
- "name": "Get team on-call users",
111197
- "description": "Gets the current on-call users for a Datadog On-Call team."
111488
+ "slug": "TWITCH_DELETE_VIDEOS",
111489
+ "name": "Delete Videos",
111490
+ "description": "Deletes one or more videos."
111491
},
111492
{
111200
- "slug": "DATADOG_GET_TEAM_ROUTING_RULES",
111201
- "name": "Get On-Call team routing rules",
111202
- "description": "Gets the Datadog On-Call routing rules configured for a team."
111493
+ "slug": "TWITCH_END_GUEST_STAR_SESSION",
111494
+ "name": "End Guest Star Session",
111495
+ "description": "BETA Programmatically ends a Guest Star session on behalf of the broadcaster."
111496
},
111497
{
111205
- "slug": "DATADOG_GET_TRACE_BY_ID",
111206
- "name": "Get Trace by ID",
111207
- "description": "DEPRECATED: Use DATADOG_SEARCH_TRACES instead. Get detailed information about a specific trace by its ID. This action retrieves comprehensive details about a distributed trace, including all spans, timing information, errors, and metadata. It's essential for: - Deep diving into specific request flows during incidents - Understanding the complete journey of a problematic request - Analyzing performance bottlenecks in detail - Correlating errors across services - Debugging complex distributed system issues The trace ID is typically obtained from logs, error reports, or trace search results. Use targeted time windows to avoid rate limiting; prefer narrow ranges over full 15-day spans when the approximate trace time is known."
111498
+ "slug": "TWITCH_END_POLL",
111499
+ "name": "End Poll",
111500
+ "description": "End an active poll."
111501
},
111502
{
111210
- "slug": "DATADOG_GET_USAGE_SUMMARY",
111211
- "name": "Get usage summary",
111212
- "description": "Retrieves usage summary information from Datadog including API calls, hosts, containers, and other billable usage metrics. Useful for cost monitoring and usage analysis. Months with no activity return empty payloads on success; absent data is expected, not an error."
111503
+ "slug": "TWITCH_END_PREDICTION",
111504
+ "name": "End Prediction",
111505
+ "description": "Locks, resolves, or cancels a Channel Points Prediction."
111506
},
111507
{
111215
- "slug": "DATADOG_LIST_ALL_TAGS",
111216
- "name": "List All Tags",
111217
- "description": "List all tags from Datadog. Tags help organize and filter your infrastructure and applications. This action shows all tags in use across your organization."
111508
+ "slug": "TWITCH_GET_AD_SCHEDULE",
111509
+ "name": "Get Ad Schedule",
111510
+ "description": "Returns the next ad's scheduled time and duration, available snooze count and refresh time, prior ad time, and remaining pre-roll-free time."
111511
},
111512
{
111220
- "slug": "DATADOG_LIST_API_KEYS",
111221
- "name": "List API Keys",
111222
- "description": "List API keys in Datadog. Retrieves all API keys in the organization for security auditing, access management, and key rotation planning. Helps maintain security posture by tracking key usage and ownership. Response contains sensitive key metadata (names, owners, last-used timestamps); restrict tool access to authorized personnel and handle output securely."
111513
+ "slug": "TWITCH_GET_ALL_STREAM_TAGS",
111514
+ "name": "Get All Stream Tags",
111515
+ "description": "Deprecated: this endpoint was retired and returns HTTP 410 Gone. Use GET_CHANNEL_INFORMATION and its tags field instead."
111516
},
111517
{
111225
- "slug": "DATADOG_LIST_APM_SERVICES",
111226
- "name": "List APM Services",
111227
- "description": "List APM services from Datadog. Application Performance Monitoring (APM) provides deep visibility into your applications, helping you track performance, errors, and dependencies."
111518
+ "slug": "TWITCH_GET_AUTHORIZATION_BY_USER",
111519
+ "name": "Get Authorization By User",
111520
+ "description": "Gets the authorization scopes that the specified user has granted the application."
111521
},
111522
{
111230
- "slug": "DATADOG_LIST_AWS_INTEGRATION",
111231
- "name": "List AWS Integration",
111232
- "description": "List AWS integrations in Datadog. Retrieves all configured AWS account integrations, showing which AWS accounts are monitored by Datadog and their configuration settings. Useful for cloud infrastructure management and ensuring comprehensive monitoring coverage."
111523
+ "slug": "TWITCH_GET_AUTOMOD_SETTINGS",
111524
+ "name": "Get AutoMod Settings",
111525
+ "description": "Gets the broadcaster’s AutoMod settings."
111526
},
111527
{
111235
- "slug": "DATADOG_LIST_DASHBOARDS",
111236
- "name": "List dashboards",
111237
- "description": "Lists all Datadog dashboards with basic information. Useful for dashboard management and getting an overview of available dashboards."
111528
+ "slug": "TWITCH_GET_BANNED_USERS",
111529
+ "name": "Get Banned Users",
111530
+ "description": "Gets all users that the broadcaster banned or put in a timeout."
111531
},
111532
{
111240
- "slug": "DATADOG_LIST_EVENTS",
111241
- "name": "List events",
111242
- "description": "Lists events from Datadog within a specified time range. Events track important occurrences like deployments, outages, and configuration changes. Combining multiple filters (tags, sources, priority) with narrow time ranges may return empty results even when events exist — start with broad filters and narrow incrementally. Large time ranges with minimal filtering can return very high event volumes; tune tags, sources, and start/end before processing results."
111533
+ "slug": "TWITCH_GET_BITS_LEADERBOARD",
111534
+ "name": "Get Bits Leaderboard",
111535
+ "description": "Gets the Bits leaderboard for the authenticated broadcaster."
111536
},
111537
{
111245
- "slug": "DATADOG_LIST_HOSTS",
111246
- "name": "List hosts",
111247
- "description": "Lists all hosts in your Datadog infrastructure with detailed information including metrics, tags, and status. Useful for infrastructure monitoring and management."
111538
+ "slug": "TWITCH_GET_BLOCKED_TERMS",
111539
+ "name": "Get Blocked Terms",
111540
+ "description": "Gets the broadcaster’s list of non-private, blocked words or phrases."
111541
},
111542
{
111250
- "slug": "DATADOG_LIST_INCIDENTS",
111251
- "name": "List Incidents",
111252
- "description": "List incidents from Datadog. Incident Management helps you track, manage, and resolve incidents efficiently with comprehensive timeline and impact tracking."
111543
+ "slug": "TWITCH_GET_BROADCASTER_SUBSCRIPTIONS",
111544
+ "name": "Get Broadcaster Subscriptions",
111545
+ "description": "Gets a list of users that subscribe to the specified broadcaster."
111546
},
111547
{
111255
- "slug": "DATADOG_LIST_LOG_INDEXES",
111256
- "name": "List Log Indexes",
111257
- "description": "Tool to retrieve a list of all log indexes configured in Datadog, including their names and configurations. Use before DATADOG_SEARCH_LOGS to identify the correct index name; searching without specifying the right index can hide valid logs and increase usage costs across high-volume indexes."
111548
+ "slug": "TWITCH_GET_CHANNEL_CHAT_BADGES",
111549
+ "name": "Get Channel Chat Badges",
111550
+ "description": "Gets the broadcaster’s list of custom chat badges."
111551
},
111552
{
111260
- "slug": "DATADOG_LIST_METRICS",
111261
- "name": "List active metrics",
111262
- "description": "Discover metric names by listing actively reporting metrics since a given timestamp. Use when you need to find what metrics exist before querying timeseries data with DATADOG_QUERY_METRICS."
111553
+ "slug": "TWITCH_GET_CHANNEL_EDITORS",
111554
+ "name": "Get Channel Editors",
111555
+ "description": "Gets the broadcaster’s list editors."
111556
},
111557
{
111265
- "slug": "DATADOG_LIST_MONITORS",
111266
- "name": "List monitors",
111267
- "description": "Get all monitor details. This endpoint allows you to retrieve information about all monitors configured in your organization. You can filter by group states, name, tags, and use pagination to manage large result sets."
111558
+ "slug": "TWITCH_GET_CHANNEL_EMOTES",
111559
+ "name": "Get Channel Emotes",
111560
+ "description": "Gets the broadcaster’s list of custom emotes."
111561
},
111562
{
111270
- "slug": "DATADOG_LIST_NOTIFICATION_CHANNELS",
111271
- "name": "List On-Call notification channels",
111272
- "description": "Lists the On-Call notification channels configured for a Datadog user."
111563
+ "slug": "TWITCH_GET_CHANNEL_FOLLOWERS",
111564
+ "name": "Get Channel Followers",
111565
+ "description": "Gets a list of users that follow the specified broadcaster. You can also use this endpoint to see whether a specific user follows the broadcaster."
111566
},
111567
{
111275
- "slug": "DATADOG_LIST_NOTIFICATION_RULES",
111276
- "name": "List On-Call notification rules",
111277
- "description": "Lists the On-Call notification rules configured for a Datadog user."
111568
+ "slug": "TWITCH_GET_CHANNEL_GUEST_STAR_SETTINGS",
111569
+ "name": "Get Channel Guest Star Settings",
111570
+ "description": "BETA Gets the channel settings for configuration of the Guest Star feature for a particular host."
111571
},
111572
{
111280
- "slug": "DATADOG_LIST_ROLES",
111281
- "name": "List Roles",
111282
- "description": "List roles from Datadog organization. Roles define sets of permissions that control what users can do within your Datadog organization."
111573
+ "slug": "TWITCH_GET_CHANNEL_ICALENDAR",
111574
+ "name": "Get Channel iCalendar",
111575
+ "description": "Gets the broadcaster’s streaming schedule as an iCalendar ."
111576
},
111577
{
111285
- "slug": "DATADOG_LIST_SERVICE_CHECKS",
111286
- "name": "List service checks",
111287
- "description": "Lists service checks from Datadog. Service checks are status checks that track the health of your services and infrastructure components."
111578
+ "slug": "TWITCH_GET_CHANNEL_INFORMATION",
111579
+ "name": "Get Channel Information",
111580
+ "description": "Gets information about one or more channels."
111581
},
111582
{
111290
- "slug": "DATADOG_LIST_SL_OS",
111291
- "name": "List SLOs",
111292
- "description": "List Service Level Objectives (SLOs) from Datadog. Service Level Objectives help you track the reliability and performance of your services by setting measurable targets for key metrics."
111583
+ "slug": "TWITCH_GET_CHANNEL_STREAM_SCHEDULE",
111584
+ "name": "Get Channel Stream Schedule",
111585
+ "description": "Gets the broadcaster’s streaming schedule."
111586
},
111587
{
111295
- "slug": "DATADOG_LIST_SYNTHETICS",
111296
- "name": "List Synthetics Tests",
111297
- "description": "List Synthetics tests from Datadog. Synthetics monitoring allows you to proactively monitor your applications and APIs by simulating user interactions and API calls from various locations."
111588
+ "slug": "TWITCH_GET_CHANNEL_TEAMS",
111589
+ "name": "Get Channel Teams",
111590
+ "description": "Gets the list of Twitch teams that the broadcaster is a member of."
111591
},
111592
{
111300
- "slug": "DATADOG_LIST_USERS",
111301
- "name": "List Users",
111302
- "description": "List users from Datadog organization. User management allows you to see team members, their roles, and access levels within your Datadog organization."
111593
+ "slug": "TWITCH_GET_CHARITY_CAMPAIGN",
111594
+ "name": "Get Charity Campaign",
111595
+ "description": "Gets information about the broadcaster’s active charity campaign."
111596
},
111597
{
111305
- "slug": "DATADOG_LIST_WEBHOOKS",
111306
- "name": "List Webhooks",
111307
- "description": "List webhooks from Datadog. Webhooks allow you to send notifications to external services when monitors trigger, enabling integration with your workflows."
111598
+ "slug": "TWITCH_GET_CHARITY_CAMPAIGN_DONATIONS",
111599
+ "name": "Get Charity Campaign Donations",
111600
+ "description": "Gets the list of donations that users have made to the broadcaster’s active charity campaign."
111601
},
111602
{
111310
- "slug": "DATADOG_MUTE_MONITOR",
111311
- "name": "Mute Monitor",
111312
- "description": "Mute a monitor in Datadog. Temporarily silences alerts from a monitor, which is useful during maintenance windows, deployments, or when investigating known issues to prevent alert fatigue."
111603
+ "slug": "TWITCH_GET_CHAT_SETTINGS",
111604
+ "name": "Get Chat Settings",
111605
+ "description": "Gets the broadcaster’s chat settings."
111606
},
111607
{
111315
- "slug": "DATADOG_QUERY_METRICS",
111316
- "name": "Query metrics",
111317
- "description": "Queries Datadog metrics and returns time series data. Useful for retrieving historical metric data, creating custom dashboards, or building reports."
111608
+ "slug": "TWITCH_GET_CHATTERS",
111609
+ "name": "Get Chatters",
111610
+ "description": "Gets the list of users that are connected to the broadcaster’s chat session."
111611
},
111612
{
111320
- "slug": "DATADOG_SEARCH_LOGS",
111321
- "name": "Search logs",
111322
- "description": "Searches Datadog logs with advanced filtering capabilities. IMPORTANT NOTES: - Sort parameter is NOT supported by the Datadog Logs API and will cause errors - Time parameters must be in milliseconds (13-digit UNIX timestamps) - Limit parameter is passed as string to the API - Log content is nested under 'content' field in API response Useful for troubleshooting, monitoring application behavior, and analyzing log patterns."
111613
+ "slug": "TWITCH_GET_CHEERMOTES",
111614
+ "name": "Get Cheermotes",
111615
+ "description": "Gets a list of Cheermotes that users can use to cheer Bits."
111616
},
111617
{
111325
- "slug": "DATADOG_SEARCH_SPANS_ANALYTICS",
111326
- "name": "Search Spans Analytics",
111327
- "description": "Search and analyze span data with aggregations in Datadog. This action uses the Datadog Spans Analytics API to perform advanced queries and aggregations on trace span data. It's essential for: - Analyzing error rates and latency patterns - Understanding service dependencies and bottlenecks - Root cause analysis during incidents - Performance monitoring and optimization The API supports complex queries with grouping, filtering, and various aggregation functions similar to log analytics. The request body must conform to the `aggregate_request` schema; schema violations return \"Invalid type. Expected 'aggregate_request'\". If `filter` or `compute` cannot satisfy this schema, use basic trace search instead."
111618
+ "slug": "TWITCH_GET_CLIPS",
111619
+ "name": "Get Clips",
111620
+ "description": "Gets clips selected by exactly one broadcaster ID, game ID, or list of clip IDs."
111621
},
111622
{
111330
- "slug": "DATADOG_SEARCH_TRACES",
111331
- "name": "Search Traces",
111332
- "description": "Search for traces in Datadog APM. This action allows you to search for distributed traces across your services. It's essential for: - Finding specific request flows during incident investigation - Analyzing performance bottlenecks across services - Understanding error propagation through your system - Correlating user requests with backend operations Traces provide the complete picture of a request as it travels through your distributed system, making them crucial for root cause analysis."
111623
+ "slug": "TWITCH_GET_CLIPS_DOWNLOAD",
111624
+ "name": "Get Clips Download",
111625
+ "description": "Provides URLs to download the video file(s) for the specified clips."
111626
},
111627
{
111335
- "slug": "DATADOG_SET_TEAM_ROUTING_RULES",
111336
- "name": "Set On-Call team routing rules",
111337
- "description": "Replaces (sets) the On-Call routing rules for a Datadog team."
111628
+ "slug": "TWITCH_GET_CONDUITS",
111629
+ "name": "Get Conduits",
111630
+ "description": "Gets the conduits for a client ID."
111631
},
111632
{
111340
- "slug": "DATADOG_SUBMIT_METRICS",
111341
- "name": "Submit metrics",
111342
- "description": "Submits custom metrics to Datadog. Useful for sending application-specific metrics, business KPIs, or custom performance indicators."
111633
+ "slug": "TWITCH_GET_CONDUIT_SHARDS",
111634
+ "name": "Get Conduit Shards",
111635
+ "description": "Gets a lists of all shards for a conduit."
111636
},
111637
{
111345
- "slug": "DATADOG_UNMUTE_MONITOR",
111346
- "name": "Unmute Monitor",
111347
- "description": "Unmute a monitor in Datadog. Re-enables alerts from a previously muted monitor, returning it to normal monitoring and alerting behavior. Alerting resumes immediately upon call, so ensure maintenance or issue resolution is fully complete before unmuting to avoid alert storms. Use this after maintenance windows or issue resolution to resume monitoring."
111638
+ "slug": "TWITCH_GET_CONTENT_CLASSIFICATION_LABELS",
111639
+ "name": "Get Content Classification Labels",
111640
+ "description": "Gets information about Twitch content classification labels."
111641
},
111642
{
111350
- "slug": "DATADOG_UPDATE_DASHBOARD",
111351
- "name": "Update Dashboard",
111352
- "description": "Update a dashboard in Datadog. Updates an existing dashboard with new configuration, widgets, or layout while preserving its identity and creation metadata."
111643
+ "slug": "TWITCH_GET_CREATOR_GOALS",
111644
+ "name": "Get Creator Goals",
111645
+ "description": "Gets the broadcaster’s list of active goals."
111646
},
111647
{
111355
- "slug": "DATADOG_UPDATE_ESCALATION_POLICY",
111356
- "name": "Update On-Call escalation policy",
111357
- "description": "Updates a Datadog On-Call escalation policy by ID."
111648
+ "slug": "TWITCH_GET_CUSTOM_POWER_UP",
111649
+ "name": "Get Custom Power-up",
111650
+ "description": "Gets a list of custom Power-ups that the specified broadcaster created."
111651
},
111652
{
111360
- "slug": "DATADOG_UPDATE_HOST_TAGS",
111361
- "name": "Update host tags",
111362
- "description": "Updates tags for a specific host in Datadog. This replaces all existing tags from the specified source with the new tags provided."
111653
+ "slug": "TWITCH_GET_CUSTOM_REWARD",
111654
+ "name": "Get Custom Reward",
111655
+ "description": "Gets a list of custom rewards that the specified broadcaster created."
111656
},
111657
{
111365
- "slug": "DATADOG_UPDATE_MONITOR",
111366
- "name": "Update monitor",
111367
- "description": "Updates an existing Datadog monitor with new configuration, thresholds, or notification settings. Only specified fields will be updated."
111658
+ "slug": "TWITCH_GET_CUSTOM_REWARD_REDEMPTION",
111659
+ "name": "Get Custom Reward Redemption",
111660
+ "description": "Gets a list of redemptions for a custom reward."
111661
},
111662
{
111370
- "slug": "DATADOG_UPDATE_NOTIFICATION_RULE",
111371
- "name": "Update On-Call notification rule",
111372
- "description": "Updates an On-Call notification rule for a user by ID."
111663
+ "slug": "TWITCH_GET_DROPS_ENTITLEMENTS",
111664
+ "name": "Get Drops Entitlements",
111665
+ "description": "Gets an organization’s list of entitlements that have been granted to a game, a user, or both."
111666
},
111667
{
111375
- "slug": "DATADOG_UPDATE_SCHEDULE",
111376
- "name": "Update On-Call schedule",
111377
- "description": "Updates a Datadog On-Call schedule by ID."
111668
+ "slug": "TWITCH_GET_EMOTE_SETS",
111669
+ "name": "Get Emote Sets",
111670
+ "description": "Gets emotes for one or more specified emote sets."
111671
+ },
111672
+ {
111673
+ "slug": "TWITCH_GET_EVENTSUB_SUBSCRIPTIONS",
111674
+ "name": "Get EventSub Subscriptions",
111675
+ "description": "Gets a list of EventSub subscriptions that the client in the access token created."
111676
+ },
111677
+ {
111678
+ "slug": "TWITCH_GET_EXTENSION_ANALYTICS",
111679
+ "name": "Get Extension Analytics",
111680
+ "description": "Gets an analytics report for one or more extensions."
111681
+ },
111682
+ {
111683
+ "slug": "TWITCH_GET_EXTENSION_BITS_PRODUCTS",
111684
+ "name": "Get Extension Bits Products",
111685
+ "description": "Gets the list of Bits products that belongs to the extension."
111686
+ },
111687
+ {
111688
+ "slug": "TWITCH_GET_EXTENSION_CONFIGURATION_SEGMENT",
111689
+ "name": "Get Extension Configuration Segment",
111690
+ "description": "Gets the specified configuration segment from the specified extension."
111691
+ },
111692
+ {
111693
+ "slug": "TWITCH_GET_EXTENSION_LIVE_CHANNELS",
111694
+ "name": "Get Extension Live Channels",
111695
+ "description": "Gets a list of broadcasters that are streaming live and have installed or activated the extension."
111696
+ },
111697
+ {
111698
+ "slug": "TWITCH_GET_EXTENSIONS",
111699
+ "name": "Get Extensions",
111700
+ "description": "Gets information about an extension."
111701
+ },
111702
+ {
111703
+ "slug": "TWITCH_GET_EXTENSION_SECRETS",
111704
+ "name": "Get Extension Secrets",
111705
+ "description": "Gets Extension shared-secret metadata with secret content redacted."
111706
+ },
111707
+ {
111708
+ "slug": "TWITCH_GET_EXTENSION_TRANSACTIONS",
111709
+ "name": "Get Extension Transactions",
111710
+ "description": "Gets an extension’s list of transactions."
111711
+ },
111712
+ {
111713
+ "slug": "TWITCH_GET_FOLLOWED_CHANNELS",
111714
+ "name": "Get Followed Channels",
111715
+ "description": "Gets a list of broadcasters that the specified user follows. You can also use this endpoint to see whether a user follows a specific broadcaster."
111716
+ },
111717
+ {
111718
+ "slug": "TWITCH_GET_FOLLOWED_STREAMS",
111719
+ "name": "Get Followed Streams",
111720
+ "description": "Gets the list of broadcasters that the user follows and that are streaming live."
111721
+ },
111722
+ {
111723
+ "slug": "TWITCH_GET_GAME_ANALYTICS",
111724
+ "name": "Get Game Analytics",
111725
+ "description": "Gets an analytics report for one or more games."
111726
+ },
111727
+ {
111728
+ "slug": "TWITCH_GET_GAMES",
111729
+ "name": "Get Games",
111730
+ "description": "Gets information about specified games."
111731
+ },
111732
+ {
111733
+ "slug": "TWITCH_GET_GLOBAL_CHAT_BADGES",
111734
+ "name": "Get Global Chat Badges",
111735
+ "description": "Gets Twitch’s list of chat badges."
111736
+ },
111737
+ {
111738
+ "slug": "TWITCH_GET_GLOBAL_EMOTES",
111739
+ "name": "Get Global Emotes",
111740
+ "description": "Gets all global emotes."
111741
+ },
111742
+ {
111743
+ "slug": "TWITCH_GET_GUEST_STAR_INVITES",
111744
+ "name": "Get Guest Star Invites",
111745
+ "description": "BETA Provides the caller with a list of pending invites to a Guest Star session."
111746
+ },
111747
+ {
111748
+ "slug": "TWITCH_GET_GUEST_STAR_SESSION",
111749
+ "name": "Get Guest Star Session",
111750
+ "description": "BETA Gets information about an ongoing Guest Star session for a particular channel."
111751
+ },
111752
+ {
111753
+ "slug": "TWITCH_GET_HYPE_TRAIN_STATUS",
111754
+ "name": "Get Hype Train Status",
111755
+ "description": "Gets the status of a Hype Train for the specified broadcaster."
111756
+ },
111757
+ {
111758
+ "slug": "TWITCH_GET_MODERATED_CHANNELS",
111759
+ "name": "Get Moderated Channels",
111760
+ "description": "Gets a list of channels that the specified user has moderator privileges in."
111761
+ },
111762
+ {
111763
+ "slug": "TWITCH_GET_MODERATORS",
111764
+ "name": "Get Moderators",
111765
+ "description": "Gets all users allowed to moderate the broadcaster’s chat room."
111766
+ },
111767
+ {
111768
+ "slug": "TWITCH_GET_PINNED_CHAT_MESSAGE",
111769
+ "name": "Get Pinned Chat Message",
111770
+ "description": "Gets the currently pinned message for the broadcaster’s chat room."
111771
+ },
111772
+ {
111773
+ "slug": "TWITCH_GET_POLLS",
111774
+ "name": "Get Polls",
111775
+ "description": "Gets a list of polls that the broadcaster created."
111776
+ },
111777
+ {
111778
+ "slug": "TWITCH_GET_PREDICTIONS",
111779
+ "name": "Get Predictions",
111780
+ "description": "Gets a list of Channel Points Predictions that the broadcaster created."
111781
+ },
111782
+ {
111783
+ "slug": "TWITCH_GET_RELEASED_EXTENSIONS",
111784
+ "name": "Get Released Extensions",
111785
+ "description": "Gets information about a released extension."
111786
+ },
111787
+ {
111788
+ "slug": "TWITCH_GET_SHARED_CHAT_SESSION",
111789
+ "name": "Get Shared Chat Session",
111790
+ "description": "Retrieves the active shared chat session for a channel."
111791
+ },
111792
+ {
111793
+ "slug": "TWITCH_GET_SHIELD_MODE_STATUS",
111794
+ "name": "Get Shield Mode Status",
111795
+ "description": "Gets the broadcaster’s Shield Mode activation status."
111796
+ },
111797
+ {
111798
+ "slug": "TWITCH_GET_STREAM_KEY",
111799
+ "name": "Get Sensitive Stream Key",
111800
+ "description": "SENSITIVE: retrieves the channel's raw stream key, which grants the ability to broadcast as the channel. Use only when explicitly required; never log, quote, persist, or disclose the output. This is non-mutating and therefore uses the strongest available read-only ability hint."
111801
+ },
111802
+ {
111803
+ "slug": "TWITCH_GET_STREAM_MARKERS",
111804
+ "name": "Get Stream Markers",
111805
+ "description": "Gets markers from either a user's most recent stream or one specified VOD; provide exactly one selector."
111806
+ },
111807
+ {
111808
+ "slug": "TWITCH_GET_STREAMS",
111809
+ "name": "Get Streams",
111810
+ "description": "Gets a list of all streams."
111811
+ },
111812
+ {
111813
+ "slug": "TWITCH_GET_STREAM_TAGS",
111814
+ "name": "Get Stream Tags",
111815
+ "description": "Deprecated: this endpoint was retired and returns HTTP 410 Gone. Use GET_CHANNEL_INFORMATION and its tags field instead."
111816
+ },
111817
+ {
111818
+ "slug": "TWITCH_GET_TEAMS",
111819
+ "name": "Get Teams",
111820
+ "description": "Gets one Twitch team by exactly one team name or team ID."
111821
+ },
111822
+ {
111823
+ "slug": "TWITCH_GET_TOP_GAMES",
111824
+ "name": "Get Top Games",
111825
+ "description": "Gets games and categories ranked by current viewer count on Twitch."
111826
+ },
111827
+ {
111828
+ "slug": "TWITCH_GET_UNBAN_REQUESTS",
111829
+ "name": "Get Unban Requests",
111830
+ "description": "Gets a list of unban requests for a broadcaster’s channel."
111831
+ },
111832
+ {
111833
+ "slug": "TWITCH_GET_USER_ACTIVE_EXTENSIONS",
111834
+ "name": "Get User Active Extensions",
111835
+ "description": "Gets the active extensions that the broadcaster has installed for each configuration."
111836
+ },
111837
+ {
111838
+ "slug": "TWITCH_GET_USER_BLOCK_LIST",
111839
+ "name": "Get User Block List",
111840
+ "description": "Gets the list of users that the broadcaster has blocked."
111841
+ },
111842
+ {
111843
+ "slug": "TWITCH_GET_USER_CHAT_COLOR",
111844
+ "name": "Get User Chat Color",
111845
+ "description": "Gets the color used for the user’s name in chat."
111846
+ },
111847
+ {
111848
+ "slug": "TWITCH_GET_USER_EMOTES",
111849
+ "name": "Get User Emotes",
111850
+ "description": "Retrieves emotes available to the user across all channels."
111851
+ },
111852
+ {
111853
+ "slug": "TWITCH_GET_USER_EXTENSIONS",
111854
+ "name": "Get User Extensions",
111855
+ "description": "Gets a list of all extensions (both active and inactive) that the broadcaster has installed."
111856
+ },
111857
+ {
111858
+ "slug": "TWITCH_GET_USERS",
111859
+ "name": "Get Users",
111860
+ "description": "Gets information about one or more users. With no id or login selectors, returns the user represented by the access token."
111861
+ },
111862
+ {
111863
+ "slug": "TWITCH_GET_VIDEOS",
111864
+ "name": "Get Videos",
111865
+ "description": "Gets published videos selected by exactly one list of video IDs, broadcaster ID, or game ID."
111866
+ },
111867
+ {
111868
+ "slug": "TWITCH_GET_VIPS",
111869
+ "name": "Get VIPs",
111870
+ "description": "Gets a list of the broadcaster’s VIPs."
111871
+ },
111872
+ {
111873
+ "slug": "TWITCH_MANAGE_HELD_AUTOMOD_MESSAGES",
111874
+ "name": "Allow or Deny Held AutoMod Message",
111875
+ "description": "Allows or denies one message that AutoMod held for review."
111876
+ },
111877
+ {
111878
+ "slug": "TWITCH_MODIFY_CHANNEL_INFORMATION",
111879
+ "name": "Modify Channel Information",
111880
+ "description": "Updates a channel’s properties."
111881
+ },
111882
+ {
111883
+ "slug": "TWITCH_PIN_CHAT_MESSAGE",
111884
+ "name": "Pin Chat Message",
111885
+ "description": "Pins a chat message to the specified broadcaster’s chat room."
111886
+ },
111887
+ {
111888
+ "slug": "TWITCH_REMOVE_BLOCKED_TERM",
111889
+ "name": "Remove Blocked Term",
111890
+ "description": "Removes the word or phrase from the broadcaster’s list of blocked terms."
111891
+ },
111892
+ {
111893
+ "slug": "TWITCH_REMOVE_CHANNEL_MODERATOR",
111894
+ "name": "Remove Channel Moderator",
111895
+ "description": "Removes a moderator from the broadcaster’s chat room."
111896
+ },
111897
+ {
111898
+ "slug": "TWITCH_REMOVE_CHANNEL_VIP",
111899
+ "name": "Remove Channel VIP",
111900
+ "description": "Removes the specified user as a VIP in the broadcaster’s channel."
111901
+ },
111902
+ {
111903
+ "slug": "TWITCH_REMOVE_SUSPICIOUS_STATUS_FROM_CHAT_USER",
111904
+ "name": "Remove Suspicious Status From Chat User",
111905
+ "description": "Remove a suspicious user status from a chatter on broadcaster’s channel."
111906
+ },
111907
+ {
111908
+ "slug": "TWITCH_RESOLVE_UNBAN_REQUESTS",
111909
+ "name": "Resolve Unban Requests",
111910
+ "description": "Resolves an unban request by approving or denying it."
111911
+ },
111912
+ {
111913
+ "slug": "TWITCH_SEARCH_CATEGORIES",
111914
+ "name": "Search Categories",
111915
+ "description": "Gets the games or categories that match the specified query."
111916
+ },
111917
+ {
111918
+ "slug": "TWITCH_SEARCH_CHANNELS",
111919
+ "name": "Search Channels",
111920
+ "description": "Gets the channels that match the specified query and have streamed content within the past 6 months."
111921
+ },
111922
+ {
111923
+ "slug": "TWITCH_SEND_A_SHOUTOUT",
111924
+ "name": "Send a Shoutout",
111925
+ "description": "Sends a Shoutout to the specified broadcaster."
111926
+ },
111927
+ {
111928
+ "slug": "TWITCH_SEND_CHAT_ANNOUNCEMENT",
111929
+ "name": "Send Chat Announcement",
111930
+ "description": "Sends an announcement to the broadcaster’s chat room."
111931
+ },
111932
+ {
111933
+ "slug": "TWITCH_SEND_CHAT_MESSAGE",
111934
+ "name": "Send Chat Message",
111935
+ "description": "Sends a message to the broadcaster’s chat room and fails if Twitch reports that it was dropped. for_source_only is app-token-only; select an S2S OAuth connection when setting it because execution metadata does not expose token family for local validation."
111936
+ },
111937
+ {
111938
+ "slug": "TWITCH_SEND_EXTENSION_CHAT_MESSAGE",
111939
+ "name": "Send Extension Chat Message",
111940
+ "description": "Sends a message to the specified broadcaster’s chat room."
111941
+ },
111942
+ {
111943
+ "slug": "TWITCH_SEND_EXTENSION_PUBSUB_MESSAGE",
111944
+ "name": "Send Extension PubSub Message",
111945
+ "description": "Sends a message to one or more viewers."
111946
+ },
111947
+ {
111948
+ "slug": "TWITCH_SEND_GUEST_STAR_INVITE",
111949
+ "name": "Send Guest Star Invite",
111950
+ "description": "BETA Sends an invite to a specified guest on behalf of the broadcaster for a Guest Star session in progress."
111951
+ },
111952
+ {
111953
+ "slug": "TWITCH_SEND_WHISPER",
111954
+ "name": "Send Whisper",
111955
+ "description": "Sends a whisper message to the specified user."
111956
+ },
111957
+ {
111958
+ "slug": "TWITCH_SET_EXTENSION_CONFIGURATION_SEGMENT",
111959
+ "name": "Set Extension Configuration Segment",
111960
+ "description": "Creates or replaces an Extension configuration segment; omitting content deletes the segment."
111961
+ },
111962
+ {
111963
+ "slug": "TWITCH_SET_EXTENSION_REQUIRED_CONFIGURATION",
111964
+ "name": "Set Extension Required Configuration",
111965
+ "description": "Updates the extension’s required_configuration string."
111966
+ },
111967
+ {
111968
+ "slug": "TWITCH_SNOOZE_NEXT_AD",
111969
+ "name": "Snooze Next Ad",
111970
+ "description": "Pushes back the timestamp of the upcoming automatic mid-roll ad by 5 minutes."
111971
+ },
111972
+ {
111973
+ "slug": "TWITCH_START_A_RAID",
111974
+ "name": "Start a raid",
111975
+ "description": "Raid another channel by sending the broadcaster’s viewers to the targeted channel."
111976
+ },
111977
+ {
111978
+ "slug": "TWITCH_START_COMMERCIAL",
111979
+ "name": "Start Commercial",
111980
+ "description": "Starts a commercial on the specified channel."
111981
+ },
111982
+ {
111983
+ "slug": "TWITCH_UNBAN_USER",
111984
+ "name": "Unban User",
111985
+ "description": "Removes the ban or timeout that was placed on the specified user."
111986
+ },
111987
+ {
111988
+ "slug": "TWITCH_UNBLOCK_USER",
111989
+ "name": "Unblock User",
111990
+ "description": "Removes the user from the broadcaster’s list of blocked users."
111991
+ },
111992
+ {
111993
+ "slug": "TWITCH_UNPIN_CHAT_MESSAGE",
111994
+ "name": "Unpin Chat Message",
111995
+ "description": "Unpins a pinned chat message from the broadcaster’s chat room."
111996
+ },
111997
+ {
111998
+ "slug": "TWITCH_UPDATE_AUTOMOD_SETTINGS",
111999
+ "name": "Update AutoMod Settings",
112000
+ "description": "Updates the broadcaster’s AutoMod settings."
112001
+ },
112002
+ {
112003
+ "slug": "TWITCH_UPDATE_CHANNEL_GUEST_STAR_SETTINGS",
112004
+ "name": "Update Channel Guest Star Settings",
112005
+ "description": "BETA Updates Guest Star channel settings; regenerating browser sources immediately invalidates all previously configured browser sources."
112006
+ },
112007
+ {
112008
+ "slug": "TWITCH_UPDATE_CHANNEL_STREAM_SCHEDULE",
112009
+ "name": "Update Channel Stream Schedule",
112010
+ "description": "Updates the broadcaster’s schedule settings, such as scheduling a vacation."
112011
+ },
112012
+ {
112013
+ "slug": "TWITCH_UPDATE_CHANNEL_STREAM_SCHEDULE_SEGMENT",
112014
+ "name": "Update Channel Stream Schedule Segment",
112015
+ "description": "Updates a scheduled broadcast segment. Changes to a recurring segment apply to every segment in its series."
112016
+ },
112017
+ {
112018
+ "slug": "TWITCH_UPDATE_CHAT_SETTINGS",
112019
+ "name": "Update Chat Settings",
112020
+ "description": "Updates the broadcaster’s chat settings."
112021
+ },
112022
+ {
112023
+ "slug": "TWITCH_UPDATE_CONDUITS",
112024
+ "name": "Update Conduits",
112025
+ "description": "Updates a conduit’s shard count."
112026
+ },
112027
+ {
112028
+ "slug": "TWITCH_UPDATE_CONDUIT_SHARDS",
112029
+ "name": "Update Conduit Shards",
112030
+ "description": "Updates up to 100 conduit shards. Twitch may accept the request with partial success; inspect errors for every shard that was not updated. The action fails if no shard was updated."
112031
+ },
112032
+ {
112033
+ "slug": "TWITCH_UPDATE_CUSTOM_REWARD",
112034
+ "name": "Update Custom Reward",
112035
+ "description": "Updates a custom reward."
112036
+ },
112037
+ {
112038
+ "slug": "TWITCH_UPDATE_DROPS_ENTITLEMENTS",
112039
+ "name": "Update Drops Entitlements",
112040
+ "description": "Updates the Drop entitlement’s fulfillment status."
112041
+ },
112042
+ {
112043
+ "slug": "TWITCH_UPDATE_EXTENSION_BITS_PRODUCT",
112044
+ "name": "Update Extension Bits Product",
112045
+ "description": "Adds or updates a Bits product that the extension created."
112046
+ },
112047
+ {
112048
+ "slug": "TWITCH_UPDATE_GUEST_STAR_SLOT",
112049
+ "name": "Update Guest Star Slot",
112050
+ "description": "BETA Allows a user to update the assigned slot for a particular user within the active Guest Star session."
112051
+ },
112052
+ {
112053
+ "slug": "TWITCH_UPDATE_GUEST_STAR_SLOT_SETTINGS",
112054
+ "name": "Update Guest Star Slot Settings",
112055
+ "description": "BETA Allows a user to update slot settings for a particular guest within a Guest Star session."
112056
+ },
112057
+ {
112058
+ "slug": "TWITCH_UPDATE_PINNED_CHAT_MESSAGE",
112059
+ "name": "Update Pinned Chat Message",
112060
+ "description": "Updates the duration of a pinned chat message."
112061
+ },
112062
+ {
112063
+ "slug": "TWITCH_UPDATE_REDEMPTION_STATUS",
112064
+ "name": "Update Redemption Status",
112065
+ "description": "Updates a redemption’s status."
112066
+ },
112067
+ {
112068
+ "slug": "TWITCH_UPDATE_SHIELD_MODE_STATUS",
112069
+ "name": "Update Shield Mode Status",
112070
+ "description": "Activates or deactivates the broadcaster’s Shield Mode."
112071
+ },
112072
+ {
112073
+ "slug": "TWITCH_UPDATE_USER",
112074
+ "name": "Update User",
112075
+ "description": "Updates the user’s information."
112076
+ },
112077
+ {
112078
+ "slug": "TWITCH_UPDATE_USER_CHAT_COLOR",
112079
+ "name": "Update User Chat Color",
112080
+ "description": "Updates the color used for the user’s name in chat."
112081
+ },
112082
+ {
112083
+ "slug": "TWITCH_UPDATE_USER_EXTENSIONS",
112084
+ "name": "Update User Extensions",
112085
+ "description": "Updates an installed extension’s information."
112086
+ },
112087
+ {
112088
+ "slug": "TWITCH_WARN_CHAT_USER",
112089
+ "name": "Warn Chat User",
112090
+ "description": "Warns a user in the specified broadcaster’s chat room, preventing them from chat interaction until the warning is acknowledged."
112091
}
112092
],
112093
"triggers": [],
112094
"authConfigDetails": [
112095
+ {
112096
+ "mode": "NO_AUTH",
112097
+ "name": "twitch_no_auth",
112098
+ "fields": {
112099
+ "auth_config_creation": {
112100
+ "required": [],
112101
+ "optional": []
112102
+ },
112103
+ "connected_account_initiation": {
112104
+ "required": [],
112105
+ "optional": []
112106
+ }
112107
+ }
112108
+ },
112109
{
112110
"mode": "OAUTH2",
111384
- "name": "datadog_oauth2",
112111
+ "name": "twitch_oauth2",
112112
+ "fields": {
112113
+ "auth_config_creation": {
112114
+ "required": [
112115
+ {
112116
+ "name": "client_id",
112117
+ "displayName": "Client id",
112118
+ "type": "string",
112119
+ "description": "Client id of the app",
112120
+ "required": true,
112121
+ "default": null
112122
+ },
112123
+ {
112124
+ "name": "client_secret",
112125
+ "displayName": "Client secret",
112126
+ "type": "string",
112127
+ "description": "Client secret of the app",
112128
+ "required": true,
112129
+ "default": null
112130
+ }
112131
+ ],
112132
+ "optional": [
112133
+ {
112134
+ "name": "oauth_redirect_uri",
112135
+ "displayName": "Redirect URI",
112136
+ "type": "string",
112137
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
112138
+ "required": false,
112139
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
112140
+ },
112141
+ {
112142
+ "name": "scopes",
112143
+ "displayName": "Scopes",
112144
+ "type": "string",
112145
+ "description": "Scopes to request from the user, comma separated",
112146
+ "required": false,
112147
+ "default": ""
112148
+ }
112149
+ ]
112150
+ },
112151
+ "connected_account_initiation": {
112152
+ "required": [],
112153
+ "optional": []
112154
+ }
112155
+ }
112156
+ },
112157
+ {
112158
+ "mode": "S2S_OAUTH2",
112159
+ "name": "twitch_app_oauth2",
112160
+ "fields": {
112161
+ "auth_config_creation": {
112162
+ "required": [
112163
+ {
112164
+ "name": "client_id",
112165
+ "displayName": "Twitch Application Client ID",
112166
+ "type": "string",
112167
+ "description": "The Client ID shown for your application in the Twitch Developer Console under Applications > Manage.",
112168
+ "required": true,
112169
+ "default": null
112170
+ },
112171
+ {
112172
+ "name": "client_secret",
112173
+ "displayName": "Twitch Application Client Secret",
112174
+ "type": "string",
112175
+ "description": "The client secret generated for the same application in the Twitch Developer Console under Applications > Manage. Keep this value secret.",
112176
+ "required": true,
112177
+ "default": null
112178
+ }
112179
+ ],
112180
+ "optional": []
112181
+ },
112182
+ "connected_account_initiation": {
112183
+ "required": [],
112184
+ "optional": []
112185
+ }
112186
+ }
112187
+ }
112188
+ ]
112189
+ },
112190
+ {
112191
+ "slug": "datadog",
112192
+ "name": "Datadog",
112193
+ "logo": "https://logos.composio.dev/api/datadog",
112194
+ "description": "Datadog offers monitoring, observability, and security for cloud-scale applications, unifying metrics, logs, and traces to help teams detect issues and optimize performance",
112195
+ "category": "server monitoring",
112196
+ "authSchemes": [
112197
+ "OAUTH2",
112198
+ "API_KEY",
112199
+ "BEARER_TOKEN"
112200
+ ],
112201
+ "toolCount": 65,
112202
+ "triggerCount": 0,
112203
+ "version": "20260826_00",
112204
+ "tools": [
112205
+ {
112206
+ "slug": "DATADOG_AGGREGATE_LOGS",
112207
+ "name": "Aggregate logs",
112208
+ "description": "Aggregate Datadog logs without downloading raw events. Use for counts, unique values, percentiles, numeric statistics, grouped breakdowns, and values over time. Use DATADOG_SEARCH_LOGS only when individual log messages are required."
112209
+ },
112210
+ {
112211
+ "slug": "DATADOG_CREATE_DASHBOARD",
112212
+ "name": "Create Dashboard",
112213
+ "description": "Create a dashboard in Datadog. Dashboards provide customizable visualizations for monitoring your infrastructure, applications, and business metrics in a unified view."
112214
+ },
112215
+ {
112216
+ "slug": "DATADOG_CREATE_DOWNTIME",
112217
+ "name": "Create downtime",
112218
+ "description": "Creates a new downtime in Datadog to suppress alerts during maintenance windows or planned outages. Useful for preventing false alarms during deployments or maintenance."
112219
+ },
112220
+ {
112221
+ "slug": "DATADOG_CREATE_ESCALATION_POLICY",
112222
+ "name": "Create On-Call escalation policy",
112223
+ "description": "Creates a Datadog On-Call escalation policy."
112224
+ },
112225
+ {
112226
+ "slug": "DATADOG_CREATE_EVENT",
112227
+ "name": "Create event",
112228
+ "description": "Creates a new event in Datadog. Events are useful for tracking deployments, outages, configuration changes, and other important occurrences."
112229
+ },
112230
+ {
112231
+ "slug": "DATADOG_CREATE_MONITOR",
112232
+ "name": "Create monitor",
112233
+ "description": "Creates a new Datadog monitor to track metrics, logs, or other data sources with configurable alerting thresholds and notifications."
112234
+ },
112235
+ {
112236
+ "slug": "DATADOG_CREATE_NOTIFICATION_CHANNEL",
112237
+ "name": "Create On-Call notification channel",
112238
+ "description": "Creates an On-Call notification channel for a Datadog user."
112239
+ },
112240
+ {
112241
+ "slug": "DATADOG_CREATE_NOTIFICATION_RULE",
112242
+ "name": "Create On-Call notification rule",
112243
+ "description": "Creates an On-Call notification rule for a Datadog user."
112244
+ },
112245
+ {
112246
+ "slug": "DATADOG_CREATE_SCHEDULE",
112247
+ "name": "Create On-Call schedule",
112248
+ "description": "Creates a Datadog On-Call schedule."
112249
+ },
112250
+ {
112251
+ "slug": "DATADOG_CREATE_SLO",
112252
+ "name": "Create SLO",
112253
+ "description": "Create a Service Level Objective (SLO) in Datadog. SLOs help you define and track reliability targets for your services, enabling data-driven decisions about service quality and reliability investments."
112254
+ },
112255
+ {
112256
+ "slug": "DATADOG_CREATE_SYNTHETIC_API_TEST",
112257
+ "name": "Create Synthetic API Test",
112258
+ "description": "Create a synthetic API test in Datadog. Creates a new synthetic API test that continuously monitors API endpoints from multiple locations worldwide. Useful for proactive monitoring of API uptime, performance, and functionality."
112259
+ },
112260
+ {
112261
+ "slug": "DATADOG_CREATE_WEBHOOK",
112262
+ "name": "Create Webhook",
112263
+ "description": "Create a webhook in Datadog. Registers a named destination endpoint; each monitor must explicitly reference the webhook by name in its message or notification settings for alerts to be delivered."
112264
+ },
112265
+ {
112266
+ "slug": "DATADOG_DELETE_DASHBOARD",
112267
+ "name": "Delete Dashboard",
112268
+ "description": "Delete a dashboard in Datadog. Permanently removes a dashboard from your organization. This action cannot be undone. Use with caution."
112269
+ },
112270
+ {
112271
+ "slug": "DATADOG_DELETE_ESCALATION_POLICY",
112272
+ "name": "Delete On-Call escalation policy",
112273
+ "description": "Deletes a Datadog On-Call escalation policy by ID. This action cannot be undone."
112274
+ },
112275
+ {
112276
+ "slug": "DATADOG_DELETE_MONITOR",
112277
+ "name": "Delete monitor",
112278
+ "description": "Deletes a Datadog monitor permanently. Use with caution as this action cannot be undone."
112279
+ },
112280
+ {
112281
+ "slug": "DATADOG_DELETE_NOTIFICATION_CHANNEL",
112282
+ "name": "Delete On-Call notification channel",
112283
+ "description": "Deletes an On-Call notification channel for a Datadog user. This action cannot be undone."
112284
+ },
112285
+ {
112286
+ "slug": "DATADOG_DELETE_NOTIFICATION_RULE",
112287
+ "name": "Delete On-Call notification rule",
112288
+ "description": "Deletes an On-Call notification rule for a Datadog user. This action cannot be undone."
112289
+ },
112290
+ {
112291
+ "slug": "DATADOG_DELETE_SCHEDULE",
112292
+ "name": "Delete On-Call schedule",
112293
+ "description": "Deletes a Datadog On-Call schedule by ID. This action cannot be undone."
112294
+ },
112295
+ {
112296
+ "slug": "DATADOG_GET_DASHBOARD",
112297
+ "name": "Get Dashboard",
112298
+ "description": "Get a specific dashboard from Datadog. Retrieves detailed information about a dashboard including its widgets, layout, template variables, and metadata."
112299
+ },
112300
+ {
112301
+ "slug": "DATADOG_GET_ESCALATION_POLICY",
112302
+ "name": "Get On-Call escalation policy",
112303
+ "description": "Retrieves a Datadog On-Call escalation policy by ID."
112304
+ },
112305
+ {
112306
+ "slug": "DATADOG_GET_MONITOR",
112307
+ "name": "Get monitor",
112308
+ "description": "Retrieves detailed information about a specific Datadog monitor, including its current state, configuration, and any active downtimes."
112309
+ },
112310
+ {
112311
+ "slug": "DATADOG_GET_NOTIFICATION_CHANNEL",
112312
+ "name": "Get On-Call notification channel",
112313
+ "description": "Retrieves an On-Call notification channel for a user by ID."
112314
+ },
112315
+ {
112316
+ "slug": "DATADOG_GET_NOTIFICATION_RULE",
112317
+ "name": "Get On-Call notification rule",
112318
+ "description": "Retrieves an On-Call notification rule for a user by ID."
112319
+ },
112320
+ {
112321
+ "slug": "DATADOG_GET_SCHEDULE",
112322
+ "name": "Get On-Call schedule",
112323
+ "description": "Retrieves a Datadog On-Call schedule by ID."
112324
+ },
112325
+ {
112326
+ "slug": "DATADOG_GET_SCHEDULED_ON_CALL_USER",
112327
+ "name": "Get scheduled on-call user",
112328
+ "description": "Gets the currently scheduled on-call user for a Datadog On-Call schedule."
112329
+ },
112330
+ {
112331
+ "slug": "DATADOG_GET_SERVICE_DEPENDENCIES",
112332
+ "name": "Get Service Dependencies",
112333
+ "description": "Get service dependency mapping from Datadog APM. This action retrieves the dependency graph for a specific service, showing both upstream services (that call this service) and downstream services (that this service calls). It's essential for: - Understanding the blast radius of service failures - Identifying critical dependencies during incidents - Analyzing service communication patterns - Planning architectural changes - Monitoring service health in context The dependency information includes call rates, error rates, and latency metrics to help assess the health of service relationships. Requires APM instrumentation on the target service; uninstrumented services return empty or incomplete dependency data."
112334
+ },
112335
+ {
112336
+ "slug": "DATADOG_GET_SYNTHETICS_LOCATIONS",
112337
+ "name": "Get Synthetics Locations",
112338
+ "description": "Tool to retrieve all available public and private locations for Synthetic tests in Datadog. Use when you need a list of location identifiers for creating or managing synthetic tests."
112339
+ },
112340
+ {
112341
+ "slug": "DATADOG_GET_TAGS",
112342
+ "name": "Get host tags",
112343
+ "description": "Retrieves all tags associated with a specific host in Datadog. Useful for understanding host metadata and organizing infrastructure."
112344
+ },
112345
+ {
112346
+ "slug": "DATADOG_GET_TEAM_ON_CALL_USERS",
112347
+ "name": "Get team on-call users",
112348
+ "description": "Gets the current on-call users for a Datadog On-Call team."
112349
+ },
112350
+ {
112351
+ "slug": "DATADOG_GET_TEAM_ROUTING_RULES",
112352
+ "name": "Get On-Call team routing rules",
112353
+ "description": "Gets the Datadog On-Call routing rules configured for a team."
112354
+ },
112355
+ {
112356
+ "slug": "DATADOG_GET_TRACE_BY_ID",
112357
+ "name": "Get Trace by ID",
112358
+ "description": "DEPRECATED: Use DATADOG_SEARCH_TRACES instead. Get detailed information about a specific trace by its ID. This action retrieves comprehensive details about a distributed trace, including all spans, timing information, errors, and metadata. It's essential for: - Deep diving into specific request flows during incidents - Understanding the complete journey of a problematic request - Analyzing performance bottlenecks in detail - Correlating errors across services - Debugging complex distributed system issues The trace ID is typically obtained from logs, error reports, or trace search results. Use targeted time windows to avoid rate limiting; prefer narrow ranges over full 15-day spans when the approximate trace time is known."
112359
+ },
112360
+ {
112361
+ "slug": "DATADOG_GET_USAGE_SUMMARY",
112362
+ "name": "Get usage summary",
112363
+ "description": "Retrieves usage summary information from Datadog including API calls, hosts, containers, and other billable usage metrics. Useful for cost monitoring and usage analysis. Months with no activity return empty payloads on success; absent data is expected, not an error."
112364
+ },
112365
+ {
112366
+ "slug": "DATADOG_LIST_ALL_TAGS",
112367
+ "name": "List All Tags",
112368
+ "description": "List all tags from Datadog. Tags help organize and filter your infrastructure and applications. This action shows all tags in use across your organization."
112369
+ },
112370
+ {
112371
+ "slug": "DATADOG_LIST_API_KEYS",
112372
+ "name": "List API Keys",
112373
+ "description": "List API keys in Datadog. Retrieves all API keys in the organization for security auditing, access management, and key rotation planning. Helps maintain security posture by tracking key usage and ownership. Response contains sensitive key metadata (names, owners, last-used timestamps); restrict tool access to authorized personnel and handle output securely."
112374
+ },
112375
+ {
112376
+ "slug": "DATADOG_LIST_APM_SERVICES",
112377
+ "name": "List APM Services",
112378
+ "description": "List APM services from Datadog. Application Performance Monitoring (APM) provides deep visibility into your applications, helping you track performance, errors, and dependencies."
112379
+ },
112380
+ {
112381
+ "slug": "DATADOG_LIST_AWS_INTEGRATION",
112382
+ "name": "List AWS Integration",
112383
+ "description": "List AWS integrations in Datadog. Retrieves all configured AWS account integrations, showing which AWS accounts are monitored by Datadog and their configuration settings. Useful for cloud infrastructure management and ensuring comprehensive monitoring coverage."
112384
+ },
112385
+ {
112386
+ "slug": "DATADOG_LIST_DASHBOARDS",
112387
+ "name": "List dashboards",
112388
+ "description": "Lists all Datadog dashboards with basic information. Useful for dashboard management and getting an overview of available dashboards."
112389
+ },
112390
+ {
112391
+ "slug": "DATADOG_LIST_EVENTS",
112392
+ "name": "List events",
112393
+ "description": "Lists events from Datadog within a specified time range. Events track important occurrences like deployments, outages, and configuration changes. Combining multiple filters (tags, sources, priority) with narrow time ranges may return empty results even when events exist — start with broad filters and narrow incrementally. Large time ranges with minimal filtering can return very high event volumes; tune tags, sources, and start/end before processing results."
112394
+ },
112395
+ {
112396
+ "slug": "DATADOG_LIST_HOSTS",
112397
+ "name": "List hosts",
112398
+ "description": "Lists all hosts in your Datadog infrastructure with detailed information including metrics, tags, and status. Useful for infrastructure monitoring and management."
112399
+ },
112400
+ {
112401
+ "slug": "DATADOG_LIST_INCIDENTS",
112402
+ "name": "List Incidents",
112403
+ "description": "List incidents from Datadog. Incident Management helps you track, manage, and resolve incidents efficiently with comprehensive timeline and impact tracking."
112404
+ },
112405
+ {
112406
+ "slug": "DATADOG_LIST_LOG_INDEXES",
112407
+ "name": "List Log Indexes",
112408
+ "description": "Tool to retrieve a list of all log indexes configured in Datadog, including their names and configurations. Use before DATADOG_SEARCH_LOGS to identify the correct index name; searching without specifying the right index can hide valid logs and increase usage costs across high-volume indexes."
112409
+ },
112410
+ {
112411
+ "slug": "DATADOG_LIST_METRICS",
112412
+ "name": "List active metrics",
112413
+ "description": "Discover metric names by listing actively reporting metrics since a given timestamp. Use when you need to find what metrics exist before querying timeseries data with DATADOG_QUERY_METRICS."
112414
+ },
112415
+ {
112416
+ "slug": "DATADOG_LIST_MONITORS",
112417
+ "name": "List monitors",
112418
+ "description": "Get all monitor details. This endpoint allows you to retrieve information about all monitors configured in your organization. You can filter by group states, name, tags, and use pagination to manage large result sets."
112419
+ },
112420
+ {
112421
+ "slug": "DATADOG_LIST_NOTIFICATION_CHANNELS",
112422
+ "name": "List On-Call notification channels",
112423
+ "description": "Lists the On-Call notification channels configured for a Datadog user."
112424
+ },
112425
+ {
112426
+ "slug": "DATADOG_LIST_NOTIFICATION_RULES",
112427
+ "name": "List On-Call notification rules",
112428
+ "description": "Lists the On-Call notification rules configured for a Datadog user."
112429
+ },
112430
+ {
112431
+ "slug": "DATADOG_LIST_ROLES",
112432
+ "name": "List Roles",
112433
+ "description": "List roles from Datadog organization. Roles define sets of permissions that control what users can do within your Datadog organization."
112434
+ },
112435
+ {
112436
+ "slug": "DATADOG_LIST_SERVICE_CHECKS",
112437
+ "name": "List service checks",
112438
+ "description": "Lists service checks from Datadog. Service checks are status checks that track the health of your services and infrastructure components."
112439
+ },
112440
+ {
112441
+ "slug": "DATADOG_LIST_SL_OS",
112442
+ "name": "List SLOs",
112443
+ "description": "List Service Level Objectives (SLOs) from Datadog. Service Level Objectives help you track the reliability and performance of your services by setting measurable targets for key metrics."
112444
+ },
112445
+ {
112446
+ "slug": "DATADOG_LIST_SYNTHETICS",
112447
+ "name": "List Synthetics Tests",
112448
+ "description": "List Synthetics tests from Datadog. Synthetics monitoring allows you to proactively monitor your applications and APIs by simulating user interactions and API calls from various locations."
112449
+ },
112450
+ {
112451
+ "slug": "DATADOG_LIST_USERS",
112452
+ "name": "List Users",
112453
+ "description": "List users from Datadog organization. User management allows you to see team members, their roles, and access levels within your Datadog organization."
112454
+ },
112455
+ {
112456
+ "slug": "DATADOG_LIST_WEBHOOKS",
112457
+ "name": "List Webhooks",
112458
+ "description": "List webhooks from Datadog. Webhooks allow you to send notifications to external services when monitors trigger, enabling integration with your workflows."
112459
+ },
112460
+ {
112461
+ "slug": "DATADOG_MUTE_MONITOR",
112462
+ "name": "Mute Monitor",
112463
+ "description": "Mute a monitor in Datadog. Temporarily silences alerts from a monitor, which is useful during maintenance windows, deployments, or when investigating known issues to prevent alert fatigue."
112464
+ },
112465
+ {
112466
+ "slug": "DATADOG_QUERY_METRICS",
112467
+ "name": "Query metrics",
112468
+ "description": "Queries Datadog metrics and returns time series data. Useful for retrieving historical metric data, creating custom dashboards, or building reports."
112469
+ },
112470
+ {
112471
+ "slug": "DATADOG_SEARCH_LOGS",
112472
+ "name": "Search logs",
112473
+ "description": "Searches Datadog logs with advanced filtering capabilities. IMPORTANT NOTES: - Sort parameter is NOT supported by the Datadog Logs API and will cause errors - Time parameters must be in milliseconds (13-digit UNIX timestamps) - Limit parameter is passed as string to the API - Log content is nested under 'content' field in API response Useful for troubleshooting, monitoring application behavior, and analyzing log patterns."
112474
+ },
112475
+ {
112476
+ "slug": "DATADOG_SEARCH_SPANS_ANALYTICS",
112477
+ "name": "Search Spans Analytics",
112478
+ "description": "Search and analyze span data with aggregations in Datadog. This action uses the Datadog Spans Analytics API to perform advanced queries and aggregations on trace span data. It's essential for: - Analyzing error rates and latency patterns - Understanding service dependencies and bottlenecks - Root cause analysis during incidents - Performance monitoring and optimization The API supports complex queries with grouping, filtering, and various aggregation functions similar to log analytics. The request body must conform to the `aggregate_request` schema; schema violations return \"Invalid type. Expected 'aggregate_request'\". If `filter` or `compute` cannot satisfy this schema, use basic trace search instead."
112479
+ },
112480
+ {
112481
+ "slug": "DATADOG_SEARCH_TRACES",
112482
+ "name": "Search Traces",
112483
+ "description": "Search for traces in Datadog APM. This action allows you to search for distributed traces across your services. It's essential for: - Finding specific request flows during incident investigation - Analyzing performance bottlenecks across services - Understanding error propagation through your system - Correlating user requests with backend operations Traces provide the complete picture of a request as it travels through your distributed system, making them crucial for root cause analysis."
112484
+ },
112485
+ {
112486
+ "slug": "DATADOG_SET_TEAM_ROUTING_RULES",
112487
+ "name": "Set On-Call team routing rules",
112488
+ "description": "Replaces (sets) the On-Call routing rules for a Datadog team."
112489
+ },
112490
+ {
112491
+ "slug": "DATADOG_SUBMIT_METRICS",
112492
+ "name": "Submit metrics",
112493
+ "description": "Submits custom metrics to Datadog. Useful for sending application-specific metrics, business KPIs, or custom performance indicators."
112494
+ },
112495
+ {
112496
+ "slug": "DATADOG_UNMUTE_MONITOR",
112497
+ "name": "Unmute Monitor",
112498
+ "description": "Unmute a monitor in Datadog. Re-enables alerts from a previously muted monitor, returning it to normal monitoring and alerting behavior. Alerting resumes immediately upon call, so ensure maintenance or issue resolution is fully complete before unmuting to avoid alert storms. Use this after maintenance windows or issue resolution to resume monitoring."
112499
+ },
112500
+ {
112501
+ "slug": "DATADOG_UPDATE_DASHBOARD",
112502
+ "name": "Update Dashboard",
112503
+ "description": "Update a dashboard in Datadog. Updates an existing dashboard with new configuration, widgets, or layout while preserving its identity and creation metadata."
112504
+ },
112505
+ {
112506
+ "slug": "DATADOG_UPDATE_ESCALATION_POLICY",
112507
+ "name": "Update On-Call escalation policy",
112508
+ "description": "Updates a Datadog On-Call escalation policy by ID."
112509
+ },
112510
+ {
112511
+ "slug": "DATADOG_UPDATE_HOST_TAGS",
112512
+ "name": "Update host tags",
112513
+ "description": "Updates tags for a specific host in Datadog. This replaces all existing tags from the specified source with the new tags provided."
112514
+ },
112515
+ {
112516
+ "slug": "DATADOG_UPDATE_MONITOR",
112517
+ "name": "Update monitor",
112518
+ "description": "Updates an existing Datadog monitor with new configuration, thresholds, or notification settings. Only specified fields will be updated."
112519
+ },
112520
+ {
112521
+ "slug": "DATADOG_UPDATE_NOTIFICATION_RULE",
112522
+ "name": "Update On-Call notification rule",
112523
+ "description": "Updates an On-Call notification rule for a user by ID."
112524
+ },
112525
+ {
112526
+ "slug": "DATADOG_UPDATE_SCHEDULE",
112527
+ "name": "Update On-Call schedule",
112528
+ "description": "Updates a Datadog On-Call schedule by ID."
112529
+ }
112530
+ ],
112531
+ "triggers": [],
112532
+ "authConfigDetails": [
112533
+ {
112534
+ "mode": "OAUTH2",
112535
+ "name": "datadog_oauth2",
112536
"fields": {
112537
"auth_config_creation": {
112538
"required": [
113234
],
113235
"toolCount": 3,
113236
"triggerCount": 0,
112086
- "version": "20260615_00",
113237
+ "version": "20260908_00",
113238
"tools": [
113239
{
113240
"slug": "ABSTRACT_EMAIL_REPUTATION_API",
118688
}
118689
]
118690
},
118691
+ {
118692
+ "slug": "airwallex",
118693
+ "name": "Airwallex",
118694
+ "logo": "https://logos.composio.dev/api/airwallex",
118695
+ "description": "Airwallex provides business accounts, payments, payouts, foreign exchange, cards, and financial operations through a unified global financial platform.",
118696
+ "category": "payment processing",
118697
+ "authSchemes": [
118698
+ "API_KEY"
118699
+ ],
118700
+ "toolCount": 7,
118701
+ "triggerCount": 0,
118702
+ "version": "00000000_00",
118703
+ "tools": [
118704
+ {
118705
+ "slug": "AIRWALLEX_GET_CURRENT_ACCOUNT",
118706
+ "name": "Get Current Account",
118707
+ "description": "Retrieve identity, status, and profile details for the connected Airwallex account."
118708
+ },
118709
+ {
118710
+ "slug": "AIRWALLEX_GET_CURRENT_BALANCES",
118711
+ "name": "Get Current Balances",
118712
+ "description": "Return available, pending, reserved, prepayment, and total balances by currency for an Airwallex account type."
118713
+ },
118714
+ {
118715
+ "slug": "AIRWALLEX_GET_SUPPORTED_CONVERSION_CURRENCIES",
118716
+ "name": "Get Supported Conversion Currencies",
118717
+ "description": "Return the connected client's currencies supported for buying and selling in conversions."
118718
+ },
118719
+ {
118720
+ "slug": "AIRWALLEX_LIST_BENEFICIARIES",
118721
+ "name": "List Beneficiaries",
118722
+ "description": "List beneficiaries, optionally filtered by identity, bank account, entity type, or creation date. Returns one page and a cursor for continuation."
118723
+ },
118724
+ {
118725
+ "slug": "AIRWALLEX_LIST_CONVERSIONS",
118726
+ "name": "List Conversions",
118727
+ "description": "List recent currency conversions, optionally filtered by currencies, request ID, status, or creation time. Returns one page and a continuation cursor."
118728
+ },
118729
+ {
118730
+ "slug": "AIRWALLEX_LIST_GLOBAL_ACCOUNTS",
118731
+ "name": "List Global Accounts",
118732
+ "description": "List global accounts, optionally filtered by country, currency, nickname, status, or creation time. Returns one page and an Airwallex bookmark cursor when another page is available."
118733
+ },
118734
+ {
118735
+ "slug": "AIRWALLEX_LIST_TRANSFERS",
118736
+ "name": "List Transfers",
118737
+ "description": "List one page of transfers created by the connected Airwallex account, optionally filtered by currency, destination, request ID, status, or creation time. Pass the returned cursor to retrieve the next page."
118738
+ }
118739
+ ],
118740
+ "triggers": [],
118741
+ "authConfigDetails": [
118742
+ {
118743
+ "mode": "API_KEY",
118744
+ "name": "airwallex_api_key",
118745
+ "fields": {
118746
+ "auth_config_creation": {
118747
+ "required": [],
118748
+ "optional": []
118749
+ },
118750
+ "connected_account_initiation": {
118751
+ "required": [
118752
+ {
118753
+ "name": "generic_api_key",
118754
+ "displayName": "API Key",
118755
+ "type": "string",
118756
+ "description": "Your sandbox API key. In the Airwallex sandbox web app, go to Settings > Developer > API keys and create or copy an API key for the single account you want this connection to access. Keep it secret; production keys do not work with this sandbox toolkit.",
118757
+ "required": true,
118758
+ "default": null
118759
+ },
118760
+ {
118761
+ "name": "generic_id",
118762
+ "displayName": "Client ID",
118763
+ "type": "string",
118764
+ "description": "Your sandbox Client ID. In the Airwallex sandbox web app, go to Settings > Developer > API keys and copy the Client ID shown with the sandbox API key you will use. Production Client IDs do not work with this sandbox toolkit.",
118765
+ "required": true,
118766
+ "default": null
118767
+ }
118768
+ ],
118769
+ "optional": []
118770
+ }
118771
+ }
118772
+ }
118773
+ ]
118774
+ },
118775
{
118776
"slug": "aivoov",
118777
"name": "Aivoov",
118829
],
118830
"toolCount": 10,
118831
"triggerCount": 0,
117597
- "version": "20260730_01",
118832
+ "version": "20260904_00",
118833
"tools": [
118834
{
118835
"slug": "AIWYN_TAX_MCP_CALCULATE_TAX",
118836
"name": "Calculate tax",
117602
- "description": "Calculate a tax return for a given jurisdiction. The 'input' argument must conform to the JSON schema returned by the tax_namespace_schema tool. Returns computed tax return document on success, or validation errors if the input is invalid. If some inputs trigger a PARTIAL DISQUALIFICATION, the document is still returned for the supported fields; review the disqualification details and estimate the impact of the unsupported fields on the taxpayer's tax owed or refund due. Use the check_tax tool first to validate the input before calculating the tax return with this tool.IMPORTANT RULES: (1) All field values must be wrapped as {\"value\": <val>} — never pass bare values. (2) Currency amounts are whole-dollar integers (e.g. $19,312.42 = 19312). (3) Every item in an array namespace (NamespaceList) must have a \"uuid\" field with a valid UUIDv4 string. UUIDv4 format: xxxxxxxx-xxxx-4xxx-[89ab]xxx-xxxxxxxxxxxx — the 3rd group MUST start with '4' (version) and the 4th group MUST start with '8', '9', 'a', or 'b' (variant). NEVER construct UUIDs manually (e.g. 'B1111111-1111-1111-1111-111111111111' is invalid). Use a UUID generator; example valid value: 'a3b4c5d6-e7f8-4a9b-8c0d-1e2f3a4b5c6d'. (4) Nested arrays (e.g. w2_state_local_tax_grp inside a w2) also require a UUIDv4 on each item. (5) Use \"who_applies_to\" to cross-reference entries: {\"value\": \"taxpayer\"} for singletons, {\"value\": \"<namespace>#<uuid>\"} for array items (e.g. \"dependent_detail#<uuid>\"). Other named reference fields (e.g. \"person\" in qualifying_person_grp, \"student\" in student_educational_instn_grp) use the same \"<namespace>#<uuid>\" format. (6) For state returns with Extended Links (state namespace extending a federal NamespaceList), each extended link item must use a UUIDv5 generated from the source item's UUID (as the namespace) and the extended namespace name (as the name). Matching is UUID-based, not positional. The number of expected instances depends on the source formula — it is NOT always a 1:1 match with the federal list (e.g. CA Form 3853 ca_household_grp expects taxpayer + spouse + all dependents). Incorrect or random UUIDs cause SILENT DATA LOSS — the server drops unrecognized UUIDs and replaces them with empty instances. Use the generate_uuid_v5 tool with the source item's UUID as the source_uuid and the extended namespace name (e.g. \"ca_provider\", \"ca_irsw2_g\") as the namespace input.Example: generate_uuid_v5(source_uuid: w2_uuid, namespace: \"ca_irsw2_g\") for a CA W-2 extension.(7) return_header is top-level, NOT nested inside return_data. Use tax_simple_return first to see the full input structure and examples. When returning the tax calculation inform the user that I'm just a tax estimator, you should consult with a tax professional."
118837
+ "description": "Calculate a tax return for a given jurisdiction. The 'input' argument must conform to the JSON schema returned by the tax_namespace_schema tool. Returns computed tax return document on success, or validation errors if the input is invalid. If some inputs trigger a PARTIAL DISQUALIFICATION, the document is still returned for the supported fields; review the disqualification details and estimate the impact of the unsupported fields on the taxpayer's tax owed or refund due. Use the check_tax tool first to validate the input before calculating the tax return with this tool.IMPORTANT RULES: (1) All field values must be wrapped as {\"value\": <val>} — never pass bare values. (2) Currency amounts are whole-dollar integers (e.g. $19,312.42 = 19312). (3) Every item in an array namespace (NamespaceList) must have a \"uuid\" field with a valid UUIDv4 string. UUIDv4 format: xxxxxxxx-xxxx-4xxx-[89ab]xxx-xxxxxxxxxxxx — the 3rd group MUST start with '4' (version) and the 4th group MUST start with '8', '9', 'a', or 'b' (variant). NEVER construct UUIDs manually (e.g. 'B1111111-1111-1111-1111-111111111111' is invalid). Use a UUID generator; example valid value: 'a3b4c5d6-e7f8-4a9b-8c0d-1e2f3a4b5c6d'. (4) Nested arrays (e.g. w2_state_local_tax_grp inside a w2) also require a UUIDv4 on each item. (5) Use \"who_applies_to\" to cross-reference entries: {\"value\": \"taxpayer\"} for singletons, {\"value\": \"<namespace>#<uuid>\"} for array items (e.g. \"dependent_detail#<uuid>\"). Other named reference fields (e.g. \"person\" in qualifying_person_grp, \"student\" in student_educational_instn_grp) use the same \"<namespace>#<uuid>\" format. (6) For state returns with Extended Links (state namespace extending a federal NamespaceList), each extended link item must use a UUIDv5 generated from the source item's UUID (as the namespace) and the extended namespace name (as the name). Matching is UUID-based, not positional. The number of expected instances depends on the source formula — it is NOT always a 1:1 match with the federal list. Incorrect or random UUIDs cause SILENT DATA LOSS — the server drops unrecognized UUIDs and replaces them with empty instances. Use the generate_uuid_v5 tool with the source item's UUID as the source_uuid and the extended namespace name as the namespace input. Example: generate_uuid_v5(source_uuid: <source item uuid>, namespace: \"ca_irsw2_g\") links a federal Form W-2G item to its California extension. NOTE: ordinary Form W-2 data does NOT use an extended link — state returns derive it automatically from the federal w2 namespace, so do not generate a UUIDv5 for it. Call tax_namespaces for the jurisdiction to see which extended namespaces it actually exposes. (7) return_header is top-level, NOT nested inside return_data. Use tax_simple_return first to see the full input structure and examples. When returning the tax calculation inform the user that I'm just a tax estimator, you should consult with a tax professional."
118838
},
118839
{
118840
"slug": "AIWYN_TAX_MCP_CHECK_TAX",
118864
{
118865
"slug": "AIWYN_TAX_MCP_TAX_NAMESPACES",
118866
"name": "Tax namespaces",
117632
- "description": "List all available input namespaces for a given jurisdiction. Use the returned names with the tax_namespace_schema tool to get the schema for a specific namespace. Requires a jurisdiction (e.g. \"us\" for federal, \"ca\" for California). Use the tax_jurisdictions tool first to discover available jurisdictions. NAMESPACE NAMING CONVENTIONS: Federal namespaces: irs1040, irs1040_schedule1, irs8962, w2, dependent_detail, etc. State namespaces: always prefixed with the state abbreviation (ca_form540, ny_it201, az_form140). NAMESPACE TYPES: Some namespaces are singletons (object), others are NamespaceLists (array) that can hold multiple items — e.g. w2 (multiple W-2s), dependent_detail (multiple dependents), irs1040_schedulec (multiple businesses). NamespaceList items require UUIDv4 fields. State NamespaceLists may act as Extended Links that extend a federal NamespaceList (e.g. ca_provider extends care_provider_grp). Extended link items must use UUIDv5 (deterministic, derived from source item UUID as namespace + extended namespace name as name). Matching is UUID-based, not positional. Wrong UUIDs cause silent data loss.Use the generate_uuid_v5 tool with the source item's UUID as the source_uuid and the extended namespace name (e.g. \"ca_provider\", \"ca_irsw2_g\") as the namespace input.Example: generate_uuid_v5(source_uuid: w2_uuid, namespace: \"ca_irsw2_g\") for a CA W-2 extension."
118867
+ "description": "List all available input namespaces for a given jurisdiction. Use the returned names with the tax_namespace_schema tool to get the schema for a specific namespace. Requires a jurisdiction (e.g. \"us\" for federal, \"ca\" for California). Use the tax_jurisdictions tool first to discover available jurisdictions. NAMESPACE NAMING CONVENTIONS: Federal namespaces: irs1040, irs1040_schedule1, irs8962, w2, dependent_detail, etc. State namespaces: always prefixed with the state abbreviation (ca_form540, ny_it201, az_form140). NAMESPACE TYPES: Some namespaces are singletons (object), others are NamespaceLists (array) that can hold multiple items — e.g. w2 (multiple W-2s), dependent_detail (multiple dependents), irs1040_schedulec (multiple businesses). NamespaceList items require UUIDv4 fields. State NamespaceLists may act as Extended Links that extend a federal NamespaceList (e.g. ca_irsw2_g extends the federal Form W-2G list). Extended link items must use UUIDv5 (deterministic, derived from source item UUID as namespace + extended namespace name as name). Matching is UUID-based, not positional. Wrong UUIDs cause silent data loss. Use the generate_uuid_v5 tool with the source item's UUID as the source_uuid and the extended namespace name as the namespace input. Example: generate_uuid_v5(source_uuid: <source item uuid>, namespace: \"ca_irsw2_g\"). NOTE: ordinary Form W-2 data does NOT use an extended link — state returns derive it automatically from the federal w2 namespace. The list this tool returns for a jurisdiction is authoritative: only namespaces it names can be passed to tax_namespace_schema or included in an input payload."
118868
},
118869
{
118870
"slug": "AIWYN_TAX_MCP_TAX_NAMESPACE_SCHEMA",
123652
],
123653
"toolCount": 113,
123654
"triggerCount": 0,
122420
- "version": "20260821_00",
123655
+ "version": "20260902_00",
123656
"tools": [
123657
{
123658
"slug": "APIFY_ACT_BUILDS_POST",
135200
}
135201
]
135202
},
135203
+ {
135204
+ "slug": "bluepillow",
135205
+ "name": "Blue Pillow Hotels & Stays",
135206
+ "logo": "https://logos.composio.dev/api/bluepillow",
135207
+ "description": "Blue Pillow provides AI agents with hotel and stay discovery, live offer comparison, recommendations, validation, and tracked booking handoff.",
135208
+ "category": "ai agents",
135209
+ "authSchemes": [
135210
+ "API_KEY"
135211
+ ],
135212
+ "toolCount": 8,
135213
+ "triggerCount": 0,
135214
+ "version": "00000000_00",
135215
+ "tools": [
135216
+ {
135217
+ "slug": "BLUEPILLOW_CREATE_BOOKING_HANDOFF",
135218
+ "name": "Create Booking Handoff",
135219
+ "description": "Create only a tracked Blue Pillow handoff link for the user to continue the booking process. This does not reserve a room, confirm a reservation, or collect payment."
135220
+ },
135221
+ {
135222
+ "slug": "BLUEPILLOW_DISCOVER_DESTINATIONS_NEAR",
135223
+ "name": "Discover Destinations Near Coordinates",
135224
+ "description": "Find cities, neighborhoods, airports, or points of interest near geographic coordinates."
135225
+ },
135226
+ {
135227
+ "slug": "BLUEPILLOW_GET_PROPERTY",
135228
+ "name": "Get Property",
135229
+ "description": "Get canonical details and optional review enrichments for one property; use search or hotel recommendation for live availability."
135230
+ },
135231
+ {
135232
+ "slug": "BLUEPILLOW_RECOMMEND_OFFER_FOR_PROPERTY",
135233
+ "name": "Recommend Offer for Property",
135234
+ "description": "Compare live OTA offers and recommend the best offer for a property the user has already selected. This endpoint has no locale or currency input, so Blue Pillow applies provider defaults; use the currency returned in the response."
135235
+ },
135236
+ {
135237
+ "slug": "BLUEPILLOW_RECOMMEND_STAY",
135238
+ "name": "Recommend Stay",
135239
+ "description": "Rank a location to one recommended stay plus alternatives. A recommendation may have no live price and unknown availability, so validate an offer before booking handoff."
135240
+ },
135241
+ {
135242
+ "slug": "BLUEPILLOW_RESOLVE_DESTINATION",
135243
+ "name": "Resolve Destination",
135244
+ "description": "Resolve a place name into destination IDs for stay search, including ambiguity and confidence information."
135245
+ },
135246
+ {
135247
+ "slug": "BLUEPILLOW_SEARCH_STAYS",
135248
+ "name": "Search Stays",
135249
+ "description": "Search one page of ranked live stay inventory with availability, prices, OTA offers, and an opaque cursor for more results."
135250
+ },
135251
+ {
135252
+ "slug": "BLUEPILLOW_VALIDATE_OFFER",
135253
+ "name": "Validate Offer",
135254
+ "description": "Re-price a previously seen EUR offer and report whether it remains valid within the provider's two-percent tolerance."
135255
+ }
135256
+ ],
135257
+ "triggers": [],
135258
+ "authConfigDetails": [
135259
+ {
135260
+ "mode": "API_KEY",
135261
+ "name": "bluepillow_api_key",
135262
+ "fields": {
135263
+ "auth_config_creation": {
135264
+ "required": [],
135265
+ "optional": []
135266
+ },
135267
+ "connected_account_initiation": {
135268
+ "required": [
135269
+ {
135270
+ "name": "generic_api_key",
135271
+ "displayName": "B2A API Key",
135272
+ "type": "string",
135273
+ "description": "Your permanent anonymous B2A bearer key. Generate one with the \"Generate API key\" control at https://b2a.bluepillow.com/ or by calling POST https://api.b2a.bluepillow.com/v1/keys without authentication, then reuse the returned key. Blue Pillow states that this key is not a sensitive secret because it identifies only a rate-limit bucket.",
135274
+ "required": true,
135275
+ "default": null
135276
+ }
135277
+ ],
135278
+ "optional": []
135279
+ }
135280
+ }
135281
+ }
135282
+ ]
135283
+ },
135284
{
135285
"slug": "bluebarry",
135286
"name": "Bluebarry",
138403
}
138404
]
138405
},
138406
+ {
138407
+ "slug": "braze",
138408
+ "name": "Braze",
138409
+ "logo": "https://logos.composio.dev/api/braze",
138410
+ "description": "Braze is a customer engagement platform for managing user data, messaging, campaigns, analytics, catalogs, templates, and workspace automation.",
138411
+ "category": "marketing automation",
138412
+ "authSchemes": [
138413
+ "API_KEY"
138414
+ ],
138415
+ "toolCount": 119,
138416
+ "triggerCount": 0,
138417
+ "version": "00000000_00",
138418
+ "tools": [
138419
+ {
138420
+ "slug": "BRAZE_BLOCKLIST_EMAILS",
138421
+ "name": "Blocklist Emails",
138422
+ "description": "HIGH IMPACT: globally unsubscribe and mark as hard bounced one to 50 exact email addresses. This can affect every profile sharing an address and prevent delivery across campaigns. Success is rejected unless Braze explicitly returns message=success. Default rate limit: 250,000 requests/hour."
138423
+ },
138424
+ {
138425
+ "slug": "BRAZE_CANCEL_SEGMENT_EXPORTS",
138426
+ "name": "Cancel Segment Exports",
138427
+ "description": "Ask Braze to cancel all ongoing exports for a segment. Braze documents no response confirmation schema, so a successful call is only the provider response and must not be treated as proof that cancellation completed."
138428
+ },
138429
+ {
138430
+ "slug": "BRAZE_CREATE_CAMPAIGN_TRIGGER_SCHEDULE",
138431
+ "name": "Schedule Campaign Trigger",
138432
+ "description": "HIGH IMPACT: schedule one durable API-triggered campaign dispatch. Provide up to 50 recipients, optionally intersected with a Connected Audience. Audience-only targeting requires broadcast=true, which cannot include individual recipients. Recipient trigger properties override shared keys. Requires a dashboard API-triggered campaign and campaigns.trigger.schedule.create. Acceptance and a schedule ID do not prove delivery."
138433
+ },
138434
+ {
138435
+ "slug": "BRAZE_CREATE_CANVAS_TRIGGER_SCHEDULE",
138436
+ "name": "Schedule Canvas Trigger",
138437
+ "description": "HIGH IMPACT: schedule one durable API-triggered Canvas entry. Provide up to 50 recipients, optionally intersected with a Connected Audience. Audience-only targeting requires broadcast=true, which cannot include individual recipients. Per-recipient context overrides shared context. Requires a dashboard API-triggered Canvas and canvas.trigger.schedule.create. Users are recorded as entries only at scheduled time; acceptance is not delivery."
138438
+ },
138439
+ {
138440
+ "slug": "BRAZE_CREATE_CATALOG",
138441
+ "name": "Create Catalog",
138442
+ "description": "Create one persistent catalog in the connected Braze workspace. The catalog name must be unique and identifies the resource for later reads or deletion."
138443
+ },
138444
+ {
138445
+ "slug": "BRAZE_CREATE_CATALOG_FIELDS",
138446
+ "name": "Create Catalog Fields",
138447
+ "description": "Asynchronously create up to 50 fields in one Braze catalog. Requires the immutable catalogs.create_fields API-key permission and shares a 50 requests/minute limit with asynchronous catalog field and selection endpoints. A 202 response only confirms acceptance; Braze documents no job ID or terminal result."
138448
+ },
138449
+ {
138450
+ "slug": "BRAZE_CREATE_CATALOG_ITEM",
138451
+ "name": "Create Catalog Item",
138452
+ "description": "Synchronously create one Braze catalog item by exact item ID. Requires the immutable catalogs.create_item API-key permission and shares a 50 requests/minute synchronous item limit. Existing IDs and body-level id fields are rejected."
138453
+ },
138454
+ {
138455
+ "slug": "BRAZE_CREATE_CATALOG_ITEMS",
138456
+ "name": "Create Multiple Catalog Items",
138457
+ "description": "Asynchronously create up to 50 Braze catalog items. Requires the immutable catalogs.add_items API-key permission and shares a 16,000 requests/minute limit with asynchronous catalog item endpoints. A 202 response confirms acceptance only; Braze documents no job ID, per-item result, or terminal completion."
138458
+ },
138459
+ {
138460
+ "slug": "BRAZE_CREATE_CATALOG_SELECTION",
138461
+ "name": "Create Catalog Selection",
138462
+ "description": "Asynchronously create one Braze catalog selection. Requires the immutable catalogs.create_selection API-key permission and shares a 50 requests/minute limit with asynchronous field and selection endpoints. Geo filters force nearest-first ordering. Storage and selection-count gates may reject the request. A 202 response confirms acceptance only and includes no documented job result."
138463
+ },
138464
+ {
138465
+ "slug": "BRAZE_CREATE_CONTENT_BLOCK",
138466
+ "name": "Create Content Block",
138467
+ "description": "Persist a reusable HTML or text Content Block in the connected Braze workspace. This creates content only; it does not send or deliver a message."
138468
+ },
138469
+ {
138470
+ "slug": "BRAZE_CREATE_EMAIL_TEMPLATE",
138471
+ "name": "Create Email Template",
138472
+ "description": "Persist an HTML email template on Braze's Templates & Media page. This creates template content only; it does not send or deliver an email."
138473
+ },
138474
+ {
138475
+ "slug": "BRAZE_CREATE_MEDIA_LIBRARY_ASSET",
138476
+ "name": "Create Media Library Asset",
138477
+ "description": "Upload one asset to Braze from a public HTTP(S) URL or local file. URL mode sends JSON; local-file mode uses the multipart asset_file contract implemented by Braze's official MCP server and does not send base64. Images, vectors, and documents are limited to 5 MB; ZIP files are limited to 50 MB total and 5 MB per supported root-level file. Videos and VCF files are dashboard-only. Media Library Public APIs must be enabled; free-trial workspaces have a default 200-asset limit. Rate limit: 100/hour."
138478
+ },
138479
+ {
138480
+ "slug": "BRAZE_CREATE_MESSAGE_SCHEDULE",
138481
+ "name": "Create Message Schedule",
138482
+ "description": "HIGH IMPACT: schedule API-only channel messages for future processing. Individual targets are limited to 50 combined IDs and aliases; otherwise explicit broadcast=true is required. Requires messages.schedule.create. The returned schedule and dispatch IDs confirm acceptance only and never delivery; rendered payload size, subscription state, and channel eligibility remain gates."
138483
+ },
138484
+ {
138485
+ "slug": "BRAZE_CREATE_PREFERENCE_CENTER",
138486
+ "name": "Create Preference Center",
138487
+ "description": "HIGH IMPACT: durably create and optionally activate a Braze-hosted preference center. Its name cannot be changed after creation. Confirm HTML, state, and identifiers before calling. Limited to 10 requests/minute per workspace; Braze publishes no separate plan-tier gate."
138488
+ },
138489
+ {
138490
+ "slug": "BRAZE_CREATE_SDK_AUTHENTICATION_KEY",
138491
+ "name": "Create SDK Authentication Key",
138492
+ "description": "HIGH IMPACT SECURITY OPERATION: create an SDK Authentication key from an RSA public key for one exact app. Set make_primary only when the new key should immediately replace the current primary key. Never submit private-key material. Braze permits at most three keys per app. Success is rejected unless Braze returns a new key ID. Default rate limit: 250,000 requests/hour."
138493
+ },
138494
+ {
138495
+ "slug": "BRAZE_CREATE_SEND_ID",
138496
+ "name": "Create Send ID",
138497
+ "description": "Create or assign a send ID for programmatic message-performance tracking. Every explicit campaign_id and send_id combination counts toward the workspace limit of 100 custom send IDs/day. Requires sends.id.create; this action creates tracking identity and does not send a message."
138498
+ },
138499
+ {
138500
+ "slug": "BRAZE_CREATE_USER_ALIASES",
138501
+ "name": "Create User Aliases",
138502
+ "description": "Add up to 50 Braze aliases to existing external-ID users or create alias-only profiles. Requires users.alias.new. Duplicate alias-label/name pairs can return success without changing a profile; a 201-style success is acceptance, not proof that every alias was attached. Shares a 20,000 requests/minute rate limit."
138503
+ },
138504
+ {
138505
+ "slug": "BRAZE_DELETE_CAMPAIGN_TRIGGER_SCHEDULE",
138506
+ "name": "Delete Campaign Trigger Schedule",
138507
+ "description": "HIGH IMPACT: durably cancel a scheduled API-triggered campaign before send time. This cannot undo sends already processed. Last-second cancellation is best-effort and may affect all, some, or none of the target users. Requires campaigns.trigger.schedule.delete; an accepted response is not proof that no sends occurred."
138508
+ },
138509
+ {
138510
+ "slug": "BRAZE_DELETE_CANVAS_TRIGGER_SCHEDULE",
138511
+ "name": "Delete Canvas Trigger Schedule",
138512
+ "description": "HIGH IMPACT: durably cancel a scheduled API-triggered Canvas before entry time. This cannot undo entries already processed. Last-second cancellation is best-effort and may affect all, some, or none of the target users. Requires canvas.trigger.schedule.delete; acceptance is not proof that no Canvas entries occurred."
138513
+ },
138514
+ {
138515
+ "slug": "BRAZE_DELETE_CATALOG",
138516
+ "name": "Delete Catalog",
138517
+ "description": "Permanently delete one Braze catalog and all of its contents by exact catalog name through DELETE /catalogs/{catalog_name}. This cannot be undone and requires catalogs.delete permission."
138518
+ },
138519
+ {
138520
+ "slug": "BRAZE_DELETE_CATALOG_FIELD",
138521
+ "name": "Delete Catalog Field",
138522
+ "description": "Asynchronously request deletion of one field by exact catalog and field name. Requires the immutable catalogs.delete_fields API-key permission and shares a 50 requests/minute field/selection limit. Fields used by a selection or as an inventory field cannot be deleted. A 202 response is acceptance, not completion."
138523
+ },
138524
+ {
138525
+ "slug": "BRAZE_DELETE_CATALOG_ITEM",
138526
+ "name": "Delete Catalog Item",
138527
+ "description": "Request deletion of one catalog item by exact catalog name and item ID. HTTP 202 with message=success confirms acceptance, not terminal deletion. Requires the immutable catalogs.delete_item API-key permission and shares a 50 requests/minute synchronous item limit."
138528
+ },
138529
+ {
138530
+ "slug": "BRAZE_DELETE_CATALOG_ITEMS",
138531
+ "name": "Delete Multiple Catalog Items",
138532
+ "description": "Asynchronously request deletion of up to 50 catalog items by exact IDs. Requires the immutable catalogs.delete_items API-key permission and shares a 16,000 requests/minute asynchronous item limit. A 202 response is only request acceptance; Braze returns no documented job ID or per-item deletion proof."
138533
+ },
138534
+ {
138535
+ "slug": "BRAZE_DELETE_CATALOG_SELECTION",
138536
+ "name": "Delete Catalog Selection",
138537
+ "description": "Asynchronously request deletion of a selection by exact catalog and selection name. Requires the immutable catalogs.delete_selection API-key permission and shares a 50 requests/minute field/selection limit. A 202 response confirms acceptance only; Braze documents no terminal deletion result."
138538
+ },
138539
+ {
138540
+ "slug": "BRAZE_DELETE_MESSAGE_SCHEDULE",
138541
+ "name": "Delete Message Schedule",
138542
+ "description": "HIGH IMPACT: durably cancel an API-only message schedule before it is sent. This cannot undo a send already processed. Requires messages.schedule.delete. An accepted cancellation does not prove that a send already being processed was stopped."
138543
+ },
138544
+ {
138545
+ "slug": "BRAZE_DELETE_SDK_AUTHENTICATION_KEY",
138546
+ "name": "Delete SDK Authentication Key",
138547
+ "description": "HIGH IMPACT SECURITY OPERATION: permanently delete one exact non-primary SDK Authentication key from one exact app. Braze refuses deletion of the primary key; select another primary first. Success is rejected unless the returned remaining-key list excludes the exact requested key ID. Default rate limit: 250,000 requests/hour."
138548
+ },
138549
+ {
138550
+ "slug": "BRAZE_DELETE_USERS",
138551
+ "name": "Delete Users",
138552
+ "description": "Permanently queue deletion of up to 50 users using exactly one identifier type. Requires users.delete and shares a 20,000 requests/minute rate limit. This cannot be undone; success reports queued count, not completion, and cache propagation can take up to five minutes."
138553
+ },
138554
+ {
138555
+ "slug": "BRAZE_DUPLICATE_CAMPAIGN",
138556
+ "name": "Duplicate Campaign",
138557
+ "description": "HIGH IMPACT: request an asynchronous, durable duplicate of a Braze campaign. The duplicate persists until explicitly deleted and can consume workspace campaign capacity. HTTP 202 confirms only that Braze accepted the request, not that campaign creation completed. Existing tags only; a supplied tag list replaces source tags. Requires campaigns.duplicate and is limited to 100 calls/minute."
138558
+ },
138559
+ {
138560
+ "slug": "BRAZE_DUPLICATE_CANVAS",
138561
+ "name": "Duplicate Canvas",
138562
+ "description": "HIGH IMPACT: request an asynchronous, durable duplicate of a Braze Canvas. The duplicate persists until explicitly deleted and can consume workspace Canvas capacity. HTTP 202 confirms only acceptance, not completed Canvas creation. Existing tags only; a supplied tag list replaces source tags. Requires canvas.duplicate and is limited to 100 calls/minute."
138563
+ },
138564
+ {
138565
+ "slug": "BRAZE_END_LIVE_ACTIVITY",
138566
+ "name": "End Live Activity",
138567
+ "description": "IRREVERSIBLE: end an SDK-registered iOS Live Activity with a final ContentState. An optional past dismissal_date removes it from the UI immediately. Requires messages.live_activity.update. HTTP 201 confirms receipt only, not APNs dispatch, display, dismissal, or delivery. An ended activity cannot be resumed."
138568
+ },
138569
+ {
138570
+ "slug": "BRAZE_EXPORT_GLOBAL_CONTROL_GROUP_USERS",
138571
+ "name": "Export Global Control Group Users",
138572
+ "description": "Start an asynchronous export of all current Global Control Group users. The response only acknowledges dispatch and identifies files; completion arrives through the callback, temporary URL, or configured cloud storage. Files are generally split per 5,000 users."
138573
+ },
138574
+ {
138575
+ "slug": "BRAZE_EXPORT_SEGMENT_USERS",
138576
+ "name": "Export Segment Users",
138577
+ "description": "Start an asynchronous newline-delimited JSON export for one segment. The response acknowledges dispatch, not completion. Only one export per segment may run at once, with at most 100 concurrent segment exports company-wide; event, purchase, campaign, and Canvas history fields contain 90 days of detail."
138578
+ },
138579
+ {
138580
+ "slug": "BRAZE_EXPORT_USERS_BY_IDENTIFIERS",
138581
+ "name": "Export Users by Identifiers",
138582
+ "description": "Return user profiles matching one or more Braze, external, alias, device, email, or phone identifiers; this reads profiles and does not track events or consume data points."
138583
+ },
138584
+ {
138585
+ "slug": "BRAZE_GENERATE_PREFERENCE_CENTER_URL",
138586
+ "name": "Generate Preference Center URL",
138587
+ "description": "Generate a user-specific URL for an API-created or drag-and-drop Braze preference center. HIGH IMPACT: the returned URL is a sensitive capability that can change that user's subscriptions. Do not log, publish, or share it. This does not support legacy preference centers. Limited to 1,000 requests/minute per workspace."
138588
+ },
138589
+ {
138590
+ "slug": "BRAZE_GET_CAMPAIGN",
138591
+ "name": "Get Campaign",
138592
+ "description": "Return configuration and delivery details for one campaign identified by its Braze campaign ID."
138593
+ },
138594
+ {
138595
+ "slug": "BRAZE_GET_CAMPAIGN_ANALYTICS",
138596
+ "name": "Get Campaign Analytics",
138597
+ "description": "Get up to 100 daily campaign analytics points. Dashboard and Currents aggregation definitions can differ."
138598
+ },
138599
+ {
138600
+ "slug": "BRAZE_GET_CAMPAIGN_TRANSLATION_SOURCE",
138601
+ "name": "Get Campaign Translation Source",
138602
+ "description": "Read the default source values inside translation tags for one campaign message variation. Requires campaigns.translations.get, translation tags on a multi-language message, and observes a 250,000 requests/minute limit."
138603
+ },
138604
+ {
138605
+ "slug": "BRAZE_GET_CANVAS",
138606
+ "name": "Get Canvas",
138607
+ "description": "Return configuration and step details for one Canvas identified by its Braze Canvas ID."
138608
+ },
138609
+ {
138610
+ "slug": "BRAZE_GET_CANVAS_ANALYTICS",
138611
+ "name": "Get Canvas Analytics",
138612
+ "description": "Export Canvas daily time-series analytics with optional variant, step, and deleted-step breakdowns. Dashboard and Currents definitions can differ."
138613
+ },
138614
+ {
138615
+ "slug": "BRAZE_GET_CANVAS_ANALYTICS_SUMMARY",
138616
+ "name": "Get Canvas Analytics Summary",
138617
+ "description": "Export Canvas analytics rollups with optional variant, step, and deleted-step breakdowns. Braze normalizes range timestamps to midnight in the company time zone."
138618
+ },
138619
+ {
138620
+ "slug": "BRAZE_GET_CANVAS_TRANSLATION_SOURCE",
138621
+ "name": "Get Canvas Translation Source",
138622
+ "description": "Read default source values inside translation tags for one Canvas step message variation. Requires canvas.translations.get, translation tags on a multi-language message, and observes a 250,000 requests/minute limit."
138623
+ },
138624
+ {
138625
+ "slug": "BRAZE_GET_CATALOG_ITEM",
138626
+ "name": "Get Catalog Item",
138627
+ "description": "Return one Braze catalog item by exact catalog name and item ID. Requires the immutable catalogs.get_item API-key permission and shares a 50 requests/minute limit with synchronous catalog item endpoints."
138628
+ },
138629
+ {
138630
+ "slug": "BRAZE_GET_CONTENT_BLOCK",
138631
+ "name": "Get Content Block",
138632
+ "description": "Return one persisted Braze Content Block by API identifier, optionally with its current campaign and Canvas inclusion records."
138633
+ },
138634
+ {
138635
+ "slug": "BRAZE_GET_CONTENT_BLOCK_TRANSLATION_SOURCE",
138636
+ "name": "Get Content Block Translation Source",
138637
+ "description": "Read default source values inside one Content Block's translation tags. Requires content_blocks.translations.get, configured translation tags, and observes a 250,000 requests/minute limit."
138638
+ },
138639
+ {
138640
+ "slug": "BRAZE_GET_CUSTOM_EVENT_ANALYTICS",
138641
+ "name": "Get Custom Event Analytics",
138642
+ "description": "Get 1 to 100 daily or hourly occurrence counts for one custom event, optionally filtered by app and analytics-enabled segment."
138643
+ },
138644
+ {
138645
+ "slug": "BRAZE_GET_EMAIL_TEMPLATE",
138646
+ "name": "Get Email Template",
138647
+ "description": "Return one stored HTML email template by API identifier. Braze does not accept drag-and-drop-editor templates on this endpoint."
138648
+ },
138649
+ {
138650
+ "slug": "BRAZE_GET_EMAIL_TEMPLATE_TRANSLATION_SOURCE",
138651
+ "name": "Get Email Template Translation Source",
138652
+ "description": "Read default source values inside an email template's translation tags. This source endpoint specifically requires templates.email.info, plus a multi-language template, and observes a 250,000 requests/minute limit."
138653
+ },
138654
+ {
138655
+ "slug": "BRAZE_GET_PREFERENCE_CENTER",
138656
+ "name": "Get Preference Center",
138657
+ "description": "Get persisted HTML, state, options, identifiers, and timestamps for one Braze preference center. Limited to 1,000 requests/minute per workspace."
138658
+ },
138659
+ {
138660
+ "slug": "BRAZE_GET_PURCHASE_SERIES",
138661
+ "name": "Get Purchase Series",
138662
+ "description": "Get 1 to 100 daily or hourly purchase quantity or revenue points, optionally filtered by app and product. The selected metric determines the exact Braze purchase endpoint."
138663
+ },
138664
+ {
138665
+ "slug": "BRAZE_GET_SEGMENT",
138666
+ "name": "Get Segment",
138667
+ "description": "Return Braze's documented configuration details for one segment identified by its segment API identifier."
138668
+ },
138669
+ {
138670
+ "slug": "BRAZE_GET_SEGMENT_ANALYTICS",
138671
+ "name": "Get Segment Analytics",
138672
+ "description": "Get up to 100 daily estimated segment-size points. Export and count segment users when an exact size is required."
138673
+ },
138674
+ {
138675
+ "slug": "BRAZE_GET_SEND_ANALYTICS",
138676
+ "name": "Get Send Analytics",
138677
+ "description": "Get up to 100 daily analytics points for a tracked send from an API campaign. Braze retains send analytics for 14 days after the send and attributes campaign conversions to the most recent send_id received by each user. Counts may not match dashboard analytics or Currents one-for-one because aggregation windows and definitions differ."
138678
+ },
138679
+ {
138680
+ "slug": "BRAZE_GET_SESSION_ANALYTICS",
138681
+ "name": "Get Session Analytics",
138682
+ "description": "Get 1 to 100 daily or hourly session-count points, optionally filtered by app and analytics-enabled segment."
138683
+ },
138684
+ {
138685
+ "slug": "BRAZE_GET_SUBSCRIPTION_GROUP_STATUS",
138686
+ "name": "Get Subscription Group Status",
138687
+ "description": "Get saved membership status for up to 50 users in one exact subscription group. External IDs take query precedence if also supplied; email and phone cannot be combined. Results are Subscribed, Unsubscribed, or Unknown and do not include the overriding global email state. Default rate limit: 250,000 requests/hour."
138688
+ },
138689
+ {
138690
+ "slug": "BRAZE_GET_USER_KPI_SERIES",
138691
+ "name": "Get User KPI Series",
138692
+ "description": "Get 1 to 100 points for one user KPI: daily active users, rolling 30-day monthly active users, daily new users, or daily uninstalls. Optionally filter to one Braze app. The selected metric determines the exact Braze KPI endpoint."
138693
+ },
138694
+ {
138695
+ "slug": "BRAZE_GET_WEBHOOK_TEMPLATE_TRANSLATION_SOURCE",
138696
+ "name": "Get Webhook Template Translation Source",
138697
+ "description": "Read default source values inside a webhook template's translation tags. Requires templates.translations.get and webhook template translations enabled by Braze; otherwise Braze may return FEATURE_NOT_ENABLED. The endpoint has a 250,000 requests/minute limit."
138698
+ },
138699
+ {
138700
+ "slug": "BRAZE_IDENTIFY_USERS",
138701
+ "name": "Identify Users",
138702
+ "description": "Assign external IDs to alias-only, email-only, or phone-only Braze profiles, merging into an existing identified profile when applicable. This is irreversible when a merge occurs: the source alias-only, email-only, or phone-only profile is removed after its data is transferred. Requires users.identify and shares a 20,000 requests/minute rate limit. A 201 success only confirms acceptance: case mismatches, duplicate matches, or prioritization can produce no merge."
138703
+ },
138704
+ {
138705
+ "slug": "BRAZE_LIST_CAMPAIGNS",
138706
+ "name": "List Campaigns",
138707
+ "description": "Return one page of Braze campaigns for discovery, optionally including archived campaigns and filtering by last edit time."
138708
+ },
138709
+ {
138710
+ "slug": "BRAZE_LIST_CAMPAIGN_TRANSLATIONS",
138711
+ "name": "List Campaign Translations",
138712
+ "description": "View every configured locale translation map for one campaign message variation, or filter by locale. Requires campaigns.translations.get, multi-language support on the message, and observes a 250,000 requests/minute limit."
138713
+ },
138714
+ {
138715
+ "slug": "BRAZE_LIST_CANVASES",
138716
+ "name": "List Canvases",
138717
+ "description": "Return one fixed provider page of up to 100 Braze Canvases for discovery, optionally including archived Canvases and filtering by last edit time. Braze exposes no page-size control; returning the complete page avoids losing continuation records. A local 10-item cap would save context tokens, not provider requests."
138718
+ },
138719
+ {
138720
+ "slug": "BRAZE_LIST_CANVAS_TRANSLATIONS",
138721
+ "name": "List Canvas Translations",
138722
+ "description": "Preview configured locale translations for one Canvas step message variation. Requires canvas.translations.get, multi-language support on the message, and observes a 250,000 requests/minute limit."
138723
+ },
138724
+ {
138725
+ "slug": "BRAZE_LIST_CATALOG_ITEMS",
138726
+ "name": "List Catalog Items",
138727
+ "description": "Return one fixed provider page of up to 50 items from a Braze catalog, preserving arbitrary item attributes and exposing Braze Link-header pagination. Braze exposes no page-size control; returning the complete page avoids losing continuation records. A local 10-item cap would save context tokens, not provider requests. Requires the immutable catalogs.get_items API-key permission and shares the 50 requests/minute synchronous catalog item limit."
138728
+ },
138729
+ {
138730
+ "slug": "BRAZE_LIST_CATALOGS",
138731
+ "name": "List Catalogs",
138732
+ "description": "Return all catalogs in the connected Braze workspace. Braze exposes no page-size control or resumable boundary, so a local 10-item cap would hide catalogs and save context tokens, not provider requests."
138733
+ },
138734
+ {
138735
+ "slug": "BRAZE_LIST_CLOUD_DATA_INGESTION_INTEGRATIONS",
138736
+ "name": "List Cloud Data Ingestion Integrations",
138737
+ "description": "Return one 10-item page of configured Cloud Data Ingestion integrations. Requires the workspace's Cloud Data Ingestion entitlement and has a 50 requests/minute limit."
138738
+ },
138739
+ {
138740
+ "slug": "BRAZE_LIST_CLOUD_DATA_INGESTION_SYNC_STATUSES",
138741
+ "name": "List Cloud Data Ingestion Sync Statuses",
138742
+ "description": "Return one 10-item page of sync statuses for a Cloud Data Ingestion integration. Requires the workspace's CDI entitlement and has a 100 requests/minute limit."
138743
+ },
138744
+ {
138745
+ "slug": "BRAZE_LIST_CONTENT_BLOCKS",
138746
+ "name": "List Content Blocks",
138747
+ "description": "Return one offset-based page of persisted Braze Content Blocks. Omit offset on the first call and use next_request only when it is returned."
138748
+ },
138749
+ {
138750
+ "slug": "BRAZE_LIST_CONTENT_BLOCK_TRANSLATIONS",
138751
+ "name": "List Content Block Translations",
138752
+ "description": "View every configured locale translation map for one Content Block, or filter by locale. Requires content_blocks.translations.get, multi-language translation tags on the block, and observes a 250,000 requests/minute limit."
138753
+ },
138754
+ {
138755
+ "slug": "BRAZE_LIST_CUSTOM_ATTRIBUTES",
138756
+ "name": "List Custom Attributes",
138757
+ "description": "Return one fixed provider page of up to 50 alphabetically sorted custom-attribute definitions and a Link-header continuation cursor. Braze exposes no page-size control; returning the complete page avoids losing continuation records. A local 10-item cap would save context tokens, not provider requests."
138758
+ },
138759
+ {
138760
+ "slug": "BRAZE_LIST_CUSTOM_EVENT_NAMES",
138761
+ "name": "List Custom Event Names",
138762
+ "description": "Return one fixed provider page of up to 250 alphabetically sorted custom event names. Braze exposes no page-size control; returning the complete page avoids losing continuation records. A local 10-item cap would save context tokens, not provider requests."
138763
+ },
138764
+ {
138765
+ "slug": "BRAZE_LIST_CUSTOM_EVENTS",
138766
+ "name": "List Custom Events",
138767
+ "description": "Return one fixed provider page of up to 50 alphabetically sorted custom-event definitions and a Link-header continuation cursor. Braze exposes no page-size control; returning the complete page avoids losing continuation records. A local 10-item cap would save context tokens, not provider requests."
138768
+ },
138769
+ {
138770
+ "slug": "BRAZE_LIST_EMAIL_TEMPLATE_LOCALE_TRANSLATIONS",
138771
+ "name": "List Email Template Locale Translations",
138772
+ "description": "View email template translations, optionally filtered to one locale. Braze documents locale_id as optional: when omitted, this action sends no locale filter and returns Braze's translation-list response without asserting which locales Braze will include. Requires templates.translations.get, a multi-language template, and observes a 250,000 requests/minute limit."
138773
+ },
138774
+ {
138775
+ "slug": "BRAZE_LIST_EMAIL_TEMPLATES",
138776
+ "name": "List Email Templates",
138777
+ "description": "Return one offset-based page of stored HTML email templates. Drag-and-drop templates are excluded; omit offset on the first call."
138778
+ },
138779
+ {
138780
+ "slug": "BRAZE_LIST_EMAIL_TEMPLATE_TRANSLATIONS",
138781
+ "name": "List Email Template Translations",
138782
+ "description": "View all configured translations and locales for one email template. Requires templates.translations.get, a multi-language template, and observes a 250,000 requests/minute limit."
138783
+ },
138784
+ {
138785
+ "slug": "BRAZE_LIST_HARD_BOUNCED_EMAILS",
138786
+ "name": "List Hard Bounced Emails",
138787
+ "description": "Return one newest-first offset page of hard-bounced emails. end_date and either start_date or email are required; an email lookup takes precedence over dates. Increase offset until a page has fewer than limit. Default rate limit: 250,000 requests/hour."
138788
+ },
138789
+ {
138790
+ "slug": "BRAZE_LIST_INVALID_PHONE_NUMBERS",
138791
+ "name": "List Invalid Phone Numbers",
138792
+ "description": "Return one newest-first offset page of invalid SMS numbers by UTC date range, or check exact E.164 numbers. Exact numbers take precedence over dates. Reasons are provider_error or deactivated. Increase offset until a page has fewer than limit. Default rate limit: 250,000 requests/hour."
138793
+ },
138794
+ {
138795
+ "slug": "BRAZE_LIST_PREFERENCE_CENTERS",
138796
+ "name": "List Preference Centers",
138797
+ "description": "List all available Braze preference centers and their IDs and timestamps. Braze exposes no page-size control or resumable boundary, so a local 10-item cap would hide centers and save context tokens, not provider requests. Limited to 1,000 requests/minute per workspace. Braze publishes no separate plan-tier gate."
138798
+ },
138799
+ {
138800
+ "slug": "BRAZE_LIST_PURCHASE_PRODUCTS",
138801
+ "name": "List Purchase Products",
138802
+ "description": "Return every product ID from an optional caller-selected provider page. Braze documents page as a string but does not publish a page size, continuation token, or terminal marker, so a local 10-item cap could hide products and would save context tokens, not provider requests."
138803
+ },
138804
+ {
138805
+ "slug": "BRAZE_LIST_SCHEDULED_BROADCASTS",
138806
+ "name": "List Scheduled Broadcasts",
138807
+ "description": "List dashboard and API scheduled campaigns and Canvas entries through an ISO 8601 end date. Recurring broadcasts appear only once at their next occurrence. Braze exposes no page-size control or resumable boundary, so a local 10-item cap would hide broadcasts and save context tokens, not provider requests. Requires messages.schedule_broadcasts and uses the default 250,000 requests/hour limit."
138808
+ },
138809
+ {
138810
+ "slug": "BRAZE_LIST_SDK_AUTHENTICATION_KEYS",
138811
+ "name": "List SDK Authentication Keys",
138812
+ "description": "HIGH IMPACT SECURITY READ: list all SDK Authentication public keys, IDs, descriptions, and primary status for one exact app. Braze exposes no page-size control or resumable boundary, so a local 10-item cap would hide security inventory and save context tokens, not provider requests. The response contains RSA public keys, never private keys. Restrict output handling because key inventory supports security administration. Default rate limit: 250,000 requests/hour."
138813
+ },
138814
+ {
138815
+ "slug": "BRAZE_LIST_SEGMENTS",
138816
+ "name": "List Segments",
138817
+ "description": "Return one fixed provider page of up to 100 Braze segments and their IDs for audience discovery. Braze exposes no page-size control; returning the complete page avoids losing continuation records. A local 10-item cap would save context tokens, not provider requests. Archived segments are excluded by Braze and cannot be requested from this endpoint."
138818
+ },
138819
+ {
138820
+ "slug": "BRAZE_LIST_UNSUBSCRIBED_EMAILS",
138821
+ "name": "List Unsubscribed Emails",
138822
+ "description": "Return one offset page of latest unsubscribe records for a UTC date range or exact email. end_date and either start_date or email are required. This is latest state, not full history; use Currents for history. Default rate limit: 250,000 requests/hour."
138823
+ },
138824
+ {
138825
+ "slug": "BRAZE_LIST_USER_SUBSCRIPTION_GROUPS",
138826
+ "name": "List User Subscription Groups",
138827
+ "description": "Return one offset page of subscription groups that have status history for users selected by exactly one email or phone identifier type. Newly created groups with no user update are omitted. limit defaults to 10 and cannot exceed 100. Default rate limit: 250,000 requests/hour."
138828
+ },
138829
+ {
138830
+ "slug": "BRAZE_LIST_WEBHOOK_TEMPLATE_TRANSLATIONS",
138831
+ "name": "List Webhook Template Translations",
138832
+ "description": "View configured translations for one webhook template, optionally filtered by locale. Requires templates.translations.get and webhook template translations enabled by Braze; otherwise Braze may return FEATURE_NOT_ENABLED. The endpoint has a 250,000 requests/minute limit."
138833
+ },
138834
+ {
138835
+ "slug": "BRAZE_MERGE_USERS",
138836
+ "name": "Merge Users",
138837
+ "description": "Asynchronously merge up to 50 Braze source profiles into retained target profiles. Each completed merge is irreversible: the source profile is removed after its data is transferred to the retained target. Requires users.merge and shares a 20,000 requests/minute rate limit. Target values take precedence for existing attributes; counters and selected dates are combined. A 202 success confirms acceptance only, and invalid non-E.164 stored phones can cause a silent skipped merge."
138838
+ },
138839
+ {
138840
+ "slug": "BRAZE_REMOVE_EXTERNAL_IDS",
138841
+ "name": "Remove Deprecated External IDs",
138842
+ "description": "Permanently remove up to 50 deprecated Braze external IDs. Requires users.external_ids.remove and is limited to 1,000 requests/minute. Primary IDs cannot be removed; inspect removal_errors because valid requests can partially fail."
138843
+ },
138844
+ {
138845
+ "slug": "BRAZE_REMOVE_HARD_BOUNCED_EMAILS",
138846
+ "name": "Remove Hard Bounced Emails",
138847
+ "description": "HIGH IMPACT: remove one to 50 exact addresses from both the Braze bounce list and the email provider's bounce list, potentially making them deliverable again. Revalidate ownership and deliverability first. Success is rejected unless Braze explicitly returns message=success. Default rate limit: 250,000 requests/hour."
138848
+ },
138849
+ {
138850
+ "slug": "BRAZE_REMOVE_INVALID_PHONE_NUMBERS",
138851
+ "name": "Remove Invalid Phone Numbers",
138852
+ "description": "HIGH IMPACT: remove one to 50 exact E.164 numbers from Braze's invalid list so they can be revalidated and may receive SMS again. Confirm number ownership and deliverability first. Success is rejected unless Braze explicitly returns message=success. Default rate limit: 250,000 requests/hour."
138853
+ },
138854
+ {
138855
+ "slug": "BRAZE_REMOVE_SPAM_EMAILS",
138856
+ "name": "Remove Emails From Spam List",
138857
+ "description": "HIGH IMPACT: remove one to 50 exact addresses from both the Braze spam list and the email provider's spam list, potentially making them deliverable again. Confirm recipient consent first. Success is rejected unless Braze explicitly returns message=success. Default rate limit: 250,000 requests/hour."
138858
+ },
138859
+ {
138860
+ "slug": "BRAZE_RENAME_EXTERNAL_IDS",
138861
+ "name": "Rename External IDs",
138862
+ "description": "Rename up to 50 primary Braze external IDs, preserving each old ID as deprecated. Requires users.external_ids.rename, is limited to 1,000 requests/minute, logs no data points, and does not affect MAU. Items process independently; inspect rename_errors and later remove deprecated IDs when migration is complete."
138863
+ },
138864
+ {
138865
+ "slug": "BRAZE_REPLACE_CATALOG_ITEM",
138866
+ "name": "Replace Catalog Item",
138867
+ "description": "Synchronously replace a Braze catalog item, creating it if item_id does not exist. Requires the immutable catalogs.replace_item API-key permission and shares a 50 requests/minute synchronous item limit."
138868
+ },
138869
+ {
138870
+ "slug": "BRAZE_REPLACE_CATALOG_ITEMS",
138871
+ "name": "Replace Multiple Catalog Items",
138872
+ "description": "Asynchronously replace or create up to 50 Braze catalog items by id. Requires the immutable catalogs.replace_items API-key permission and shares a 16,000 requests/minute asynchronous item limit. Catalog storage limits can reject the request. A 202 response is acceptance only, with no documented job or terminal result."
138873
+ },
138874
+ {
138875
+ "slug": "BRAZE_REPLACE_MEDIA_LIBRARY_ASSET_FILE",
138876
+ "name": "Replace Media Library Asset File",
138877
+ "description": "HIGH IMPACT: request replacement of the file associated with one exact Braze media-library asset ID using a public HTTP(S) URL. The existing asset ID and hosted URL are preserved only when Braze confirms success. The replacement extension must exactly match. Replacement supports images, SVGs, documents, fonts, contact cards, and code files; video is unsupported and provider-enforced size limits apply. This action supports the implemented asset_url mode only and does not claim replacement from HTTP status alone. Rate limit: 100/hour."
138878
+ },
138879
+ {
138880
+ "slug": "BRAZE_SEND_CAMPAIGN_TRIGGER",
138881
+ "name": "Send Campaign Trigger",
138882
+ "description": "HIGH IMPACT: immediately request an API-triggered campaign send. Provide up to 50 recipients, optionally intersected with a Connected Audience. Audience-only targeting requires broadcast=true; broadcast cannot include individual recipients. An accepted send cannot be retracted. Recipient attributes can update a profile or, with send_to_existing_only=false and an external ID, create a profile. Requires an active dashboard API-triggered campaign and campaigns.trigger.send. A dispatch ID means Braze accepted one batched transmission; it does not prove per-user dispatch or delivery. Per-recipient errors are returned."
138883
+ },
138884
+ {
138885
+ "slug": "BRAZE_SEND_CANVAS_TRIGGER",
138886
+ "name": "Send Canvas Trigger",
138887
+ "description": "HIGH IMPACT: immediately request entry into an API-triggered Canvas. Provide up to 50 recipients, optionally intersected with a Connected Audience. Audience-only targeting requires broadcast=true; broadcast cannot include individual recipients. Accepted entry cannot be retracted. Recipient attributes can update a profile or, with send_to_existing_only=false and an external ID, create a profile. Requires canvas.trigger.send and an active Canvas. A paused or archived 201 response is rejected because no entry occurs. A dispatch ID is acceptance, never proof of message delivery; per-recipient errors are preserved."
138888
+ },
138889
+ {
138890
+ "slug": "BRAZE_SEND_MESSAGES",
138891
+ "name": "Send API-Only Messages",
138892
+ "description": "HIGH IMPACT: immediately request API-only messages to existing Braze users. Individual targets are limited to 50 combined external IDs and aliases; without individuals you must explicitly set broadcast=true with a segment or Connected Audience. An accepted send cannot be retracted. Requires messages.send. Channel payloads enforce documented required fields, enums, and exclusions; rendered payload size and channel eligibility are provider gates, and a dispatch ID confirms acceptance only, not recipient dispatch or delivery."
138893
+ },
138894
+ {
138895
+ "slug": "BRAZE_SEND_TRANSACTIONAL_CAMPAIGN",
138896
+ "name": "Send Transactional Campaign",
138897
+ "description": "HIGH IMPACT: send one immediate transactional email from a Braze Transactional Email campaign to exactly one external-ID or alias recipient; an accepted send cannot be retracted. Recipient attributes can update a profile or create a missing external-ID profile before sending. This is a select-package paid capability requiring an active transactional campaign, transactional.send, and hourly units. external_send_id deduplicates for 24 hours. sent and processed are not delivery; aborted and bounced are terminal failures, while delivered confirms inbox-provider acceptance."
138898
+ },
138899
+ {
138900
+ "slug": "BRAZE_SET_EMAIL_SUBSCRIPTION_STATUS",
138901
+ "name": "Set Global Email Subscription Status",
138902
+ "description": "HIGH IMPACT: set the global email subscription state for one to 50 exact addresses, including addresses not yet attached to a profile. Global unsubscribed overrides every subscription group. Success is rejected unless Braze explicitly returns message=success. Default rate limit: 250,000 requests/hour."
138903
+ },
138904
+ {
138905
+ "slug": "BRAZE_SET_PRIMARY_SDK_AUTHENTICATION_KEY",
138906
+ "name": "Set Primary SDK Authentication Key",
138907
+ "description": "HIGH IMPACT SECURITY OPERATION: make one exact existing SDK Authentication key the primary key for one exact app. This changes which key new SDK clients should use. Success is rejected unless the returned key list marks that exact key primary. Default rate limit: 250,000 requests/hour."
138908
+ },
138909
+ {
138910
+ "slug": "BRAZE_SET_SUBSCRIPTION_GROUP_STATUS",
138911
+ "name": "Set Subscription Group Status",
138912
+ "description": "HIGH IMPACT: batch subscribe or unsubscribe up to 50 users in one exact group. Email-only or phone-only calls can affect every profile sharing the identifier; external IDs may be combined with one channel identifier. Orphaned channel states persist up to 30 days. LINE group use requires approval from the Braze customer success manager. message=success confirms acceptance only, not the resulting state. In particular, SMS double opt-in can no-op when no user profile exists. Shared V1/V2 rate limit: 5,000 requests/minute."
138913
+ },
138914
+ {
138915
+ "slug": "BRAZE_SET_SUBSCRIPTION_GROUP_STATUSES",
138916
+ "name": "Set Subscription Group Statuses",
138917
+ "description": "HIGH IMPACT: batch subscribe or unsubscribe users across multiple groups. Each group update must use exactly one of external_ids, emails, or E.164 phones; only external IDs may span email and SMS groups in one call. Orphaned channel states persist up to 30 days. LINE group use requires approval from the Braze customer success manager. message=success confirms acceptance only, not resulting states. In particular, SMS double opt-in can no-op when no user profile exists. Shared V1/V2 rate limit: 5,000 requests/minute."
138918
+ },
138919
+ {
138920
+ "slug": "BRAZE_START_LIVE_ACTIVITY",
138921
+ "name": "Start Live Activity",
138922
+ "description": "HIGH IMPACT: remotely request an iOS Live Activity start for exactly one target mode: up to 50 external users, one Connected Audience, or one segment. Requires Swift SDK push-to-start setup, matching ActivityAttributes and ContentState shapes, payload-size compliance, and messages.live_activity.start. HTTP 201 means Braze received a valid request; it does not prove APNs dispatch, display, or delivery."
138923
+ },
138924
+ {
138925
+ "slug": "BRAZE_TRACK_USERS",
138926
+ "name": "Create and Update Users",
138927
+ "description": "Asynchronously ingest Braze attributes, custom events, or purchases, up to 75 combined objects per portable request. Attribute objects can create or update profiles; event and purchase objects are durably recorded. Requires users.track. Each custom attribute consumes a data point; rate limits vary by contract (3,000 requests per three seconds for data-point pricing). Inspect errors because valid requests can partially process, and separate calls are not ordered. Conflicting data may process out of order; wait five minutes between requests containing conflicting data to guarantee final ordering. Callers should batch writes instead of making one-object calls when possible."
138928
+ },
138929
+ {
138930
+ "slug": "BRAZE_TRIGGER_CLOUD_DATA_INGESTION_SYNC",
138931
+ "name": "Trigger Cloud Data Ingestion Sync",
138932
+ "description": "HIGH IMPACT: enqueue a sync for an existing Cloud Data Ingestion integration. This can ingest durable user or non-user data and consume data points. A 202 success only confirms acceptance, not completion; poll sync statuses. Requires CDI entitlement and is limited to 20 requests/minute."
138933
+ },
138934
+ {
138935
+ "slug": "BRAZE_UPDATE_CAMPAIGN_TRANSLATIONS",
138936
+ "name": "Update Campaign Translations",
138937
+ "description": "Submit a durable update request with translation-tag string values for one campaign message locale. This does not publish, launch, send, or prove delivery; read back the translations to verify resulting stored content. A launched campaign must first have its message saved as a draft. Requires campaigns.translations.update and has a 250,000 requests/minute limit."
138938
+ },
138939
+ {
138940
+ "slug": "BRAZE_UPDATE_CAMPAIGN_TRIGGER_SCHEDULE",
138941
+ "name": "Update Campaign Trigger Schedule",
138942
+ "description": "HIGH IMPACT: durably replace the full schedule for a previously scheduled API-triggered campaign. Omitted local or optimal-time flags do not carry forward. Near send time changes are best-effort, and a local-time schedule cannot be updated after its time passed in any zone. Requires campaigns.trigger.schedule.update; the change persists until updated, deleted, or sent, and acceptance does not prove every recipient was changed."
138943
+ },
138944
+ {
138945
+ "slug": "BRAZE_UPDATE_CANVAS_TRANSLATIONS",
138946
+ "name": "Update Canvas Translations",
138947
+ "description": "Submit a durable update request with translation-tag string values for one Canvas step message locale. This does not publish, launch, send, or prove delivery; read back the translations to verify resulting stored content. A launched Canvas must first have its message saved as a draft. Requires canvas.translations.update and has a 250,000 requests/minute limit."
138948
+ },
138949
+ {
138950
+ "slug": "BRAZE_UPDATE_CANVAS_TRIGGER_SCHEDULE",
138951
+ "name": "Update Canvas Trigger Schedule",
138952
+ "description": "HIGH IMPACT: durably replace the full schedule for a previously scheduled API-triggered Canvas. Omitted local or optimal-time flags do not carry forward, and near-send changes are best-effort. Requires canvas.trigger.schedule.update; the change persists until updated, deleted, or entered, and acceptance does not prove every intended entry was changed."
138953
+ },
138954
+ {
138955
+ "slug": "BRAZE_UPDATE_CATALOG_ITEM",
138956
+ "name": "Update Catalog Item",
138957
+ "description": "Synchronously patch one existing Braze catalog item. Requires the immutable catalogs.update_item API-key permission and shares a 50 requests/minute synchronous item limit. The item ID belongs only in the path."
138958
+ },
138959
+ {
138960
+ "slug": "BRAZE_UPDATE_CATALOG_ITEMS",
138961
+ "name": "Update Multiple Catalog Items",
138962
+ "description": "Asynchronously patch up to 50 existing Braze catalog items. Requires the immutable catalogs.update_items API-key permission and shares a 16,000 requests/minute asynchronous item limit. A 202 response confirms acceptance only and supplies no documented job ID, per-item result, or completion proof."
138963
+ },
138964
+ {
138965
+ "slug": "BRAZE_UPDATE_CONTENT_BLOCK",
138966
+ "name": "Update Content Block",
138967
+ "description": "Persist changes to one existing Braze Content Block by API identifier. This updates stored content only; it does not send or deliver a message."
138968
+ },
138969
+ {
138970
+ "slug": "BRAZE_UPDATE_CONTENT_BLOCK_TRANSLATIONS",
138971
+ "name": "Update Content Block Translations",
138972
+ "description": "Submit a durable update request with translation-tag string values for one Content Block locale. This does not publish, send, or prove delivery in a message using the block; read back the translations to verify resulting stored content. Requires content_blocks.translations.update and has a 250,000 requests/minute limit."
138973
+ },
138974
+ {
138975
+ "slug": "BRAZE_UPDATE_EMAIL_TEMPLATE",
138976
+ "name": "Update Email Template",
138977
+ "description": "Persist one or more changes to an existing Braze email template by API identifier. This updates stored content only; it does not send or deliver email."
138978
+ },
138979
+ {
138980
+ "slug": "BRAZE_UPDATE_EMAIL_TEMPLATE_TRANSLATIONS",
138981
+ "name": "Update Email Template Translations",
138982
+ "description": "Submit a durable update request with translation-tag string values for one email template locale. This does not send, schedule, publish, or prove email delivery; read back the translations to verify resulting stored content. Requires templates.translations.update and has a 250,000 requests/minute limit."
138983
+ },
138984
+ {
138985
+ "slug": "BRAZE_UPDATE_LIVE_ACTIVITY",
138986
+ "name": "Update Live Activity",
138987
+ "description": "Update an SDK-registered iOS Live Activity without ending it. Requires matching ContentState shape, payload-size compliance, and messages.live_activity.update. An optional dismissal_date updates when the activity is removed from the UI without ending it. Use END_LIVE_ACTIVITY for the irreversible terminal operation. HTTP 201 confirms receipt only, not APNs dispatch, display, dismissal, or delivery."
138988
+ },
138989
+ {
138990
+ "slug": "BRAZE_UPDATE_MESSAGE_SCHEDULE",
138991
+ "name": "Update Message Schedule",
138992
+ "description": "HIGH IMPACT: durably update the schedule, documented channel message objects, or both for an API-only scheduled message. The replacement persists until updated, deleted, or sent. Requires messages.schedule.update; acceptance confirms neither dispatch nor delivery."
138993
+ },
138994
+ {
138995
+ "slug": "BRAZE_UPDATE_PREFERENCE_CENTER",
138996
+ "name": "Update Preference Center",
138997
+ "description": "HIGH IMPACT: durably update a Braze preference center's required page HTML and confirmation HTML, plus an optional title, state, or options configuration. Omitted title, state, and options are not sent. The immutable name is not accepted. Limited to 10 requests/minute per workspace."
138998
+ },
138999
+ {
139000
+ "slug": "BRAZE_UPDATE_PUSH_CREDENTIALS",
139001
+ "name": "Update Push Credentials",
139002
+ "description": "HIGH IMPACT: replace one app's push credentials for exactly one platform. A bad credential can stop push delivery. Braze documents no endpoint-specific rate limit or public plan gate; the workspace must expose the Apps credential API."
139003
+ },
139004
+ {
139005
+ "slug": "BRAZE_UPDATE_USER_ALIASES",
139006
+ "name": "Update User Aliases",
139007
+ "description": "Asynchronously request renaming of up to 50 existing Braze aliases. Requires users.alias.update and shares a 20,000 requests/minute rate limit. A success response confirms acceptance only, not completion; update ordering is not guaranteed, and a nonmatching old alias may produce no change."
139008
+ },
139009
+ {
139010
+ "slug": "BRAZE_UPDATE_WEBHOOK_TEMPLATE_TRANSLATIONS",
139011
+ "name": "Update Webhook Template Translations",
139012
+ "description": "Submit a durable update request with translation-tag string values for one webhook template locale. This does not invoke, publish, deliver, or prove delivery of a webhook; read back the translations to verify resulting stored content. Requires templates.translations.update and webhook template translations enabled by Braze; otherwise Braze may return FEATURE_NOT_ENABLED. The endpoint has a 250,000 requests/minute limit."
139013
+ }
139014
+ ],
139015
+ "triggers": [],
139016
+ "authConfigDetails": [
139017
+ {
139018
+ "mode": "API_KEY",
139019
+ "name": "braze_api_key",
139020
+ "fields": {
139021
+ "auth_config_creation": {
139022
+ "required": [],
139023
+ "optional": []
139024
+ },
139025
+ "connected_account_initiation": {
139026
+ "required": [
139027
+ {
139028
+ "name": "full",
139029
+ "displayName": "REST Endpoint",
139030
+ "type": "string",
139031
+ "description": "Copy the exact REST endpoint shown for your workspace in Braze under Settings > APIs and Identifiers > API Keys, for example https://rest.iad-01.braze.com or https://rest.fra-01.braze.eu. Use the REST endpoint, not an SDK endpoint, and omit a trailing slash.",
139032
+ "required": true,
139033
+ "default": null
139034
+ },
139035
+ {
139036
+ "name": "generic_api_key",
139037
+ "displayName": "REST API Key",
139038
+ "type": "string",
139039
+ "description": "Create or copy a server-side REST API key under Settings > APIs and Identifiers > API Keys in your Braze workspace. Use a separate Braze REST API key for each connected integration. The key must include every endpoint permission needed by the tools you use and the campaigns.list permission used to validate the connection. Braze does not allow a key's permissions or IP allowlist to be changed after creation, so create a replacement key if either must change.",
139040
+ "required": true,
139041
+ "default": null
139042
+ }
139043
+ ],
139044
+ "optional": []
139045
+ }
139046
+ }
139047
+ }
139048
+ ]
139049
+ },
139050
{
139051
"slug": "bread_butter",
139052
"name": "Bread & Butter",
142616
}
142617
]
142618
},
142619
+ {
142620
+ "slug": "calendly_mcp",
142621
+ "name": "Calendly MCP",
142622
+ "logo": "https://logos.composio.dev/api/calendly_mcp",
142623
+ "description": "Calendly MCP lets agents manage event types and availability, find open times, generate scheduling links, book meetings, and cancel scheduled events.",
142624
+ "category": "model context protocol",
142625
+ "authSchemes": [
142626
+ "DCR_OAUTH"
142627
+ ],
142628
+ "toolCount": 36,
142629
+ "triggerCount": 0,
142630
+ "version": "20260902_00",
142631
+ "tools": [
142632
+ {
142633
+ "slug": "CALENDLY_MCP_AVAILABILITY_GET_USER_AVAILABILITY_SCHEDULE",
142634
+ "name": "Availability-get user availability schedule",
142635
+ "description": "Use: Fetch details for one named availability schedule.\nWhen: User asks about specific schedule rules or needs rules for a named schedule.\nNeeds: Schedule URI from `availability-list_user_availability_schedules`.\nDo: Read `rules` array and `timezone` for display or to inform event-type updates.\nAvoid: Writing to this schedule—use event-type-level update for changes.\nThen: Report schedule details to user or use rules for availability queries."
142636
+ },
142637
+ {
142638
+ "slug": "CALENDLY_MCP_AVAILABILITY_LIST_USER_AVAILABILITY_SCHEDULES",
142639
+ "name": "Availability-list user availability schedules",
142640
+ "description": "Use: List all named availability schedules for the connected user.\nWhen: User asks about availability schedules or you need to identify one by name.\nNeeds: User URI from `users-get_current_user`.\nDo: Use returned `uri` to fetch schedule details or associate with an event type.\nAvoid: Confusing user availability schedules with event-type-level schedules.\nThen: Use schedule URI in `availability-get_user_availability_schedule` for details."
142641
+ },
142642
+ {
142643
+ "slug": "CALENDLY_MCP_AVAILABILITY_LIST_USER_BUSY_TIMES",
142644
+ "name": "Availability-list user busy times",
142645
+ "description": "Use: List a user's busy time blocks within a date range.\nWhen: User asks when they are busy or you need to avoid conflicts before suggesting slots.\nNeeds: User URI from `users-get_current_user` and ISO 8601 start/end range.\nDo: Pass user URI and date range; use returned intervals to report conflicts.\nAvoid: Substituting for `event_types-list_event_type_available_times`—they differ.\nThen: Use busy intervals to inform scheduling recommendations."
142646
+ },
142647
+ {
142648
+ "slug": "CALENDLY_MCP_EVENT_TYPES_CREATE_EVENT_TYPE",
142649
+ "name": "Event types-create event type",
142650
+ "description": "Use: Create a new event type on the connected account.\nWhen: User explicitly asks to create a new event type.\nNeeds: Host user URI from `users-get_current_user`.\nDo: Set name, duration, and host URI; omit optional fields unless user specified them.\nAvoid: Creating duplicates—call `event_types-list_event_types` first to check for existing types.\nThen: Confirm the new event type URI and share the scheduling URL."
142651
+ },
142652
+ {
142653
+ "slug": "CALENDLY_MCP_EVENT_TYPES_GET_EVENT_TYPE",
142654
+ "name": "Event types-get event type",
142655
+ "description": "Use: Fetch full details for one event type by URI.\nWhen: Before updating an event type or confirming its current configuration.\nNeeds: Event type URI.\nDo: Use the returned fields as the baseline for any patch payload.\nAvoid: Constructing update payloads without reading current state first.\nThen: Proceed with `event_types-update_event_type` using the returned data as base."
142656
+ },
142657
+ {
142658
+ "slug": "CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPE_AVAILABILITY_SCHEDULE",
142659
+ "name": "Event types-list event type availability schedule",
142660
+ "description": "Use: Read the current availability schedule (rules) for an event type.\nWhen: Before calling `event_types-update_event_type_availability_schedule`.\nNeeds: Event type URI.\nDo: Retain the full `rules` array verbatim—it is the required base for updates.\nAvoid: Calling the update endpoint without first reading the current rules.\nThen: Pass the rules to `event_types-update_event_type_availability_schedule` with only the needed edits."
142661
+ },
142662
+ {
142663
+ "slug": "CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPE_AVAILABLE_TIMES",
142664
+ "name": "Event types-list event type available times",
142665
+ "description": "Use: List bookable time slots for an event type within a date range.\nWhen: User wants slots, or to confirm availability before booking.\nNeeds: Event type URI and start/end date range (ISO 8601).\nDo: Pass `start_time` verbatim to subsequent tool calls; do not rewrite UTC values.\nAvoid: Stale data, or trusting a prior local label—re-check UTC `start_time` if questioned.\nThen: Pass UTC `start_time` to `meetings-create_invitee`."
142666
+ },
142667
+ {
142668
+ "slug": "CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPES",
142669
+ "name": "Event types-list event types",
142670
+ "description": "Use: List all event types for the connected user or org.\nWhen: Start of any event-type task, or when selecting an event type by name.\nNeeds: User URI from `users-get_current_user`.\nDo: Filter by current user URI unless user explicitly asks about a different host or org.\nAvoid: Assuming a cached list is current—call fresh each session.\nThen: Carry the selected `uri` into get, update, or availability tools."
142671
+ },
142672
+ {
142673
+ "slug": "CALENDLY_MCP_EVENT_TYPES_UPDATE_EVENT_TYPE",
142674
+ "name": "Event types-update event type",
142675
+ "description": "Use: Update fields on an existing event type.\nWhen: User asks to change name, duration, description, or other settings.\nNeeds: Event type URI from `event_types-list_event_types` or `event_types-get_event_type`.\nDo: Read current state first with `event_types-get_event_type`; patch only requested fields.\nAvoid: Sending fields not read from current state—partial writes may reset unset fields.\nThen: Confirm changes with `event_types-get_event_type`."
142676
+ },
142677
+ {
142678
+ "slug": "CALENDLY_MCP_EVENT_TYPES_UPDATE_EVENT_TYPE_AVAILABILITY_SCHEDULE",
142679
+ "name": "Event types-update event type availability schedule",
142680
+ "description": "Use: Overwrite the availability schedule for an event type.\nWhen: User requests schedule changes (hours, days, one-off date overrides) for an event type.\nNeeds: Event type URI and current rules from `event_types-list_event_type_availability_schedule`.\nDo: Must copy existing rules verbatim, modify only requested entries, send full rules array with IANA timezone. wday rules need `wday` field; date rules need `date` field (YYYY-MM-DD); `intervals` is list of `{from, to}` in HH:MM 24h.\nAvoid: Constructing rules from scratch or sending a partial array—this endpoint overwrites all rules.\nThen: Re-read schedule with `event_types-list_event_type_availability_schedule` to confirm."
142681
+ },
142682
+ {
142683
+ "slug": "CALENDLY_MCP_LIST_CALENDLY_SKILLS",
142684
+ "name": "List calendly skills",
142685
+ "description": "List or search available Calendly skill guides. Each skill gives domain-specific context, recommended tool usage, and best practices for working with Calendly MCP tools. Call this when the user's goal has no obvious single tool (e.g. reschedule or move a meeting). Load a matching skill before using related workflow tools. Use `keywords` to search by name or description (any keyword may match), and `include_header=true` to include each skill's description and related skills."
142686
+ },
142687
+ {
142688
+ "slug": "CALENDLY_MCP_LOAD_CALENDLY_SKILL",
142689
+ "name": "Load calendly skill",
142690
+ "description": "Load a Calendly skill guide that provides domain-specific context, recommended queries, and best practices for working with Calendly tools. Required after listing when a skill matches; do not guess multi-step flows from tool names alone. Use `list_calendly_skills` to discover available skills, or load directly by name. Set `header_only=true` to preview a skill's description and related skills without loading full content."
142691
+ },
142692
+ {
142693
+ "slug": "CALENDLY_MCP_LOCATIONS_LIST_USER_MEETING_LOCATIONS",
142694
+ "name": "Locations-list user meeting locations",
142695
+ "description": "Use: List allowed meeting location kinds for a user.\nWhen: Before creating bookings that need a `location` payload.\nNeeds: User URI from `users-get_current_user`.\nDo: Read supported location `kind` values; choose one compatible with the event type.\nAvoid: Submitting a location kind not configured for the host or event type.\nThen: Use chosen kind in `meetings-create_invitee` location payload."
142696
+ },
142697
+ {
142698
+ "slug": "CALENDLY_MCP_MEETINGS_CANCEL_EVENT",
142699
+ "name": "Meetings-cancel event",
142700
+ "description": "Use: Cancel a scheduled meeting on behalf of the connected host\nWhen: User confirms they want to cancel a specific meeting.\nNeeds: Meeting URI from `meetings-list_events` or `meetings-get_event`.\nDo: Pass meeting URI and optional cancellation reason.\nAvoid: Canceling without confirmation; this notifies all invitees. For reschedule, surface `reschedule_url` instead.\nThen: Inform user the meeting is canceled and optionally list remaining meetings."
142701
+ },
142702
+ {
142703
+ "slug": "CALENDLY_MCP_MEETINGS_CREATE_INVITEE",
142704
+ "name": "Meetings-create invitee",
142705
+ "description": "Use: Book a meeting slot for an invitee on a Calendly event type.\nWhen: User provides invitee name, email, and a confirmed available time slot.\nNeeds: Event type URI, `start_time` from `event_types-list_event_type_available_times`, invitee name and email. Include `location` if the event type has configured locations.\nDo: Set invitee name/email as the person being booked; host is the connected user from `users-get_current_user`. Never swap host and invitee fields.\nAvoid: Booking without confirming slot availability first, or omitting `location` when event type requires it.\nThen: Confirm booking with invitee details and meeting URI."
142706
+ },
142707
+ {
142708
+ "slug": "CALENDLY_MCP_MEETINGS_CREATE_INVITEE_NO_SHOW",
142709
+ "name": "Meetings-create invitee no show",
142710
+ "description": "Use: Mark an invitee as a no-show for a past meeting.\nWhen: User reports an invitee did not attend.\nNeeds: Invitee URI from `meetings-list_event_invitees`.\nDo: Pass invitee URI; operation is idempotent.\nAvoid: Marking no-show before the meeting end time.\nThen: Confirm no-show is recorded and carry forward the no-show URI."
142711
+ },
142712
+ {
142713
+ "slug": "CALENDLY_MCP_MEETINGS_DELETE_INVITEE_NO_SHOW",
142714
+ "name": "Meetings-delete invitee no show",
142715
+ "description": "Use: Remove a no-show mark from an invitee.\nWhen: User asks to undo a no-show marking.\nNeeds: No-show URI from `meetings-create_invitee_no_show`.\nDo: Pass no-show URI; operation is idempotent.\nAvoid: Calling without confirming a no-show record exists.\nThen: Confirm no-show has been removed."
142716
+ },
142717
+ {
142718
+ "slug": "CALENDLY_MCP_MEETINGS_GET_EVENT",
142719
+ "name": "Meetings-get event",
142720
+ "description": "Use: Fetch details for a single scheduled meeting.\nWhen: User asks about a specific meeting or before canceling/examining invitees.\nNeeds: Meeting URI from `meetings-list_events`.\nDo: Use returned `event_type`, `start_time`, `end_time`, and `location` for display or next actions.\nAvoid: Calling this without a known meeting URI. list meetings first.\nThen: Use meeting URI in `meetings-list_event_invitees` or `meetings-cancel_event`."
142721
+ },
142722
+ {
142723
+ "slug": "CALENDLY_MCP_MEETINGS_GET_EVENT_INVITEE",
142724
+ "name": "Meetings-get event invitee",
142725
+ "description": "Use: Fetch details for a single meeting invitee.\nWhen: User asks about a specific attendee's booking details.\nNeeds: Meeting URI from `meetings-list_events` and Invitee URI from `meetings-list_event_invitees`.\nDo: Use returned fields for display or no-show status. Reschedule: surface `reschedule_url`.\nAvoid: Calling without known meeting and invitee URIs.\nThen: Use invitee URI in no-show tools if needed."
142726
+ },
142727
+ {
142728
+ "slug": "CALENDLY_MCP_MEETINGS_GET_INVITEE_NO_SHOW",
142729
+ "name": "Meetings-get invitee no show",
142730
+ "description": "Use: Fetch the no-show record for a meeting invitee.\nWhen: User asks whether a no-show was recorded for an invitee.\nNeeds: No-show URI from `meetings-create_invitee_no_show`.\nDo: Check returned record for no-show status and timestamp.\nAvoid: Calling if no no-show has been recorded—returns 404.\nThen: Report no-show status to user."
142731
+ },
142732
+ {
142733
+ "slug": "CALENDLY_MCP_MEETINGS_LIST_EVENT_INVITEES",
142734
+ "name": "Meetings-list event invitees",
142735
+ "description": "Use: List all invitees for a scheduled meeting.\nWhen: User asks who is attending a meeting or you need invitee URIs.\nNeeds: Meeting URI from `meetings-list_events`.\nDo: Use returned invitee `uri` for no-show marking or detail lookups.\nAvoid: Calling without a meeting URI. list meetings first.\nThen: Use invitee URI in `meetings-get_event_invitee` or `meetings-create_invitee_no_show`. For reschedule, surface each invitee's `reschedule_url`."
142736
+ },
142737
+ {
142738
+ "slug": "CALENDLY_MCP_MEETINGS_LIST_EVENTS",
142739
+ "name": "Meetings-list events",
142740
+ "description": "Use: List scheduled meetings for user/org.\nWhen: Upcoming/past meetings or to find meetings by date.\nNeeds: User/org URI via `users-get_current_user`.\nDo: Filter status (active/canceled), date range; carry `uri`.\nAvoid: Fetching unfiltered when the user has a specific date.\nThen: Enrich via `meetings-list_event_invitees` before listing/naming meetings, unless asked for only a count; then `uri` in `meetings-get_event`/`meetings-cancel_event`."
142741
+ },
142742
+ {
142743
+ "slug": "CALENDLY_MCP_ORGANIZATIONS_CREATE_ORGANIZATION_INVITATION",
142744
+ "name": "Organizations-create organization invitation",
142745
+ "description": "Use: Invite a user to the organization by email.\nWhen: User asks to add a new member.\nNeeds: Org URI and invitee email address.\nDo: Check `organizations-list_organization_invitations` first to avoid duplicate invites.\nAvoid: Calling without confirming no pending invite exists for this email.\nThen: Confirm invitation sent and optionally show pending invitations."
142746
+ },
142747
+ {
142748
+ "slug": "CALENDLY_MCP_ORGANIZATIONS_GET_ORGANIZATION",
142749
+ "name": "Organizations-get organization",
142750
+ "description": "Use: Fetch details for the connected user's organization.\nWhen: User asks about the org or you need the org URI for org-scoped list tools.\nNeeds: Org URI from `users-get_current_user` (`resource.current_organization`).\nDo: Use returned `uri` for org-scoped event type or membership queries.\nAvoid: Calling without an org URI.\nThen: Use org URI in `organizations-list_organization_memberships`."
142751
+ },
142752
+ {
142753
+ "slug": "CALENDLY_MCP_ORGANIZATIONS_GET_ORGANIZATION_MEMBERSHIP",
142754
+ "name": "Organizations-get organization membership",
142755
+ "description": "Use: Fetch details for a single org membership.\nWhen: You need role or status for a specific member.\nNeeds: Membership URI from `organizations-list_organization_memberships`.\nDo: Check `role` and `status` fields for permissions context.\nAvoid: Calling without a known membership URI.\nThen: Use membership data to confirm before invite or removal actions."
142756
+ },
142757
+ {
142758
+ "slug": "CALENDLY_MCP_ORGANIZATIONS_LIST_ORGANIZATION_INVITATIONS",
142759
+ "name": "Organizations-list organization invitations",
142760
+ "description": "Use: List pending invitations for the organization.\nWhen: User asks to see pending invites or check if someone was already invited.\nNeeds: Org URI from `users-get_current_user`.\nDo: Check returned list before sending a new invite to avoid duplicates.\nAvoid: Sending a new invitation without checking for existing pending ones.\nThen: Use invitation URI in `organizations-revoke_organization_invitation` if needed."
142761
+ },
142762
+ {
142763
+ "slug": "CALENDLY_MCP_ORGANIZATIONS_LIST_ORGANIZATION_MEMBERSHIPS",
142764
+ "name": "Organizations-list organization memberships",
142765
+ "description": "Use: List all members of an organization.\nWhen: User asks who is in the org or you need to find a member's user URI.\nNeeds: Org URI from `users-get_current_user`.\nDo: Use returned `user.uri` for per-user event-type or availability queries.\nAvoid: Fetching the full list when you only need the connected user—use `users-get_current_user` instead.\nThen: Use member URI in user-scoped tools or `organizations-get_organization_membership`."
142766
+ },
142767
+ {
142768
+ "slug": "CALENDLY_MCP_ORGANIZATIONS_REVOKE_ORGANIZATION_INVITATION",
142769
+ "name": "Organizations-revoke organization invitation",
142770
+ "description": "Use: Revoke a pending organization invitation.\nWhen: User asks to cancel a pending invite.\nNeeds: Organization URI from `users-get_current_user` and Invitation URI from `organizations-list_organization_invitations`.\nDo: Confirm with user before revoking; this cannot be undone.\nAvoid: Revoking without confirming the invite is still pending.\nThen: Confirm revocation and optionally refresh invitations list."
142771
+ },
142772
+ {
142773
+ "slug": "CALENDLY_MCP_ROUTING_FORMS_GET_ROUTING_FORM",
142774
+ "name": "Routing forms-get routing form",
142775
+ "description": "Use: Fetch details for a single routing form.\nWhen: User asks about a specific form or its questions.\nNeeds: Routing form URI from `routing_forms-list_routing_forms`.\nDo: Use returned question IDs for submission filtering.\nAvoid: Calling without a known form URI.\nThen: Use form details to answer user questions or list submissions."
142776
+ },
142777
+ {
142778
+ "slug": "CALENDLY_MCP_ROUTING_FORMS_GET_ROUTING_FORM_SUBMISSION",
142779
+ "name": "Routing forms-get routing form submission",
142780
+ "description": "Use: Fetch details for a single routing form submission.\nWhen: User asks about a specific submission or response.\nNeeds: Submission URI from `routing_forms-list_routing_form_submissions`.\nDo: Read `questions_and_answers` for the submitted values.\nAvoid: Calling without a known submission URI.\nThen: Report submission details to user."
142781
+ },
142782
+ {
142783
+ "slug": "CALENDLY_MCP_ROUTING_FORMS_LIST_ROUTING_FORMS",
142784
+ "name": "Routing forms-list routing forms",
142785
+ "description": "Use: List routing forms for the org.\nWhen: User asks about routing forms or you need to find a form by name.\nNeeds: Org URI from `users-get_current_user`.\nDo: Use returned `uri` to fetch form details.\nAvoid: Assuming form names without listing first.\nThen: Use form URI in `routing_forms-get_routing_form`."
142786
+ },
142787
+ {
142788
+ "slug": "CALENDLY_MCP_ROUTING_FORMS_LIST_ROUTING_FORM_SUBMISSIONS",
142789
+ "name": "Routing forms-list routing form submissions",
142790
+ "description": "Use: List submissions for a routing form.\nWhen: User asks to see form responses or analyze routing data.\nNeeds: Routing form URI from `routing_forms-list_routing_forms`.\nDo: Use pagination params for large result sets.\nAvoid: Fetching all submissions without date/count filters on high-volume forms.\nThen: Use submission URI in `routing_forms-get_routing_form_submission`."
142791
+ },
142792
+ {
142793
+ "slug": "CALENDLY_MCP_SCHEDULING_LINKS_CREATE_SINGLE_USE_SCHEDULING_LINK",
142794
+ "name": "Scheduling links-create single use scheduling link",
142795
+ "description": "Use: Create a single-use scheduling link using the event type's settings unchanged.\nWhen: User wants a one-time link with no overrides. For per-link customization (duration, scheduling window, location, availability), use `shares-create_share` instead.\nNeeds: Event type URI from `event_types-list_event_types`.\nDo: Each call creates a new link; store the returned `booking_url`.\nAvoid: Using when any override is requested — this endpoint cannot customize the link. Don't create more links than needed; each call creates a distinct non-reusable link.\nThen: Share `booking_url` with the intended invitee."
142796
+ },
142797
+ {
142798
+ "slug": "CALENDLY_MCP_SHARES_CREATE_SHARE",
142799
+ "name": "Shares-create share",
142800
+ "description": "Use: Create a single-use share link for a one-on-one event type with per-link overrides\nWhen: User wants a single-use link with any customization (duration, scheduling window, location, or availability).\nNeeds: Event type URI from `event_types-list_event_types`.\nDo: Set only fields to override; omitted fields inherit from event type.\nAvoid: Group event types (one-on-one only). This overrides event-type fields, not invitee prefill values.\nThen: Share the returned `booking_url` with the recipient."
142801
+ },
142802
+ {
142803
+ "slug": "CALENDLY_MCP_USERS_GET_CURRENT_USER",
142804
+ "name": "Users-get current user",
142805
+ "description": "Use: Resolve the connected host account and canonical user URI.\nWhen: Start any scheduling, booking, event-type, or availability workflow.\nNeeds: No inputs.\nDo: Call once and keep `resource.uri`, `timezone`, and `scheduling_url` for downstream calls.\nAvoid: Skipping this and guessing host identity.\nThen: Use `resource.uri` in list/get tools unless the user explicitly names another host."
142806
+ },
142807
+ {
142808
+ "slug": "CALENDLY_MCP_USERS_GET_USER",
142809
+ "name": "Users-get user",
142810
+ "description": "Use: Fetch profile for a specific user by URI.\nWhen: User asks about another person's account or you hold a user URI from org/membership data.\nNeeds: User URI.\nDo: Pass the user URI from org/membership data; do not use this to look up the connected user.\nAvoid: Calling this without a known URI - use `users-get_current_user` for the connected user.\nThen: Use returned `resource.uri` and `resource.timezone` for event-type or availability lookups scoped to that user."
142811
+ }
142812
+ ],
142813
+ "triggers": [],
142814
+ "authConfigDetails": [
142815
+ {
142816
+ "mode": "DCR_OAUTH",
142817
+ "name": "calendly_mcp_DCR_OAuth",
142818
+ "fields": {
142819
+ "auth_config_creation": {
142820
+ "required": [],
142821
+ "optional": [
142822
+ {
142823
+ "name": "client_id",
142824
+ "displayName": "Client id",
142825
+ "type": "string",
142826
+ "description": "Client id of the app",
142827
+ "required": false,
142828
+ "default": null
142829
+ },
142830
+ {
142831
+ "name": "client_secret",
142832
+ "displayName": "Client secret",
142833
+ "type": "string",
142834
+ "description": "Client secret of the app",
142835
+ "required": false,
142836
+ "default": null
142837
+ },
142838
+ {
142839
+ "name": "oauth_redirect_uri",
142840
+ "displayName": "Redirect URI",
142841
+ "type": "string",
142842
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
142843
+ "required": false,
142844
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
142845
+ },
142846
+ {
142847
+ "name": "scopes",
142848
+ "displayName": "Scopes",
142849
+ "type": "string",
142850
+ "description": "Scopes to request from the user, comma separated",
142851
+ "required": false,
142852
+ "default": ""
142853
+ }
142854
+ ]
142855
+ },
142856
+ "connected_account_initiation": {
142857
+ "required": [],
142858
+ "optional": []
142859
+ }
142860
+ }
142861
+ }
142862
+ ]
142863
+ },
142864
{
142865
"slug": "callerapi",
142866
"name": "Callerapi",
143738
}
143739
]
143740
},
143741
+ {
143742
+ "slug": "candid_mcp",
143743
+ "name": "Candid MCP",
143744
+ "logo": "https://logos.composio.dev/api/candid_mcp",
143745
+ "description": "Candid MCP lets agents research nonprofit organizations, funders, funding opportunities, social-sector knowledge, and related news using Candid data.",
143746
+ "category": "model context protocol",
143747
+ "authSchemes": [
143748
+ "DCR_OAUTH"
143749
+ ],
143750
+ "toolCount": 6,
143751
+ "triggerCount": 0,
143752
+ "version": "20260902_00",
143753
+ "tools": [
143754
+ {
143755
+ "slug": "CANDID_MCP_CURRENT_DATE",
143756
+ "name": "Current date",
143757
+ "description": "Get the current day to reference for any time-sensitive data requests.\n\nALWAYS call this tool:\n* At the beginning of conversations involving dates or timelines\n* Before searching news or time-sensitive data\n* When interpreting or presenting any temporal information (recent, upcoming, last year, etc.)\n* Before making statements about when events occurred or will occur\n\nNever assume the correct date.\nIf data only includes partial date information, use this tool to infer missing details.\n\nReturns\n-------\ndate\n Today's date"
143758
+ },
143759
+ {
143760
+ "slug": "CANDID_MCP_IDENTIFY_LOCATIONS",
143761
+ "name": "Identify locations",
143762
+ "description": "Uses natural language processing to find and match named geographies found in the supplied text. The output\nwill supply identified geographies from [Geonames](https://www.geonames.org/). These geographies can be used for\nother Candid tools like organization search to get more specific results.\n\nKey Usage Requirements:\n- This tools is most effective when the input text is a full sentence or more and grammatically correct\n- It uses a NLP model to resolve geographic names and then matches them using graph inferencing\n\nParameters\n----------\ntext : str\n Text describing working in the social sector. This should be related to the social and/or philanthropic sector.\n\nExamples\n--------\n>>> geo_detect(text='Homeless shelters in new york city')\n\nReturns\n-------\nlist[GeocodingRecord]\n Matched geographies responses. This is an array of data objects which contain the `name` of the geography as it\n appeared in the supplied text, and the best match to a Geonames geography. For many Candid knowledge tools the\n `geonames_id` value will be most useful."
143763
+ },
143764
+ {
143765
+ "slug": "CANDID_MCP_IDENTIFY_MENTIONED_ORGANIZATIONS",
143766
+ "name": "Identify mentioned organizations",
143767
+ "description": "Resolve and link organization names to official Candid nonprofit profiles. Use after any response that mentions\nnonprofit or foundation names to generate clickable profile links.\n\nThis uses the Candid Search in a lookup mode, and then finds the best result(s) using a heuristic string\nsimilarity search.\n\nThis tool is focused on getting links to the organization's Candid profile for the user to click and explore in\nmore detail.\n\nUse the URLs here to replace organization names in the chat response with links to the organization's profile. Links\nto Candid profiles **MUST** be used to do the following:\n1. Generate direct links to Candid organization profiles\n2. Provide a mechanism for users to easily access detailed organizational information\n3. Enhance responses with authoritative source links\n\nKey Usage Requirements:\n- This tool should be used after a knowledge resources result if organization names are mentioned\n- This tool should be used after a web search if organization names are mentioned\n- This tool should not be used after any Candid tool which returns a `profile_link` URL field\n- Always incorporate returned profile URLs directly into the response text\n- Replace organization name mentions with hyperlinked Candid profile URLs\n- Prioritize creating a seamless user experience by making URLs contextually relevant\n\nExample Desired Output:\nInstead of: 'The Gates Foundation does impressive work.'\nUse: 'The [Gates Foundation](https://app.candid.org/profile/XXXXX) does impressive work.'\n\nFailure to integrate the URLs into the response is considered an incomplete implementation.\n\nExamples\n--------\n>>> identify_mentioned_organizations(organizations=['Gates Foundation', 'Candid'])\n\nParameters\n----------\norganizations : list[str]\n A list of organization name strings found in a chat response message which need to be matches\n\nReturns\n-------\ndict[str, OrganizationRecord]\n mapping input name --> Candid Search organization record of the best potential match, including the profile URL"
143768
+ },
143769
+ {
143770
+ "slug": "CANDID_MCP_KNOWLEDGE_RESOURCES",
143771
+ "name": "Knowledge resources",
143772
+ "description": "Get answers to questions about the social and philanthropic sector directly fom Candid's subject matter experts.\n\nThis knowledge includes help articles and video training sessions from Candid's subject matter experts, blog posts\nabout the sector from Candid staff and trusted partner authors, research documents about the sector and news\narticles curated about activity happening in the sector around the world.\n\nSearches are performed through a combination of vector and keyword searching. Results are then re-ranked against\nthe original query to get the best results.\n\nSearch results often come back with specific organizations named, especially if referencing the news. In these cases\nthe organizations should be identified in Candid's data and links to their profiles **MUST** be included in final\nchat response to the user.\n\nKey Usage Requirements:\n- Identify names of nonprofits and foundations in the returned text using `identify_mentioned_organizations`\n- Always incorporate returned profile URLs directly into the response text\n- Replace organization name mentions with hyperlinked Candid profile URLs\n- Prioritize creating a seamless user experience by making URLs contextually relevant\n\nParameters\n----------\nquery : str\n Text describing a user's question or a description of investigative work which requires support from Candid's\n knowledge base\nsources : list[SourceNames]\n One or more sources of knowledge from different areas at Candid.\n * Candid Blog: Blog posts from Candid staff and trusted partners intended to help those in the sector or\n illuminate ongoing work\n * Candid Help: Candid FAQs to help user's get started with Candid's product platform and learning resources\n * Candid Learning: Training documents from Candid's subject matter experts\n * Candid News: News articles and press releases about real-time activity in the philanthropic sector\n * IssueLab Research Reports: Academic research reports about the social/philanthropic sector\n * YouTube Training: Transcripts from video-based training seminars from Candid's subject matter experts\nnews_days_ago : int, optional\n How many days in the past to search for news articles, if a user is asking for recent trends then this value\n should be set lower >~ 10, by default 60\n If output is a string then that means there was some error, and retry should be considered\n\nReturns\n-------\nlist[KnowledgeArticle]"
143773
+ },
143774
+ {
143775
+ "slug": "CANDID_MCP_SEARCH_ORGANIZATIONS",
143776
+ "name": "Search organizations",
143777
+ "description": "Find nonprofits and grantmaking organizations in Candid's database by name, mission, EIN, location, or type of\nwork. Use to look up a specific organization, find peer organizations, or discover organizations working on a topic.\n\nSearch for organizations by name, description or work, program descriptions and locations. Here are some\nguidelines:\n* `query` controls hybrid searching involving both vector search and keyword search\n* `query` can be used to find organizations based on a description of work\n* if the query is intended to be a lookup of an organization by name, then adding quotes around the `query` string\n circumvents vector search, and prioritizes keyword matching on names (eg. `query=Candid` --> `query='Candid'`)\n* if the query is an EIN (eg. 12-3456789) then keyword searching is prioritized to get exact matches\n* adding location information such as postal codes and/or admin1 (state/province abbreviations) will filter results\n* adding subject or population codes will filter results\n* these results are not comprehensive and are limited to a small set size, several invocations may be necessary to\nexplore\n\nThis tool should be used as a first step in any downstream task which requires identifying the nonprofit that the\nuser is identifying with. Often, the `nonprofit_id` is required, and that can be found via a search.\n\nSubjects and populations can be determined using the `autocode` tool using unstructured text describing the user's\nintended search. Codes strictly filter results, and aren't necessary for general retrieval queries, but may be\nused when the user is drilling down on data.\n\nGeographies can be determined using the geo detection tool using unstructured text describing the user's\nintended search. Geographies strictly filter results, and aren't necessary for general retrieval queries, but may be\nused when the user is drilling down on data.\nKey Usage Requirements:\n- Always incorporate returned profile URLs directly into the response text\n- Replace funding organization name mentions with hyperlinked Candid profile URLs\n- Prioritize creating a seamless user experience by making URLs contextually relevant\n- Use relevant recipient data as well as inferred metadata to provide explanations about recommendation relevance\n\nParameters\n----------\nquery : str\n Free text query which drives the search functionality. This uses a hybrid approach of vector and keyword\n searching, but under certain conditions expressed in the 'guidelines' this may disable vector search.\nlocated_postal_code : str | None, optional\n Postal code of the organization to be searched, if provided, by default None\nlocated_admin1 : str | None, optional\n Admin1 code (state/province abbreviation) of the organization to be searched, if provided, by default None\nsubject_codes : str | None, optional\n Subject codes from Candid's PCS taxonomy, comma separated, by default None\npopulations_served_codes : str | None, optional\n Population groups served codes from Candid's PCS taxonomy, comma separated, by default None\ngeonameids_of_geographies_served : str | None, optional\n Geonames ID values for geographies served by organizations in search results, comma separted, by default None\ngeonameids_of_organization_location : str | None, optional\n Geonames ID values for location(s) of the organizations in search results, comma separted, by default None\norg_seal_status : str | None, optional\n Comma separated seals of transparency the resulting organizations should have where the values can be:\n * PLATINUM\n * GOLD\n * SILVER\n * BRONZE\n * NOSEAL\n \"PLATINUM\" is the most transparent, \"NOSEAL\" means the organization has claimed their Candid profile but\n abandoned the data update process for whatever reason. None puts no restrictions on this, by default None\nleader_demographics : str | None, optional\n Comma separated demographic categories for the result organization's leader where values can be:\n * Woman leader or co-leader\n * BIPOC leader or co-leader\n * LGBTQ+ leader or co-leader\n * Leader or co-leader with a disability\n None puts no restrictions on this, by default None\n\nExamples\n--------\n>>> organization_search(query='Homeless shelters in new york city')\n>>> organization_search(\n query='Homeless shelters in new york city,\n located_admin1='NY',\n geonameids_of_geographies_served='5128581'\n)\n>>> organization_search(\n query='Homeless shelters in new york city,\n subject_codes='SS090200,SS070102',\n populations_served_codes='PG030100',\n geonameids_of_geographies_served='5128581'\n)\n\nReturns\n-------\nlist[OrganizationRecord]\n List of the top organization search results"
143778
+ },
143779
+ {
143780
+ "slug": "CANDID_MCP_TAXONOMY_TERMS",
143781
+ "name": "Taxonomy terms",
143782
+ "description": "Uses natural language processing to align input text to Candid's taxonomy, the Philanthropy Classification\nSystem (PCS). The taxonomy describes activity in the social and philanthropic sectors including the purpose of the\nactivity and what population groups the activity serves. These taxonomy codes can be used for other Candid tools\nlike organization search to get more specific results.\nA complete description of the taxonomy is available to the public at https://taxonomy.candid.org.\n\nParameters\n----------\ntext : str\n Text describing working in the social sector. This should be related to the social and/or philanthropic sector.\n\nExamples\n--------\n>>> autocode(text='Housing assistance programs for homeless veterans')\n\nReturns\n-------\nlist[AutocodingRecord]\n Taxonomy responses. The items in the list are each taxonomy terms which the NLP model has determined is relevant\n given the input text. This also includes confidence scores."
143783
+ }
143784
+ ],
143785
+ "triggers": [],
143786
+ "authConfigDetails": [
143787
+ {
143788
+ "mode": "DCR_OAUTH",
143789
+ "name": "candid_mcp_DCR_OAuth",
143790
+ "fields": {
143791
+ "auth_config_creation": {
143792
+ "required": [],
143793
+ "optional": [
143794
+ {
143795
+ "name": "client_id",
143796
+ "displayName": "Client id",
143797
+ "type": "string",
143798
+ "description": "Client id of the app",
143799
+ "required": false,
143800
+ "default": null
143801
+ },
143802
+ {
143803
+ "name": "client_secret",
143804
+ "displayName": "Client secret",
143805
+ "type": "string",
143806
+ "description": "Client secret of the app",
143807
+ "required": false,
143808
+ "default": null
143809
+ },
143810
+ {
143811
+ "name": "oauth_redirect_uri",
143812
+ "displayName": "Redirect URI",
143813
+ "type": "string",
143814
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
143815
+ "required": false,
143816
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
143817
+ },
143818
+ {
143819
+ "name": "scopes",
143820
+ "displayName": "Scopes",
143821
+ "type": "string",
143822
+ "description": "Scopes to request from the user, comma separated",
143823
+ "required": false,
143824
+ "default": "openid,profile,email,claudeai"
143825
+ }
143826
+ ]
143827
+ },
143828
+ "connected_account_initiation": {
143829
+ "required": [],
143830
+ "optional": []
143831
+ }
143832
+ }
143833
+ }
143834
+ ]
143835
+ },
143836
{
143837
"slug": "canny",
143838
"name": "Canny",
148947
}
148948
]
148949
},
148950
+ {
148951
+ "slug": "chartmogul",
148952
+ "name": "ChartMogul",
148953
+ "logo": "https://logos.composio.dev/api/chartmogul",
148954
+ "description": "ChartMogul is a subscription analytics and revenue data platform for managing customers, billing data, metrics, and sales opportunities.",
148955
+ "category": "analytics",
148956
+ "authSchemes": [
148957
+ "API_KEY"
148958
+ ],
148959
+ "toolCount": 10,
148960
+ "triggerCount": 0,
148961
+ "version": "00000000_00",
148962
+ "tools": [
148963
+ {
148964
+ "slug": "CHARTMOGUL_CREATE_CUSTOMER",
148965
+ "name": "Create Customer",
148966
+ "description": "Create a customer under a ChartMogul data source using a caller-owned external ID and optional profile or lead details."
148967
+ },
148968
+ {
148969
+ "slug": "CHARTMOGUL_DELETE_CUSTOMER",
148970
+ "name": "Delete Customer",
148971
+ "description": "Request permanent deletion of a customer and all associated ChartMogul data by UUID. ChartMogul accepts this asynchronously, so confirm disappearance with LIST_CUSTOMERS when completion matters."
148972
+ },
148973
+ {
148974
+ "slug": "CHARTMOGUL_GET_ACCOUNT",
148975
+ "name": "Get Account",
148976
+ "description": "Return the connected ChartMogul account's identity, reporting currency, time zone, week start, and optionally selected churn and refund settings."
148977
+ },
148978
+ {
148979
+ "slug": "CHARTMOGUL_GET_CUSTOMER",
148980
+ "name": "Get Customer",
148981
+ "description": "Return one customer and its identifiers, lifecycle status, revenue values, ownership, location, and attributes by ChartMogul UUID."
148982
+ },
148983
+ {
148984
+ "slug": "CHARTMOGUL_GET_KEY_METRICS",
148985
+ "name": "Get Key Metrics",
148986
+ "description": "Return all key subscription metrics and current summaries for a date range, optionally grouped by interval and filtered by countries or plans."
148987
+ },
148988
+ {
148989
+ "slug": "CHARTMOGUL_LIST_ACTIVITIES",
148990
+ "name": "List Activities",
148991
+ "description": "Return one page of ChartMogul MRR activities for an optional date range, movement type, and date order, with a cursor when more are available."
148992
+ },
148993
+ {
148994
+ "slug": "CHARTMOGUL_LIST_CUSTOMERS",
148995
+ "name": "List Customers",
148996
+ "description": "Return one page of customers filtered by source, identifier, email, status, or billing system."
148997
+ },
148998
+ {
148999
+ "slug": "CHARTMOGUL_LIST_PLANS",
149000
+ "name": "List Plans",
149001
+ "description": "Return one page of subscription plans, optionally filtered by source, external ID, or billing system."
149002
+ },
149003
+ {
149004
+ "slug": "CHARTMOGUL_LIST_SOURCES",
149005
+ "name": "List Sources",
149006
+ "description": "Return the account's billing data sources, optionally filtered by name or system and with selected source settings included."
149007
+ },
149008
+ {
149009
+ "slug": "CHARTMOGUL_UPDATE_CUSTOMER",
149010
+ "name": "Update Customer",
149011
+ "description": "Update selected profile, ownership, location, timing, website, or lead-status fields on an existing ChartMogul customer. Omitted fields remain unchanged; tags and custom attributes are not replaced."
149012
+ }
149013
+ ],
149014
+ "triggers": [],
149015
+ "authConfigDetails": [
149016
+ {
149017
+ "mode": "API_KEY",
149018
+ "name": "chartmogul_api_key",
149019
+ "fields": {
149020
+ "auth_config_creation": {
149021
+ "required": [],
149022
+ "optional": []
149023
+ },
149024
+ "connected_account_initiation": {
149025
+ "required": [
149026
+ {
149027
+ "name": "generic_api_key",
149028
+ "displayName": "Read & Write API Key",
149029
+ "type": "string",
149030
+ "description": "Create a separate integration key in ChartMogul under Profile > View Profile > API Keys: click Add API Key, give it a name, select the Read & Write access level, create it, then reveal and copy the key. Staff, Admin, or Owner roles can create a Read & Write key; keep it secret.",
149031
+ "required": true,
149032
+ "default": null
149033
+ }
149034
+ ],
149035
+ "optional": []
149036
+ }
149037
+ }
149038
+ }
149039
+ ]
149040
+ },
149041
{
149042
"slug": "chaser",
149043
"name": "Chaser",
151886
}
151887
]
151888
},
151889
+ {
151890
+ "slug": "clarify_mcp",
151891
+ "name": "Clarify MCP",
151892
+ "logo": "https://logos.composio.dev/api/clarify_mcp",
151893
+ "description": "Clarify MCP lets agents query and update CRM records, create tasks and lists, analyze pipelines, and work with companies, people, deals, meetings, and campaigns.",
151894
+ "category": "model context protocol",
151895
+ "authSchemes": [
151896
+ "DCR_OAUTH"
151897
+ ],
151898
+ "toolCount": 46,
151899
+ "triggerCount": 0,
151900
+ "version": "20260902_00",
151901
+ "tools": [
151902
+ {
151903
+ "slug": "CLARIFY_MCP_ADD_COMMENT",
151904
+ "name": "Add-comment",
151905
+ "description": "Add a comment to a supported entity.\n\n## Important notes\n\nAfter adding a comment, tell the user what was commented on in a friendly, conversational way."
151906
+ },
151907
+ {
151908
+ "slug": "CLARIFY_MCP_CREATE_CAMPAIGN",
151909
+ "name": "Create-campaign",
151910
+ "description": "Create a new email campaign (sequence) in DRAFT mode. To edit an existing\ncampaign, use the update-campaign tool instead.\n\n📖 **For comprehensive campaign rules and examples**: Use `read-context` with context: \"campaign-docs\"\n\n## When to use this tool\n\n- When the user asks to create a new email campaign or sequence\n- When duplicating a campaign (first fetch it with `get-campaigns`, then call this tool with the email steps)\n\n## Structuring the campaign\n\nStructure email steps with subjects, bodies (HTML), and timing. Campaigns start in DRAFT mode.\n\nWhen drafting campaign emails:\n- Keep subject lines under 50 characters, conversational, not overly formal\n- Use a warm, conversational tone while remaining professional\n- Be concise and include a clear call to action if appropriate\n- Start with a friendly greeting and end with a warm closing\n\n## Essential rules\n\n1. **Email/Delay Pattern**: Emails and delays MUST alternate. Always specify `delay_after_days` on each step\n2. **First email**: `delay_after_days: 0`. Subsequent emails: minimum 1 day\n3. **Campaigns are Workflows**: Use this tool for campaigns, not generic workflow tools\n4. Campaign emails are templates sent to multiple people\n5. Use variable placeholders: {{path||fallback}} with fallback, or {{path}} without fallback\n6. Only use the variables listed below (do not invent variables)\n\n## Threading: send_as_reply\n\nSet `send_as_reply: true` on a step to thread it as a reply under the previous\nstep (uses the prior message id and \"Re: <previous subject>\"). Use it when a\nfollow-up bumps the prior email and the recipient should see it inline:\n\n- **Use** `send_as_reply: true` for content like \"circling back\", \"just bumping\n this\", \"wanted to follow up\", or any step that explicitly references the\n prior email's call to action without a new pitch.\n- **Leave it off (default)** when the step introduces a new angle, case study,\n or call to action; recipients triage by subject, and a fresh subject signals\n fresh content.\n\nRules:\n- Step 1 always starts a new thread (`send_as_reply` must be false / omitted).\n- When `send_as_reply: true`, the step's `subject` is ignored at send time\n (the previous step's subject is reused with \"Re: \" prepended), but you must\n still provide a sensible `subject` for storage.\n\nFallback rules (fallbacks make emails feel natural when data is missing):\n- ALWAYS include fallbacks for human-identifiable information:\n→ Person names (first_name, last_name, full_name) → use \"there\", \"Friend\", etc.\n→ Company/organization names → use \"your company\", \"your organization\", \"your team\"\n→ Job titles and roles → use \"your role\", etc.\n→ Location/city names → use \"your area\", \"your region\", etc.\n- Skip fallbacks ONLY for technical/structured data:\n→ URLs, email addresses, phone numbers\n→ Dates, timestamps, IDs\n→ Numerical values and metrics\n\n## Examples\n\n<example>\nCreate a campaign:\n{\n \"campaign_name\": \"New Leads Nurture\",\n \"email_steps\": [\n {\n \"subject\": \"Welcome, {{person.name.first_name||there}}\",\n \"body\": \"<p>Hi {{person.name.first_name||there}},</p><p>Thanks for your interest!</p>\",\n \"delay_after_days\": 0\n },\n {\n \"subject\": \"Resources for {{person.company_id.name||your team}}\",\n \"body\": \"<p>Hey {{person.name.first_name||there}},</p><p>Here are some helpful resources...</p>\",\n \"delay_after_days\": 3\n }\n ]\n}\n</example>\n\n## Important notes\n\n- List is optional for drafts (can be selected later in UI before activation)\n- Email account connection is optional for drafts (required before activating)\n- Campaigns are created in DRAFT mode (enabled: false)\n- delay_after_days: 0 = immediate, 3 = day 3, 7 = day 7\n- Minimum 1 day enforced between consecutive emails automatically\n- Body should be formatted as HTML. Put each paragraph in its own <p> tag; paragraphs render with a blank line between them. Use <br/> only for a hard line break within a paragraph (e.g. between signature lines)\n- When describing timing to users, say \"immediately\" for delay_after_days = 0, \"on day 3\" for delay_after_days = 3"
151911
+ },
151912
+ {
151913
+ "slug": "CLARIFY_MCP_CREATE_EMAIL_DRAFT",
151914
+ "name": "Create-email-draft",
151915
+ "description": "Create an email draft in the user's connected Gmail or Outlook account for them to review, edit, and send themselves. Nothing is sent; use send-email when the user wants the message to go out now.\n\nThe tool result repeats the draft's recipients, subject, and body, along with the Nylas draft ID needed to revise it.\n\nThe body is plain text that will be converted to rich text blocks. Use these conventions:\n- Lines starting with \"- \" become bullet list items\n- Lines starting with \"1. \", \"2. \", etc. become numbered list items\n- Blank lines become paragraph breaks (consecutive blank lines are collapsed)\n- Lines starting with \"# \" or \"## \" become bold section labels\n- **bold** spans become bold text\n- Markdown links [label](https://example.com) and bare URLs become clickable links\n- Never put a placeholder or fabricated link in the body (e.g. [Recording] *(link)*, [link], or a guessed URL). Include a link only if you have the real URL from a tool result; if a referenced resource has no link available, leave it out and say in your reply that it needs to be added\n- Markdown horizontal rules like \"---\" are treated as section dividers and are not shown\n- Everything else becomes a regular paragraph\n\nFollow the system prompt and any activated email-writing skill for the user's\npreferred voice, tone, structure, and formatting judgment. If a skill gives\nmore specific email-writing guidance that conflicts with these generic style\ndefaults, prefer the skill. If no more specific guidance applies, write like a\nnormal email, not a dashboard or report. Keep bodies compact and easy to scan:\n- Prefer short paragraphs and a small number of bullets\n- Use section labels only when they materially improve scanability\n- Use at most one blank line between sections or paragraphs\n- Keep section labels attached to their content; do not add a blank line immediately after a section label\n- Keep lists attached to the sentence or item they explain; do not add a blank line immediately before a bullet or numbered list\n- Avoid em dashes and dash-heavy constructions; use commas, colons, parentheses, or separate sentences instead\n- Do not use decorative separators, tables, code fences, blockquotes, or report-style spacing\n\n## Threading\n\nWhen the user asks you to reply to an existing inbound email or thread, populate replyToMessageId so the draft threads correctly in Gmail/Outlook. Look up the value from the message_id field on a Message record (use get-records or query-data on the Message entity to find the inbound message you are replying to). Omit replyToMessageId when composing a brand new email that is not part of an existing inbound thread.\n\nreplyToMessageId and replacesDraftId are different ids and must not be swapped. replyToMessageId is the short Nylas message_id of an inbound message (e.g. 19df41adc5abe23b). replacesDraftId is a Nylas draft id from a prior create-email-draft result (the \"Nylas draft ID:\" line). Never pass a Nylas draft id as replyToMessageId, and never pass a message_id as replacesDraftId.\n\n## Iterating on a draft\n\nWhen the user is revising a draft you already created earlier in this conversation (e.g. \"make it shorter\", \"rewrite it\", \"tweak the opener\", \"also add ...\"), set replacesDraftId to the Nylas draft ID from that prior create-email-draft tool result. This updates the existing Gmail draft in place instead of leaving a duplicate behind. The Nylas draft ID appears on the \"Nylas draft ID:\" line of the prior tool result. Prefer this over creating a second draft whenever the user is iterating on the same email.\n\nOmit replacesDraftId when you are drafting a brand new email; for example for a different recipient, a different thread, or any message that is not a revision of the most recent draft to the same audience.\n\n## Recipients\n\nRecipient addresses (to/cc/bcc) must come from a CRM person record. Look them up with get-records or by querying the person entity before drafting; never guess an address from a name and company domain. Any recipient that matches no person record is rejected unless you pass it in confirmedNewRecipients (only for addresses the user supplied for a brand-new contact)."
151916
+ },
151917
+ {
151918
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_AGENT",
151919
+ "name": "Create-or-update-agent",
151920
+ "description": "Create or update an agent, an autonomous AI assistant.\n\n## When to use this tool\n\n- When the user asks you to create or update an agent\n\n## Before you build: is an agent the right tool?\n\nRun these checks before planning. If one fails, say so and propose the better path\nrather than building a degraded agent.\n\n**1. Can the platform do it?** The triggers below are the only events an agent can\nrespond to. Notably, there is no delay trigger: \"do X three days after event Y\" must\nbe re-expressed as a recurring schedule that queries for records that have reached\nthat state. Also confirm the request fits the cadence, delivery-channel, and\ndata-access limits documented in the planning and trigger sections below.\n\n**2. Is an agent the right fit?** An agent is right whenever a task needs to run\nautomatically on a trigger and involves any reasoning, including per-record\nclassification like \"categorize as ICP\" or \"classify meeting type.\" One ask isn't an\nagent: \"keep a collection of records matching criteria\" is a dynamic list. Scope every\nagent tightly (see \"Narrow the scope with filters\" below): ask how the relevant\nrecords enter Clarify, and if they share a label or marker, suggest a dynamic list and\nan `On add to list` trigger so the agent runs only for that subset rather than every\nrecord. For enrichment, use\n`find-leads`/`import-leads` for net-new prospects and a\nfiltered agent for existing records.\n\n## Before creating a new agent\n\nDo not immediately create an agent when the user asks. First, have a brief conversation\nto understand their goal and tailor the agent to their needs. Ask the user clarifying questions.\n\n1. **Check for existing agents**: Use `get-agents` to see what agents already\n exist in the workspace. This is a silent background check; if no agents exist, do not\n acknowledge it; just continue. If an agent already covers the requested use case, point the\n user to it instead of creating a duplicate. If one is close, mention it and ask whether they'd\n like to update the existing agent or create a separate one.\n You can only update or delete an agent you created. `get-agents` shows each\n agent's `Owner` (name and email); you own an agent when its Owner is you. Never pass the\n `agentId` of an agent owned by someone else; updating it will be rejected. When the only\n close match belongs to another person, create a new agent for this user instead of trying\n to update theirs.\n2. **Understand the use case**: Ask what they want the agent to do, what triggers it,\n and what the expected outcome is. Dig into vague requirements, e.g., if the user says\n \"categorize people as ICP\", ask what their ICP definition is (unless the org description\n already defines it). If they say \"update fields after meetings\", ask which fields.\n3. **Narrow the scope, or batch on a schedule**: When a trigger would fire on every record\n of a type (empty filters — e.g., all person creates, all deal updates) or on every email\n (an unfiltered `message` trigger), call this out to the user as high-volume before saving,\n rather than quietly narrowing it yourself. Explain the cost: every matching event starts a\n billed run, even when the agent reads the record and correctly decides to do nothing, so\n breadth drives cost regardless of the agent's judgment. Then propose a concrete way to\n tighten scope and let the user decide. Two levers:\n - **Filters** (specific lists, field conditions, record types) keep the per-event trigger\n but skip runs that don't match.\n - **A schedule trigger** replaces many per-event runs with one recurring run that queries\n for the records needing work and processes them in a batch — far fewer runs. Prefer this\n only when the work tolerates a delay (up to the schedule interval) and the target records\n can be found by a query (they've reached some state), not when the agent must react\n immediately (e.g., alert the moment a deal is won) or needs the change event's\n before/after values.\n4. **Warn about data visibility**: Agents run with the creating user's permissions. They can\n only see emails the user sent, received, or was CC'd on, and meetings the user is a\n participant of, unless teammates have shared access to meetings and emails via Settings.\n Tell the user this when creating agents that process emails or meetings, and suggest they\n ask teammates to share access via Settings if the agent needs broader visibility.\n5. **Suggest complementary agents**: If the agent they want would benefit from a\n prerequisite agent (e.g., they want post-meeting CRM updates but don't have an agent\n that classifies meeting types first), mention that and offer to create both.\n6. **Consider delivery channel**: If the agent produces output that the user needs to see\n (e.g., pipeline reviews, daily summaries, alerts when deals change stage), ask how they\n want it delivered. The only supported delivery channels are:\n - **Slack** (via Slack MCP connector): post to a channel or DM. Most common for scheduled reports and alerts.\n - **Email**: send a summary email to the user or a distribution list.\n Do not suggest delivery channels that don't exist (e.g., posting in chat, push notifications, in-app alerts).\n Only ask about delivery when the agent produces user-facing output, not for agents that silently update CRM fields.\n7. **Select tools and connectors**: Based on the agent's purpose, set `tools` and\n `mcp_servers` to explicitly list every tool the agent needs. Only listed tools are\n available; omitted tools cannot be used. For each tool, set its permission:\n - `always_allow`: the agent can use this tool without asking\n - `needs_approval`: the agent must ask the user before using this tool\n Set read-only tools (e.g., `query-data`, `get-records`) to `always_allow` by default.\n\n **Current state vs. history**: `query-data` reads the live CRM\n (PostgreSQL): current field values, open deals, this week's pipeline. It cannot see\n how a record changed over time. For any question about change history or\n point-in-time state (stage transitions, deals that moved to a later stage this\n week, time-in-stage, records created or updated per day, who changed a field and\n when) grant `query-analytics`, which queries the analytics event log\n of every CRM change (including historical stage transitions). Never have an agent\n approximate history from `_updated_at` or claim stage transitions aren't stored;\n they are recorded and queryable via `query-analytics`.\n\n For write tools (e.g., `create-or-update-records`, `send-email`), always ask the user\n whether they want the agent to use them freely or require approval each time. Present it\n concisely: \"Should the agent update records automatically, or ask you first?\"\n If the agent needs an MCP connector (e.g., Slack for posting messages, Linear for issue tracking),\n add it to `mcp_servers` and list the specific tools needed with their permissions.\n Server IDs come from existing agent configurations (via `get-agents`); calling\n with an unknown server ID returns an error listing the workspace's available MCP servers\n and their IDs.\n\n **Connect connectors before saving**: an agent can only use an MCP connector the\n user has actually connected. Before calling this tool with any `mcp_servers`, first\n check their status with `get-mcp-servers`. For any required connector that\n is not connected, call `connect-mcp-server` and wait for the user to finish\n connecting it (re-check with `get-mcp-servers`) before saving the agent.\n Never save the agent while a required connector is still unconnected; saving will fail\n validation, and the user should connect everything first. If the user must connect\n multiple connectors, get them all connected before the single create/update call.\n\n **Replacement semantics**: both `tools` and `mcp_servers` are full replacements, not\n merges. When updating an agent, always include the complete set of tools and servers the\n agent needs, not just the ones being added. Omitting a previously configured tool removes\n it. To keep existing tools unchanged, omit the `tools` / `mcp_servers` field entirely.\n When adding a tool to an existing agent, first use `get-agents` to read the\n current configuration, then pass the full set including the new addition. Whenever you change\n an agent's tools, review its instructions in the same update and revise any step that no\n longer matches the available tools, so instructions and tools never drift apart.\n\n **Tool dependencies**: some tools require other tools to function. If you include\n any tool on the left, you must also include the tool(s) on the right:\n - `query-data` → `get-schema` (the agent needs to load CRM schema before writing SQL)\n - `query-analytics` → `get-schema` (the agent needs CRM field names to read them out of the event log)\n - `create-or-update-records` → `get-schema` (the agent needs to discover writable field names)\n - `create-or-update-list` → `get-schema` (lists are defined by SQL queries that need schema knowledge)\n - `import-leads` → `find-leads` (importing requires search context from a find-leads search)\n\n **Write instructions in plain language**: describe what the agent should do (\"look up the\n person record\", \"update the company\", \"post to the channel\"), never the literal tool name or\n MCP tool ID. Tool names can change, and naming them in the instructions wastes a tool-search\n step and can confuse the agent. The `tools` and `mcp_servers` fields decide what the agent\n can use; the instructions only describe the goal.\n\n8. **Choose a model**: Set `model` from the task's complexity yourself. Use `fast` for simple, narrow,\n deterministic work (classification, field extraction, tagging/routing, short\n summaries) and high-volume triggers — it is faster and meaningfully cheaper. Use\n `smart` (the default) for multi-step reasoning, judgment, or quality-sensitive\n writing like emails and summaries. Only ask the user to pick when the task's\n complexity is genuinely ambiguous.\n\nSkip this planning step when the user provides a fully detailed specification upfront\n(trigger, instructions, and expected behavior). When updating an existing agent, skip\nplanning unless the request is vague and you need more context to make the right change.\n\n## Backfill existing records\n\nUsers often want an agent to process existing records, not just future ones. When they mention\n\"backfill\", \"run on existing data\", or \"process all current records\":\n\nDo not suggest creating a separate backfill agent. Instead, add backfill capability to the\nsame agent by including an hourly schedule trigger alongside the event-based triggers. The\nagent's instructions should include a backfill section that:\n1. Queries for unprocessed records in batches each run.\n2. Tracks progress by filtering for records that still need processing.\n3. When all records are processed, the agent edits its own instructions and triggers to\n remove the backfill logic and the schedule trigger, keeping only the event-based triggers\n for ongoing processing.\n4. Notifies the user via Slack that backfill is complete.\n\n## Popular agent ideas\n\nWhen the user is exploring what agents can do or has a vague request, suggest ideas from\nthis list if they are relevant to the user's business context. These are just starting\npoints; only suggest ones that make sense for the user's situation:\n\n- **Post-meeting CRM update**: After a meeting transcript is ready, extract key takeaways,\n update deal stage, next steps, and relevant fields on the associated records.\n- **Meeting type classification**: When a meeting is created, classify it (e.g., discovery,\n demo, negotiation, check-in) based on attendees, title, and context, then set the\n meeting type field.\n- **Post-email CRM update**: After an important email is received or sent, update relevant\n deal or contact fields (e.g., sentiment, next action).\n- **Weekly pipeline review** (Slack): Summarize pipeline changes, stale deals, and upcoming\n closes, then post to a Slack channel.\n- **Deal stage change alert** (Slack): When a deal moves to a key stage (e.g., closed-won,\n closed-lost), post a summary to Slack.\n\n## After creating or updating an agent\n\nOnce the agent is fully configured and ready to use, suggest a test run to the user. Do this after both creating\nand updating an agent. If you are still configuring it across multiple steps, wait until it is\ncomplete before suggesting a run.\n\nWhen you tell the user the agent is ready, also tell them which model tier it runs on\n(`fast` or `smart`) and why you chose it, so the model choice is never silent. On an\nupdate, mention the tier only when you changed it.\n\nIf the agent's trigger is broad or high-volume (fires on every record of a type, or on every\nemail), also tell the user you flagged it and what you suggested to narrow the scope — or, if\nthey chose to keep it broad, note that — so the cost trade-off is never silent.\n\nWhen you have just created a new agent, also give the user a brief heads-up that running an agent\nconsumes variable credits with a 1-credit minimum, and link the pricing docs:\nhttps://docs.clarify.ai/en/articles/15193255-agents#h_bbf4c7aa36. For an existing agent that has run at least once, use\n`get-agents` to inspect its stats and use Avg Credits/Run as its typical per-run cost.\nIf an agent has no run history, say there is no cost history yet and do not estimate or provide a\ncost range.\n\n## When the user reports an agent issue\n\nIf the user says an agent isn't working or asks why it did something unexpected,\ndo not immediately change the agent's instructions. First, consider:\n\n1. Check whether the agent's current instructions already address the issue.\n If they don't, you can update them directly.\n2. If the instructions look correct, use `get-agent-runs` to fetch the most\n recent run transcript and diagnose what actually happened.\n3. After diagnosing, explain your findings and suggest targeted fixes. Then offer\n to rerun.\n\nWhen the reported problem is a wrong or broken record URL, do not repair or guess a\ncorrected URL from the existing instructions; that text is not a source of truth for\nURLs. Take the correct URL from tool output, such as the `Link:` in the run transcript\n(via `get-agent-runs`), and copy it exactly, or rewrite the instructions to\nhave the agent use the `Link:` its own tools return."
151921
+ },
151922
+ {
151923
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_ARTIFACT",
151924
+ "name": "Create-or-update-artifact",
151925
+ "description": "Create a new artifact or write a new version to an existing artifact. An\nartifact is a named document with versioned content (e.g. a report, a plan,\na draft) that the user can view and revisit over time.\n\n## When to use this tool\n\nPick the surface that fits the ask:\n\n- Answer inline in the chat reply for a single fact, number, or short answer.\n Do NOT create an artifact for a quick factual lookup. A qualifier like\n \"quick\" or \"simple\" on a report or dashboard ask describes the effort, not\n the format, so that ask still gets an artifact.\n- Create an artifact whenever the user wants a durable, revisitable\n deliverable — a report, dashboard, analysis, breakdown, summary, overview,\n deck, or plan, even when they never say the word \"artifact\". Reach for one\n especially for a multi-part deliverable, or for current-state / snapshot\n data. Artifacts open at their own URL and the user revisits them, so produce\n one instead of dumping the whole thing into the chat transcript.\n- If the deliverable is really just a browsable set of records of a single\n object type (columns are direct fields, no aggregation or charts), a Clarify\n list via `create-or-update-list` fits better than an artifact.\n When the user asked for a report or analysis but a list would serve them,\n offer the list and explain the distinction first; if they explicitly asked\n for a list, just build it.\n\n## Referring to it in chat\n\nWhen you mention the result to the user, name it by what it is — a dashboard,\nreport, sales document, or plan. Do not call it an \"artifact\" unless the user\nused that word first.\n\n## Requirements and prerequisites\n\nComplete all four steps before you call this tool with new SQL. Every step is\nrequired.\n\n1. Read the \"artifact-docs\" context with\n `read-context`, and complete every step it requires. It names\n any further context to read, because which ones exist depends on the\n workspace.\n2. Run every query before you put it in `content`. Prove the independent ones\n together — emit them as one batch of parallel tool calls in a single turn,\n not one query per turn. Only a query that needs an earlier query's result\n stays serial.\n3. State any definition you resolved yourself, and ask the user whether to save\n it.\n4. Call `get-artifact-component-doc` once. Pass every\n `@clarify/ui/*` component this version uses in one `specifiers` list.\n Call it every time, even for a component you used before in this\n conversation, or one you already know. Docs can change between calls,\n within one conversation or overnight. Do not trust memory from earlier\n in this conversation for current props. The one-line summaries below\n help you pick a component. They do not give its props.\n\nNever guess a stage name, a date field, or a metric definition. Never put a\nquery in an artifact that you have not run. Never end the turn holding an\nunsaved definition you have not offered to save. Never use a component's\nprops from memory or from its one-line summary. Always call\n`get-artifact-component-doc` first. No exceptions.\n\n## How it works\n\nOmit `artifact_id` to create a new artifact (`name` is required in this\ncase). Pass an existing `artifact_id` to write a new version onto that\nartifact instead.\n\nSupply the new version in one of two ways — pass `content` or `edits`,\nnever both:\n\n- `content` — the full JSX source. Use it to create an artifact, or to fully\n replace an existing version.\n- `edits` — a list of targeted `{ old_string, new_string }` replacements\n applied to the currently-saved source on the server. Prefer this to update\n an existing artifact, especially a large one: you send only the changed\n regions, so the update is smaller and faster and never has to re-emit the\n whole file. Read the saved source first with\n `get-artifact-source` and copy each `old_string` exactly,\n whitespace included; each must match once, or set `replace_all` to replace\n every occurrence.\n\nWhen updating an artifact you did not just author in this conversation, first\nread its current source with `get-artifact-source` so you patch\nwhat is actually saved — and while you are there, fold any clear upgrade it\nflags into the same version (a hand-rolled pattern a current component now\ncovers, or stale query and chart code), and tell the user what you improved.\nSet `type` to \"Dashboard\" when the content you authored is an interactive\ndashboard; leave it unset for other kinds of library item.\n\n## Authoring the content (JSX)\n\n`content` is the JavaScript/JSX source for ONE React component — not an HTML\ndocument. Clarify transpiles it (Babel, automatic JSX runtime) and mounts it in\na sandboxed iframe; the scaffold owns the HTML shell, the theme, React/ReactDOM,\nand the mount call. Your source must:\n\n- Export a component named `ArtifactContents` (a default export also works).\n- Import what it uses from the provided modules: `react` (v19.2.8) (hooks),\n `recharts` (v3.8.1) (charts ONLY), `framer-motion` (v12.40.0) (animation —\n import `m`, not `motion`; the scaffold already wraps the mount in\n `LazyMotion`), and the Clarify design-system components below\n (`@clarify/ui/*` — chrome, layout, controls). JSX is supported — do not add a\n build step or import anything else.\n- Prefer the design-system components for structure and text (cards, buttons,\n the `@clarify/ui/text` typography set); reach for bespoke components and/or\n standard HTML elements only for what they don't cover.\n- Render ALL text through the `@clarify/ui/text` components (`Heading1`–`Heading4`,\n `Text`, `CaptionText`, …) — not raw `<p>`/`<span>`/`<h*>` and not Tailwind\n text utilities (`text-lg`, `font-semibold`, `text-gray-500`) — so type and\n color stay on the design scale.\n- Use Tailwind utility classes for LAYOUT ONLY — the theme ships the standard\n layout, spacing, and sizing utilities (e.g. `className=\"flex flex-col gap-4 p-4\"`).\n For a one-off color use the theme's CSS custom properties inline\n (e.g. `style={{ color: 'var(--color-brand-500)' }}`); chart colors come from\n `useArtifactTheme()` instead (see Charts below). Avoid arbitrary-value\n classes (`p-[37px]`) — only standard utilities are guaranteed to be emitted.\n- Don't set background colors (e.g. `bg-gray-50`). Let the theme background\n show through, and use `@clarify/ui/card` for raised surfaces. Only set one\n when the user asks for a specific color.\n- NOT emit `<!doctype>`, `<html>`, `<head>`, `<body>`, a root/mount node, a\n `<script>` tag, or any `createRoot(...)` call — the scaffold provides all of\n that, and emitting them breaks the artifact.\n\n## Clarify design-system components\n\nThese `@clarify/ui/*` modules are available in the frame and render with the\nworkspace theme (light/dark) automatically. Import only what you use. See\n\"Requirements and prerequisites\" above for when to call\n`get-artifact-component-doc` for a component's exact props.\n\n- `@clarify/ui/button` — A themed button. Use for actions inside an artifact (filters, toggles, links). Standard button attributes (onClick, disabled, type) work as usual.\n- `@clarify/ui/card` — A themed surface for grouping content into panels — the default frame for a section, chart, or stat. Compose the parts; CardTitle renders a heading, CardDescription muted subtext.\n- `@clarify/ui/text` — The themed typography set — use these for ALL text instead of raw <p>/<span>/<h*> or Tailwind text utilities, so weight, size, and color stay on the design scale. DisplayText/Heading1–Heading4 are headings (largest → smallest); CaptionText is small muted; LinkText is an anchor.\n- `@clarify/ui/avatar` — A circular avatar for a person or company. Compose AvatarImage with an AvatarFallback (initials shown while the image loads or is missing). Set size via className (e.g. size-8).\n- `@clarify/ui/badge` — A small status/label pill — deal stage, a count, a state.\n- `@clarify/ui/tabs` — A sectioned content switcher. Each TabsTrigger and its TabsContent share a `value`; drive it with defaultValue (uncontrolled) or value + onValueChange.\n- `@clarify/ui/clarify-avatar` — Clarify's branded avatar: shows the image, else colored initials, shaped by the object type (round for people, squared for companies/deals).\n- `@clarify/ui/name-chip` — A compact name + avatar chip for a person or company (a deal owner, a contact). Falls back to colored initials when there is no image.\n- `@clarify/ui/dashboard-header` — The header at the top of a dashboard — title and an optional scope line (period, owner, filters applied). The \"Last updated\" freshness label and the refresh-all button are added automatically from the dashboard's own queries; do not pass them. Use exactly one per dashboard; for a section title inside the report use BlockHeader instead.\n- `@clarify/ui/filter-bar` — A row that lays out filter and selector controls under the header, for reports meant to be re-sliced by the viewer. Skip it on a fixed view; it is only layout — put the controls inside it.\n- `@clarify/ui/date-range-picker` — A dashboard's time control, placed in the FilterBar. Only add it when the artifact has ClickHouse (event) queries the range can scope — timeRange applies to ClickHouse only, so a Postgres-only (current-state) artifact must not include one; it would scope nothing. It opens on the last 30 days by default, so keep that default unless the report needs another window. To change it, defaultQuickSelect must be one of the built-in presets exactly — \"Today\", \"Yesterday\", \"Last 7 days\", \"Last 30 days\", \"Last 90 days\", \"Month to date\", \"Year to date\", or a quarter label like \"Q3 2026\" — an unrecognized label (e.g. \"Last 6 months\") is ignored and falls back to the 30-day default; for any other span pass defaultDateRange instead. Hold its onApply({ from, to }) range in state and pass it to each ClickHouse section as useQuery(sql, { timeRange: range }) — the backend scopes the query to it, so the picker label always matches what the queries run. Its Clear button sets the picker to \"all time\": onApply then fires with from/to undefined, so useQuery runs over all data — never pass a partial range. onApply also gives `previous` (the equal-length window just before the range, present only for a preset) for period-over-period comparison. Never fetch all rows and slice client-side, and never interpolate the dates into your SQL.\n- `@clarify/ui/filter` — A dropdown filter for the FilterBar — lets the viewer narrow the dashboard by a value (owner, stage, region). Single-select by default (value is a string, onChange fires undefined when cleared); pass multiple for multi-select (value is a string[]). Hold the selection in state and pass it to each section's useQuery so the backend scopes the query; never fetch all rows and slice client-side.\n- `@clarify/ui/block` — The card every metric, chart, or table sits in — never render one bare. Give it the section title with `title` (plus optional `info` for a definition and `description`), and pass the section's `query` (a useQuery result). The Block renders that query's loading skeleton, error, empty, and refresh states, then reveals your content once the rows arrive — so never hand-write isLoading/error/empty branches. Build the content from `query.rows`. Every query-driven block MUST also pass `underlyingQuery={{ sql, source?, title?, columns }}` — the detail records behind the aggregate — so the block offers a \"See underlying data\" drilldown (a block with a `query` but no `underlyingQuery` is incomplete). Author the detail SQL as the individual records (no GROUP BY), match its `source` to the block's query, and author `columns` with the right headers, formats (currency/percent/count/date), alignment, and any `render` — leave `columns` out only when you can't determine them, and the table falls back to auto-deriving number/date/text from the query's column types. Make every row's name link to its record by projecting `entity_id` and `entity_type` next to the record's name (aliased `name`) — on Postgres `deal._id AS entity_id, 'deal' AS entity_type, deal.name AS name` (use the record's own entity in place of `deal`); on ClickHouse `entity_id`, `entity_type_base AS entity_type`, and `argMax(JSONExtractString(properties,'name'), timestamp) AS name`. Keep a `name` column in `columns` — it renders the record as a clickable link — but leave `entity_id` and `entity_type` out of `columns`; they only carry the link target and never render.\n- `@clarify/ui/block-header` — A block's header — a title, an optional description, an optional info tooltip for a definition, and an action row. Prefer passing `title`/`info`/`description` straight to `Block` (it renders this header for you); reach for BlockHeader directly only for a header outside a Block. Keep it to title, description, and one info affordance.\n- `@clarify/ui/section-divider` — A light separator, optionally labeled, between clusters of blocks in a long artifact. Prefer whitespace first; reach for this only when a section break needs to be explicit.\n- `@clarify/ui/use-query` — The only way to fetch live workspace data — a React hook with loading, refreshing, and error state, a refresh action, and auto-refetch when the SQL or timeRange changes. Give each data section its own useQuery so one slow or failed query never blanks the others. Pass a time window as useQuery(sql, { timeRange }) to scope the query server-side; never interpolate dates into the SQL. Give every query a title — the same string you pass to that Block — surfaced in server logs so a failing query is identifiable without decoding its SQL. Show a period-over-period comparison by default on time-scoped sections: add compareToPrevious — pass `range.previous ?? true` (`true` runs the same SQL for the equal-length window right before timeRange; the DateRangePicker onApply payload's `previous` is calendar-precise) — and read the prior period from `previousRows` (same shape as `rows`). It is a no-op without a timeRange.\n- `@clarify/ui/artifact-theme` — The theme for charts. Call useArtifactTheme() and spread its `charts` values onto stock Recharts props so colors, axis, legend, and tooltip match the report and re-theme with light/dark — never hardcode chart colors. Pick the color group by the decision tree (stop at first match): positive/negative state → `charts.positive`/`charts.negative`/`charts.neutral`; ordinal dimension (stage, priority, tier, size/amount band) → `charts.sequential[i]` light-to-dark ordered by the band sequence (not the measure), even for a single series; more than one series in one space → `charts.categorical[i]` (six colors, wrap past six with `categorical[i % 6]`; `charts.other` for null/unknown only); otherwise a single `charts.primary`. Give pie/donut slices a thin `charts.pieStroke` border (half-opacity, blends light/dark). The legend key is a circle in our font (charts.legend). Order the data and the legend by rank (the measure, descending), else the data's natural order; alphabetical only as a last resort, never by default. Size the chart on the chart itself with `responsive width=\"100%\" height={320}` — a fixed pixel height is required and a parent div's height does not flow into the chart. Give the Y axis headroom so the tallest value never touches the top — on bar/line/area set `domain={[0, (max) => Math.ceil(max * 1.1)]}` on the `<YAxis>`.\n- `@clarify/ui/value-text` — Formats a single value for display — number, currency, percent, count, duration, or date. Reach for it for every numeric or date value so formatting stays consistent; it inherits the surrounding text size and color. Percent takes a fraction (0.12 → 12%); duration takes milliseconds; set `compact` to abbreviate large numbers ($2,480,000 → \"$2.48M\").\n- `@clarify/ui/trend-indicator` — A change indicator: a direction arrow, the change value, and a comparison label. You rarely build this by hand — on a KPI, add a `comparison` to `MetricBlock` (`comparison={{ field, label }}`) and it renders this for you from the query. The comparison is free: `useQuery(sql, { compareToPrevious })` re-runs the SAME query for the prior period, so you never write a second query or diff values yourself — no reason to skip a trend on a time-scoped tile. Construct `TrendIndicator` directly only for a bespoke comparison whose two sides you already hold. `direction` sets the arrow; `sentiment` sets the color and defaults from direction — set `sentiment` to invert when up is bad (churn, cost).\n- `@clarify/ui/metric-block` — A single KPI tile: a small title (with an optional definition tooltip), a large value, and — under it — an optional period-over-period trend and/or a muted caption. Self-contained (its own card) — drop it straight into a KPI strip, never wrap it in a Block. Group them in a 3-across grid and wrap to more rows as the count grows. Set `compact` to abbreviate large headline numbers ($2.48M, 47K). Give each tile its OWN `query` (a useQuery result) whose SQL returns exactly one row and the single value shown, and read it as `query.rows[0]?.<col>`. Do the aggregation in SQL (count/sum/avg/…, or a ratio via `countIf(…) / count()`) so a zero result shows as the value (0) rather than an empty state — never pass a multi-row query and derive the value in JS (`rows.reduce(…)`, summing or dividing across rows, or plucking one row out of many). Show a period-over-period trend by default whenever the tile is time-scoped: run the query with compareToPrevious and pass `comparison={{ field: \"<col>\", label: \"vs previous period\" }}` — `field` names the same column `value` reads, and the tile pulls the prior value and window straight from the query and computes the change itself (never compute a delta in JSX). Add `isInverted: true` for up-is-bad metrics (churn, cost). It shows a % for a nonzero prior, the raw figure for a prior of 0 (0 → 10 reads \"+10\"), or \"Same as …\" when unchanged; a missing/non-numeric prior or value shows no trend. `description` is a separate muted caption. Whenever the tile has a `query`, it MUST also pass `underlyingQuery={{ sql, source?, title?, columns }}` — the detail records behind the metric — so the tile offers a \"See underlying data\" drilldown (a query-backed tile with no `underlyingQuery` is incomplete); author it as the individual records (no GROUP BY) and give `underlyingQuery.columns` the right headers and formats, leaving them out only when the right columns are unknown. Make every row's name link to its record by projecting `entity_id` and `entity_type` next to the record's name (aliased `name`) — on Postgres `deal._id AS entity_id, 'deal' AS entity_type, deal.name AS name` (use the record's own entity in place of `deal`); on ClickHouse `entity_id`, `entity_type_base AS entity_type`, and `argMax(JSONExtractString(properties,'name'), timestamp) AS name`. Keep a `name` column in `columns` — it renders the record as a clickable link — but leave `entity_id` and `entity_type` out of `columns`; they only carry the link target and never render. A static tile with no `query` skips it.\n- `@clarify/ui/data-table` — A sortable table of rows — reach for it whenever a block shows tabular data. Presentational: it renders already-loaded rows, so wrap it in a Block that owns the loading / empty / error chrome and pass `rows={query.rows}` and `truncated={query.truncated}`. For columns, either pass `columnTypes={query.columns}` to auto-derive them (numbers right-align, dates format, headers show even on 0 rows) and omit `columns`; or pass explicit `columns` — `{ key, header?, format?, align?, render? }` — when you need currency/percent/count formatting or a custom cell (auto-derive only knows number/date). `key` reads and sorts the cell; `header` defaults to `key`; `format` is one of number | currency | percent | count | duration | date; `align=\"right\"` suits numbers; `render: (row) => …` draws a badge/chip/link (sorting still follows `key`). For sticky total / subtotal rows, pass `footerRows` — an array of `{ cells: { [columnKey]: cell } }`, one entry per row, top-to-bottom; each cell is EITHER `{ aggregate: \"sum\" | \"avg\" | \"min\" | \"max\" | \"count\" }` (computed over the shown rows and formatted with that column's format; `count` renders as an integer; on a date column only `count` applies, the others are dropped) OR `{ content: <node> }` for a label (\"Total\") or a precomputed value. An aggregate totals only the shown rows, so a `sum` under-counts when `truncated`. Every row always renders; by default ~10 show before the table scrolls — usually omit `visibleRows` and set it only to change how many are visible before scrolling, never to the total row count (that caps nothing and falls back to the default ~10). Do aggregation and column selection in SQL — never trim wide rows in the component.\n- `@clarify/ui/chart-tooltip` — The Recharts `<Tooltip>` wearing Clarify's tooltip frame (dark rounded card). It IS the Recharts Tooltip, so render it directly inside a Recharts chart (`<ChartTooltip />`) and never pass it to another element's `content` prop — nesting one inside a Tooltip's `content` recurses without end. It only restyles the surrounding card and leaves Recharts to render the content.\n\n## Fetching live data\n\nRender live workspace data with the `useQuery` hook (`@clarify/ui/use-query`) —\nthe preferred way to fetch. It wraps the data path with loading, error, and\nrefresh state, so a section needs no fetch boilerplate. The iframe has no\nnetwork access, so never `fetch` or import from another origin.\n\n- `const query = useQuery(sql)` → `{ rows, columns, rowCount, truncated, isLoading, isRefreshing, error, refresh, source }`.\n Import it from `@clarify/ui/use-query`. Give EACH data section its own\n `useQuery` — never gate the whole artifact behind one spinner — so one slow\n or failed query never blanks the sections that are ready.\n- **Hand the query to a `Block`; do NOT hand-write loading/error/empty.**\n Wrap each section in `<Block title=\"…\" query={query}>…</Block>` (or, for a\n KPI, `<MetricBlock … query={query} value={query.rows[0]?.x} />`). The Block\n owns that query's loading skeleton, error state, empty state, and refresh\n control, and reveals your content once the rows arrive. Never write your own\n `if (isLoading)` / `if (error)` / `if (!rows.length)` branch or a\n `LoadingOrError`-style helper, and never pass `isLoading ? null : value` —\n that duplicates the Block and drifts from the design system. Read `rows`\n straight off the query (`query.rows`) for the content you render inside.\n- **Do all aggregation, math, and filtering in SQL — never in JS.** The query\n returns exactly the rows and values you render; JSX only reads `query.rows`\n and displays them. Never sum, divide, average, count, slice, or filter across\n rows in JSX (`rows.reduce(…)`, `rows.filter(…)`, `rows.slice(…)`) — push it\n into the SQL (`count()`, `sum(m_amount)`, `avg(…)`, a ratio via\n `countIf(…) / count()`, or a `WHERE` / `GROUP BY` / `ORDER BY` / `LIMIT`).\n A `MetricBlock` is the scalar case: its query returns exactly one row and the\n single value shown, read as `query.rows[0]?.<col>` (a scalar query also makes\n a zero result render as `0` rather than an empty state).\n- **Show a period-over-period trend by default.** \"Is this up or down from\n before?\" is the first question a reader asks of any KPI or trend, so a\n comparison is the highest-value thing most sections carry — add one to\n **every time-scoped `MetricBlock` and single-measure line chart** unless a\n prior period is genuinely not meaningful (see the skip list). This costs you\n nothing extra: do NOT write a second query and do NOT diff values in JS. Add\n `compareToPrevious={range.previous ?? true}` to the section's EXISTING\n `useQuery` (the DateRangePicker's calendar-precise prior window, else the\n equal-length shift) — the host re-runs that same SQL for the prior period and\n returns it as `previousRows` (same shape as `rows`). Never hesitate for lack\n of a comparison query; the flag *is* the comparison query.\n - On a `MetricBlock`, pass `comparison={{ field: \"<col>\", label: \"vs previous period\" }}`\n where `field` is the same column `value` reads; the tile pulls the prior\n value and window from the query and computes the change itself — never\n compute a delta in JSX. Add `isInverted: true` when up is bad (churn, cost).\n - On a line chart, plot the prior window as a second series (see \"Comparing\n two periods on a chart\" under Charts).\n - Skip it only where there is no meaningful prior period: a non-time snapshot\n (no `timeRange`), a Postgres current-state read, a pure breakdown or\n distribution (share by stage / owner / category), or a cumulative\n running-total measure. It is a no-op without a `timeRange`.\n- The result carries `{ columns, rows, rowCount, truncated }`. `columns` is\n `{ name, type }[]` (type is one of number | string | boolean | date |\n datetime), present even for a 0-row result — hand it to a `DataTable`'s\n `columnTypes` to auto-align/format and keep headers on an empty result. When\n `truncated` is true the row cap was hit — tell the user the data was limited.\n `error` is the typed failure (with a `code`); `refresh()` re-runs the query.\n- Choose the store per query with `useQuery(sql, { source })`. The default\n (omit it) is ClickHouse, the analytics event log — use it for history,\n trends, point-in-time, and stage transitions. Pass `{ source: 'postgres' }`\n only when the question is about current record state (the values as they are\n now, a plain SELECT), which the event log can't answer as directly. The SQL\n dialect differs per source (see the schema guidance below), so pick the\n source first, then write for it.\n- Pass a static SQL string literal so the query stays predictable and\n validatable — never build SQL from runtime values, including dates. To scope\n a query to a time window, pass the range to `useQuery` (below); the backend\n applies it — never interpolate `from`/`to` into the SQL.\n- To scope a section to a time window (e.g. a DateRangePicker's range), pass it\n as the second argument: `useQuery(sql, { timeRange: { from, to } })`. The\n backend applies it as a table-level row filter on `analytics.event`, so every\n read of that table — nested subqueries, CTEs, and each `UNION` branch — is\n filtered independently and the SQL stays static; never add your own\n `timestamp` bounds for the picker's window. `useQuery` re-runs on its own when\n the SQL or range changes, so the report re-slices on Apply with no extra\n wiring. `timeRange` applies to the ClickHouse source only — a Postgres query\n ignores it, so write explicit date `WHERE` filters there.\n- **Scope every ClickHouse query to the artifact's window with `{ timeRange }`.**\n The default source is the event log, so a metric read over all history is\n almost never what the reader wants — pass `{ timeRange }` to every ClickHouse\n `useQuery`, and give the artifact a date control (a\n `@clarify/ui/date-range-picker`) to drive it. Add the picker **only when the\n artifact has ClickHouse queries** — `timeRange` applies to ClickHouse only, so\n a Postgres-only artifact (current record state) has nothing for it to scope\n and must not include one; write explicit date `WHERE` filters in that SQL\n instead. The picker defaults to the last 30 days, so a dashboard opens on a\n bounded window and its queries stay fast; the viewer can Clear it to all time.\n For a fixed snapshot with no picker, state the window in the UI.\n- **Give every `useQuery` a `title` — the same string you pass to that\n section's `Block`.** So a section wrapped in `<Block title=\"Deals by stage\">`\n fetches with `useQuery(sql, { title: 'Deals by stage' })`. The title is\n forwarded to the server logs so a failing query is identifiable without\n decoding its SQL; it has no effect on the result.\n\n### Minimal example\n\n```jsx\nimport { BarChart, Bar, XAxis, YAxis, CartesianGrid } from 'recharts';\nimport { useQuery } from '@clarify/ui/use-query';\nimport { useArtifactTheme } from '@clarify/ui/artifact-theme';\nimport { Block } from '@clarify/ui/block';\n\nexport function ArtifactContents() {\n const { charts } = useArtifactTheme();\n const query = useQuery(\n \"SELECT entity_type, count() AS events FROM analytics.event WHERE workspace_slug = '<your workspace>' GROUP BY entity_type ORDER BY events DESC\",\n { title: 'Events by type' },\n );\n\n // No isLoading/error/empty branches — the Block renders those from `query`\n // and shows the chart once `query.rows` is ready.\n return (\n <div style={{ padding: 24 }}>\n <Block title=\"Events by type\" query={query}>\n <BarChart responsive width=\"100%\" height={320} data={query.rows}>\n <CartesianGrid stroke={charts.grid.stroke} vertical={false} />\n <XAxis dataKey=\"entity_type\" tick={{ fill: charts.axis.tick, fontSize: charts.axis.fontSize }} />\n <YAxis domain={[0, (max) => Math.ceil(max * 1.1)]} tick={{ fill: charts.axis.tick, fontSize: charts.axis.fontSize }} />\n <Bar dataKey=\"events\" fill={charts.primary} />\n </BarChart>\n </Block>\n </div>\n );\n}\n```\n\n## Charts\n\nCharts are Recharts (imported from `recharts`), styled by the artifact theme so\nevery report's charts read as one system. Four rules:\n\n- **Size the chart with `responsive` + `width=\"100%\"` + a fixed pixel `height`,\n set on the chart itself** — e.g. `<BarChart responsive width=\"100%\" height={320}>`.\n `responsive` keeps the width fluid; the height must be an explicit number\n because a chart has no intrinsic height. Put these on the chart, not a parent\n `<div>` — Recharts draws to the chart's own box, so a parent's height does not\n flow in and a bare `<BarChart responsive>` collapses to nothing. Do not use\n `ResponsiveContainer`.\n- **Give the Y axis headroom — the tallest value must never touch the top of\n the frame.** Recharts otherwise caps the domain at the data's max, so the\n biggest bar or point runs into the top edge. On bar/line/area, set\n `domain={[0, (max) => Math.ceil(max * 1.1)]}` on the `<YAxis>`: keep the\n baseline at 0 and round the top up past the tallest value. Pie/donut have no\n axis, so this does not apply.\n- **Take every color and label style from `useArtifactTheme()`** — never a\n hardcoded hex, a raw `var(--color-*)`, or an opacity/tint variant.\n `const { charts } = useArtifactTheme()` gives the color groups below plus\n `charts.axis`, `charts.grid`, `charts.legend`, `charts.tooltip`, and\n `charts.cursor`; spread each onto the matching Recharts prop (`fill`,\n `stroke`, `tick`, …). Color must encode something — if it doesn't, don't\n spend it; most charts are single-series and monochrome. Pick the group by\n this decision tree, top to bottom, stop at the first match:\n\n 1. **Positive/negative or good/bad state** (won vs lost, on-target vs\n at-risk, period delta) → the semantic set: `charts.positive`,\n `charts.negative`, `charts.neutral` (excluded/no-value). If a chart uses\n semantic colors, every series in it is semantic — never mix semantic and\n categorical.\n 2. **Ordinal dimension** (stage, priority, tier, score/size band, an age or\n amount bucket like \"51-250\" or \"1K-5K\") → `charts.sequential[i]`, light\n to dark. This holds even for a single series — a lone bar or line over an\n ordinal dimension is sequential, NOT `primary`. Order the axis by the\n dimension's own sequence (1-10 → 100K+, P0 → S4), never by the measure,\n so lightness climbs monotonically down the axis; spread across the ramp\n rather than clustering (e.g. steps 0, 2, 3, 5). Steps 0–2 are fills only\n — never lines or points. Never put a categorical color on an ordinal\n dimension.\n 3. **More than one series in the same space** (stacked/grouped bar,\n multi-line, stacked area, pie, donut, treemap) → `charts.categorical[i]`\n in order. Six distinct colors; beyond six categories, wrap with\n `charts.categorical[i % 6]` so colors repeat rather than run out.\n `charts.other` is reserved for \"Unknown\"/\"No value\"/excluded categories\n only — never a real category past the sixth — and always sits last in\n stack and legend.\n 4. **Everything else** → a single `charts.primary`. When in doubt, this.\n\n Assign deterministically so the same data yields the same colors on every\n render and a category keeps its color across a dashboard. For categorical\n and `primary`, sort rows by the charted measure descending, then assign in\n token order. For a sequential/ordinal chart, order rows by the dimension's\n natural sequence instead (rule 2), not the measure, so the ramp reads in\n order. This row order sets the legend order too — the legend follows\n row/series order. The precedence in general: order by rank (the charted\n measure, descending); if there is no measure to rank by, keep the data's\n natural order; fall back to alphabetical only as a last resort, when neither\n exists — never sort categories alphabetically by default. When a chart\n plots more than one series, give each a `name` and add\n `<Legend iconType={charts.legend.iconType} wrapperStyle={{ color: charts.legend.text, fontSize: charts.legend.fontSize }} />`.\n State the rule you applied when explaining a generated chart (\"single\n series, so primary\"). See the `@clarify/ui/artifact-theme` entry above for\n the full pattern.\n- **Give pie/donut slices a blended border.** Spread\n `stroke={charts.pieStroke} strokeWidth={1}` onto each `<Cell>` — a\n half-opacity separator that reads in both light and dark. Never set a solid\n white stroke; it looks wrong on a dark background.\n- **Render the tooltip as `<ChartTooltip />` (from `@clarify/ui/chart-tooltip`)\n directly inside the chart** — it IS the Recharts `<Tooltip>`, already framed.\n Never pass it to another element's `content` (e.g. `content={<ChartTooltip/>}`):\n `ChartTooltip` is the Tooltip, so nesting one inside a Tooltip's `content`\n recurses without end and crashes the report.\n- **Don't bucket a metric by time unless the user asked for that grouping.**\n Reach for a time `GROUP BY` (`toDate(timestamp)`, `toStartOfWeek/Month(…)`)\n ONLY when the request names the granularity — \"by month\", \"per week\",\n \"grouped by day\", \"weekly\", \"monthly\". \"Over time\", \"trend\", or \"as a line\n chart\" is NOT that request: a time series already IS a trend, so it can't be\n the trigger. By default show a single aggregate over the report's window —\n \"deals created\", not \"deals created per month\" — and let the report's date\n filter (`timeRange`, above) set the period. Grouping by a non-time category\n (stage, owner) is unaffected.\n- **Compare two periods on a line chart by default.** A single-measure line\n chart over the window should almost always show the prior period too, so\n fetch with `compareToPrevious` and draw it as a second series: pair\n `query.rows[i]` with `query.previousRows[i]` into one data array\n (`{ bucket, current, previous }`) and plot two `<Line>`s. Color them\n `charts.categorical[0]` / `charts.categorical[1]` (never hardcode); a dashed\n previous line (`strokeDasharray`) reads as the baseline. This index pairing\n is chart data shaping, not the banned in-JSX aggregation. Skip the overlay\n only for a multi-series chart (a breakdown already uses the series slots) or\n a non-time category chart.\n\n## The `analytics.event` table (ClickHouse)\n\nRead-only SQL runs against ClickHouse, not PostgreSQL — use ClickHouse syntax\n(`JSONExtractString`, `toDate`, `argMax`, etc.). Every CRM record lives in\nONE append-only CDC event log, `analytics.event` — NOT a table of current\nrecords; every create/update/delete is its own row. There is no `deal` /\n`company` / `person` table (`FROM deal` fails with \"Unknown table\nexpression identifier\"). Always query `FROM analytics.event` and pick the\nentity with `WHERE entity_type = '<type>'`.\n\nSchema is inspired by PostHog: one wide event table with a JSON-stringified\n`properties` payload plus a structured `actor` column. Hot keys are promoted\nto materialized columns (below); everything else is read from `properties`\nwith `JSONExtract*`.\n\nEvery event carries a FULL snapshot of the record's fields in `properties` —\ncreate, update, and delete alike. An update is not a delta: it repeats every\nfield the record has, not just the ones that changed. So the single latest\nevent per entity already holds every current field, and you never need to\nstitch fields together across events. (The one exception: fields marked\nsensitive are omitted from `properties` entirely.)\n\n- `_id` (String) — Event id\n- `workspace_slug` (String) — Workspace (tenant) slug\n- `entity_type` (String) — Subject type: `deal`, `company`, `person`,\n`meeting`, `message`, or `c_<slug>` for a custom object\n- `entity_id` (String) — Subject record id\n- `type` (String) — Event type: `clarify:create` |\n`clarify:update` | `clarify:delete` (full enum below)\n- `timestamp` (DateTime64(6,'UTC')) — Event time; use `toDate(timestamp)` for day grouping\n- `properties` (String/JSON) — A full snapshot of the record's fields at event\ntime (every field, not just the changed ones); read with\n`JSONExtractString/Float/Bool(properties, '<field>')`\n- `diff` (String/JSON) — On update events, the field-level changes this event\napplied: a JSON array of `{op, path, val, oldVal}` (`path` locates the field,\n`oldVal` → `val` is the transition). Empty (`''`) on create and no-op events.\nUse it to detect WHEN a field changed — see \"Detecting when a field changed\"\n- `actor` (Tuple) — `actor._id`, `actor.anonymous_id`, `actor.entity`,\n`actor.source_id` (all String, native paths — no `JSONExtract` needed); usable in `GROUP BY` / `ORDER BY`\n- `m_stage` (String) — Materialized `JSONExtractString(properties,'stage')`; empty if absent\n- `m_amount` (Float64) — Materialized `JSONExtractFloat(properties,'amount')`; `0` if absent\n- `m_close_date` (Nullable(Date)) — Materialized `toDateOrNull(properties.close_date)`;\n`NULL` if absent/unset. A native date — range-filter and group it directly\n(`m_close_date >= '2026-01-01'`, `toStartOfMonth(m_close_date)`) with no `toDate` wrapper\n\n### Reading fields is ClickHouse, not PostgreSQL\n\nPostgreSQL JSONB operators `->` and `->>` do not exist in ClickHouse — `properties->>'description'` fails. Read fields with `JSONExtractString(properties, 'description')` (or `JSONExtractFloat` / `JSONExtractBool`). There is no `JSONExtractFloat64` — use\n`JSONExtractFloat`. If a query fails because a function does not exist, use\nthe alternative ClickHouse suggests (e.g. `JSONExtractRaw`).\n\n### Materialized columns\n\nPrefer the materialized columns `m_stage` / `m_amount` / `m_close_date` over\n`JSONExtract*(properties, 'stage'|'amount'|'close_date')` when the key matches —\nthey are typed, indexed, and skip a JSON parse per row. They are populated from\nwhatever `properties.stage` / `properties.amount` / `properties.close_date`\ncarries on each row, regardless of `entity_type`, so they work for a custom\nobject with those fields too. For `m_stage` / `m_amount`, empty / `0` means the\nevent didn't carry the key. `m_close_date` instead uses `NULL` for an absent or\nunset close date (a date has no neutral sentinel), so test presence with\n`m_close_date IS NOT NULL`, not `!= ''`.\n\n`m_stage` (like every snapshot field) is the value the record held *when the\nevent fired*, not a transition. Counting `m_stage = 'Won'` answers \"records that\nwere in Won while something happened to them\" — an enrichment sweep, a note, or\nan owner change re-emits the unchanged stage — so it tracks activity, not\noutcomes. For \"records that *entered* a stage\", read `diff` instead (see\n\"Detecting when a field changed\").\n\n### Allowed `type` values\n\n- `CdcEventType` — `clarify:create`, `clarify:update`, `clarify:merge`, `clarify:delete`, `clarify:add-to-list`, `clarify:remove-from-list`, `clarify:set-relationship`, `clarify:unset-relationship`, `clarify:grant-access`, `clarify:update-access`, `clarify:revoke-access`, `clarify:meeting`\n\n### Scope every query (this is what keeps it fast)\n\nThe table is a `ReplacingMergeTree` ordered by\n`(workspace_slug, entity_type, entity_id, timestamp, _id)`. Filter from the\nleft of that key so ClickHouse prunes the table:\n\n- Always make `workspace_slug = '<your workspace>'` the first `WHERE`\ncondition — it is the leading sort-key column and prunes almost the whole\ntable. Use the Workspace value from your context; if it isn't there, call the\n`get-current-user` tool to get it before querying.\n- Always filter by `entity_type` next; add `entity_id` too for\nsingle-record questions (that hits the sort-key prefix and reads a tiny slice).\n- Time-series / activity / trend queries must also carry a `timestamp` range\n(e.g. `timestamp >= now() - INTERVAL 90 DAY`) — both to scope the report and\nto bound the scan. Current-state reconstruction is the exception (below): it\nneeds the full history per entity, so do NOT put a `timestamp` floor on it.\n- Filtering only by columns outside the sort key (`type`, `m_stage`,\n`m_amount`, `m_close_date`, or any `JSONExtract*` value) forces a full scan\n— pair them with the sort-key columns above.\n- Name the columns you need — avoid `SELECT *`. It returns the wide `data`\npayload and computes the `properties` JSON alias for every row; list just\nthe columns the report uses (`entity_id`, `timestamp`, `m_stage`, …).\n- Prefer `GROUP BY` on low-cardinality columns (`entity_type`, `m_stage`,\n`toDate(timestamp)`, `entity_id`), not on a freeform\n`JSONExtractString(properties, '<field>')` of a high-cardinality field (a\nnote, description, or free text) — that forces a JSON parse per row and\nexplodes the group count.\n- When you only need to eyeball a few recent rows, bound the read with\n`ORDER BY timestamp DESC LIMIT <n>` instead of scanning the whole slice.\n- Date literals: prefer relative helpers (`now() - INTERVAL 1 MONTH`,\n`toStartOfMonth(now())`, `today() - 7`) — you have no reliable wall clock,\nand a hardcoded boundary silently drifts. A bare\n`timestamp >= '2026-04-01T00:00:00Z'` rejects the ISO `T`/`Z`; use\nspace-separated `'2026-04-01 00:00:00'`,\n`parseDateTime64BestEffort('2026-04-01T00:00:00Z')`, or\n`CAST('2026-04-01T00:00:00Z' AS DateTime64(6, 'UTC'))`.\n\n### Good vs bad query shapes\n\n- Scope by the sort key, don't filter on a column alone:\n- Bad: `SELECT count() FROM analytics.event WHERE m_stage = 'Won'` — no\n `workspace_slug` / `entity_type`, so it scans every workspace.\n- Good: `... WHERE workspace_slug = '<your workspace>' AND entity_type = 'deal' AND m_stage = 'Won'`.\n- Name columns, don't `SELECT *`:\n- Bad: `SELECT * FROM analytics.event WHERE ...`.\n- Good: `SELECT entity_id, timestamp, m_stage FROM analytics.event WHERE ...`.\n- Bound a trend with a time range:\n- Bad: `SELECT toDate(timestamp) AS day, count() FROM ... GROUP BY day` with\n no `timestamp` floor — scans all history.\n- Good: add `AND timestamp >= now() - INTERVAL 90 DAY`.\n- Group low-cardinality, cap exploratory reads:\n- Bad: `... GROUP BY JSONExtractString(properties, 'notes')`, or reading raw\n rows with no `LIMIT`.\n- Good: `... GROUP BY m_stage`, or `ORDER BY timestamp DESC LIMIT 20` to\n peek at recent rows.\n\n### Reconstruct current state from the log\n\nTo report on CURRENT state, rebuild it from the event history:\n\n- Every event stores a full snapshot of the record, so reconstruct current field values with plain `argMax(<field>, timestamp)` grouped by `entity_id` — never a `JSONHas` / `<field> != ''` / `!= 0` presence guard, which resurrects a stale earlier value for a field that was later cleared or set back to 0. Read a JSON field with\n`argMax(JSONExtractString(properties,'<field>'), timestamp)`, or a\nmaterialized column directly with `argMax(m_stage, timestamp)`.\n- Drop deleted records: `HAVING argMax(type, timestamp) != 'clarify:delete'`.\n- Reconstruct in a CTE, then filter/aggregate over the CTE — filtering a mutable\nfield inside the per-entity scan changes which event counts as \"latest\" and\nproduces wrong totals.\n\n```sql\nWITH deal_current AS (\nSELECT\n entity_id,\n argMax(m_stage, timestamp) AS stage,\n argMax(m_amount, timestamp) AS amount\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\nGROUP BY entity_id\nHAVING argMax(type, timestamp) != 'clarify:delete'\n)\nSELECT stage, count() AS deals, sum(amount) AS pipeline\nFROM deal_current\nWHERE stage NOT IN ('Closed Won', 'Closed Lost')\nGROUP BY stage\n```\n\n### Count stage transitions in a period\n\nA snapshot count (`m_stage = 'Won'`) can't answer \"how many deals were won this\nquarter\" — it counts deals *touched* while already won. Count the transition\ninstead: the events where `stage` moved into a closed value, plus deals created\ndirectly in one. The `UNION` branch is required because `diff` is empty on\ncreate — it catches deals imported straight into a closed stage.\n\n```sql\n-- Deals that ENTERED a closed stage inside the window.\nWITH closed AS (\nSELECT entity_id, timestamp, m_stage AS stage_at_event\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\n AND type = 'clarify:update'\n AND arrayExists(d -> JSONExtractString(d, 'path', 1) = 'stage'\n AND JSONExtractString(d, 'val') IN ('Won', 'Lost'),\n JSONExtractArrayRaw(diff))\nUNION ALL\n-- diff is empty on create: catches deals imported directly into a closed stage\nSELECT entity_id, timestamp, m_stage\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\n AND type = 'clarify:create' AND m_stage IN ('Won', 'Lost')\n)\nSELECT countIf(final_stage = 'Won') AS deals_won,\n count() AS deals_closed,\n countIf(final_stage = 'Won') / nullIf(count(), 0) AS win_rate\nFROM (SELECT entity_id, argMax(stage_at_event, timestamp) AS final_stage\n FROM closed GROUP BY entity_id)\n```\n\nThe outer `argMax` collapses each deal to its last transition in the window, so a\ndeal that goes Won → Lost inside it counts once, as Lost. There is no delete\nguard here on purpose — a deal won in the window was won even if the record was\nlater deleted; to drop since-deleted deals, reconstruct current state (above) and\nkeep only the `entity_id`s that are still live. Matching on `val` works because\n`stage` is not sensitive; a sensitive field's `val` reads `'REDACTED'` (its\n`path` is kept), so for those match on `path` presence alone.\n\nFor a \"closed per month\" trend, bucket by the event `timestamp` — that is when\nthe transition actually happened. One data limitation to surface, not hide: on a\nbatch-imported workspace every `clarify:create` lands on the\nimport date, so deals that closed before they were imported collapse onto that\ndate — the log has no real historical close date for them. `m_close_date` does\nnot fill that gap: it is the *expected* close date (often in the future), right\nfor a pipeline-by-expected-close forecast but wrong as a \"when did we win\"\nbucket.\n\n### Detecting when a field changed\n\nA field being non-empty on an event does NOT mean it changed on that event —\nevery event repeats all fields, so an edit to one field re-emits the rest\nunchanged. Use the `diff` column: on an update it lists exactly the fields that\nchanged, so \"did this field change on this event\" is a plain row filter. Unlike\ncomparing snapshots across events, this composes with a `timestamp` range and\nstays fast. A field changed on an event when `diff` holds an entry whose first\n`path` element is that field:\n`arrayExists(d -> JSONExtractString(d, 'path', 1) = 'stage', JSONExtractArrayRaw(diff))`.\nThe matching entry also carries the transition — `oldVal` → `val` — so you can\nreport \"moved from X to Y\" without reading other events.\n\nCaveats: `diff` is populated on `clarify:update` events only — it\nis empty on `clarify:create`, so if you also need the value set\nat creation (e.g. a deal's first stage), `UNION` in the create event. A change\nto a sensitive field shows `val`/`oldVal` as `'REDACTED'` but keeps its `path`,\nso the change is still detectable. Do NOT count a stage question off the\nsnapshot: `m_stage != ''` counts every edit to a record that has a stage, and\n`m_stage = 'Won'` counts every edit to an already-won deal — neither is a stage\nchange. Match on `diff` instead (see \"Count stage transitions in a period\").\n\n### Join across entities\n\nEvery entity lives in the same `analytics.event` table, so a cross-entity\nreport is CTEs joined on a foreign key stored in `properties`. Reconstruct\neach entity's current state in its own CTE (the pattern above), then join on the\nid — a deal's `company_id` links to the company's `entity_id`.\n\nScope the looked-up CTE to only the ids the join needs: add\n`AND entity_id IN (SELECT <fk> FROM <driving_cte>)` to its `WHERE`.\n`entity_id` is a sort-key column, so this prunes reconstruction to a tiny\nslice instead of rebuilding every record of that entity type — the difference\nbetween a many-second and a sub-second query.\n\n```sql\nWITH deal_current AS (\nSELECT\n entity_id,\n argMax(JSONExtractString(properties,'company_id'), timestamp) AS company_id,\n argMax(m_amount, timestamp) AS amount\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\nGROUP BY entity_id\nHAVING argMax(type, timestamp) != 'clarify:delete'\n),\ncompany_current AS (\nSELECT\n entity_id,\n argMax(JSONExtractString(properties,'name'), timestamp) AS name\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'company'\n AND entity_id IN (SELECT company_id FROM deal_current)\nGROUP BY entity_id\nHAVING argMax(type, timestamp) != 'clarify:delete'\n)\nSELECT c.name AS company, sum(d.amount) AS pipeline\nFROM deal_current d\nJOIN company_current c ON c.entity_id = d.company_id\nGROUP BY c.name\nORDER BY pipeline DESC\n```\n\n### Common pitfalls\n\n- `FROM deal` / `FROM company` — no per-entity tables exist. Query\n`analytics.event` and filter `entity_type`.\n- Reconstruction returns stale values — you added a `JSONHas` / presence\nguard. Use plain `argMax` (see \"Reconstruct current state from the log\").\n- Wrong totals when filtering a mutable field — you filtered it inside the\nper-entity scan. Reconstruct in a CTE first, then filter over the CTE.\n- Slow cross-entity join — the looked-up CTE rebuilt every record of its entity\ntype. Add `AND entity_id IN (SELECT <fk> FROM <driving_cte>)` so it only\nreconstructs the records the join needs.\n- `JSONExtractFloat64` does not exist — use `JSONExtractFloat`.\n\n## Postgres source — current record state\n\nPass `useQuery(sql, { source: 'postgres' })` to read current record state\nstraight from Postgres — the values as they are now: deals in each stage right\nnow, counts and sums of present field values. Use it when the question is about\nthe present. For history, trends, point-in-time, or stage transitions, use the\nClickHouse source instead — Postgres holds no history.\n\n- The schema is per-workspace and is NOT included here. Call\n`get-schema` (format \"read\") for the entities you need before\nyou write SQL, then prove the query with `query-data`.\n- Query each entity by its table name (`deal`, `person`, `company`, …). The\nprimary key is `_id`; audit columns are `_created_at` / `_updated_at`.\n- Many columns are JSONB — use `->` / `->>`. A name stored as\n`{first_name, last_name}` needs `->>`, not a bare ILIKE. Multi-select and\nlabel arrays are `{items: string[]}`; test membership with `?|`\n(`(person.labels -> 'items') ?| ARRAY['ICP']`), never `@>`.\n- To-one links are foreign-key columns (`deal.company_id`, `deal.owner_id`);\nmany-to-many links go through join tables named by the two entities in\nalphabetical order (`person_deal`, `person_meeting`).\n- Postgres holds current values only — there is no history or point-in-time.\nDo NOT pass `timeRange` to a Postgres query — it is rejected. Write explicit\ndate `WHERE` filters instead. For stage transitions, past values, or trends\nover time, use the ClickHouse source.\n\n## Keep queries simple\n\nPrefer several small, focused queries (one per section) over one large\nmulti-join — it fits the per-section loading/error model above, so one slow or\nfailed query never blanks the sections that are ready. When a query uses a time\nwindow, state the window in the UI so the reader knows the period and as-of\ndate, and whether it is a fixed snapshot (absolute dates) or a rolling window\n(relative, recomputed on each open).\n\n## Dashboards\n\nWhen `type` is \"Dashboard\", the report is a multi-section overview. Its\nsections can be ClickHouse (event / time-series), Postgres (current record\nstate), or a mix of both in the same dashboard.\n\nDesign it metric-first: for each section ask \"what does it answer when the viewer\nchanges the window?\" A section that only makes sense at one fixed window is the\nwrong shape. When the ask is about change over time, prefer a dynamic,\ndate-filterable ClickHouse section (the event log, scoped by `timeRange`) over a\nstatic Postgres current-state snapshot — a snapshot can't move with the window.\n\n- Lead with a `@clarify/ui/dashboard-header`. Add a `@clarify/ui/filter-bar`\n holding a `@clarify/ui/date-range-picker` **when any section has a ClickHouse\n query the range can scope.** The picker drives `timeRange`, which applies to\n ClickHouse only — so it scopes the dashboard's ClickHouse sections and its\n Postgres sections ignore it. Omit the picker only when *every* section is\n Postgres, since it would then scope nothing. When you include it, it defaults\n to the last 30 days — keep that default unless the report needs another\n window, then pass `defaultQuickSelect` (e.g. `\"Last 7 days\"`).\n- When present, the picker is the dashboard's time control. Hold its `onApply`\n payload (`{ from, to, previous }`) in React state and pass it to each\n ClickHouse section as `useQuery(sql, { timeRange: range })`, so those sections\n re-filter when the viewer changes the period. Never fetch all rows and\n filter in the client, and never interpolate the dates into the SQL. (Postgres\n queries ignore `timeRange` — see \"Fetching live data\".)\n- **A dashboard is the strongest case for trends — its whole point is\n change-over-time against a chosen window.** Pass\n `compareToPrevious: range.previous ?? true` on essentially every KPI tile and\n single-measure line chart, so each `MetricBlock` shows its `TrendIndicator`\n and each trend line carries its prior-period baseline. A dashboard where the\n KPIs show a bare number with no trend is the wrong default.\n- Before adding a time-bucketed chart (a `GROUP BY` month/week), ask: if the\n viewer picks \"Last 7 days\", does it still render a useful answer? A weekly bar\n chart over a 7-day window is one bar. A time-scoped section usually answers \"is\n this better or worse than before?\" — that's a KPI with comparison (a\n `MetricBlock` with `compareToPrevious`), not a time-bucketed bar chart. Reach\n for the bucketed chart only when the user asks for a trend by period (see the\n time `GROUP BY` chart rule above).\n\nA pipeline-health dashboard leads with a KPI strip that answers the window's\nheadline questions, each a comparison — deals won, win rate, pipeline created:\n\n```jsx\nconst range = /* the DateRangePicker's applied { from, to, previous } */;\nconst won = useQuery(dealsWonSql, {\n timeRange: range,\n title: 'Deals won',\n compareToPrevious: range.previous ?? true,\n});\n// winRate is the same shape with format=\"percent\"; pipelineCreated with format=\"currency\"\nreturn (\n <div className=\"grid grid-cols-3 gap-4\">\n <MetricBlock\n title=\"Deals won\"\n query={won}\n value={won.rows[0]?.deals_won}\n format=\"number\"\n comparison={{ field: 'deals_won', label: 'vs previous period' }}\n // detail SQL must project name (AS name), entity_id, and entity_type so rows link\n underlyingQuery={{ sql: dealsWonDetailSql }}\n />\n {/* win rate, pipeline created — same shape */}\n </div>\n);\n```\n\n## Important notes\n\nArtifacts are read-only. `useQuery` runs SELECTs only; an artifact\ncannot create, update, or delete records or take any action. Do not build\nbuttons, forms, or controls that mutate data, and do not tell the user an\nartifact will perform a write or an action — offer the closest thing you can\nactually do instead.\n\nWhen you tell the user about the artifact in chat, describe WHAT it shows and\nwhat it answers, not HOW you built it. Skip the CSS, query, and debugging\ndetails unless the user asks for them.\n\nThis tool only persists the content or edits it is given; it does not generate\nor edit content itself. Author the full source, or the exact edit strings,\nyourself before calling this tool."
151926
+ },
151927
+ {
151928
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_CALENDAR_EVENT",
151929
+ "name": "Create-or-update-calendar-event",
151930
+ "description": "Create a new calendar event or update an existing one.\n\n## When to use this tool\n\n- To create a new event: omit `event_id` and provide `title` and `when`.\n- To update an existing event: provide `event_id` along with the fields to change.\n\n## Important notes\n\n- Only the fields you provide are updated; omitted fields remain unchanged.\n- For recurring events, updates apply to the whole series.\n- `notify_participants` defaults to `true` on create (invite goes out) and\n `false` on update (so minor edits don't spam attendees). Set it explicitly\n when rescheduling or making changes attendees should know about.\n- When updating `participants`, the default is `add`: the listed emails are\n merged into the existing attendee list. To remove attendees, set\n `participants_mode` to `replace`: anyone not listed will be removed.\n- Get the user's timezone from get-current-user and pass it explicitly via `when.timezone` for timed events. Don't guess.\n- The write happens as soon as this tool is called, with no confirmation step. Confirm with the user first."
151931
+ },
151932
+ {
151933
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_CUSTOM_OBJECT",
151934
+ "name": "Create-or-update-custom-object",
151935
+ "description": "Create a new custom object type or update an existing one in the workspace.\n\n## When to use this tool\n\n- When the user asks to create a new custom object type\n- When the user asks to update the name, plural label, description, or avatar (icon and background color) of an existing custom object\n\n## How it works\n\n- Without entity: creates a new custom object (name, plural, and description are required)\n- With entity: updates the specified custom object's metadata, including its avatar icon and background color\n\n## Recommended workflow for create\n\n1. Discuss with the user what the custom object represents\n2. Ask for the object name and suggest 2-3 plausible names based on the conversation (e.g., \"Contract\", \"Ticket\", \"Project\"). Confirm plural and description with the user as well.\n3. Call this tool to create the object\n4. Immediately call `create-or-update-fields` with the returned entity identifier to add fields\n\n## Description guidance\n\nThe description field is stored as AI context for this object type, directly influencing how AI understands and works with records of this type. A good description captures what business concept this object represents and how the team uses it.\n\nBefore creating a new object, if the user has not provided a description, ask them for one. Work with them to craft a description that captures the object's purpose. Only proceed without a description if the user explicitly declines."
151936
+ },
151937
+ {
151938
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_FIELDS",
151939
+ "name": "Create-or-update-fields",
151940
+ "description": "Create new fields or update existing field metadata (name, options, AI config) on any entity (company, person, deal, meeting, or custom object). Does not support changing an existing field's type or nullable/required status.\nAlso known as custom fields. Rename fields, add enum/select options (existing options are preserved; pass an empty options array to clear all), change option colors, and configure AI autofill.\nSupports all field types: text, number, currency, date, enum, multi-select, markdown, attachment, and relationships.\n\nYou must use `read-context` with context=\"field-docs\" before creating or updating fields to load field type guidelines, AI prompt writing instructions, and examples.\n\n## Important notes\n\n- Field deletion is permanent. Clarify cannot restore or recover a deleted field. Never tell a user a deleted field can be brought back.\n- If a user asks to restore or undelete a field, explain it can't be recovered and offer to create a new field with that name instead: it will be a fresh, separate field.\n\n## Board / Kanban views group by an existing field\n\nA board (Kanban) view groups records into columns by one specific enum field, usually the object's built-in `status` field, or the field configured for that board. Creating a new enum field (e.g. a custom `stage`) does NOT change which field the board groups by, and you cannot see a view's board-grouping configuration from here.\n\n- When a user wants records to move between board columns, set values on the field the board already groups by (commonly `status`), or ask the user which field the board should group by. Do not create a parallel new enum and tell the user the board will use it.\n- If records don't land in the expected column but the data reads back correctly, do not blame a display, refresh, or caching issue. The likely cause is that the board groups by a different field than the one you set."
151941
+ },
151942
+ {
151943
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_LIST",
151944
+ "name": "Create-or-update-list",
151945
+ "description": "Create or update a dynamic list: a saved view whose membership is defined by a SQL query. Dynamic lists are the only list type Clarify supports today.\n\n## When to use this tool\n\n- To create a new list: omit list_id and provide title + sql\n- To update an existing list: provide list_id along with the fields to change\n\nPrefer creating a new list over editing an existing one. When the user is exploring, filtering, or slicing what they are looking at (\"show me just X\", \"filter to Y\", \"without Z\"), create a new list (omit list_id) instead of changing the list they are viewing. Editing a saved list changes it for everyone it is shared with. Only pass list_id when the user explicitly asks to change that saved list itself, and only pass title with a list_id when the user explicitly asks to rename it.\n\nA list is the right surface when the user wants a browsable, filterable set of records of one object type. If they want aggregations, charts, or a multi-part deliverable, that is a report or dashboard (`create-or-update-artifact`), not a list. If the user explicitly asked for a list, build it without asking; if they asked for a report but the result is really just a list of records, offer the list and explain the distinction first.\n\n## If the user asks for a \"static list\" or to manually curate a list\n\nStatic lists are deprecated. Clarify no longer offers them as a list type, although some legacy static lists may still exist in the workspace. Do not call this tool to create one.\n\nTell the user static lists are no longer supported, then offer the workaround: add a label to the records they want to track, and create a dynamic list that filters on that label. All built-in entities (companies, people, deals) have a built-in `labels` field with color-coded user-defined values, so the user can add or remove the label to control list membership manually.\n\n## SQL restrictions\n\nThis tool supports a restricted SQL subset. The query is used for both display and counting (via COUNT(*) wrapping), so certain patterns are incompatible:\n\n- **SELECT ***: Use explicit, table-qualified column names (e.g., \"SELECT person.name, person.email_addresses FROM person\")\n- **DISTINCT ON**: Not compatible with COUNT(*) wrapping. Use GROUP BY for deduplication instead.\n- **CTEs (WITH ... AS)**: Not supported. Rewrite using JOINs or WHERE clauses.\n- **Subqueries in FROM**: SELECT ... FROM (subquery) is not supported. Query the table directly with WHERE/JOIN clauses.\n- **LIMIT / OFFSET**: Not supported. A dynamic list is a continuously-evaluated membership filter, not a ranked snapshot; the LIMIT is dropped during evaluation, so a \"top N\" query silently matches every qualifying record. To bound a list, narrow membership with a WHERE clause (e.g. a recency window like \"meeting.start > NOW() - INTERVAL '30 days'\") or have the user add a label and filter on it. ORDER BY is fine; it sets the default sort, not membership.\n- Column names must be table-qualified (e.g., \"person.name\" not just \"name\")\n- Aggregate functions in ORDER BY or HAVING must also appear in the SELECT clause\n- **Filtering labels / multi-select fields**: these store JSONB as `{items: string[]}`. Filter membership with the array-overlap operator, e.g. `(person.labels -> 'items') ?| ARRAY['BDR Prospect']`. Do not use the `@>` containment operator; it works in the database but the list UI cannot render or edit a filter built with it.\n\n## Filtering by the current user\n\nTo make a list relative to whoever is viewing it (e.g. \"my tasks\", \"deals I own\"), compare against current_setting('app.current_user_id', TRUE), which resolves to the viewing user's ID at query time so the list works for every viewer.\n\n- Use it directly in a WHERE clause: WHERE task.assignee_id = current_setting('app.current_user_id', TRUE)\n- Do not hardcode a specific user's ID, and do not use template tokens like {{current_user_id}}; they are not substituted and the list will match nothing.\n\n## Important notes\n\n- Only the fields you provide will be updated; omitted fields remain unchanged\n- The tool validates both the main query and count query to ensure the list will work when opened\n- Creating a new list publishes it immediately. Updating an existing list (passing list_id with a new sql) does not publish: the change is saved as a draft version and stays not-live until the user applies it. Relay the apply link from the tool response and tell the user to review and apply it with \"Save for everyone\"; do not tell the user the update is already live. Metadata-only edits (title, description, emoji) apply immediately.\n\n## Column choice for list views\n\nLists render one row per root record, so every SELECT column must belong to the root entity.\n\n- The record-title column (the primary field, aliased `<entity>:__object__`) is always shown and cannot be removed through the list query; the backend re-adds it on save. Do not tell the user you removed the title column. Which columns are visible and their order is a per-view UI setting the user controls from the list header's column menu, not something this tool changes.\n- Prefer scalar fields on the root entity (e.g. `person.name`, `person.email_addresses`).\n- Do not select the record's `_id` (shown as \"Record ID\") column unless the user explicitly asks for it. The record identity is always available on the row; surfacing the raw UUID as a column is rarely useful and clutters the list.\n- Alias the title column onto the entity's **primary field**, never onto another column. `SELECT person._id AS \"person:__object__\"` renders every row blank and unclickable; `SELECT person.name AS \"person:__object__\"` is correct. Omitting the title column entirely is also fine — the backend adds it.\n- To show a to-one relationship as a column, join the related table aliased `<root>$<fk_column>` and select its primary field aliased `<root>$<fk_column>:__object__`, e.g. `SELECT \"person$company_id\".name AS \"person$company_id:__object__\" FROM \"person\" LEFT JOIN \"company\" AS \"person$company_id\" ON \"person\".company_id = \"person$company_id\"._id`. Do not select the bare `*_id` foreign key as a column: the grid matches columns against the schema's reachable fields, a raw foreign key is not one, and the column is silently dropped from the view.\n- Do not SELECT columns from many-to-many related tables. Joining through a join table produces duplicate rows, and the list view can't render an m2m relationship as a single cell.\n- If the user explicitly asks to display a many-to-many field as a column, explain that lists only show direct fields on the root record, and the full relationship is available on the record detail page.\n\nAfter creating or updating a list:\n1. Tell the user what was created or updated in a friendly, conversational way\n2. Provide a clickable markdown link to open the list (the tool response will include this)\n3. If the tool response includes a prefilled Lead Finder link (returned when a new company or person list matches 0 records), relay it: offer it as the way to fill the list, using the exact markdown link from the response\n4. Keep your response concise"
151946
+ },
151947
+ {
151948
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_RECORDS",
151949
+ "name": "Create-or-update-records",
151950
+ "description": "Create or update records in Clarify. Supports bulk operations of up to 25 records per call.\n\n- **Without id**: Create a new record\n- **With id**: Update an existing record by ID\n\nThis tool also links and unlinks relationships between records, not just attributes -- see the Relationships section below for trigger words and examples.\n\nAll records in a single call must be the same operation: either all creates (no `id`) or all updates (with `id`). Split mixed batches into two separate calls.\n\nEach call is atomic: if any record in the batch fails, the entire batch is rolled back and no records are written. When working with user-supplied IDs (CSVs, pasted lists) verify the IDs exist with query-data first, or use smaller batches to limit the blast radius of a single bad ID.\n\n## Before creating or updating records\n\n- Writable fields are not included in this tool's description. You must call get-schema with format \"write\" and only the entities you need before creating or updating records, unless the write schema for those entities was already loaded earlier in this conversation. Do not guess field names.\n- Never tell a user a field can be set before confirming it appears in the write schema. Computed / read-only fields (system-managed, e.g. interaction dates) are deliberately omitted from the write schema: they cannot be set here, and a field missing from the write schema is read-only or nonexistent, not something to recreate as a custom field. Do not offer to set such a field or to create a custom field of the same name. Explain that it updates automatically (from meetings and emails) and offer the real workaround, such as logging a meeting.\n- Before creating a company, deal, or person, use the query-data tool to search for existing records by name (ILIKE). Use a broad search, not a narrow ID filter.\n- If the search returns potential matches, present them to the user and ask whether to use an existing record or create a new one.\n- If no matches are found, proceed to create without asking for confirmation.\n- When creating a meeting, provide `title` (string), `start` (ISO 8601 datetime), and `end` (ISO 8601 datetime) in attributes. Set attendees via the `participants` attribute using the format `{ set: [{ email: \"alice@example.com\", name: \"Alice\" }, ...] }`. People, companies, and associations are created automatically from participants.\n- Meetings also support `summary` (markdown string for meeting summary/recap) and `notes` (markdown string for meeting notes or transcript). Pass these as plain markdown strings in attributes.\n- If the meeting data includes a timezone, pass it as the `timezone` attribute (IANA timezone string like \"America/Chicago\"). Naive datetimes in `start`/`end` will be interpreted in that timezone. If no timezone is provided, the user's preferred timezone is used. UTC datetimes (with Z or offset) are stored as-is.\n\n## Relationships\n\nPass all relationships (to-one and to-many) via the `relationships` parameter using this format:\n`[{ \"relationshipFieldName\": \"<field>\", \"operation\": \"link\" | \"unlink\", \"targets\": [{ \"entity\": \"<entity>\", \"_id\": \"<id>\" }] }]`\n\nUse `operation: \"link\"` or `operation: \"unlink\"` when the user says link, unlink, connect, disconnect, associate, dissociate, or relate -- any create/remove of a relationship between two records, for example:\n- \"Link this deal to Acme Corp\" -> link\n- \"Unlink this contact from the deal\" -> unlink\n- \"Connect this deal to Acme Corp\" -> link\n- \"Dissociate this contact from the deal\" -> unlink\n\nA relationship-only call is valid: `attributes` can be omitted (it defaults to `{}`) when only `relationships` is populated, e.g. to link or unlink a record without changing any other field.\n\nThe specific relationship fields available per entity are returned by get-schema with format \"write\".\n\n## Creating deals and tasks\n\nWhen creating a deal or a task, do not create a bare record with only a name. Fill in the fields that make it useful: inferring what you can and asking the user only for what you genuinely cannot.\n\n- **Owner / assignee defaults to the current user.** Unless the user names someone else, set a new deal's `owner_id` (and a new task's `assignee_id`) to the current user. Pass it via `relationships`, e.g. `{ \"relationshipFieldName\": \"owner_id\", \"operation\": \"link\", \"targets\": [{ \"entity\": \"user\", \"_id\": \"<current user id>\" }] }` (use `assignee_id` for tasks). The current user's record ID is in the \"Information about the user\" section of your context; MCP clients can get it from get-current-user.\n- **Infer before asking.** Before creating a deal, try to fill `amount`, `close_date`, and `stage`, and to link the relevant company and people, from context already available to you: recent meetings and emails with that company, and existing related records (use query-data and get-records). Link the named company (creating it first if it does not exist, per the notes below) and any clearly-relevant people.\n- **Ask only for the gaps.** If a field that matters can't be confidently inferred, ask the user for it in one short round rather than silently creating an empty record, and let them skip. Do not block creation if the user clearly just wants a quick record.\n- **Amount is a committed actual.** Never invent or estimate a deal's `amount`. If you don't have a committed, agreed value, ask the user or leave it unset; do not guess from projections.\n\n## Collection fields (labels, multi-select, emails, etc.)\n\nCollection fields require an explicit operation. Do not pass raw arrays or { \"items\": [...] }.\n\n- **Append** (add values): `{ \"append\": [\"value1\", \"value2\"] }`\n- **Remove** (remove values): `{ \"remove\": [\"value1\"] }`\n- **Set** (replace all values): `{ \"set\": [\"value1\", \"value2\"] }`\n- **Append + Remove** (do both in one call): `{ \"append\": [\"new\"], \"remove\": [\"old\"] }`\n\n\"set\" cannot be combined with \"append\" or \"remove\". Use \"set\" alone to replace all values or clear them with `{ \"set\": [] }`.\n\nWhen creating records, use \"set\" for initial values: `{ \"labels\": { \"set\": [\"Enterprise\"] } }`.\nWhen updating records, choose the operation that matches the user's intent. If the user says \"add label X\", use \"append\". If they say \"remove label X\", use \"remove\".\nBefore using \"set\" on an existing record, first query the record's current collection values so you know what you're replacing. \"set\" overwrites the entire collection; if you use it without checking, you will silently discard existing values the user wants to keep.\n\n## Updating records\n\nWhen updating, you are modifying an existing record, not creating one. Do not re-run create-time logic or re-estimate values.\n\n- Only include a field when you have an explicit, new signal its value changed. No new signal for a field means leave it out of the call; do not re-send or re-estimate it.\n- Before overwriting a field that already has a value, read its current value and change it only if it genuinely changed.\n- Treat amount/value fields as actuals: set them only to committed, agreed values, never projections or estimates.\n- Do not move a deal's stage to a winning or final stage, or backward, without a clear signal the change actually happened.\n- For a calendar-synced meeting, a field sourced from the connected calendar event (e.g. title, start, participants) cannot be updated here; the tool returns an error naming the blocked field. Custom fields and any field not sourced from the calendar can still be updated. Ad-hoc meetings created in Clarify have no restricted fields.\n- Meetings support `summary` (markdown string for meeting summary/recap) and `notes` (markdown string for meeting notes or transcript). Pass these as plain markdown strings in attributes. These can be set on any meeting (ad-hoc or calendar-synced).\n- Attachments cannot be created here; a file must be uploaded through the app's attachment upload flow. You can update an existing attachment by `id` (e.g. to set custom fields), but its system fields (`s3_key`, `source`, `status`, and its record links) are read-only and will be rejected.\n\n## Upsert mode (match_on)\n\nWhen creating records that may already exist, pass `match_on` with a unique field to match on (marked unique in the schema, e.g. `domains` for companies, `email_addresses` for people) to upsert instead of failing on duplicates. For each record, if exactly one existing record already has the same value for that field, the incoming attributes are merged into it and its ID is returned; records with no match are created. A value that matches multiple existing records errors; merge those records first. Scalar unique fields match exactly; collection fields match case-insensitively; non-unique fields are rejected. The whole batch still succeeds atomically. This avoids the re-query-and-retry dance after a duplicate error. `match_on` only applies to creates; do not combine it with records that have an `id`. Collection field operations (`set`/`append`/`remove`) are honored against the matched record, not flattened into a plain replace.\n\n## Important notes\n\n- Rich-text fields shown as `markdown` in the write schema (for example a task's `description`, a deal's `summary`, or a meeting's `summary`) accept a plain markdown string in `attributes` and are converted to rich text automatically. Never open any rich-text/markdown field (`summary`, `prep`, `notes`, `description`, and any custom one) with a heading that restates or mirrors the field name; the field is already labeled in the UI; start directly with the content.\n- When setting numeric values (like deal amount), store the exact value the user provides. Never multiply or divide to convert between units (e.g. MRR to ARR).\n- Relationship fields (like `company_id`, `owner_id`, `people`) must be passed via `relationships`, not inside `attributes`. Use `attributes` only for scalar/non-relationship fields.\n- All relationships are optional. Records like tasks, deals, and people can be created or updated without linking to other records. Never require the user to provide a related record (e.g., a deal) before creating or updating a task.\n- When the user references a person or company that doesn't exist in the CRM, create the person/company record first using this tool, then link it to the main record. Do not ask the user to manually create the contact or provide unrelated context like a deal.\n- If you need to process more than 25 records, call this tool multiple times with batches of up to 25.\n- For a single record, use a single-element array.\n\n- After creating or updating records:\n 1. Tell the user what was done in a friendly, conversational way\n 2. Refer to records by name only.\n 3. Never include a record URL in prose; the tool result already carries each record's link."
151951
+ },
151952
+ {
151953
+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_WORKFLOW",
151954
+ "name": "Create-or-update-workflow",
151955
+ "description": "Create a new workflow or update an existing one.\n\n- **Without workflow_id**: Create a new workflow with a trigger\n- **With workflow_id**: Add, update, or delete blocks within a workflow, or update its description\n\n## Before creating a new workflow (no workflow_id)\n\nDo not call this tool to create a new workflow yet. For any automation request (including\none where the user says \"workflow\"), an agent is the recommended default. First recommend\ncreating an agent and ask the user whether they'd prefer that, then wait for their answer.\nDo not read workflow docs or gather workflow details until they reply. Only create a workflow\nif they explicitly confirm they need a workflow and not an agent. (This gate applies to create\nmode only; updating an existing workflow via workflow_id does not require re-asking.)\n\nImportant: Must use `read-context` with context=\"workflow-docs\" for details on workflow format and workflow code support\n\n## When to use this tool\n\n- Add new steps to a workflow\n- Change the configuration of a workflow step\n- Remove steps from a workflow\n- Update input fields for a block\n- Modify block parameters based on user feedback\n- Update the workflow description\n\n## Create mode (no workflow_id)\n\nProvide name, description, and trigger_plugin_id. After creation, call this tool again with the workflow_id to add action blocks.\n\n## Update mode (with workflow_id)\n\n- **Add a block**: Provide plugin_id and input. Optionally specify insert_after to control position.\n- **Update a block**: Provide block_id and input with the fields to change.\n- **Delete a block**: Provide block_id and set delete_block to true.\n- **Update description only**: Provide workflow_description without block_id or input.\n- **Update trigger input**: Set block_id to the trigger ID and provide input.\n- **Change trigger type**: Provide trigger_plugin_id (and optionally trigger_input) to replace the trigger plugin. Filters are cleared because they reference plugin-specific event paths.\n- **Update trigger filters**: Include `trigger_filters` in any call: alone, combined with `workflow_description`, or alongside a block add/update/delete. The array **replaces** all existing filters; pass `[]` to clear them.\n\n## Code blocks (`code:execute`)\n\nThe `code:execute` block takes a two-field input. `runtime` is fixed; only `code` varies:\n\n```json\n{\n \"plugin_id\": \"code:execute\",\n \"input\": {\n \"runtime\": \"clarify-nodejs@0.0.1\",\n \"code\": \"export async function handler(input, { clarify, _, workflowContext }) { /* ... */ }\"\n }\n}\n```\n\nPass the handler source as a raw JS string; no markdown fences. See the `workflow-docs` context for the SDK surface, execution constraints (30s timeout, allowed packages), and error semantics.\n\n**IMPORTANT**: Whenever you add, update, or delete blocks (or change the trigger), check whether the workflow's existing description still describes the flow. If your change makes it stale or incomplete, pass an updated `workflow_description` in the same call (no need to ask first) and briefly mention that you updated it. Leave the description untouched when it still fits."
151956
+ },
151957
+ {
151958
+ "slug": "CLARIFY_MCP_DELETE_AGENT",
151959
+ "name": "Delete-agent",
151960
+ "description": "Delete an agent by its ID.\n\n## When to use this tool\n\n- When the user asks to delete or remove an agent they created\n\n## Important notes\n\n- This action is permanent and cannot be undone\n- Only the creator of an agent can delete it"
151961
+ },
151962
+ {
151963
+ "slug": "CLARIFY_MCP_DELETE_ARTIFACT",
151964
+ "name": "Delete-artifact",
151965
+ "description": "Delete an artifact by its ID. An artifact is a named, versioned report or\ndocument that the user can view and revisit.\n\n## When to use this tool\n\nUse this when the user asks to delete or remove an artifact (a report or\ndocument) they no longer want. You need the artifact's ID — look it up first\nif you only have its name.\n\n## How it works\n\nDeletes the artifact along with all of its saved versions. This is permanent\nand cannot be undone. The user is asked to confirm before the artifact is\nremoved."
151966
+ },
151967
+ {
151968
+ "slug": "CLARIFY_MCP_DELETE_CALENDAR_EVENT",
151969
+ "name": "Delete-calendar-event",
151970
+ "description": "Cancel a calendar event.\n\n## When to use this tool\n\nUse to cancel an event the user owns or has edit access to. For events the\nuser is only invited to, use respond-to-calendar-event instead.\n\n## Important notes\n\n- For recurring events, this cancels the whole series.\n- `notify_participants` defaults to `true` so attendees see the cancellation.\n- The cancellation runs as soon as this tool is called, with no confirmation step. Confirm with the user first."
151971
+ },
151972
+ {
151973
+ "slug": "CLARIFY_MCP_DELETE_CAMPAIGN",
151974
+ "name": "Delete-campaign",
151975
+ "description": "Delete a campaign by its ID.\n\n## When to use this tool\n\n- When the user asks to delete or remove a campaign\n\n## Important notes\n\n- This action is permanent and cannot be undone\n- The campaign must be disabled (draft) before it can be deleted\n- Only the campaign owner or an admin can delete a campaign"
151976
+ },
151977
+ {
151978
+ "slug": "CLARIFY_MCP_DELETE_CUSTOM_OBJECT",
151979
+ "name": "Delete-custom-object",
151980
+ "description": "Delete a custom object type by its entity identifier.\n\n## When to use this tool\n\n- When the user asks to delete or remove a custom object type\n\n## Important notes\n\n- This action is permanent and cannot be undone\n- All records of this type will be deleted\n- Only custom objects (entity starting with \"c_\") can be deleted"
151981
+ },
151982
+ {
151983
+ "slug": "CLARIFY_MCP_DELETE_FIELDS",
151984
+ "name": "Delete-fields",
151985
+ "description": "Delete one or more custom fields from an existing object (built-in entities like person, company, deal, or custom objects like c_my_object).\n\n## When to use this tool\n\n- When a user wants to remove custom fields they no longer need\n- When cleaning up unused or obsolete fields from any object\n\n## Important\n\n- This is a destructive operation: deleted fields and their data cannot be recovered\n- Always confirm the deletion plan with the user before calling this tool\n- Protected (system) fields cannot be deleted\n- Relationship fields are deleted on both sides automatically"
151986
+ },
151987
+ {
151988
+ "slug": "CLARIFY_MCP_DELETE_LIST",
151989
+ "name": "Delete-list",
151990
+ "description": "Delete a list (saved view) by its ID.\n\n## When to use this tool\n\n- When the user asks to delete or remove a list they created\n\n## Important notes\n\n- This action is permanent and cannot be undone\n- Default lists cannot be deleted\n- The last remaining list for an entity cannot be deleted\n- Only the list owner can delete a shared list"
151991
+ },
151992
+ {
151993
+ "slug": "CLARIFY_MCP_DELETE_RECORDS",
151994
+ "name": "Delete-records",
151995
+ "description": "Delete one or more records by their IDs. Supports bulk deletion of up to 25 records per call.\n\n## When to use this tool\n\n- When the user asks to delete or remove specific records\n\n## Important notes\n\n- This action is permanent and cannot be undone\n- All relationships involving the deleted records are also removed\n- Use only if you already have the IDs for the records\n- If you need to delete more than 25 records, call this tool multiple times with batches of up to 25."
151996
+ },
151997
+ {
151998
+ "slug": "CLARIFY_MCP_DELETE_WORKFLOW",
151999
+ "name": "Delete-workflow",
152000
+ "description": "Delete a workflow by its ID.\n\n## When to use this tool\n\n- When the user asks to delete or remove a workflow\n\n## Important notes\n\n- This action is permanent and cannot be undone\n- The workflow will stop executing after deletion\n- Only the workflow owner or an admin can delete a workflow"
152001
+ },
152002
+ {
152003
+ "slug": "CLARIFY_MCP_FIND_LEADS",
152004
+ "name": "Find-leads",
152005
+ "description": "Search Clarify's built-in prospect database of companies and people to find new leads matching criteria like industry, location, headcount, job title, seniority, and funding stage, and save (publish) a search the user wants to keep. Use this for prospecting and lead discovery on any page where leads, prospects, or outbound targets are discussed. Under the hood, a search is created as a draft (or draft version) from a custom-dialect SQL query - follow the rules and examples below exactly.\n\n## Modes: draft vs publish\n\nThis tool has two modes, set by the `mode` parameter (default `draft`):\n\n- `draft`: run a SQL query to create a new draft search, or a draft refinement of an existing one, and preview the matches. This is the default and covers all prospecting and refinement.\n- `publish`: save an existing draft search so it appears under the user's \"My saved searches\". Call with `mode: \"publish\"`, the search's `search_id`, and (when the search has an unapplied refinement) its `version_id`. No `sql` is needed to publish.\n\n## Draft vs saved searches\n\nA `draft` result is **not** a saved search: it doesn't appear under the user's \"My saved searches\" until it's published. Never tell the user a search you just created is \"saved\"; describe it as a draft. If the user asks whether it's saved, say it's a draft and offer to save it. When the user asks to save (or \"publish\") a search, call this tool again with `mode: \"publish\"` and the search's `search_id`.\n\n## Interpreting the result count\n\nThe number returned is an upper bound on matching rows in the prospect database. Some of those rows may already exist in the user's CRM and some may overlap with each other. The actual number of net-new importable records can be lower and is only known at import time. Never present the match count as \"unique importable leads\" or use it to estimate credit spend — use it only to describe how many rows match the filters.\n\n## Important Rules\n\n- Parameters like version_id and search_id should preferably come from the document context, which is the source of truth for identifiers. If the document context does not include a version_id, you may use the most recent version_id from the conversation if it is contextually relevant.\n\n## When to use this tool\n\nUse this tool when a user wants to find leads matching specific criteria and preview them as a draft search:\n- Construct a SQL query following the rules below\n- Provide a `search_label` parameter (e.g., \"SF Companies with 50+ employees\")\n- The tool creates a draft search or draft version that the user can see and interact with (see \"Draft vs saved searches\" above)\n\n## When not to use this tool\n\nDo not call this tool when the user's intent is ambiguous between existing CRM data and new leads.\nWhen the user searches for companies or people without using the word \"lead\" or \"prospect\", and the conversation does not already establish context, you must ask the user to clarify before calling any tool.\nAsk whether they want to find new leads/prospects to add to the CRM, or look up existing companies/people already in the CRM.\nOnly call this tool after the user confirms they want new leads.\n\n## Versioning vs Creating Searches\n\nWhen the user wants to update/modify a search:\n1. Always use the SQL from the referenced version as the base query and only modify what the user explicitly asks to change.\n2. Keep the same entity type and update the SQL query and search_label\n\nUpdate (provide search_id) when user says: \"no\", \"actually\", \"refine\", \"filter\", \"change\", \"update\", \"modify\" or refers to \"it\"/\"that search\"/\"the search\"\n\nCreate (omit search_id) when user explicitly asks for a \"new search\" or different entity type (company vs person)\n\n## SQL Rules\n\n1. Use ILIKE, all matching is case-insensitive.\n2. Database may convert ILIKE `'%foo%'` into `'foo%'` pattern (prefix-only pattern matching) depending on field type (full text search vs keyword matching). Names are processed with prefix matching only.\n3. No SELECT * — explicitly list all columns.\n4. Always have the first column be the primary object field with the alias `table_name:__object__`.\n5. Never select _id or id fields — they are not queryable.\n6. Always prefix columns with table names: `tam_company.name`, not `name`.\n7. Only select top-level columns — nested JSONB fields are not allowed in SELECT clauses.\n8. All selected columns require aliases in the format \"table_name:column_name\".\n9. For JSONB array fields (industries, domains, etc.), use this exact syntax to filter:\n `(table.field -> 'items') ?| ARRAY['Value1', 'Value2']`\n Do not use CONTAINS, the `@>` containment operator, or standard SQL array syntax - only the exact pattern above works.\n10. Before applying filters to enum fields, review the allowed values listed in \"Available Tables and Columns\" and include all relevant matches in a single WHERE clause.\n11. When filtering by role or title, prefer `job_title ILIKE '%keyword%'`; it matches the person's actual title and covers most queries (e.g., \"founders\", \"CTOs\", \"account executives\", \"sales managers\", \"engineers\"). The `seniority` and `function` fields are coarse categorical enums with very few values; only use them when the user's query maps exactly to an enum value and a broad categorical filter is clearly intended.\n12. Never use `ILIKE ANY(ARRAY[...])` or `= ANY(ARRAY[...])` — ARRAY/ANY is not valid here. To match any of several title keywords, OR together separate `job_title ILIKE '%keyword%'` conditions; to match any of several exact enum values, use `IN (...)` on that column.\n13. Never include `ORDER BY` in find-leads SQL. The TAM database returns errors when ORDER BY is present, even on sortable fields. If the user uses words like \"recently\", \"latest\", or \"top\", interpret them as filters (e.g. `latest_role_change_at >= '2026-01-01'`), not as a sort instruction. Never write `ORDER BY`, regardless of which column the user mentions.\n14. If the user asks to sort or rank explicitly, explain that find-leads cannot sort results and offer to filter by date or another field instead.\n15. NOT with JSONB array operators (?|) is unreliable and returns zero results. Use positive filters instead of negation (e.g., filter for the industries you want rather than excluding ones you don't).\n16. Never use OR to group multiple `->>'key'` conditions — it corrupts parentheses around JSONB access. Instead, use `IN` on a single key.\n Correct: `WHERE table.primary_location->>'city' IN ('San Francisco', 'New York', 'Boston')`\n Incorrect: `WHERE (table.primary_location->>'city' = 'San Francisco' AND ...) OR (table.primary_location->>'city' = 'New York' AND ...)`\n This applies to all JSONB object fields (primary_location, company_location, name), not just locations.\n17. Tech-stack / tooling criteria (e.g. \"uses Kubernetes\", \"on PostgreSQL\") are a COMPANY attribute: filter `tam_company.tech_stack_products` with the JSONB-array syntax `(tam_company.tech_stack_products -> 'items') ?| ARRAY['Kubernetes']`. Never filter tech stack via a person's `skills` field. Because queries are single-table (no JOINs), a tech-stack criterion means the query must target tam_company; you cannot filter tam_person by a company's tech stack.\n18. Never filter on `smart_tags` — it is not a reliable structured filter. Map every criterion to a structured column (job_title, seniority, function, employee_range / company_employee_range, tech_stack_products, industries, primary_location).\n19. Single-table queries only — JOINs are not supported.\n20. When creating a new search, use the default query for the entity as the base and only add a WHERE clause. When refining an existing search, preserve the existing SELECT columns unless the user explicitly asks to add or remove columns.\n21. Never filter by tam_person email fields (email_addresses, personal_email_addresses) in WHERE clauses — these fields are masked until leads are imported into the CRM, so filtering by them would produce unreliable results. You may still SELECT them for display.\n\n## Company Name Matching\n\nThe TAM database stores **parent company names**, not subsidiary or regional office names.\nWhen users provide subsidiary names (e.g., \"Globex France S.A.R.L.\", \"Initech Solutions Japan K.K.\"), extract the core company name and use prefix matching:\n\nCorrect: `tam_person.company_name LIKE 'Globex%'`: matches \"Globex\", \"Globex Inc.\", \"Globex France S.A.R.L.\"\nIncorrect: `tam_person.company_name = 'Globex France S.A.R.L.'` — exact match will likely miss the record\nIncorrect: `tam_person.company_name IN ('Globex France S.A.R.L.', ...)` — exact subsidiary names rarely exist in the database\n\nWhen matching multiple companies, use OR with LIKE prefix patterns on the core name:\n```sql\nWHERE (\n tam_person.company_name LIKE 'Globex%'\n OR tam_person.company_name LIKE 'Initech%'\n OR tam_person.company_name LIKE 'Stark Industries%'\n)\n```\n\n**Important**: Because only prefix matching is available, short company names (e.g., \"Nova\") may produce false positives (e.g., matching \"Novartis\"). Use the most distinctive prefix possible. If the user provides both a short name and a more specific variant, prefer the longer one (e.g., `'Nova Dynamics%'` over `'Nova%'`).\n\n## Examples\n\nFollow the SQL patterns in these examples exactly. The lead finder database uses custom JSONB syntax that differs from standard SQL.\n\nExample: Find me companies in SF with > 50 people\n\n```sql\nSELECT tam_company.name AS \"tam_company:__object__\",\n tam_company.domains AS \"tam_company:domains\",\n tam_company.employee_range AS \"tam_company:employee_range\",\n tam_company.industries AS \"tam_company:industries\",\n tam_company.description AS \"tam_company:description\",\n tam_company.primary_location AS \"tam_company:primary_location\"\nFROM tam_company\nWHERE tam_company.primary_location->>'city' = 'San Francisco'\n AND tam_company.primary_location->>'state' = 'California'\n AND tam_company.employee_range IN ('51-250', '251-1K', '1K-5K', '5K-10K', '10K-50K', '50K-100K', '100K+')\n```\n\nExample: Find me SaaS company leads in New York\n\n```sql\nSELECT\n tam_company.name AS \"tam_company:__object__\",\n tam_company.domains AS \"tam_company:domains\",\n tam_company.employee_range AS \"tam_company:employee_range\",\n tam_company.industries AS \"tam_company:industries\",\n tam_company.description AS \"tam_company:description\",\n tam_company.primary_location AS \"tam_company:primary_location\",\n tam_company.website AS \"tam_company:website\"\nFROM tam_company\nWHERE tam_company.primary_location->>'city' = 'New York'\n AND tam_company.primary_location->>'state' = 'New York'\n AND (tam_company.industries -> 'items') ?| ARRAY['SaaS']\n```\n\nExample: Find me people who work in sales at tech companies\n\n```sql\nSELECT\n tam_person.name AS \"tam_person:__object__\",\n tam_person.email_addresses AS \"tam_person:email_addresses\",\n tam_person.job_title AS \"tam_person:job_title\",\n tam_person.company_name AS \"tam_person:company_name\",\n tam_person.company_industries AS \"tam_person:company_industries\",\n tam_person.primary_location AS \"tam_person:primary_location\",\n tam_person.seniority AS \"tam_person:seniority\"\nFROM tam_person\nWHERE tam_person.function = 'Sales & Business Development'\n AND (tam_person.company_industries -> 'items') ?| ARRAY['Software Development', 'Information Technology & Services']\n```\n\nExample: Find me founders in San Francisco\nNote: \"founder\" is a specific title — use `job_title ILIKE`, not seniority.\n\n```sql\nSELECT\n tam_person.name AS \"tam_person:__object__\",\n tam_person.email_addresses AS \"tam_person:email_addresses\",\n tam_person.job_title AS \"tam_person:job_title\",\n tam_person.company_name AS \"tam_person:company_name\",\n tam_person.primary_location AS \"tam_person:primary_location\",\n tam_person.seniority AS \"tam_person:seniority\"\nFROM tam_person\nWHERE tam_person.job_title ILIKE '%founder%'\n AND tam_person.primary_location->>'city' = 'San Francisco'\n AND tam_person.primary_location->>'state' = 'California'\n```\n\nExample: Find me companies in San Francisco, New York, and Boston\n\n```sql\nSELECT tam_company.name AS \"tam_company:__object__\",\n tam_company.domains AS \"tam_company:domains\",\n tam_company.employee_range AS \"tam_company:employee_range\",\n tam_company.industries AS \"tam_company:industries\",\n tam_company.description AS \"tam_company:description\",\n tam_company.primary_location AS \"tam_company:primary_location\"\nFROM tam_company\nWHERE tam_company.primary_location->>'city' IN ('San Francisco', 'New York', 'Boston')\n```\n\nExample of filtering by `tam_person.company_employee_range`:\n\n```sql\nSELECT\n tam_person.name AS \"tam_person:__object__\",\n tam_person.email_addresses AS \"tam_person:email_addresses\",\n tam_person.company_employee_range AS \"tam_person:company_employee_range\",\n tam_person.company_location AS \"tam_person:company_location\"\nFROM tam_person\nWHERE\n tam_person.company_employee_range IN ('51-250', '251-1K')\n```\n\n## Importing or adding leads to the CRM\nIf user asks to add or import leads to the CRM, use the `import-leads` tool and not the create-or-update-records tool."
152006
+ },
152007
+ {
152008
+ "slug": "CLARIFY_MCP_GET_AGENT_RUNS",
152009
+ "name": "Get-agent-runs",
152010
+ "description": "List an agent's runs, executions, invocations, and past run history, or\nfetch one run with its full transcript. Use this tool for any question\nabout what an agent has done, when it ran, or how often it has fired.\n\n## When to use this tool\n\n- \"List runs for this agent\" / \"show me the agent's runs\"\n- \"Agent history\" / \"past runs\" / \"recent runs\" / \"last run\"\n- \"How many times has this agent run\" / \"count runs for an agent\"\n- Debugging why an agent behaved a certain way: fetch the run to see the\n messages, tool calls, and responses that happened\n- The user provides an agent id and asks \"show me what it did\"\n\n## Not the same as get-workflow-runs\n\nAgents and workflows both have runs but they live in different tables.\nUse this tool (not `get-workflow-runs`) whenever the subject is an\nagent or an agent id. Passing an agent id to `get-workflow-runs`\nsilently returns nothing.\n\n## How it works\n\n- Without `run_id`: returns a paginated list of recent runs for the agent\n- With `run_id`: returns the full run including its message transcript\n- A \"run\" is the chat session an agent produced when one of its triggers\n fired — user and assistant messages, tool calls, results, and errors\n\n## Pagination\n\n- When the user asks for \"more\" runs / next page / older runs, call this\n tool again with the same agent_id and a larger `offset`\n\n## Reading status and credits\n\nEach run reports a **Status** (e.g. \"In progress\", \"Completed\", \"Failed\") —\nuse it, not credits, to judge whether a run has finished. **Credits Used** is\na running cost total, not a progress indicator: a response that incurs AI\ncost adds at least 1 credit, so `0` credits means no such response has\ncompleted — the run may be not started, still generating its first response,\nor have failed before producing one. Never infer completion or a run's cost\nfrom the credit number alone; read Status for progress, and use the Created\ntime to gauge how long a run has been running.\n\n## Read the transcript before describing a run\n\nWhenever the user asks what a specific run did, or to summarize or explain one,\ncall this tool with that run's `run_id` first. The list mode returns only\ncounts and credits, never the messages, so describing a run from the list alone\nmeans inventing its content. Only the `run_id` transcript shows what happened.\n\nWhen the user reports that an agent isn't working as expected, proactively\nfetch the most recent run transcript before suggesting changes. Compare what\nhappened in the run against the agent's instructions to diagnose the root cause.\n\nAfter diagnosing, explain what you found with specifics from the transcript.\nSuggest targeted fixes via `create-or-update-agent`, then offer to\nrerun."
152011
+ },
152012
+ {
152013
+ "slug": "CLARIFY_MCP_GET_AGENTS",
152014
+ "name": "Get-agents",
152015
+ "description": "List agents visible to the current user, or fetch a single agent by ID.\n\n## When to use this tool\n\n- When the user asks to see their agents or list available agents\n- When you need to look up an agent's instructions or configuration\n- When the user asks about a specific agent by name or ID\n\n## How it works\n\n- Without agentId: returns all visible agents with description only\n- With agentId: returns the full agent details including complete instructions and configured triggers"
152016
+ },
152017
+ {
152018
+ "slug": "CLARIFY_MCP_GET_ARTIFACT_COMPONENT_DOC",
152019
+ "name": "Get-artifact-component-doc",
152020
+ "description": "Get the full prop contract for one or more Clarify design-system components\navailable to artifacts — each component's summary, a usage snippet, and every\nprop with its type and allowed values.\n\n## When to use this tool\n\nThe create-or-update-artifact tool lists the available `@clarify/ui/*`\ncomponents with a one-line summary each. Call this before using components you\nare unsure about to get their exact props and allowed values, and call it when\nan existing artifact fails to render against a component so you can repair it\nagainst the current contract.\n\n## How it works\n\nPass one or more `specifiers` exactly as listed (e.g. `@clarify/ui/button`) —\nbatch everything you need in a single call. Returns each component's\ndocumentation as markdown. Props are extracted from the component source, so\nthe values are always current.\n\n## Runtime dependency versions\n\nThe artifact runtime pins `framer-motion` (v12.40.0), `react` (v19.2.8), `react-dom` (v19.2.8), `recharts` (v3.8.1). See the\ncreate-or-update-artifact tool for which of these your artifact JSX may\nimport directly; the rest run internally (e.g. `react-dom` powers the\nscaffold's mount call). `@clarify/ui/*` itself is not independently\nversioned — it tracks this package."
152021
+ },
152022
+ {
152023
+ "slug": "CLARIFY_MCP_GET_ARTIFACT_SOURCE",
152024
+ "name": "Get-artifact-source",
152025
+ "description": "Read the current source of an existing artifact — the JSX of its applied\nversion, plus its name and description.\n\n## When to use this tool\n\nUse this before updating an artifact so you patch its real current source\nrather than rewriting it from memory. It is the read half of the artifact\nedit loop: read the source here, apply your fix, then pass the full revised\ncontent to `create-or-update-artifact` with the same\n`artifact_id` to save a new version. It is especially useful when recovering\nfrom a render or query error reported to you for an artifact you did not\nauthor in this conversation.\n\n## Upgrade while you're here\n\nThe saved source may predate the current authoring guidance — an older\nartifact can hand-roll something a `@clarify/ui/*` component or hook now\ncovers, or use query and chart code that has since improved. While you have\nthe source open to make the requested change, compare it against the current\ncomponent catalog and the query and chart guidance in\n`create-or-update-artifact`, and fold any clear upgrade into the\nsame new version: swap a hand-rolled pattern for the component that now covers\nit, and bring stale query or chart code up to the current guidance. Change\nonly what is a clear improvement — leave the rest of the source untouched.\nThen tell the user in plain terms that you upgraded it, without the build\ndetails, e.g. \"I also updated the UI to the latest version for more features.\"\n\n## Returns\n\nThe applied version's JSX source (a React component named `ArtifactContents`),\nthe artifact's name, and its description. Fails if the artifact does not exist\nor has no applied version yet."
152026
+ },
152027
+ {
152028
+ "slug": "CLARIFY_MCP_GET_CALENDAR_EVENTS",
152029
+ "name": "Get-calendar-events",
152030
+ "description": "List the current user's calendar events in a time range.\n\n## When to use this tool\n\n- To answer \"what's on my calendar today/tomorrow/next week\"\n- To find a specific upcoming meeting by title or topic\n- To gather context (attendees, conferencing link) before drafting an email or\n creating a follow-up event\n\n## How it works\n\nReads from Clarify's synced calendar data: no live API call to Google or\nMicrosoft. Filters meetings the current user attends in the given time range.\n\n## Returns\n\nA list of events with both `event_id` (Nylas calendar event ID, used by the\nwrite tools) and `_id` (Clarify meeting ID, used by other meeting tools).\nWhen more events match than `limit`, the response notes the truncation.\n\n## Important notes\n\n- Time range is required. Be reasonable: a 7-day window is a good default.\n- The optional `query` filter does case-insensitive substring matching on\n title and description."
152031
+ },
152032
+ {
152033
+ "slug": "CLARIFY_MCP_GET_CAMPAIGN_RECIPIENTS",
152034
+ "name": "Get-campaign-recipients",
152035
+ "description": "List the individual people enrolled in a campaign, with their per-person engagement — who opened, who clicked, who replied, and when.\n\n## When to use this tool\n\n- Answer \"who clicked\", \"who opened\", \"who replied\", \"who hasn't responded\"\n- Build a follow-up or retarget audience from the people who engaged with a campaign\n- Check where a specific person is in a campaign, or why their run stopped\n\nUse `get-campaigns` instead when you need campaign-level totals and rates rather than the people behind them. Get the `campaign_id` from that tool first.\n\n📖 **For campaign rules and examples**: Use read-context with context: \"campaign-docs\"\n\n## Returns\n\nOne entry per recipient: person name, email, person ID, delivery status, opened/clicked/replied flags, and the timestamp of their most recent open, click, and reply.\n\n## Pagination\n\n- When the user asks for \"more\" results, use the EXACT same inputs and only change the offset parameter\n- The tool will tell you the next offset value to use\n\n## Examples\n\n<example>\n{\n \"campaign_id\": \"0195f2c1-...\",\n \"event\": [\"clicked\"]\n}\n</example>\n\n<example>\n{\n \"campaign_id\": \"0195f2c1-...\",\n \"status\": \"completed\",\n \"limit\": 25\n}\n</example>"
152036
+ },
152037
+ {
152038
+ "slug": "CLARIFY_MCP_GET_CAMPAIGNS",
152039
+ "name": "Get-campaigns",
152040
+ "description": "List campaigns in the workspace, or fetch a single campaign by ID with full details.\n\n## When to use this tool\n\n- Without campaign_id: discover existing campaigns, search by name, get campaign IDs\n- With campaign_id: read a campaign's full email content, inspect subjects/bodies/timing, check performance metrics, get details before duplicating with `create-campaign`\n\n📖 **For comprehensive campaign rules and examples**: Use `read-context` with context: \"campaign-docs\"\n\n## Returns\n\n**List mode** (no campaign_id):\n- Campaign name, ID, description, status, email step count, target list, created/updated info\n\n**Detail mode** (with campaign_id):\n- Full campaign details including all email steps with subjects, bodies (HTML with variables), and timing\n- Campaign-level performance: open rate, click-through rate, response rate, bounce rate\n- Per-email-step engagement: sent, opened, clicked, replied, bounced counts\n\nAll engagement here is aggregate counts only. To find out *which people* opened, clicked, or replied — and when — use `get-campaign-recipients`.\n\n## Pagination (list mode only)\n\n- When user asks for \"more\" results, use the EXACT same search inputs and only change the offset parameter\n- The tool will tell you the next offset value to use\n\n## Duplicating a campaign\n\nTo duplicate a campaign, call this tool with campaign_id first, then pass the returned email steps and settings to `create-campaign` with a new name like \"Copy of <original>\". Copy the `list_id` so the duplicate targets the same audience. Do NOT copy from_name. Let the new campaign use the current user's sender identity. If the original sender differs from the current user, also remove the original sender's personal sign-off from email bodies."
152041
+ },
152042
+ {
152043
+ "slug": "CLARIFY_MCP_GET_CURRENT_USER",
152044
+ "name": "Get-current-user",
152045
+ "description": "Get information about the current authenticated user, including their timezone.\n\n## When to use this tool\n\nUse this to understand who \"me\", \"my\", and \"I\" refer to in user queries.\n\n## Important notes\n\nWhen interpreting relative dates (e.g., \"last 2 weeks\", \"yesterday\"):\n- Calculate dates in the user's timezone returned by this tool\n- Convert to UTC and ISO format for database queries"
152046
+ },
152047
+ {
152048
+ "slug": "CLARIFY_MCP_GET_LISTS",
152049
+ "name": "Get-lists",
152050
+ "description": "Get list metadata (saved views) for an entity type, or fetch a single list by ID.\n\nOnly dynamic lists (membership driven by a SQL query) are returned. Legacy static and default lists are filtered out.\n\n## When to use this tool\n\n- Without list_id: discover existing lists, search by name or description, or filter by creator or owner\n- With list_id: fetch full details for a specific list\n\nSupports case-insensitive substring search and filtering by creator (created_by) or owner (owner_id) when no list_id is provided.\n\n## Returns\n\n- List name (title)\n- Description\n- SQL query\n- Layout (table, board)\n- Owner and creator (user name, email, and user ID)\n- Last edited (when a person last changed the list's query or layout, and who — or \"No edits recorded\"). This does not track title, emoji, or description edits.\n\n## Pagination\n\n- When user asks for \"more\" results, use the EXACT same search inputs and only change the offset parameter\n- The tool will tell you the next offset value to use (e.g., \"Call this tool again with offset=25 to continue\")"
152051
+ },
152052
+ {
152053
+ "slug": "CLARIFY_MCP_GET_RECORDS",
152054
+ "name": "Get-records",
152055
+ "description": "Retrieve detailed information about specific records by their IDs.\n\nThis tool provides comprehensive context about records, including relationships, AI summaries, and other details.\n\nUse this tool when you need to:\n- Understand the current state of specific records before answering questions or taking actions\n- Read meeting recording transcripts with full speaker attribution\n- Read email content, subject, body, and participants\n- Get rich context about records found via query-data\n\nTypical workflow: Use query-data to find record IDs, then pass them here for full details.\n\nMeeting-specific guidance:\n- For meeting: returns metadata, summary (AI-generated), notes (user-written), and associated recordings. If summary is null, check notes before concluding no content exists\n- For meeting_recording: returns the full transcript with speaker names and timestamps\n- When the user asks for exact quotes, verbatim wording, or \"what exactly was said\", fetch the meeting_recording transcript via get-records. The meeting summary is paraphrased and does not preserve the original words."
152056
+ },
152057
+ {
152058
+ "slug": "CLARIFY_MCP_GET_SCHEMA",
152059
+ "name": "Get-schema",
152060
+ "description": "Get the schema for Clarify entities.\n\n## When to use this tool\n\nUse the read format when working with SQL queries and the query-data tool. Use the write format when creating or updating records with the create-or-update-records tool.\n\nPass the specific entities you need. Read defaults to the CRM database, and omitting entities returns every CRM entity, a large result that is re-sent on every later turn, so only omit it when you genuinely need the whole model.\n\nFor lead columns (funding stage, employee range, industries, location), request the tam_company or tam_person entities to get the schema for the find-leads tool. The analytics event log schema comes with the query-analytics tool directly, so you do not need this tool for it.\n\n## Databases\n\nClarify has three databases:\n\n- CRM database (company, person, deal, meeting, user, task): your workspace data. Use with the query-data tool. Read returns these by default.\n- Leads database (tam_company, tam_person): prospecting data for finding new leads. Request these entities explicitly. Use with the find-leads tool.\n- Analytics database (ClickHouse, single `analytics.event` table): historical event log of every CRM change: point-in-time and change-history questions. Its schema comes with the query-analytics tool.\n\n## Formats\n\n- read: schema for reading data via SQL queries with the query-data tool, or lead columns for the find-leads tool.\n Returns all columns, types (including JSONB structure), relationships, join tables, and custom fields. Defaults to CRM entities.\n\n- write: writable fields for the create-or-update-records tool.\n Returns fields that can be set when creating or updating records."
152061
+ },
152062
+ {
152063
+ "slug": "CLARIFY_MCP_GET_WORKFLOW_RUNS",
152064
+ "name": "Get-workflow-runs",
152065
+ "description": "Get execution runs for a workflow. Returns run history with status and timing.\n\n## When to use\n- Check if a workflow is executing correctly\n- Review recent run history\n- Count failures or investigate patterns\n\n## Returns\n- Run ID, status, start/end times, duration\n- Record that triggered the run (if applicable)\n- To get full details of a specific run, use the get-records tool with entity \"workflow-run\" and the run ID\n\n## Pagination\n- When the user asks for \"more\" results, use the same inputs and only change the offset"
152066
+ },
152067
+ {
152068
+ "slug": "CLARIFY_MCP_GET_WORKFLOWS",
152069
+ "name": "Get-workflows",
152070
+ "description": "Get and search workflows in the workspace, or fetch a single workflow with its full configuration.\n\nWhen called without `workflow_id`, returns metadata for matching workflows (supports case-insensitive substring search and enabled/disabled filtering). When called with `workflow_id`, returns the full configuration for that one workflow (trigger with input and filters, every action block) and ignores the other inputs.\n\n## When to use this tool\n\n- Find a workflow by name to get its ID\n- Discover existing workflows in the workspace\n- Get the workflow ID before calling `get-workflow-runs` or `create-or-update-workflow`\n- Confirm a workflow's trigger filters match what the user asked for (pass `workflow_id`)\n- Inspect a specific block's input or filters before editing it (pass `workflow_id`)\n- Walk the full block order (trigger → blocks → exits) to debug a misconfigured workflow (pass `workflow_id`)\n\n## Returns\n\nWithout `workflow_id` (list mode), for each workflow:\n- Workflow ID\n- Name and description\n- Status (active/draft)\n- Trigger plugin ID\n- Number of action blocks\n- Created and updated timestamps\n\nWith `workflow_id` (single mode):\n- Workflow ID, name, description, status (active/draft), and timestamps\n- Trigger: plugin ID, input, filters\n- Each block: ID, plugin ID, input, filters, prev/next links\n\n## Pagination\n\nWhen the user asks for \"more\" results, use the same inputs and only change the offset"
152071
+ },
152072
+ {
152073
+ "slug": "CLARIFY_MCP_IMPORT_LEADS",
152074
+ "name": "Import-leads",
152075
+ "description": "Import leads from a tam_company or tam_person search into Clarify.\n\n## Important Rules\n\n- Parameters like versionId and searchId should preferably come from the document context, which is the source of truth for identifiers. If the document context does not include a versionId, you may use the most recent versionId from the conversation if it is contextually relevant.\n- When a versionId is provided, the version will be applied to the search and the search will be published before starting the import\n- Always provide a descriptive searchTitle that reflects the current filters/query of the search (e.g., \"SF Companies with 50+ employees\")\n- Always provide a searchEmoji — a single emoji that represents the theme of the search (e.g., \"🏢\" for companies, \"🌉\" for SF-related searches)\n\nWhen the user asks to import leads without specifying a count:\n- For tam_company searches, import all leads without asking — company imports never consume credits regardless of size.\n- For tam_person searches with fewer than 100 leads, import them all without asking.\n- For tam_person searches with 100 or more leads, ask whether they want to import a small sample (e.g. 10) to test first or all leads from the search. Inform the user that importing people costs 1 credit(s) per net-new person, so importing all N people will cost up to N × 1 credits total.\n\n## How charges work\n\nCredits are charged only for net-new tam_person records that get inserted. Records that already exist in the CRM are skipped by the system and never charged. tam_company imports are always free. When a batch returns 0 net-new records (all matches already exist in the CRM), nothing is charged. Never tell the user they have \"burned credits on duplicates\" or suggest a refund in that case; there is nothing to refund.\n\nNever explain internal decision logic, thresholds, or tool behavior to the user. For example, do not say things like \"Since there are fewer than 100, I'll import them all.\" Just perform the action and describe what you did in user-friendly terms.\n\n## Extra fields\n\nThis tool can import any field from the TAM database — not just the core fields. When the user asks for additional data (e.g., \"import with industries and tech stack\", \"I want ownership status too\", \"add seniority\"), use the extraFields parameter. The import automatically creates CRM fields that don't exist yet and populates them with TAM data. Do not create fields manually — this tool handles it.\n\nThis also works for records that already exist in the CRM. If the user wants to backfill a field (e.g., \"add industries to my existing companies\"), re-run the import with extraFields and the existing records will be updated with the new field values.\n\nAvailable extra fields for companies: alternative_names (Alternative names), website (Website), type (Type), industries (Industries), specialities (Specialities), workforce_headcount (Workforce headcount), summary (Summary), funding_last_round_type (Last funding round type), funding_last_round_amount_usd (Last funding round amount (USD)), funding_last_round_date (Last funding round date), investments (Investments), financing_profile_status (Financing status), financing_profile_ipo_date (IPO date), financing_profile_market_cap (Market cap), ownership_status (Ownership status), ownership_status_detailed (Ownership status (detailed)), stock_exchange (Stock exchange), customer_types (Customer types), tech_stack_products (Tech stack products), patent_count (Patent count), contact_info_email (Contact email), contact_info_phone (Contact phone), contact_info_url (Contact URL), identifiers_stock_ticker (Stock ticker), identifiers_naics_code (NAICS code), identifiers_duns_code (DUNS code), identifiers_cage_code (CAGE code), is_acquired (Is acquired), is_exited (Is exited), is_government (Is government), is_non_profit (Is non-profit), is_shut_down (Is shut down), is_stealth (Is stealth).\n\nAvailable extra fields for people: personal_email_addresses (Personal email addresses), headline (Headline), function (Function), seniority (Seniority), hiring (Hiring), open_to_work (Open to work), skills (Skills), smart_tags (Smart tags), investor_data_type (Investor type), investor_data_geo_focus (Investor geo focus), investor_data_industry_focus (Investor industry focus).\n\nIf the user says \"import all fields\" or \"include everything\", pass all available field names for the entity type. If the user doesn't mention extra fields, omit the parameter."
152076
+ },
152077
+ {
152078
+ "slug": "CLARIFY_MCP_IMPORT_MEETING_TRANSCRIPT",
152079
+ "name": "Import-meeting-transcript",
152080
+ "description": "Import a meeting transcript from an external source (Granola, Notion, Circleback).\n\n## When to use this tool\n\nUse after finding a meeting in an external source. Pass the source and transcript ID\ndirectly; the tool fetches the content from the source system.\n\n## How it works\n\n1. Provide the Clarify meeting ID to attach the transcript to\n2. Specify the source (granola, notion, or circleback)\n3. Provide the transcript/page ID from the source system\n\nThe tool calls the source's MCP server directly to fetch the transcript,\nparses it, and uploads it to the meeting.\n\n## Important notes\n\n- The workspace must have the source MCP server connected\n- The user must have authorized with the source MCP server\n- For Circleback: the source_id must be the numeric meeting ID (e.g. \"7927294\"), not the\n URL slug. Use the Circleback SearchMeetings tool first to resolve the numeric ID.\n- After importing, tell the user the transcript was attached"
152081
+ },
152082
+ {
152083
+ "slug": "CLARIFY_MCP_MANAGE_ACCESS",
152084
+ "name": "Manage-access",
152085
+ "description": "Manage who can access a specific object — a list, meeting, message, or record\n(deal, company, person, or a custom object) — by granting, updating, revoking,\nor reading its access grants, or reassigning its owner.\n\n## When to use this tool\n\n- When the user asks to share a list, meeting, message, or record with a\n teammate or with the whole workspace\n- When the user asks to share every email/message on a record (e.g. \"share all\n emails on this deal with the team\") — use `mode: \"related\"`\n- When the user asks to change someone's access level (view vs edit)\n- When the user asks to stop sharing / remove access\n- When the user asks who an object is shared with\n- When the user asks to change who owns a list or record — reassign ownership\n to someone else\n\n## How it works\n\nSet `action` to one of \"grant\", \"update\", \"revoke\", \"read\", or \"reassign\"\nand point `target` at what you're managing. `target` has two modes:\n\n- `mode: \"direct\"` — a single object by `entity` (list, meeting, message, or\n a record object type such as deal/company/person/custom) and `objectId`.\n Supports every action.\n- `mode: \"related\"` — every message related to an anchor record, addressed by\n `anchorEntity` (e.g. deal, company, person), `anchorId`, and\n `relatedEntity: \"message\"`. Bulk-shares the messages you own on that record.\n Supports grant, revoke, and read only (no update or reassign).\n\n- grant / update: pass `grantees` and an `accessLevel` (\"view\" or \"edit\").\n- revoke: pass either `grantees` or `all: true` (not both). Revoke asks the\n user to confirm before removing access.\n- read: returns the current grantees and their access levels.\n- reassign: pass `newOwnerId` (a user record id) to transfer ownership to\n that user. The previous owner keeps edit access. To reassign several\n objects to the same new owner at once, add the other object ids to\n `objectIds` (`target.objectId` is always included) — they transfer in a\n single confirmed call.\n\n## Grantees\n\nA grantee is `{ granteeType, userId }`:\n- `granteeType: \"user\"` shares with one person and requires `userId` (a\n user record id — resolve names/emails to an id first).\n- `granteeType: \"workspace\"` shares with everyone in the workspace and takes\n no id.\n\n## Important notes\n\n- Only the owner (or a workspace permission admin) can change an object's\n access or reassign its ownership; meetings require a participant.\n Unauthorized requests are rejected.\n- A workspace admin can reassign the owner of a record only when it is\n workspace-visible, never a private one. The owner can always reassign their\n own, and list ownership transfer has no such restriction.\n- Meetings and messages have no owner and cannot be reassigned.\n- In related mode, only the messages you own on the anchor record are shared;\n messages you don't own are never touched.\n- Access levels are \"view\" or \"edit\" only."
152086
+ },
152087
+ {
152088
+ "slug": "CLARIFY_MCP_MERGE_RECORDS",
152089
+ "name": "Merge-records",
152090
+ "description": "Merge two or more records into a single primary record in Clarify.\nAll data from the source records (fields, relationships, list memberships, notes) will be merged into the primary record.\nSource records are deleted after merging."
152091
+ },
152092
+ {
152093
+ "slug": "CLARIFY_MCP_QUERY_ANALYTICS",
152094
+ "name": "Query-analytics",
152095
+ "description": "Execute read-only ClickHouse SQL against the analytics event log.\n\n## When to use this tool\n\nUse `query-analytics` for **historical / point-in-time** questions\nabout CRM records: anything that requires looking at the sequence of changes\nover time, not just the current state. Examples:\n\n- \"What was the sequence of stage changes for this deal?\"\n- \"How long did this deal sit in 'In progress'?\"\n- \"What was the total amount of all deals in each stage on a specific date?\"\n- \"How many deals were created per day last week?\"\n- \"Who last edited this record, and when?\"\n\n## When NOT to use this tool\n\nFor **current state** questions (\"which deals are open?\", \"what's this\ncompany's domain?\"), use the `query-data` tool: it queries PostgreSQL\ndirectly and is faster for live values. Only fall back to\n`query-analytics` when you need history.\n\n## How it works\n\n- The query runs against ClickHouse, not PostgreSQL. Use ClickHouse SQL\nsyntax (`JSONExtractString`, `toDate`, `argMax`, etc.).\n- When the user hasn't asked for a specific time frame, scope the query to\nthe last 30 days with `AND timestamp >= now() - INTERVAL 30 DAY` to keep\nit fast and the results relevant.\n- Statements are read-only: INSERT / UPDATE / DELETE / DDL are rejected\nby ClickHouse.\n- Results are capped to the `maxResultRows` parameter (default 1024). Rows\nbeyond the cap are dropped server-side, even if your SQL omits a `LIMIT`.\n\n# Analytics database (ClickHouse)\n\nHistorical event log of every change to the CRM. **Read-only.** Query it to\nanswer point-in-time and change-history questions like:\n\n- \"What was the sequence of events that led to the current stage of this deal?\"\n- \"How long did this deal sit in the 'In progress' stage?\"\n- \"How many deals were created per day last week?\"\n\n## The `analytics.event` table (ClickHouse)\n\nRead-only SQL runs against ClickHouse, not PostgreSQL — use ClickHouse syntax\n(`JSONExtractString`, `toDate`, `argMax`, etc.). Every CRM record lives in\nONE append-only CDC event log, `analytics.event` — NOT a table of current\nrecords; every create/update/delete is its own row. There is no `deal` /\n`company` / `person` table (`FROM deal` fails with \"Unknown table\nexpression identifier\"). Always query `FROM analytics.event` and pick the\nentity with `WHERE entity_type = '<type>'`.\n\nSchema is inspired by PostHog: one wide event table with a JSON-stringified\n`properties` payload plus a structured `actor` column. Hot keys are promoted\nto materialized columns (below); everything else is read from `properties`\nwith `JSONExtract*`.\n\nEvery event carries a FULL snapshot of the record's fields in `properties` —\ncreate, update, and delete alike. An update is not a delta: it repeats every\nfield the record has, not just the ones that changed. So the single latest\nevent per entity already holds every current field, and you never need to\nstitch fields together across events. (The one exception: fields marked\nsensitive are omitted from `properties` entirely.)\n\n- `_id` (String) — Event id\n- `workspace_slug` (String) — Workspace (tenant) slug\n- `entity_type` (String) — Subject type: `deal`, `company`, `person`,\n`meeting`, `message`, or `c_<slug>` for a custom object\n- `entity_id` (String) — Subject record id\n- `type` (String) — Event type: `clarify:create` |\n`clarify:update` | `clarify:delete` (full enum below)\n- `timestamp` (DateTime64(6,'UTC')) — Event time; use `toDate(timestamp)` for day grouping\n- `properties` (String/JSON) — A full snapshot of the record's fields at event\ntime (every field, not just the changed ones); read with\n`JSONExtractString/Float/Bool(properties, '<field>')`\n- `diff` (String/JSON) — On update events, the field-level changes this event\napplied: a JSON array of `{op, path, val, oldVal}` (`path` locates the field,\n`oldVal` → `val` is the transition). Empty (`''`) on create and no-op events.\nUse it to detect WHEN a field changed — see \"Detecting when a field changed\"\n- `actor` (Tuple) — `actor._id`, `actor.anonymous_id`, `actor.entity`,\n`actor.source_id` (all String, native paths — no `JSONExtract` needed); usable in `GROUP BY` / `ORDER BY`\n- `m_stage` (String) — Materialized `JSONExtractString(properties,'stage')`; empty if absent\n- `m_amount` (Float64) — Materialized `JSONExtractFloat(properties,'amount')`; `0` if absent\n- `m_close_date` (Nullable(Date)) — Materialized `toDateOrNull(properties.close_date)`;\n`NULL` if absent/unset. A native date — range-filter and group it directly\n(`m_close_date >= '2026-01-01'`, `toStartOfMonth(m_close_date)`) with no `toDate` wrapper\n\n### Reading fields is ClickHouse, not PostgreSQL\n\nPostgreSQL JSONB operators `->` and `->>` do not exist in ClickHouse — `properties->>'description'` fails. Read fields with `JSONExtractString(properties, 'description')` (or `JSONExtractFloat` / `JSONExtractBool`). There is no `JSONExtractFloat64` — use\n`JSONExtractFloat`. If a query fails because a function does not exist, use\nthe alternative ClickHouse suggests (e.g. `JSONExtractRaw`).\n\n### Materialized columns\n\nPrefer the materialized columns `m_stage` / `m_amount` / `m_close_date` over\n`JSONExtract*(properties, 'stage'|'amount'|'close_date')` when the key matches —\nthey are typed, indexed, and skip a JSON parse per row. They are populated from\nwhatever `properties.stage` / `properties.amount` / `properties.close_date`\ncarries on each row, regardless of `entity_type`, so they work for a custom\nobject with those fields too. For `m_stage` / `m_amount`, empty / `0` means the\nevent didn't carry the key. `m_close_date` instead uses `NULL` for an absent or\nunset close date (a date has no neutral sentinel), so test presence with\n`m_close_date IS NOT NULL`, not `!= ''`.\n\n`m_stage` (like every snapshot field) is the value the record held *when the\nevent fired*, not a transition. Counting `m_stage = 'Won'` answers \"records that\nwere in Won while something happened to them\" — an enrichment sweep, a note, or\nan owner change re-emits the unchanged stage — so it tracks activity, not\noutcomes. For \"records that *entered* a stage\", read `diff` instead (see\n\"Detecting when a field changed\").\n\n### Allowed `type` values\n\n- `CdcEventType` — `clarify:create`, `clarify:update`, `clarify:merge`, `clarify:delete`, `clarify:add-to-list`, `clarify:remove-from-list`, `clarify:set-relationship`, `clarify:unset-relationship`, `clarify:grant-access`, `clarify:update-access`, `clarify:revoke-access`, `clarify:meeting`\n\n### Scope every query (this is what keeps it fast)\n\nThe table is a `ReplacingMergeTree` ordered by\n`(workspace_slug, entity_type, entity_id, timestamp, _id)`. Filter from the\nleft of that key so ClickHouse prunes the table:\n\n- Always make `workspace_slug = '<your workspace>'` the first `WHERE`\ncondition — it is the leading sort-key column and prunes almost the whole\ntable. Use the Workspace value from your context; if it isn't there, call the\n`get-current-user` tool to get it before querying.\n- Always filter by `entity_type` next; add `entity_id` too for\nsingle-record questions (that hits the sort-key prefix and reads a tiny slice).\n- Time-series / activity / trend queries must also carry a `timestamp` range\n(e.g. `timestamp >= now() - INTERVAL 90 DAY`) — both to scope the report and\nto bound the scan. Current-state reconstruction is the exception (below): it\nneeds the full history per entity, so do NOT put a `timestamp` floor on it.\n- Filtering only by columns outside the sort key (`type`, `m_stage`,\n`m_amount`, `m_close_date`, or any `JSONExtract*` value) forces a full scan\n— pair them with the sort-key columns above.\n- Name the columns you need — avoid `SELECT *`. It returns the wide `data`\npayload and computes the `properties` JSON alias for every row; list just\nthe columns the report uses (`entity_id`, `timestamp`, `m_stage`, …).\n- Prefer `GROUP BY` on low-cardinality columns (`entity_type`, `m_stage`,\n`toDate(timestamp)`, `entity_id`), not on a freeform\n`JSONExtractString(properties, '<field>')` of a high-cardinality field (a\nnote, description, or free text) — that forces a JSON parse per row and\nexplodes the group count.\n- When you only need to eyeball a few recent rows, bound the read with\n`ORDER BY timestamp DESC LIMIT <n>` instead of scanning the whole slice.\n- Date literals: prefer relative helpers (`now() - INTERVAL 1 MONTH`,\n`toStartOfMonth(now())`, `today() - 7`) — you have no reliable wall clock,\nand a hardcoded boundary silently drifts. A bare\n`timestamp >= '2026-04-01T00:00:00Z'` rejects the ISO `T`/`Z`; use\nspace-separated `'2026-04-01 00:00:00'`,\n`parseDateTime64BestEffort('2026-04-01T00:00:00Z')`, or\n`CAST('2026-04-01T00:00:00Z' AS DateTime64(6, 'UTC'))`.\n\n### Good vs bad query shapes\n\n- Scope by the sort key, don't filter on a column alone:\n- Bad: `SELECT count() FROM analytics.event WHERE m_stage = 'Won'` — no\n`workspace_slug` / `entity_type`, so it scans every workspace.\n- Good: `... WHERE workspace_slug = '<your workspace>' AND entity_type = 'deal' AND m_stage = 'Won'`.\n- Name columns, don't `SELECT *`:\n- Bad: `SELECT * FROM analytics.event WHERE ...`.\n- Good: `SELECT entity_id, timestamp, m_stage FROM analytics.event WHERE ...`.\n- Bound a trend with a time range:\n- Bad: `SELECT toDate(timestamp) AS day, count() FROM ... GROUP BY day` with\nno `timestamp` floor — scans all history.\n- Good: add `AND timestamp >= now() - INTERVAL 90 DAY`.\n- Group low-cardinality, cap exploratory reads:\n- Bad: `... GROUP BY JSONExtractString(properties, 'notes')`, or reading raw\nrows with no `LIMIT`.\n- Good: `... GROUP BY m_stage`, or `ORDER BY timestamp DESC LIMIT 20` to\npeek at recent rows.\n\n### Reconstruct current state from the log\n\nTo report on CURRENT state, rebuild it from the event history:\n\n- Every event stores a full snapshot of the record, so reconstruct current field values with plain `argMax(<field>, timestamp)` grouped by `entity_id` — never a `JSONHas` / `<field> != ''` / `!= 0` presence guard, which resurrects a stale earlier value for a field that was later cleared or set back to 0. Read a JSON field with\n`argMax(JSONExtractString(properties,'<field>'), timestamp)`, or a\nmaterialized column directly with `argMax(m_stage, timestamp)`.\n- Drop deleted records: `HAVING argMax(type, timestamp) != 'clarify:delete'`.\n- Reconstruct in a CTE, then filter/aggregate over the CTE — filtering a mutable\nfield inside the per-entity scan changes which event counts as \"latest\" and\nproduces wrong totals.\n\n```sql\nWITH deal_current AS (\nSELECT\nentity_id,\nargMax(m_stage, timestamp) AS stage,\nargMax(m_amount, timestamp) AS amount\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\nGROUP BY entity_id\nHAVING argMax(type, timestamp) != 'clarify:delete'\n)\nSELECT stage, count() AS deals, sum(amount) AS pipeline\nFROM deal_current\nWHERE stage NOT IN ('Closed Won', 'Closed Lost')\nGROUP BY stage\n```\n\n### Count stage transitions in a period\n\nA snapshot count (`m_stage = 'Won'`) can't answer \"how many deals were won this\nquarter\" — it counts deals *touched* while already won. Count the transition\ninstead: the events where `stage` moved into a closed value, plus deals created\ndirectly in one. The `UNION` branch is required because `diff` is empty on\ncreate — it catches deals imported straight into a closed stage.\n\n```sql\n-- Deals that ENTERED a closed stage inside the window.\nWITH closed AS (\nSELECT entity_id, timestamp, m_stage AS stage_at_event\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\nAND type = 'clarify:update'\nAND arrayExists(d -> JSONExtractString(d, 'path', 1) = 'stage'\n AND JSONExtractString(d, 'val') IN ('Won', 'Lost'),\n JSONExtractArrayRaw(diff))\nUNION ALL\n-- diff is empty on create: catches deals imported directly into a closed stage\nSELECT entity_id, timestamp, m_stage\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\nAND type = 'clarify:create' AND m_stage IN ('Won', 'Lost')\n)\nSELECT countIf(final_stage = 'Won') AS deals_won,\n count() AS deals_closed,\n countIf(final_stage = 'Won') / nullIf(count(), 0) AS win_rate\nFROM (SELECT entity_id, argMax(stage_at_event, timestamp) AS final_stage\n FROM closed GROUP BY entity_id)\n```\n\nThe outer `argMax` collapses each deal to its last transition in the window, so a\ndeal that goes Won → Lost inside it counts once, as Lost. There is no delete\nguard here on purpose — a deal won in the window was won even if the record was\nlater deleted; to drop since-deleted deals, reconstruct current state (above) and\nkeep only the `entity_id`s that are still live. Matching on `val` works because\n`stage` is not sensitive; a sensitive field's `val` reads `'REDACTED'` (its\n`path` is kept), so for those match on `path` presence alone.\n\nFor a \"closed per month\" trend, bucket by the event `timestamp` — that is when\nthe transition actually happened. One data limitation to surface, not hide: on a\nbatch-imported workspace every `clarify:create` lands on the\nimport date, so deals that closed before they were imported collapse onto that\ndate — the log has no real historical close date for them. `m_close_date` does\nnot fill that gap: it is the *expected* close date (often in the future), right\nfor a pipeline-by-expected-close forecast but wrong as a \"when did we win\"\nbucket.\n\n### Detecting when a field changed\n\nA field being non-empty on an event does NOT mean it changed on that event —\nevery event repeats all fields, so an edit to one field re-emits the rest\nunchanged. Use the `diff` column: on an update it lists exactly the fields that\nchanged, so \"did this field change on this event\" is a plain row filter. Unlike\ncomparing snapshots across events, this composes with a `timestamp` range and\nstays fast. A field changed on an event when `diff` holds an entry whose first\n`path` element is that field:\n`arrayExists(d -> JSONExtractString(d, 'path', 1) = 'stage', JSONExtractArrayRaw(diff))`.\nThe matching entry also carries the transition — `oldVal` → `val` — so you can\nreport \"moved from X to Y\" without reading other events.\n\nCaveats: `diff` is populated on `clarify:update` events only — it\nis empty on `clarify:create`, so if you also need the value set\nat creation (e.g. a deal's first stage), `UNION` in the create event. A change\nto a sensitive field shows `val`/`oldVal` as `'REDACTED'` but keeps its `path`,\nso the change is still detectable. Do NOT count a stage question off the\nsnapshot: `m_stage != ''` counts every edit to a record that has a stage, and\n`m_stage = 'Won'` counts every edit to an already-won deal — neither is a stage\nchange. Match on `diff` instead (see \"Count stage transitions in a period\").\n\n### Join across entities\n\nEvery entity lives in the same `analytics.event` table, so a cross-entity\nreport is CTEs joined on a foreign key stored in `properties`. Reconstruct\neach entity's current state in its own CTE (the pattern above), then join on the\nid — a deal's `company_id` links to the company's `entity_id`.\n\nScope the looked-up CTE to only the ids the join needs: add\n`AND entity_id IN (SELECT <fk> FROM <driving_cte>)` to its `WHERE`.\n`entity_id` is a sort-key column, so this prunes reconstruction to a tiny\nslice instead of rebuilding every record of that entity type — the difference\nbetween a many-second and a sub-second query.\n\n```sql\nWITH deal_current AS (\nSELECT\nentity_id,\nargMax(JSONExtractString(properties,'company_id'), timestamp) AS company_id,\nargMax(m_amount, timestamp) AS amount\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'deal'\nGROUP BY entity_id\nHAVING argMax(type, timestamp) != 'clarify:delete'\n),\ncompany_current AS (\nSELECT\nentity_id,\nargMax(JSONExtractString(properties,'name'), timestamp) AS name\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>' AND entity_type = 'company'\nAND entity_id IN (SELECT company_id FROM deal_current)\nGROUP BY entity_id\nHAVING argMax(type, timestamp) != 'clarify:delete'\n)\nSELECT c.name AS company, sum(d.amount) AS pipeline\nFROM deal_current d\nJOIN company_current c ON c.entity_id = d.company_id\nGROUP BY c.name\nORDER BY pipeline DESC\n```\n\n### Common pitfalls\n\n- `FROM deal` / `FROM company` — no per-entity tables exist. Query\n`analytics.event` and filter `entity_type`.\n- Reconstruction returns stale values — you added a `JSONHas` / presence\nguard. Use plain `argMax` (see \"Reconstruct current state from the log\").\n- Wrong totals when filtering a mutable field — you filtered it inside the\nper-entity scan. Reconstruct in a CTE first, then filter over the CTE.\n- Slow cross-entity join — the looked-up CTE rebuilt every record of its entity\ntype. Add `AND entity_id IN (SELECT <fk> FROM <driving_cte>)` so it only\nreconstructs the records the join needs.\n- `JSONExtractFloat64` does not exist — use `JSONExtractFloat`.\n\n### Time-in-stage\n\nSelect the stage-transition events with the `diff` filter (see \"Detecting when\na field changed\"), and `UNION` in each deal's `clarify:create`\nevent so the first stage's clock starts at creation. Then, over that filtered\nset, take each transition's gap to the next with\n`leadInFrame(timestamp) OVER (PARTITION BY entity_id ORDER BY timestamp ROWS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING)`\n— that gap is how long the deal held the stage. The frame is required:\n`leadInFrame` defaults to a frame ending at the current row and would never see\nthe next event. The latest transition has no next event, so its `leadInFrame`\nis the zero date — treat that as \"still in this stage\" (`now()`). Don't treat\nevery `clarify:update` as a transition — every event repeats the\ncurrent stage whether or not it changed.\n\n## Examples\n\n<example>\n-- Deals created per day in the last 7 days\nSELECT toDate(timestamp) AS day, count() AS created\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>'\nAND entity_type = 'deal'\nAND type = 'clarify:create'\nAND timestamp >= now() - INTERVAL 7 DAY\nGROUP BY day\nORDER BY day\n</example>\n\n<example>\n-- Stage changes for a single deal (only the events where the stage actually\n-- changed — a non-empty stage alone is not a change, since every event repeats\n-- all fields). `diff` lists the fields an update changed, so keep the events\n-- whose diff touched `stage`; the matching entry carries the old→new value.\nSELECT\ntimestamp,\nm_stage AS stage,\narrayFirst(d -> JSONExtractString(d, 'path', 1) = 'stage',\n JSONExtractArrayRaw(diff)) AS stage_change,\nJSONExtractString(stage_change, 'oldVal') AS from_stage,\nJSONExtractString(stage_change, 'val') AS to_stage,\nactor._id AS actor_id\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>'\nAND entity_type = 'deal'\nAND entity_id = '<deal-id>'\nAND type = 'clarify:update'\nAND arrayExists(d -> JSONExtractString(d, 'path', 1) = 'stage',\n JSONExtractArrayRaw(diff))\nORDER BY timestamp\n</example>\n\n<example>\n-- Stage-change events per day across all deals. `diff` records the fields each\n-- update changed, so a stage change = an update whose diff touched `stage`. No\n-- window function and no boundary caveat: each event is self-contained, so the\n-- timestamp range is exact.\nSELECT toDate(timestamp) AS day, count() AS stage_changes\nFROM analytics.event\nWHERE workspace_slug = '<your workspace>'\nAND entity_type = 'deal'\nAND type = 'clarify:update'\nAND arrayExists(d -> JSONExtractString(d, 'path', 1) = 'stage',\n JSONExtractArrayRaw(diff))\nAND timestamp >= now() - INTERVAL 90 DAY\nGROUP BY day\nORDER BY day\n</example>"
152096
+ },
152097
+ {
152098
+ "slug": "CLARIFY_MCP_QUERY_DATA",
152099
+ "name": "Query-data",
152100
+ "description": "Execute PostgreSQL queries to retrieve data from Clarify.\n\n## When to use this tool\n- Counting records (e.g., \"How many deals are open?\")\n- Aggregations (SUM, AVG, COUNT, MAX, MIN, GROUP BY)\n- List queries (e.g., \"Show me 50 recent meetings\")\n- Filtering by timestamps (e.g., deals created in Q4, meetings last week)\n- Searching/filtering large datasets (e.g., \"Show all deals from Q4\" or \"Find records updated this week\")\n\n## For detailed record context, use get-records\nAfter finding record IDs with this tool, use get-records for:\n- Full record details, relationships, and AI summaries\n- Meeting recording transcripts with speaker attribution\n- Email content, subject, body, and participants\n- Example: query-data to find IDs, then get-records to read details\n\n## When not to use this tool\n\nThis tool queries existing CRM records. When users want to find new companies or people to add to the CRM (leads/prospects), search for the lead finder tools instead.\n\n- Do not use this tool when the user mentions \"leads\" or \"prospects\" and wants to source new contacts (e.g., by industry, location, employee count, job title).\n Search for the lead finder tools that query the lead database instead.\n- Still use this tool when the user mentions \"leads\" or \"prospects\" but the context clearly refers to existing CRM records (e.g., \"leads in my pipeline\", \"prospects with last product activity in last 30 days\").\n Activity history, emails, meetings, and pipeline stages only exist for CRM records, not in the lead database. But the user is still asking about leads/prospects, so we still use this tool.\n- Ask the user to clarify when they search for companies or people without using the word \"lead\" or \"prospect\", and the conversation does not already establish a CRM context.\n Ask whether they want to find new leads/prospects to add to the CRM, or look up existing companies/people already in the CRM.\n If the conversation already establishes CRM context, use this tool without asking.\n\n## Before writing SQL\n- This tool does not include any schema. Workspaces have custom fields and JSONB columns that vary per workspace, so you cannot know the column names without loading the schema first. Always call get-schema with format \"read\" and the entities you need before writing SQL, unless the schema for those entities was already returned by get-schema earlier in this conversation.\n- Call get-current-user if the query involves \"me\", \"my\", or \"I\", if the tool is available\n- Always prefix columns with table names (e.g., `person.name`, not `name`)\n- Use ILIKE for case-insensitive matching (not LIKE)\n- Query timestamps using UTC/ISO 8601 format (e.g., '2025-12-22T00:00:00Z')\n- Results will have timestamps formatted in the user's timezone for readability\n- For many-to-many relationships, use INNER JOIN with join tables\n\n## Working with JSONB Columns\n\nMany columns store data as JSONB objects. Check the schema returned by get-schema to identify JSONB columns. Only use JSONB operators (->, ->>) on columns explicitly marked as \"JSONB with format\" in the schema.\n\n### JSONB Access Operators\n- `->` - Extract JSON object (returns JSONB): `column->'key'`\n- `->>` - Extract text value (returns TEXT): `column->>'key'`\n- `jsonb_array_elements(column->'items')` - Iterate over JSONB arrays\n\n### JSONB Column Patterns\n\nObject with nested fields (e.g., `JSONB with format {first_name: string, last_name: string}`):\n- Access nested field: `column->>'first_name'`\n- Concatenate fields: `CONCAT(column->>'first_name', ' ', column->>'last_name')`\n- Filter: `column->>'first_name' ILIKE '%john%'`\n\nArray of items (e.g., `JSONB with format {items: string[]}`):\n- Get first item: `column->'items'->>0`\n- Iterate items: `jsonb_array_elements(column->'items') as item`\n- Access nested in item: `(item->>'email')`\n\n### Filtering multi-select and label arrays\nFor columns with format `{items: string[]}` (multi-select enums, the built-in `labels` field, etc.), filter membership with the array-overlap operator `?|`:\n- Has any of: `(person.labels -> 'items') ?| ARRAY['BDR Prospect', 'ICP']`\nDo not use the `@>` containment operator or `CONTAINS`. `@>` works in the database, but a list built with it cannot be rendered or edited in the list UI; always use the `?|` pattern above.\n\n### Checking if JSONB collection fields are empty\nFor columns with format `{items: string[]}` (multi-select enums, email addresses, etc.), an empty field can be either NULL or `{\"items\": []}`. Always check for both:\n- Is empty: `(column IS NULL OR (column->'items') = '[]'::JSONB)`\n- Is not empty: `(column IS NOT NULL AND (column->'items') <> '[]'::JSONB)`\nDo not use only `IS NULL` or `IS NOT NULL` for these fields; that misses records with empty arrays.\n\n## Time-Based Queries\n\nUse the current time from `get-current-user` tool or system context as reference.\n\n### \"Last\" vs \"Next\" Terminology\n- \"last meeting\" = Most recent past meeting: `WHERE meeting.start < NOW() ORDER BY meeting.start DESC LIMIT 1`\n- \"next meeting\" = Soonest future meeting: `WHERE meeting.start > NOW() ORDER BY meeting.start ASC LIMIT 1`\n- \"recent meetings\" = Meetings in the past, not upcoming ones\n- \"upcoming meetings\" = Meetings in the future\n\n### Time Period Interpretation\nWhen user mentions \"Q4 2025\", \"last quarter\", or similar:\n- Activity in that period: Filter by date: `WHERE meeting.start >= '2025-10-01' AND meeting.start < '2026-01-01'`\n- Content mentioning that period (e.g., \"meetings where Q4 was discussed\"): Search transcripts/summaries, not date filter\n\n## User-Scoped Queries\n\nWhen querying data related to \"me\", \"my\", or \"I\":\n- Use the current user's ID to filter records\n- Remember: `user` and `person` are different tables - `user` = internal workspace members, `person` = external contacts\n- For meetings: `INNER JOIN user_meeting ON meeting._id = user_meeting.meeting_id WHERE user_meeting.user_id = '<user-id>'`\n - External meetings have attendees who are not workspace users. Check `person_meeting` but exclude persons whose email matches a user: `EXISTS (SELECT 1 FROM person_meeting pm JOIN person p ON p._id = pm.person_id WHERE pm.meeting_id = meeting._id AND NOT EXISTS (SELECT 1 FROM \"user\" u WHERE u.email IN (SELECT jsonb_array_elements_text(p.email_addresses->'items'))))`\n - Internal meetings have no truly external attendees (inverse of above)\n- For tasks: Filter by `assignee_id`: `WHERE task.assignee_id = '<user-id>'`\n- For deals: Filter by `owner_id`: `WHERE deal.owner_id = '<user-id>'`\n\n## Deal Analytics\n\n### Comparison operators for thresholds\nWhen users reference a threshold amount:\n- \"above $300\", \"over $300\", \"at least $300\": `deal.amount >= 300`\n- \"below $500\", \"under $500\": `deal.amount < 500`\n- \"more than $300\", \"fewer than 5\": use strict comparison (`>` / `<`)\n\n### Time-bounded deal metrics\nWhen users ask about deals in a specific time period (e.g., \"January deals\", \"Q4 closed deals\", \"deals closed this month\"), always filter by `close_date` within that period in addition to any stage filter. Do not filter only by stage -- that returns all historically closed deals, not deals closed in the requested period. Only add a closed stage filter when the user is asking about closed or won deals specifically. Do not add a closed stage filter for queries about open or in-progress deals.\n- Example: \"deals closed in January 2026\" requires `deal.stage IN (<closed stages from schema>) AND deal.close_date >= '2026-01-01' AND deal.close_date < '2026-02-01'`\n- Example: \"deals expected to close in Q1\" should only filter by `close_date` without a closed stage constraint\n\n## Association Queries\n\nWhen finding emails or meetings \"related to\" a company or entity, join through the relationship graph instead of searching message body text.\n\n- Emails related to a company: JOIN person_message with person WHERE person.company_id = <company_id>. Do not use raw_body ILIKE '%company name%' -- body text matching picks up incidental mentions and links unrelated contacts.\n- Meetings related to a company: JOIN person_meeting with person WHERE person.company_id = <company_id>.\n- Emails for a specific person: JOIN person_message WHERE person_message.person_id = <person_id>.\n- Only use body/subject text search when the user explicitly asks to search email content (e.g., \"find emails mentioning Project X\").\n\n## Activity Counting\n\nActivity includes: meetings, messages, tasks, and comments. To count activity:\n\n- Comments: Query `comment` table with `entity = '<entity-type>'` and `owner_id = <entity>._id`. Use `_created_at` as timestamp.\n- Meetings: Join through `person_meeting` join table. If entity relates to `person` via join table (e.g., `person_deal`) or foreign key (e.g., `person.company_id`), join: entity → person → `person_meeting` → `meeting`. Use `meeting.start` as timestamp.\n- Messages: Join through `person_message` join table. Same pattern as meetings: entity → person → `person_message` → `message`. Use `message.received_at` as timestamp.\n- Tasks: Join via foreign key `task.deal_id`. For deals: direct join. For companies: join `deal` first (via `deal.company_id`), then `task`. Use `task._created_at` as timestamp.\n\nPattern: Create CTEs for each activity type, UNION ALL them, then LEFT JOIN to your entity table. Use COUNT() and MAX() for totals and last activity date.\n\n## Comments\n\nComments are notes left on records. The comment table has no schema in get-schema: use these columns directly:\n- `_id`: UUID primary key\n- `entity`: parent entity type (e.g., 'company', 'deal', 'person', 'meeting', 'task')\n- `owner_id`: parent record ID\n- `message`: JSONB rich text; use `message::text` for raw content\n- `_created_by`: user ID of the comment author. JOIN with `\"user\"` on `_created_by = \"user\"._id` for author name\n- `_created_at`: timestamp\n\n## Existence Checking\n\nBefore creating a record, search broadly by name to check if it already exists. Duplicate records with the same name but different IDs are common.\n\n- Use ILIKE name matching: WHERE deal.name ILIKE '%Snowplow%' or WHERE company.name ILIKE '%Snowplow%'. Do not rely solely on a single foreign key (e.g., WHERE deal.company_id = '<id>') -- this misses records linked to duplicate/variant company records.\n- When checking for existing deals, search by both the deal name and the related company name.\n\n## Name search strategies\n\nWhen a name search returns no results, try variations before asking the user to clarify. Records are often stored differently than expected (e.g., \"BrightLoop\" vs \"Bright Loop\"):\n\n- Remove spaces: `ILIKE '%brightloop%'`\n- Search individual keywords: `name ILIKE '%bright%' OR name ILIKE '%loop%'`\n- For a person's first name, also try common nickname/diminutive variants (e.g. Tim/Timothy, Bob/Robert, Liz/Elizabeth, Bill/William, Mike/Michael) and a prefix match (`name->>'first_name' ILIKE 'Tim%'`) before concluding no match exists\n- If a broad search returns many results, pick the closest match rather than asking the user to choose\n\nBefore matching a name column with ILIKE, check its type in the get-schema output. A name stored as a JSONB object (shown as `JSONB with format {...}`) is not text: a bare `name ILIKE` on it fails with `operator does not exist: jsonb ~~*`. This is common for the display name on people-type entities (for example a person or workspace user whose name is `{first_name, last_name}`). Extract the text first, e.g. `name->>'first_name' ILIKE '%...%'` or `CONCAT(name->>'first_name', ' ', name->>'last_name') ILIKE '%...%'` (see \"Working with JSONB Columns\" above). Only columns the schema marks scalar (e.g. a plain `string` email) work with a direct ILIKE.\n\n## Meetings\n\nMeetings are personal data, like emails: a meeting belongs to its participants\n(the users with a `user_meeting` row), not to the whole workspace. Meeting\ncontent can be sensitive, so scope meeting queries to the current user by default.\n\n- Default: return only the current user's own meetings by INNER JOINing\n `user_meeting` (see User-Scoped Queries for the exact join). This applies to\n bare requests with no other anchor -- \"today's meetings\", \"recent meetings\", a\n daily/EOD digest -- exactly as you filter emails to the current user.\n- Only query across all users' meetings when the user explicitly asks for the\n team's or workspace's meetings.\n- Meetings anchored to a specific company, person, or deal are the exception:\n join through `person_meeting` (see Association Queries) instead of\n `user_meeting`.\n\n## Meeting Recordings & Transcripts\n\nMeeting recordings are linked to meetings via meeting_recording.meeting_id.\nThe meeting_recording table is queryable via SQL (use entity=meeting for the query):\n- Find recordings: SELECT meeting_recording._id FROM meeting_recording WHERE meeting_recording.meeting_id = '<meeting-id>'\n- Read transcript: use get-records with entity=meeting_recording and the recording IDs\n\nA meeting can have multiple recordings. To avoid duplicate rows, filter with an\nEXISTS subquery instead of JOINing meeting_recording directly:\nSELECT meeting._id, meeting.title FROM meeting WHERE EXISTS (SELECT 1 FROM meeting_recording WHERE meeting_recording.meeting_id = meeting._id)\n\nWhen listing or showing meetings (e.g., \"show me my last 5 recorded meetings\"):\n- Always include summary and/or notes in the SELECT columns, not just metadata (title, date, status)\n- Present the summary content inline so the user sees what each meeting was about\n- If summaries are available, offer to show full transcripts for any specific meeting\n\nWhen answering questions about a single meeting (summary, follow-up email, action items):\n- Check for recordings and read the transcript via get-records before responding\n\nWhen answering questions across multiple meetings:\n- Prefer using the summary and notes fields first (available on the meeting record)\n- Only read individual transcripts if the user explicitly asks or summaries are insufficient\n\nMeeting content fields:\n- \"summary\": AI-generated meeting summary (on meeting record)\n- \"notes\": User-written meeting notes (on meeting record, separate from summary)\n- If summary is null, check notes before concluding the meeting has no content\n\nA substring match inside a summary is not evidence that a topic was requested or\ndiscussed. Summaries often enumerate ABSENT topics (\"No mention of dialers,\nenrichment, or reporting tools\"), so an ILIKE '%dialer%' hit can be a negation.\nBefore attributing a request or interest to a person or meeting from a summary\nmatch, read the matching summary text and confirm the term appears in an\naffirmative context. Do not count a negated mention as a positive signal, and\ndo not report a corrected count as fact until you have re-read the source.\n\n## Emails & Messages\n\nThe message table contains sent and received emails. Use entity=message to query directly.\nSensitive columns (raw_body, subject) are protected by database-level RLS; only messages\nthe current user has access to will return content. Use get-records with entity=message for full\nformatted email content with participant details.\nFilter by user_id for the current user's emails, received_at for time ranges, and person_message join for specific contacts.\nNever claim you cannot access emails -- sent and received emails are queryable. Unsent drafts are not.\n\n## Pagination\n- When user asks for \"more\" results, use the EXACT same SQL query and only change the offset parameter\n- The tool will tell you the next offset value to use (e.g., \"Call this tool again with offset=25 to continue\")\n\n## Data Limitations\n\nTables contain current field values only. You cannot determine what a field's value was at a past date with this tool.\n\nWhat you can answer:\n- Deals currently in stage X: `WHERE deal.stage = 'In progress'`\n- Deals created/updated in a period: `WHERE deal._created_at >= '2025-10-01'`\n- Deals closed in a period: `WHERE deal.stage IN (<closed stages from schema>) AND deal.close_date >= '2025-10-01' AND deal.close_date < '2025-11-01'` (see \"Time-bounded deal metrics\" above)\n\nWhat requires the query-analytics tool instead:\n- \"How many deals were in stage X on December 1st?\" (requires historical snapshots)\n- \"What was the pipeline value entering Q4?\" (requires reconstructing past state)\n- \"Which deals changed stage last month?\" (requires stage transition history)\n\nFor historical or point-in-time questions like these (past field values, stage transitions, change history, trends over time), use the query-analytics tool. It queries the analytics event log of every CRM change and can reconstruct past state."
152101
+ },
152102
+ {
152103
+ "slug": "CLARIFY_MCP_READ_CONTEXT",
152104
+ "name": "Read-context",
152105
+ "description": "Read Clarify product knowledge and documentation.\n\nUse this whenever you need to understand a feature, apply best practices, or reference detailed technical documentation.\n\nAvailable contexts:\n- field-docs: Field type guidelines, AI prompt writing instructions, available relationship data, and examples for creating or updating custom fields\n- calendar-docs: Guide for the calendar tools: timezone handling, timed vs all-day events, resolving participants by name via CRM lookup, participant rules (always include the user), choosing which connected account a create lands on (other writes follow the event owner), update-replaces-not-merges semantics, recurrence (RRULE), notify_participants defaults, and event-ID conventions.\n- campaign-docs: Complete guide to email campaigns including structure, variables, enrollment, exit conditions, and best practices\n- artifact-docs: The required data rules for authoring an artifact: which store its SQL runs on, how to prove a query, and how to size a result for the frame, plus what makes a dashboard, QBR, or sales document effective. Read before you write SQL for a dashboard, report, or artifact."
152106
+ },
152107
+ {
152108
+ "slug": "CLARIFY_MCP_RESPOND_TO_CALENDAR_EVENT",
152109
+ "name": "Respond-to-calendar-event",
152110
+ "description": "RSVP to a calendar event you've been invited to.\n\n## When to use this tool\n\nUse to accept, decline, or tentatively accept a meeting invite. The user must\nbe a participant on the event.\n\n## Important notes\n\n- The RSVP sends as soon as this tool is called, with no confirmation step. Confirm with the user first.\n- Status values: `yes` (accept), `no` (decline), `maybe` (tentative)."
152111
+ },
152112
+ {
152113
+ "slug": "CLARIFY_MCP_RUN_WORKFLOW",
152114
+ "name": "Run-workflow",
152115
+ "description": "Start a workflow run. Three modes are supported, picked by which input is set:\n\n1. **Replay**: pass `workflow_run_id`: copies the trigger state of a completed\n run and re-executes the action blocks against the current workflow definition.\n2. **Run on a record**: pass `record` ({ entity, id }): for workflows whose\n trigger is an entity CDC event (e.g. on-create-person). The record is fetched\n and shaped into a synthetic trigger event so downstream blocks see the same\n `{{trigger.state.event.object.*}}` surface as a real run.\n3. **Run from a raw event**: pass `trigger_event`: a JSON object passed through\n to the manual-run service. For webhook-triggered workflows, the value is\n wrapped as `{ type: 'clarify-webhook:automation-webhook', data: { body, headers: {} } }`\n automatically.\n\nExactly one of `workflow_run_id`, `record`, or `trigger_event` must be set.\n\n## When to use this tool\n\n- The user is iterating on a workflow and wants to test it against a specific\n record, a sample payload, or a previously completed run\n- After editing a workflow with create-or-update-workflow to fix a\n failing run, immediately call this tool to verify the fix\n\n## How it works\n\n- For modes 2 and 3, the workflow must be published (`published_at` not null)\n and of type `workflow`; sequences and system workflows have their own paths\n- For mode 1, the source run must be in a terminal state (success, failed,\n cancelled)\n- This produces real side effects (e.g. sends emails, updates records); there\n is no sandbox\n- Waits up to 30 seconds for the new run to finish; emits an artifact so the\n user can open the run page either way\n\n## Returns\n\n- The new run ID and its terminal status (success / failed / cancelled), waiting\n up to 30 seconds\n- On failure: the failing block's recent logs are included inline; read them\n before deciding the next edit\n- For longer-running workflows, returns the still-active status with a hint to\n poll get-workflow-runs\n\n## Important notes\n\n- Limit fix-and-rerun loops to 5 attempts on the same workflow in one\n conversation. After 5 unsuccessful runs, stop and post the latest failure log\n to the user; further guessing is unlikely to help\n- To find an existing run ID for the replay mode, call\n get-workflow-runs first"
152116
+ },
152117
+ {
152118
+ "slug": "CLARIFY_MCP_SEND_EMAIL",
152119
+ "name": "Send-email",
152120
+ "description": "Send an email immediately through the user's connected email account.\n\n## When to use this tool\n\nUse this tool when the user wants to send an email right now, without reviewing or editing it first. For example: \"send John an email about the meeting\" or \"email the team about the deadline\".\n\nIf the user wants to review, edit, or compose an email before sending, use the create-email-draft tool instead.\n\n## How it works\n\n1. The email is sent through the user's connected Gmail or Outlook account\n2. The email sends as soon as this tool is called, with no confirmation step. Confirm with the user first\n3. On success the email appears in their Sent folder\n\n## Threading\n\nWhen the user asks you to reply to an existing email or thread, populate replyToMessageId so the sent message threads correctly in Gmail/Outlook. Look up the value from the message_id field on a Message record (use get-records or query-data on the Message entity to find the inbound message you are replying to). Omit replyToMessageId when sending a brand new email that is not part of an existing thread.\n\n## Body format\n\nThe body is plain text that will be converted to rich text. Use these conventions:\n- Lines starting with \"- \" become bullet list items\n- Lines starting with \"1. \", \"2. \", etc. become numbered list items\n- Blank lines become paragraph breaks (consecutive blank lines are collapsed)\n- Lines starting with \"# \" or \"## \" become bold section labels\n- **bold** spans become bold text\n- Markdown links [label](https://example.com) and bare URLs become clickable links\n- Never put a placeholder or fabricated link in the body (e.g. [Recording] *(link)*, [link], or a guessed URL). Include a link only if you have the real URL from a tool result; if a referenced resource has no link available, leave it out and say in your reply that it needs to be added\n- Markdown horizontal rules like \"---\" are treated as section dividers and are not shown\n- Everything else becomes a regular paragraph\n\nFollow the system prompt and any activated email-writing skill for the user's\npreferred voice, tone, structure, and formatting judgment. If a skill gives\nmore specific email-writing guidance that conflicts with these generic style\ndefaults, prefer the skill. If no more specific guidance applies, write like a\nnormal email, not a dashboard or report. Keep bodies compact and easy to scan:\n- Prefer short paragraphs and a small number of bullets\n- Use section labels only when they materially improve scanability\n- Use at most one blank line between sections or paragraphs\n- Keep section labels attached to their content; do not add a blank line immediately after a section label\n- Keep lists attached to the sentence or item they explain; do not add a blank line immediately before a bullet or numbered list\n- Avoid em dashes and dash-heavy constructions; use commas, colons, parentheses, or separate sentences instead\n- Do not use decorative separators, tables, code fences, blockquotes, or report-style spacing\n\n## Recipients\n\nRecipient addresses (to/cc/bcc) must come from a CRM person record. Look them up with get-records or by querying the person entity before sending; never guess an address from a name and company domain. Any recipient that matches no person record is rejected unless you pass it in confirmedNewRecipients (only for addresses the user supplied for a brand-new contact).\n\n## Important notes\n\n- The user must have a connected email account (Gmail or Outlook via Nylas)\n- On success, tell the user the email was sent and to whom. If the tool reports an error, tell the user it could not be sent and why; never claim an email was sent when the tool returned an error"
152121
+ },
152122
+ {
152123
+ "slug": "CLARIFY_MCP_SUBMIT_FEEDBACK",
152124
+ "name": "Submit-feedback",
152125
+ "description": "Submit concise feature requests or feedback about MCP tools. Use when:\n- Missing functionality prevents completing a user's request\n- User requests a new feature or reports a limitation\n- User suggests improvements\n\nKeep feedback brief and focused on what's needed or what could be improved."
152126
+ },
152127
+ {
152128
+ "slug": "CLARIFY_MCP_UPDATE_CAMPAIGN",
152129
+ "name": "Update-campaign",
152130
+ "description": "Update an existing email campaign: rename it, change its target list, adjust the\nsender, edit its email steps, or configure send time windows. To create a new\ncampaign, use the create-campaign tool instead.\n\nRequires a `campaign_id` (get it from the `get-campaigns` tool).\n\n📖 **For comprehensive campaign rules and examples**: Use `read-context` with context: \"campaign-docs\"\n\n## When to use this tool\n\n- When the user asks to rename a campaign, change its target list, adjust the sender, or edit email steps (subjects, bodies, timing)\n- When the user asks to configure when a campaign's emails can be sent (send time windows)\n\n## Editing email steps\n\nEach email_step must specify an operation:\n- **update**: Modify an existing step (requires step_number, optional: subject, body)\n- **remove**: Delete a step (requires step_number)\n- **insert**: Add a new step (requires step_number, subject, body, delay_after_days)\n\nTo append at the end, use step_number equal to the current number of steps + 1.\n\nA **update** with `body` **replaces the entire body of that step**. To add to\nor tweak part of an existing email, first read the current body with\n`get-campaigns`, apply your change to it, and send the full\nupdated body. Never regenerate a body from scratch for a targeted edit, or you\nwill discard the user's existing content. If you cannot make a requested change\nwithout replacing content the user wrote, confirm with them first.\n\nCampaign email bodies support text and images. Tables, videos, and other\nembedded content are not supported and are silently dropped. Do not attempt to\ninsert those; tell the user they aren't supported yet. An image must be an\n<img src=\"...\"> pointing at an already-hosted public URL. A plain link to a\nfile (for example a PDF URL) is fine.\n\n## Essential rules\n\n1. **Email/Delay Pattern**: Emails and delays MUST alternate. When inserting an email, always specify `delay_after_days`\n2. **First email**: `delay_after_days: 0`. Subsequent emails: minimum 1 day\n3. **Campaigns are Workflows**: Use this tool for campaigns, not generic workflow tools\n4. Campaign emails are templates sent to multiple people\n5. Use variable placeholders: {{path||fallback}} with fallback, or {{path}} without fallback\n6. Only use the variables listed below (do not invent variables)\n7. Campaigns that have already been sent cannot be modified\n\n## Threading: send_as_reply\n\nSet `send_as_reply: true` on a step to thread it as a reply under the previous\nstep (uses the prior message id and \"Re: <previous subject>\"). Use it when a\nfollow-up bumps the prior email and the recipient should see it inline:\n\n- **Use** `send_as_reply: true` for content like \"circling back\", \"just bumping\n this\", \"wanted to follow up\", or any step that explicitly references the\n prior email's call to action without a new pitch.\n- **Leave it off (default)** when the step introduces a new angle, case study,\n or call to action; recipients triage by subject, and a fresh subject signals\n fresh content.\n\nRules:\n- Step 1 always starts a new thread (`send_as_reply` must be false / omitted).\n- When `send_as_reply: true`, the step's `subject` is ignored at send time\n (the previous step's subject is reused with \"Re: \" prepended), but you must\n still provide a sensible `subject` for storage.\n\nFallback rules (fallbacks make emails feel natural when data is missing):\n- ALWAYS include fallbacks for human-identifiable information:\n→ Person names (first_name, last_name, full_name) → use \"there\", \"Friend\", etc.\n→ Company/organization names → use \"your company\", \"your organization\", \"your team\"\n→ Job titles and roles → use \"your role\", etc.\n→ Location/city names → use \"your area\", \"your region\", etc.\n- Skip fallbacks ONLY for technical/structured data:\n→ URLs, email addresses, phone numbers\n→ Dates, timestamps, IDs\n→ Numerical values and metrics\n\n## Examples\n\n<example>\nUpdate a campaign step:\n{\n \"campaign_id\": \"abc-123-def\",\n \"email_steps\": [\n {\n \"operation\": \"update\",\n \"step_number\": 2,\n \"subject\": \"Quick follow-up, {{person.name.first_name||there}}\"\n }\n ]\n}\n</example>\n\n<example>\nInsert a new step:\n{\n \"campaign_id\": \"abc-123-def\",\n \"email_steps\": [\n {\n \"operation\": \"insert\",\n \"step_number\": 2,\n \"subject\": \"Quick check-in\",\n \"body\": \"<p>Hi {{person.name.first_name||there}},</p><p>Just wanted to follow up...</p>\",\n \"delay_after_days\": 3\n }\n ]\n}\n</example>\n\n## Send Time Windows\n\nUse `send_windows` to control when campaign emails can be sent. Emails scheduled\noutside the configured windows are held until the next open window in the\ncreator's timezone.\n\n- Pass `null` to disable windows (emails can be sent at any time).\n- Pass a `{ windows: { <day>: { start, end } | null } }` object to set windows.\n Days map to lowercase names: `sunday`, `monday`, `tuesday`, `wednesday`,\n `thursday`, `friday`, `saturday`. A `null` value for a day means no sending\n that day. `start` and `end` are 24-hour `\"HH:mm\"` strings with `start < end`\n (same-day windows only).\n- Omit `send_windows` entirely to leave existing windows unchanged.\n\n<example>\nSet business-hours-only send windows:\n{\n \"campaign_id\": \"abc-123-def\",\n \"send_windows\": {\n \"windows\": {\n \"sunday\": null,\n \"monday\": { \"start\": \"09:00\", \"end\": \"17:00\" },\n \"tuesday\": { \"start\": \"09:00\", \"end\": \"17:00\" },\n \"wednesday\": { \"start\": \"09:00\", \"end\": \"17:00\" },\n \"thursday\": { \"start\": \"09:00\", \"end\": \"17:00\" },\n \"friday\": { \"start\": \"09:00\", \"end\": \"17:00\" },\n \"saturday\": null\n }\n }\n}\n</example>\n\n## Important notes\n\n- delay_after_days: 0 = immediate, 3 = day 3, 7 = day 7\n- Minimum 1 day enforced between consecutive emails automatically\n- Body should be formatted as HTML. Put each paragraph in its own <p> tag; paragraphs render with a blank line between them. Use <br/> only for a hard line break within a paragraph (e.g. between signature lines)\n- When describing timing to users, say \"immediately\" for delay_after_days = 0, \"on day 3\" for delay_after_days = 3\n- Use get-campaigns tool to find campaign IDs for updates"
152131
+ }
152132
+ ],
152133
+ "triggers": [],
152134
+ "authConfigDetails": [
152135
+ {
152136
+ "mode": "DCR_OAUTH",
152137
+ "name": "clarify_mcp_DCR_OAuth",
152138
+ "fields": {
152139
+ "auth_config_creation": {
152140
+ "required": [],
152141
+ "optional": [
152142
+ {
152143
+ "name": "client_id",
152144
+ "displayName": "Client id",
152145
+ "type": "string",
152146
+ "description": "Client id of the app",
152147
+ "required": false,
152148
+ "default": null
152149
+ },
152150
+ {
152151
+ "name": "client_secret",
152152
+ "displayName": "Client secret",
152153
+ "type": "string",
152154
+ "description": "Client secret of the app",
152155
+ "required": false,
152156
+ "default": null
152157
+ },
152158
+ {
152159
+ "name": "oauth_redirect_uri",
152160
+ "displayName": "Redirect URI",
152161
+ "type": "string",
152162
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
152163
+ "required": false,
152164
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
152165
+ },
152166
+ {
152167
+ "name": "scopes",
152168
+ "displayName": "Scopes",
152169
+ "type": "string",
152170
+ "description": "Scopes to request from the user, comma separated",
152171
+ "required": false,
152172
+ "default": "email,offline_access,openid,profile"
152173
+ }
152174
+ ]
152175
+ },
152176
+ "connected_account_initiation": {
152177
+ "required": [],
152178
+ "optional": []
152179
+ }
152180
+ }
152181
+ }
152182
+ ]
152183
+ },
152184
{
152185
"slug": "clarity_ai_mcp",
152186
"name": "Clarity AI MCP",
152432
}
152433
]
152434
},
152435
+ {
152436
+ "slug": "clay_mcp",
152437
+ "name": "Clay MCP",
152438
+ "logo": "https://logos.composio.dev/api/clay_mcp",
152439
+ "description": "Clay MCP lets agents research companies and contacts, run enrichment providers and Clay functions, and return enriched prospect data for authorized workspaces.",
152440
+ "category": "model context protocol",
152441
+ "authSchemes": [
152442
+ "DCR_OAUTH"
152443
+ ],
152444
+ "toolCount": 17,
152445
+ "triggerCount": 0,
152446
+ "version": "20260902_00",
152447
+ "tools": [
152448
+ {
152449
+ "slug": "CLAY_MCP_ADD_COMPANY_DATA_POINTS",
152450
+ "name": "Add-company-data-points",
152451
+ "description": "Add data points to companies in an existing search. Supports enriching ALL companies or specific companies via entityIds.\n\n## Quick Reference\n- **This tool**: Enrich COMPANIES with funding, tech stack, headcount, etc.\n- **add-contact-data-points**: Enrich CONTACTS with emails, work history, etc.\n- Requires a taskId from a previous find-and-enrich-* tool call\n- **Use entityIds to enrich specific companies** — do NOT create a new search to enrich one company from an existing search\n- **ANY research question about companies = call this tool** with a Custom data point\n\n## IMPORTANT: When to Call This Tool\n**Check before enriching:** If the user asks about a specific company's data (e.g. \"what's their tech stack?\"), call get-task-context FIRST — the user may have already enriched it through the widget. Only call this tool if get-task-context shows the enrichment hasn't been run.\n\nCall this tool whenever the user asks to FETCH or ADD new information about companies, including:\n- Standard data points (tech stack, funding, headcount, etc.)\n- **Any open-ended research question** — use Custom type for these\n\nDo NOT try to answer company research questions from your own knowledge. ALWAYS call this tool or get-task-context to fetch the data.\n\nExamples that MUST trigger this tool:\n- \"What's their tech stack?\" → Standard type\n- \"Find recent product announcements\" → Custom type\n- \"Get me their latest news\" → Custom type\n- \"What's their revenue model?\" → Custom type\n- \"Find their competitors\" → Custom type\n- \"Any recent acquisitions?\" → Custom type\n\n## Parameters\n\n### taskId (required)\nThe task ID returned from find-and-enrich-company, find-and-enrich-contacts-at-company, or find-and-enrich-list-of-contacts.\n- Do NOT fabricate a taskId—use the one from the prior search\n- If no search exists yet, prompt the user to search first\n\n### dataPoints (required)\nArray of data points to add.\n- Standard: { type: \"<DataPointType>\" }\n- Custom: { type: \"Custom\", customDataPoint: \"<brief description>\" }\n\n**Available standard types:** Headcount Growth, Recent News, Investors, Company Competitors, Company Customers, Tech Stack, Website Traffic, Open Jobs, Revenue Model, Annual Revenue, Latest Funding\n\n**Custom type**: Use for ANY research question not covered by standard types. Examples:\n- \"recent product announcements\" → { type: \"Custom\", customDataPoint: \"recent product announcements\" }\n- \"B2B vs B2C classification\" → { type: \"Custom\", customDataPoint: \"B2B vs B2C classification\" }\n- \"company founders\" → { type: \"Custom\", customDataPoint: \"company founders\" }\n\n### entityIds (optional)\nArray of entityIds to enrich. When omitted, enriches all companies in the search.\n- Use the entityId values from the company data returned by a previous search tool call\n- Useful when the user wants to enrich specific companies\n\n## Examples\n\n| User request | dataPoints |\n|--------------|------------|\n| \"What's their tech stack?\" | [{ type: \"Tech Stack\" }] |\n| \"Get funding info and headcount\" | [{ type: \"Latest Funding\" }, { type: \"Headcount\" }] |\n| \"Find recent product announcements\" | [{ type: \"Custom\", customDataPoint: \"recent product announcements\" }] |\n| \"Are they B2B or B2C?\" | [{ type: \"Custom\", customDataPoint: \"B2B vs B2C classification\" }] |\n| \"What's in the news about them?\" | [{ type: \"Custom\", customDataPoint: \"recent news and headlines\" }] |\n\n## Response Behavior\n\n- Confirm briefly: \"Fetching [data point] for [company/companies].\"\n- For single-company requests, name the company instead of saying \"all companies.\"\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task."
152452
+ },
152453
+ {
152454
+ "slug": "CLAY_MCP_ADD_CONTACT_DATA_POINTS",
152455
+ "name": "Add-contact-data-points",
152456
+ "description": "Add data points to contacts in an existing search. Supports enriching ALL contacts or specific contacts via entityIds.\n\n## Quick Reference\n- **This tool**: Enrich CONTACTS with emails, work history, etc.\n- **add-company-data-points**: Enrich COMPANIES with funding, tech stack, headcount, etc.\n- Requires a taskId from a previous find-and-enrich-* tool call\n- **Use entityIds to enrich specific contacts** — do NOT create a new search to enrich one person from an existing search\n- **ANY research question about contacts = call this tool** with a Custom data point\n\n## IMPORTANT: When to Call This Tool\n**Check before enriching:** If the user asks about a specific contact's data (e.g. \"what's Patrick's email?\"), call get-task-context FIRST — the user may have already enriched it through the widget. Only call this tool if get-task-context shows the enrichment hasn't been run.\n\nCall this tool whenever the user asks to FETCH or ADD new information about contacts, including:\n- Standard data points (email, work history, etc.)\n- **Any open-ended research question** — use Custom type for these\n\nDo NOT try to answer contact research questions from your own knowledge. ALWAYS call this tool or get-task-context to fetch the data.\n\nExamples that MUST trigger this tool:\n- \"Get their emails\" → Standard type\n- \"Find their recent publications\" → Custom type\n- \"What have they posted on LinkedIn?\" → Custom type\n- \"Summarize their career trajectory\" → Custom type\n- \"Any recent job changes?\" → Custom type\n- \"Score them against my ICP\" → Custom type\n\n## Parameters\n\n### taskId (required)\nThe task ID returned from find-and-enrich-contacts-at-company or find-and-enrich-list-of-contacts.\n- Do NOT fabricate a taskId—use the one from the prior search\n- If no search exists yet, prompt the user to search first\n\n### dataPoints (required)\nArray of data points to add.\n- Standard: { type: \"<DataPointType>\" }\n- Custom: { type: \"Custom\", customDataPoint: \"<brief description>\" }\n\n**Available standard types:** Email, Summarize Work History, Find Thought Leadership\n\n**Custom type**: Use for ANY research question not covered by standard types. Examples:\n- \"recent publications\" → { type: \"Custom\", customDataPoint: \"recent publications\" }\n- \"LinkedIn activity\" → { type: \"Custom\", customDataPoint: \"recent LinkedIn posts\" }\n- \"ICP fit score\" → { type: \"Custom\", customDataPoint: \"ICP fit score based on seniority and tenure\" }\n\n### entityIds (optional)\nArray of entityIds to enrich. When omitted, enriches all contacts in the search.\n- Use the entityId values from the contact data returned by a previous search tool call\n- Useful when the user wants to enrich specific contacts (e.g., \"get John's email\")\n\n## Examples\n\n| User request | dataPoints |\n|--------------|------------|\n| \"Get their emails\" | [{ type: \"Email\" }] |\n| \"Add work history\" | [{ type: \"Summarize Work History\" }] |\n| \"Find their recent publications\" | [{ type: \"Custom\", customDataPoint: \"recent publications\" }] |\n| \"What's their LinkedIn activity?\" | [{ type: \"Custom\", customDataPoint: \"recent LinkedIn posts\" }] |\n| \"Score them for senior leaders in NYC\" | [{ type: \"Custom\", customDataPoint: \"ICP fit: senior leader in NYC\" }] |\n| \"Get John's email\" (single contact) | [{ type: \"Email\" }] + entityIds: [\"<john's entityId>\"] |\n\n## Response Behavior\n\n- Confirm briefly: \"Fetching [data point] for all contacts.\"\n- For single-contact requests, name the contact instead of saying \"all contacts.\"\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task."
152457
+ },
152458
+ {
152459
+ "slug": "CLAY_MCP_ASK_QUESTION_ABOUT_ACCOUNTS",
152460
+ "name": "Ask-question-about-accounts",
152461
+ "description": "Ask a natural language question about one or more accounts available in Clay Audiences. Depending on your workspace settings and whether Salesforce owner data is available, this may be limited to accounts you own in Salesforce. An AI agent analyzes account data including contacts, opportunities, Gong calls, and emails to answer your question.\n\nIMPORTANT: Both \"accountIds\" and \"question\" parameters are REQUIRED — you must always provide both when calling this tool.\n\n## Quick Reference\n- **This tool**: Ask questions or get analysis about specific accounts (e.g., \"What's the status of this deal?\", \"Who are the key stakeholders?\")\n- **query-objects**: Call this first to get account entity IDs before calling this tool, unless you already have account IDs. Find and list accessible accounts by natural-language filters.\n- **find-and-enrich-company**: Only for prospecting publicly available company info. Do NOT use find-and-enrich-company when the user is asking about their own accounts or deals; use this tool instead.\n- For ambiguous queries (e.g., \"Tell me about Acme\"), call query-objects first. If the account exists, use this tool. If not, fall back to find-and-enrich-company.\n\n## Prerequisites\nYou need the `accountId` (numeric) for each account you want to ask about. If you don't have it:\n1. Call `query-objects` to find accounts by name or other natural-language filters. Use `onlyMine: true` when the user asks about \"my\" accounts or accounts they personally own; omit it when they ask about accounts in general.\n2. Use the returned account `entityId` values as `accountIds`\n\nAccess to specific accounts depends on your workspace settings. Some workspaces allow questions about any account in the audience, while others restrict questions to accounts you own in Salesforce when Salesforce owner data is available.\n\n## Parameters\n\n### accountIds (required — MUST be provided)\nArray of numeric account IDs from returned account `entityId` values in the `query-objects` response. Supports 1-10 accounts.\n- For single-account questions: provide one ID (e.g., [12345])\n- For multi-account questions (e.g., comparisons): provide multiple IDs (e.g., [12345, 67890]). The tool returns individual analyses for each account — you should synthesize and compare the results yourself.\n\n### question (required — MUST be provided)\nA natural language question about the account(s). Be specific for best results.\n\n## Correct Usage\nYou MUST always call this tool with BOTH parameters like this:\n{ \"accountIds\": [12345], \"question\": \"What is the deal status?\" }\n\n## Examples\n\n| User says | How to handle |\n|-----------|---------------|\n| \"What's happening with the Acme deal?\" | 1. Call `query-objects` with query: \"Acme account\" to get the account entityId. 2. Call this tool with that entityId in accountIds and the question. |\n| \"What's happening with my Acme deal?\" | 1. Call `query-objects` with query: \"Acme account\" and onlyMine: true to get the account entityId. 2. If Clay says owner-scoped filtering is unavailable, explain that Clay can still search audience accounts but cannot determine ownership in this workspace. 3. Otherwise call this tool with that entityId in accountIds and the question. |\n| \"Compare my top two accounts\" | 1. Call `query-objects` with query: \"my accounts\" and onlyMine: true to find accounts. 2. If owner-scoped filtering is unavailable, explain that Clay can still analyze audience accounts but cannot determine ownership in this workspace. 3. Otherwise call this tool with both entityIds in accountIds and the question. The tool returns individual analyses per account; synthesize and compare the results yourself. |\n| \"Who are the key contacts at account 12345?\" | Call this tool directly with accountIds: [12345] and question: \"Who are the key contacts?\" (ID already known). |\n\n## Response Behavior\n- Returns a detailed text answer from the AI agent based on each account's data\n- The agent analyzes contacts, opportunities, Gong call transcripts, and emails\n- For multi-account requests, individual analyses are returned per account — you are responsible for comparing or synthesizing the results\n- This tool may take longer than other tools due to the depth of analysis"
152462
+ },
152463
+ {
152464
+ "slug": "CLAY_MCP_FIND_AND_ENRICH_COMPANY",
152465
+ "name": "Find-and-enrich-company",
152466
+ "description": "Find and enrich a single company by domain or LinkedIn URL.\n\n## Quick Reference\n- **This tool**: Prospect and research PUBLICLY AVAILABLE company info (e.g., \"Tell me about Stripe\", \"What's OpenAI's funding?\"). This is for prospecting external data, NOT for querying the user's own account data.\n- **find-and-enrich-contacts-at-company**: Find TYPES of people (e.g., \"engineers at Stripe\")\n- **find-and-enrich-list-of-contacts**: Find SPECIFIC named people (e.g., \"John Smith at Stripe\")\n- **query-objects** + **ask-question-about-accounts**: Ask about the user's OWN accounts, deals, CRM data, or relationships (e.g., \"What's happening with my Acme deal?\", \"How's our relationship with Stripe?\")\n- Do NOT use if user wants to find people; use the contact tools instead\n- Do NOT use if user is asking about their own accounts, deals, opportunities, or CRM data; use query-objects and ask-question-about-accounts instead\n- For ambiguous queries about a company (e.g., \"Tell me about Acme\"), prefer checking query-objects first. Only use this tool if the account is not found or the user is explicitly prospecting.\n\n## Parameters\n\n### companyIdentifier (required)\nDomain (e.g., \"stripe.com\") or LinkedIn company URL. Company names alone will fail.\n- Convert known companies: \"Stripe\" → \"stripe.com\"\n- If ambiguous (e.g., \"Delta\"), ask the user to clarify\n\n### companyDataPoints (optional)\nEnrich the company when creating a NEW search. For existing searches, use add-company-data-points instead.\n\n**⚠️ CRITICAL: NEVER add data points unless the user EXPLICITLY asks for them.**\nEnrichments cost credits. Only include data points when the user's message specifically requests that data.\n- \"Tell me about Stripe\" → NO data points\n- \"What's Stripe's funding?\" → add Latest Funding (user explicitly asked)\n- Do NOT add Headcount Growth, Recent News, or any other data point \"to be helpful\" — only what the user asked for\n\n**DataPoint format:**\n- Standard: { type: \"<DataPointType>\" }\n- Custom: { type: \"Custom\", customDataPoint: \"<brief description>\" }\n\n**Important:** Only include `customDataPoint` field when type is \"Custom\"\n\n**Available companyDataPoints:** Headcount Growth, Recent News, Investors, Company Competitors, Company Customers, Tech Stack, Website Traffic, Open Jobs, Revenue Model, Annual Revenue, Latest Funding\n\n## Examples\n\n| User request | Parameters |\n|--------------|------------|\n| \"Tell me about Stripe\" | companyIdentifier: \"stripe.com\" (NO companyDataPoints — user did not ask for enrichments) |\n| \"What's OpenAI's funding?\" | companyIdentifier: \"openai.com\", companyDataPoints: [{ type: \"Latest Funding\" }] |\n| \"Canva's competitors and tech stack\" | companyIdentifier: \"canva.com\", companyDataPoints: [{ type: \"Company Competitors\" }, { type: \"Tech Stack\" }] |\n| \"Notion's product roadmap\" | companyIdentifier: \"notion.so\", companyDataPoints: [{ type: \"Custom\", customDataPoint: \"product roadmap\" }] |\n\n## Response Behavior\n\n- Summarize the company result briefly (e.g., \"Found Stripe\").\n- The tool returns a taskId for use with add-company-data-points, custom functions, or get-task-context.\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task."
152467
+ },
152468
+ {
152469
+ "slug": "CLAY_MCP_FIND_AND_ENRICH_CONTACTS_AT_COMPANY",
152470
+ "name": "Find-and-enrich-contacts-at-company",
152471
+ "description": "Search for contacts at a company by role, title, name, or department.\n\n## Quick Reference\n- **This tool**: Find TYPES of people (e.g., \"engineers at Stripe\", \"VPs at OpenAI\") or search by name (e.g., \"someone named Urmanov at Allstate\")\n- **find-and-enrich-list-of-contacts**: Find SPECIFIC named people (e.g., \"John Smith at Stripe\")\n- **Follow-ups**: ALWAYS re-call this tool—never filter results in chat. When ambiguous, ask the user.\n\n## Parameters\n\n### companyIdentifier (required)\nDomain (e.g., \"stripe.com\") or LinkedIn company URL. Company names alone will fail.\n- Convert known companies: \"Stripe\" → \"stripe.com\"\n- If ambiguous (e.g., \"Delta\"), ask the user to clarify\n\n### contactFilters (optional)\nNarrow results. Only add filters the user explicitly requests.\n\n**Rules:**\n- Filters combine with AND; values within arrays combine with OR\n- Keep compound titles as ONE string: \"VP Finance\" → [\"VP Finance\"], NOT [\"VP\", \"Finance\"]\n- Use specific terms to avoid false matches:\n - ✓ \"Software Engineer\" not \"Engineer\" (matches Sales Engineer, etc.)\n - ✓ \"Product Manager\" not \"Manager\" (matches Account Manager, etc.)\n\n**Available filters:**\n| Filter | Type | Description |\n|--------|------|-------------|\n| names | string[] | Search by name — can be first name, last name, or full name (e.g., [\"Smith\"], [\"John Smith\"]) |\n| job_title_keywords | string[] | Titles to include |\n| job_title_exclude_keywords | string[] | Titles to exclude (e.g., [\"Intern\"]) |\n| profile_keywords | string[] | Keywords anywhere in the LinkedIn profile (headline, about, experience, etc.). Use for broad keyword searches, e.g. [\"AI\", \"machine learning\"] or [\"founder\", \"co-founder\"] |\n| certification_keywords | string[] | Certifications (e.g., [\"AWS\", \"CPA\"]) |\n| languages | string[] | Profile languages |\n| school_names | string[] | Schools attended |\n| current_role_min_months_since_start_date | number | Min months in role (tenured) |\n| current_role_max_months_since_start_date | number | Max months in role (new hires) |\n| locations | string[] | Locations to include (use formal names: \"United States\", \"California\") |\n| locations_exclude | string[] | Locations to exclude |\n\n### dataPoints (optional)\nEnrich contacts/companies when creating a NEW search. For existing searches, use add-contact-data-points or add-company-data-points instead.\n\n**⚠️ CRITICAL: NEVER add data points unless the user EXPLICITLY asks for them.**\nEnrichments cost credits. Only include data points when the user's message specifically requests that data.\n- \"Find engineers at Stripe\" → NO data points\n- \"Find engineers at Stripe and get their emails\" → add Email (user explicitly asked)\n- \"Tell me about OpenAI\" → NO data points\n- Do NOT add Headcount Growth, Recent News, or any other data point \"to be helpful\" — only what the user asked for\n\n**Structure:** { contactDataPoints?: DataPoint[], companyDataPoints?: DataPoint[] }\n\n**DataPoint format:**\n- Standard: { type: \"<DataPointType>\" }\n- Custom: { type: \"Custom\", customDataPoint: \"<brief description>\" }\n\n**Important:** Only include `customDataPoint` field when type is \"Custom\"\n\n**Available contactDataPoints:** Email, Summarize Work History, Find Thought Leadership\n\n**Available companyDataPoints:** Headcount Growth, Recent News, Investors, Company Competitors, Company Customers, Tech Stack, Website Traffic, Open Jobs, Revenue Model, Annual Revenue, Latest Funding\n\n**Examples:**\n| User request | dataPoints |\n|--------------|------------|\n| \"engineers at Stripe\" | NONE — user did not ask for enrichments |\n| \"engineers at Stripe with emails\" | { contactDataPoints: [{type: \"Email\"}] } |\n| \"Canva's competitors and funding\" | { companyDataPoints: [{type: \"Company Competitors\"}, {type: \"Latest Funding\"}] } |\n| \"VPs at Figma with emails + company tech stack\" | { contactDataPoints: [{type: \"Email\"}], companyDataPoints: [{type: \"Tech Stack\"}] } |\n| \"Notion's product roadmap\" (custom) | { companyDataPoints: [{type: \"Custom\", customDataPoint: \"product roadmap\"}] } |\n\n## Examples\n\n| User says | Parameters |\n|-----------|------------|\n| \"Find people at OpenAI\" | companyIdentifier: \"openai.com\" |\n| \"VP Finance at HubSpot\" | companyIdentifier: \"hubspot.com\", contactFilters: { job_title_keywords: [\"VP Finance\"] } |\n| \"VPs and Directors in California at HubSpot\" | companyIdentifier: \"hubspot.com\", contactFilters: { job_title_keywords: [\"VP\", \"Director\"], locations: [\"California\"] } |\n| \"Marketing managers outside the US at Salesforce\" | companyIdentifier: \"salesforce.com\", contactFilters: { job_title_keywords: [\"Marketing Manager\"], locations_exclude: [\"United States\"] } |\n| \"New hires at Stripe (last 3 months)\" | companyIdentifier: \"stripe.com\", contactFilters: { current_role_max_months_since_start_date: 3 } |\n| \"Find people mentioning AI at OpenAI\" | companyIdentifier: \"openai.com\", contactFilters: { profile_keywords: [\"AI\", \"artificial intelligence\", \"machine learning\"] } |\n| \"Find founders at YC companies\" | companyIdentifier: \"ycombinator.com\", contactFilters: { profile_keywords: [\"founder\", \"co-founder\"] } |\n| \"Find someone named Urmanov at Allstate\" | companyIdentifier: \"allstate.com\", contactFilters: { names: [\"Urmanov\"] } |\n\n## Handling Follow-ups\n\nANY search modification requires re-calling this tool. Never filter in chat.\n\n**Interpret user intent:**\n- \"also/too/as well\" → ADD to existing filters\n- \"only/just\" → NARROW within current context (e.g., \"VPs only\" after Finance search → \"VP Finance\")\n- \"actually/instead/switch\" → REPLACE filters entirely\n- **When ambiguous, ask the user** rather than guessing\n\n**Examples:**\n1. User: \"Find SDRs at Verkada\" → { job_title_keywords: [\"SDR\", \"Sales Development\"] }\n User: \"Get AEs too\" → ADD: { job_title_keywords: [\"SDR\", \"Sales Development\", \"Account Executive\"] }\n\n2. User: \"Find Finance people at Ramp\" → { job_title_keywords: [\"Finance\"] }\n User: \"Make it VPs only\" → NARROW: { job_title_keywords: [\"VP Finance\"] }\n\n3. User: \"Find Finance people at Ramp\" → { job_title_keywords: [\"Finance\"] }\n User: \"Actually show me all VPs\" → REPLACE: { job_title_keywords: [\"VP\"] }\n\n## Response Behavior\n\n- Summarize the search briefly (e.g., \"Found 20 engineers at OpenAI\").\n- The tool returns a taskId for use with add-contact-data-points, add-company-data-points, custom functions, or get-task-context.\n- For emails, use add-contact-data-points with the taskId.\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task.\n\n## Zero Results\n\nSuggest broadening in order:\n1. Remove or broaden title keywords (e.g., \"Software Engineer\" → \"Engineer\")\n2. Remove location filter\n3. Remove tenure filter\n4. Verify company domain is correct"
152472
+ },
152473
+ {
152474
+ "slug": "CLAY_MCP_FIND_AND_ENRICH_LIST_OF_CONTACTS",
152475
+ "name": "Find-and-enrich-list-of-contacts",
152476
+ "description": "Find and enrich specific named contacts at their companies.\n\n## Quick Reference\n- **This tool**: Find SPECIFIC named people (e.g., \"John Smith at OpenAI\", \"Jane Doe at Stripe\")\n- **find-and-enrich-contacts-at-company**: Find TYPES of people (e.g., \"engineers at Stripe\")\n- Do NOT use if user only provides company names without contact names\n- Do NOT use to enrich contacts already in an existing search — use **add-contact-data-points** with entityIds instead\n\n## Parameters\n\n### contacts (required)\nArray of { contactName, companyIdentifier } objects.\n- **contactName**: First name, last name, or full name (e.g., \"John\", \"Smith\", or \"John Smith\")\n- **companyIdentifier**: Domain or company LinkedIn URL (NOT person LinkedIn URLs)\n - Domains: \"openai.com\", \"stripe.com\"\n - LinkedIn: \"linkedin.com/company/openai\"\n - Company names: Convert if confident (e.g., \"Stripe\" → \"stripe.com\"), otherwise ask user\n\n### dataPoints (optional)\nEnrich contacts/companies when creating a NEW search. For existing searches, use add-contact-data-points or add-company-data-points instead.\n\n**⚠️ CRITICAL: NEVER add data points unless the user EXPLICITLY asks for them.**\nEnrichments cost credits. Only include data points when the user's message specifically requests that data.\n- \"Find engineers at Stripe\" → NO data points\n- \"Find engineers at Stripe and get their emails\" → add Email (user explicitly asked)\n- \"Tell me about OpenAI\" → NO data points\n- Do NOT add Headcount Growth, Recent News, or any other data point \"to be helpful\" — only what the user asked for\n\n**Structure:** { contactDataPoints?: DataPoint[], companyDataPoints?: DataPoint[] }\n\n**DataPoint format:**\n- Standard: { type: \"<DataPointType>\" }\n- Custom: { type: \"Custom\", customDataPoint: \"<brief description>\" }\n\n**Important:** Only include `customDataPoint` field when type is \"Custom\"\n\n**Available contactDataPoints:** Email, Summarize Work History, Find Thought Leadership\n\n**Available companyDataPoints:** Headcount Growth, Recent News, Investors, Company Competitors, Company Customers, Tech Stack, Website Traffic, Open Jobs, Revenue Model, Annual Revenue, Latest Funding\n\n**Examples:**\n| User request | dataPoints |\n|--------------|------------|\n| \"engineers at Stripe\" | NONE — user did not ask for enrichments |\n| \"engineers at Stripe with emails\" | { contactDataPoints: [{type: \"Email\"}] } |\n| \"Canva's competitors and funding\" | { companyDataPoints: [{type: \"Company Competitors\"}, {type: \"Latest Funding\"}] } |\n| \"VPs at Figma with emails + company tech stack\" | { contactDataPoints: [{type: \"Email\"}], companyDataPoints: [{type: \"Tech Stack\"}] } |\n| \"Notion's product roadmap\" (custom) | { companyDataPoints: [{type: \"Custom\", customDataPoint: \"product roadmap\"}] } |\n\n## Examples\n\n| User request | contacts |\n|--------------|----------|\n| \"Find John Smith at OpenAI\" | [{ contactName: \"John Smith\", companyIdentifier: \"openai.com\" }] |\n| \"Look up Jane Doe at Stripe and Bob Lee at Figma\" | [{ contactName: \"Jane Doe\", companyIdentifier: \"stripe.com\" }, { contactName: \"Bob Lee\", companyIdentifier: \"figma.com\" }] |\n\n## Follow-ups\n- \"Add [name] at [company] too\" → Re-call with ALL contacts (previous + new)\n- \"Actually look up [different people]\" → Re-call with only the new contacts\n\n## Response Behavior\n\n- Summarize the search briefly (e.g., \"Found 20 engineers at OpenAI\").\n- The tool returns a taskId for use with add-contact-data-points, add-company-data-points, custom functions, or get-task-context.\n- For emails, use add-contact-data-points with the taskId.\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task."
152477
+ },
152478
+ {
152479
+ "slug": "CLAY_MCP_GET_CREDITS_AVAILABLE",
152480
+ "name": "Get-credits-available",
152481
+ "description": "Check if credits are available for the workspace. Returns hasWorkspaceCredits, hasSalesRepCredits, and (when credit budgets are enabled) hasBudgetCredits."
152482
+ },
152483
+ {
152484
+ "slug": "CLAY_MCP_GET_CURRENT_WORKSPACE",
152485
+ "name": "Get-current-workspace",
152486
+ "description": "Report which Clay workspace this connection is pinned to. Returns workspaceName, workspaceId, and workspaceUrl. Use when the user asks which workspace they are connected to, or to confirm where searches and enrichments will run."
152487
+ },
152488
+ {
152489
+ "slug": "CLAY_MCP_GET_SUBROUTINE_INPUT_OPTIONS",
152490
+ "name": "Get subroutine input options",
152491
+ "description": "Fetch the available dropdown options for a subroutine input that has a configured options source."
152492
+ },
152493
+ {
152494
+ "slug": "CLAY_MCP_GET_TASK",
152495
+ "name": "Get-task",
152496
+ "description": "Get task status and results by task ID. This tool handles all task types (search, direct) and returns the current state.\n\n## When to Use This Tool\n\nThis is a private tool used by the widget for polling task status.\n\n## Parameters\n\n**taskId** (required)\n- The task ID to retrieve. Accepts:\n - Universal task IDs: mcp-task-* (from run_subroutine_direct, etc.)\n - Legacy search IDs: cgas-search-id-* (backwards compatible)\n\n**page** (optional)\n- For direct tasks: 1-based page of entities (100 per page). Defaults to 1. The response includes totalEntities, hasMore, and overall completion status so callers don't need every entity to know the task state. isComplete means every entity finished (completed or errored), not that all succeeded."
152497
+ },
152498
+ {
152499
+ "slug": "CLAY_MCP_GET_TASK_CONTEXT",
152500
+ "name": "Get-task-context",
152501
+ "description": "Retrieve the current state of a task — all entities, enrichment values, and statuses.\n\n## When to Use\nCall this when you need the actual data behind an entity to answer the user's question — e.g. the user asks \"what's John's email?\", \"what X profiles did you get?\", \"show me the enrichment results\", or any question about data that may have been enriched. The initial response from search/data-points tools only includes base fields (name, title, company, LinkedIn); ALL enrichment values (emails, X/Twitter profiles, work history, custom data points) are only available through this tool.\n\n**IMPORTANT:** If the user asks about a data type and you don't see it in the initial search response, that does NOT mean it wasn't found — it means you need to call this tool to check.\n\n## Parameters\n- taskId (required): Task ID from a previous tool call. Accepts mcp-task-* IDs and legacy cgas-* search IDs.\n- entityIds (optional): Return only these entities.\n- page (optional): For direct tasks (run_subroutine_direct), a 1-based page of entities — up to 100 per page. Defaults to 1. Ignored when entityIds is provided.\n\n## Response\nReturns entities and their enrichment values for the task. Each enrichment has a name, state (\"completed\" / \"in-progress\" / \"error\"), and value.\n\nDirect tasks are paginated: the response includes page, pageSize, totalEntities, and hasMore, plus processedEntities/isComplete for overall progress. isComplete means every entity finished (completed or errored), not that all succeeded. When hasMore is true, call again with the next page to retrieve more entities — or pass entityIds to fetch specific ones."
152502
+ },
152503
+ {
152504
+ "slug": "CLAY_MCP_LIST_SUBROUTINES",
152505
+ "name": "List subroutines",
152506
+ "description": "List available functions. Available functions: Company Address, Company Industry, Company Employee Count, Company Domain, Company Job Openings, Company Revenue (Exact), Company Latest Funding, Enrich Person, Company News, Enrich Company, Find People at Company, Person Full Name, Person Job Title, Enrich Person and Find Contact Details, Person Location, Website Traffic, Website Technology Stack, Work Email. Call this to see their required inputs before using run_subroutine."
152507
+ },
152508
+ {
152509
+ "slug": "CLAY_MCP_QUERY_OBJECTS",
152510
+ "name": "Query-objects",
152511
+ "description": "Query audience accounts, contacts, or deals using natural language. This tool translates your description into a structured filter, validates it against the database, and returns matching entities with their field values.\n\n## Parameters\n\n### query (required)\nDescribe what you're looking for in plain language. The tool automatically determines whether you're querying accounts, contacts, or deals.\n\n### audienceName (optional, string)\nName of a saved audience segment to scope results to. The query filter is applied within this segment.\n\n### onlyMine (optional, boolean)\nWhen true, restrict results to accounts owned by the calling user in Salesforce. Only applies when the query targets accounts.\n\n### limit (optional, default 50, max 100)\nMax number of rows returned. Keep below 100 to stay LLM-context friendly.\n\n### offset (optional, default 0)\nPagination offset. Increment by limit to fetch additional pages.\n\n## Response\n`{ entityType, explanation, totalMatched, accounts | contacts }`\n\n- `entityType`: The detected entity type (ACCOUNT or CONTACT)\n- `explanation`: Human-readable summary of the applied filter\n- `totalMatched`: Total entities matching the filter\n- Each entity carries its `entityId`, `externalRecordId`, and `fields` (keyed by display name) with values\n\n## Examples\n\n| User says | query parameter |\n|-----------|----------------|\n| \"Show me my healthcare accounts\" | \"healthcare accounts\" (+ onlyMine: true) |\n| \"Find contacts whose title is VP Engineering\" | \"contacts with title VP Engineering\" |\n| \"Accounts with open opportunities over $100k\" | \"accounts with opportunities over $100k\" |\n| \"VPs at tech companies with 500+ employees\" | \"VPs at tech companies with 500+ employees\" |\n| \"Healthcare accounts in my Enterprise Target list\" | \"healthcare accounts\" (+ audienceName: \"Enterprise Target\") |\n\n## Notes\n- No need to discover field IDs first — this tool handles field discovery internally\n- If the filter cannot be constructed from your description, a descriptive error is returned\n- For deep analysis of specific accounts (contacts, emails, calls), use `ask-question-about-accounts` with the account IDs from this tool's results"
152512
+ },
152513
+ {
152514
+ "slug": "CLAY_MCP_RUN_SUBROUTINE",
152515
+ "name": "Run subroutine",
152516
+ "description": "Execute a function on contacts/companies FROM AN EXISTING SEARCH (Company Address, Company Industry, Company Employee Count, Company Domain, Company Job Openings, Company Revenue (Exact), Company Latest Funding, Enrich Person, Company News, Enrich Company, Find People at Company, Person Full Name, Person Job Title, Enrich Person and Find Contact Details, Person Location, Website Traffic, Website Technology Stack, Work Email).\n\n## STOP! Choose the right tool:\n- User gave you specific values (LinkedIn URL, name, email)? → Use run_subroutine_direct instead!\n- User wants to run on contacts from a previous search? → Use THIS tool (run_subroutine)\n\n## Usage (only if you have a taskId from a previous search)\n- Single contact: pass taskId + entityIds + fieldMapping\n- All contacts: pass taskId + fieldMapping\n\n## fieldMapping format\nFormat: { \"entityField\": \"subroutineInput\" }\n- KEY = entity field name (from contact data, e.g. \"name\", \"url\", \"domain\")\n- VALUE = subroutine input name (from list_subroutines, e.g. \"full_name\", \"linkedin_url\")\nExample: {\"name\": \"full_name\", \"url\": \"linkedin_url\", \"domain\": \"company_domain\"}\n\n## IMPORTANT\nDo NOT try to generate or summarize the function results yourself from your own knowledge.\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task."
152517
+ },
152518
+ {
152519
+ "slug": "CLAY_MCP_RUN_SUBROUTINE_DIRECT",
152520
+ "name": "Run subroutine direct",
152521
+ "description": "Execute a custom function on one or more sets of provided inputs. NO existing task or entityIds needed.\n\n## When to Use This Tool\nUse this tool when the user provides specific input values (like a LinkedIn URL, name, email, or a list of domains) and wants to run a function on that data directly. This is the PREFERRED tool when the user gives you concrete values to work with — for one value or many.\n\n## When NOT to Use This Tool\nDo NOT use this tool if you need to run on contacts from an existing search. Use run_subroutine instead for batch operations on search results.\n\n## Usage\nProvide:\n- subroutine_id: from list_subroutines\n- inputs: an ARRAY of input objects, one per run. Each object's keys must match the input names from list_subroutines. Use a single-element array to run once.\n Example (one): [{\"Linkedin URL\": \"https://linkedin.com/in/someone\"}]\n Example (many): [{\"Domain\": \"clay.com\"}, {\"Domain\": \"google.com\"}]\n\n## IMPORTANT\nEach input set consumes credits (N sets = N runs). Do NOT try to generate or summarize the function results yourself from your own knowledge.\nClay may render results in a widget in hosts that support MCP Apps, such as ChatGPT, claude.ai, and Cursor.\nOther terminal/coding-agent hosts such as Codex, Claude Code, Windsurf, and CLI environments do not show the widget.\nIf you are unsure whether the widget is visible, assume it is not visible.\n- If a widget is visible, avoid repeating the full widget contents unless the user asks for full contents; then call get-task-context with the taskId and answer inline.\n- In terminal/coding-agent environments, when no widget is visible, or when the user asks for actual values/results, call get-task-context with the taskId and answer inline.\n- **NEVER tell the user that data was not found, not returned, or unavailable without first calling get-task-context.** The initial search/tool response only includes base fields — enrichment results (emails, X/Twitter profiles, work history, custom data points, etc.) are only available via get-task-context.\n- **When the user asks about a specific value** (e.g. \"what's Patrick's email?\", \"what X profiles did you get?\"), call get-task-context FIRST to check if the data has already been enriched — the user may have triggered enrichments through the widget. Only call add-contact-data-points / add-company-data-points if get-task-context shows the enrichment hasn't been run yet.\n- Use get-task-context to poll until async results complete; if values are still in-progress, wait and retry rather than answering with missing values.\n- If get-task-context is not available, fall back to get-task.\n\n## Response Behavior\nConfirm briefly: \"Running [function name]—results will appear shortly.\""
152522
+ },
152523
+ {
152524
+ "slug": "CLAY_MCP_RUN_SUBROUTINE_NO_MAPPING",
152525
+ "name": "Run subroutine no mapping",
152526
+ "description": "Run a custom subroutine on search entities. The backend automatically generates the field mapping."
152527
+ },
152528
+ {
152529
+ "slug": "CLAY_MCP_TRACK_EVENT",
152530
+ "name": "Track-event",
152531
+ "description": "Track an analytics event with optional properties."
152532
+ }
152533
+ ],
152534
+ "triggers": [],
152535
+ "authConfigDetails": [
152536
+ {
152537
+ "mode": "DCR_OAUTH",
152538
+ "name": "clay_mcp_DCR_OAuth",
152539
+ "fields": {
152540
+ "auth_config_creation": {
152541
+ "required": [],
152542
+ "optional": [
152543
+ {
152544
+ "name": "client_id",
152545
+ "displayName": "Client id",
152546
+ "type": "string",
152547
+ "description": "Client id of the app",
152548
+ "required": false,
152549
+ "default": null
152550
+ },
152551
+ {
152552
+ "name": "client_secret",
152553
+ "displayName": "Client secret",
152554
+ "type": "string",
152555
+ "description": "Client secret of the app",
152556
+ "required": false,
152557
+ "default": null
152558
+ },
152559
+ {
152560
+ "name": "oauth_redirect_uri",
152561
+ "displayName": "Redirect URI",
152562
+ "type": "string",
152563
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
152564
+ "required": false,
152565
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
152566
+ },
152567
+ {
152568
+ "name": "scopes",
152569
+ "displayName": "Scopes",
152570
+ "type": "string",
152571
+ "description": "Scopes to request from the user, comma separated",
152572
+ "required": false,
152573
+ "default": "mcp"
152574
+ }
152575
+ ]
152576
+ },
152577
+ "connected_account_initiation": {
152578
+ "required": [],
152579
+ "optional": []
152580
+ }
152581
+ }
152582
+ }
152583
+ ]
152584
+ },
152585
{
152586
"slug": "clearout",
152587
"name": "Clearout",
154843
}
154844
]
154845
},
154846
+ {
154847
+ "slug": "clio_manage",
154848
+ "name": "Clio Manage (US)",
154849
+ "logo": "https://logos.composio.dev/api/clio_manage",
154850
+ "description": "Clio Manage legal practice management for United States-region accounts on app.clio.com. Manage clients, matters, calendars, tasks, time, and billing. Canada, EU, and Australia accounts require separate regional OAuth applications and hosts.",
154851
+ "category": "crm",
154852
+ "authSchemes": [
154853
+ "OAUTH2"
154854
+ ],
154855
+ "toolCount": 99,
154856
+ "triggerCount": 0,
154857
+ "version": "00000000_00",
154858
+ "tools": [
154859
+ {
154860
+ "slug": "CLIO_MANAGE_ASSIGN_TASK_TEMPLATE_LIST",
154861
+ "name": "Assign Task Template List",
154862
+ "description": "Assign one Clio task template list to a matter, creating its tasks with assignee notifications disabled. The action reads the current Matter ETag before the PATCH and does not retry a rejected write. Clio does not return guaranteed generated Task IDs or provide atomic undo; find and delete generated tasks separately if cleanup is needed. Requires Matters and Tasks access."
154863
+ },
154864
+ {
154865
+ "slug": "CLIO_MANAGE_CREATE_ACTIVITY",
154866
+ "name": "Create Activity",
154867
+ "description": "Create a Clio time or expense activity. Requires Clio's Activities write permission."
154868
+ },
154869
+ {
154870
+ "slug": "CLIO_MANAGE_CREATE_CALENDAR",
154871
+ "name": "Create Calendar",
154872
+ "description": "Create a Clio custom calendar. Requires the Calendars write permission selected on the Clio developer application."
154873
+ },
154874
+ {
154875
+ "slug": "CLIO_MANAGE_CREATE_CALENDAR_ENTRY",
154876
+ "name": "Create Calendar Entry",
154877
+ "description": "Create a Clio calendar entry. Only internal Clio calendars can be attendees because Clio always emails contact attendees. Calendar notifications are disabled. Requires Clio's Calendars write permission."
154878
+ },
154879
+ {
154880
+ "slug": "CLIO_MANAGE_CREATE_COMMUNICATION",
154881
+ "name": "Create Communication",
154882
+ "description": "Record a phone or email communication in Clio. This creates a communication log; it does not place a call or send an email. Notification subscribers are intentionally unsupported. Requires Communications write permission in the Clio developer application."
154883
+ },
154884
+ {
154885
+ "slug": "CLIO_MANAGE_CREATE_CONTACT",
154886
+ "name": "Create Contact",
154887
+ "description": "Create a Clio person or company, including new email addresses and phone numbers. A Company requires name; a Person requires first_name or last_name. Requires Clio's Contacts write permission."
154888
+ },
154889
+ {
154890
+ "slug": "CLIO_MANAGE_CREATE_DOCUMENT",
154891
+ "name": "Create Document Upload Initiation",
154892
+ "description": "Create only the Clio document record and signed-upload initiation. This action does not upload bytes, follow signed destinations, finalize an upload, or create a version of an existing document. Upload without Clio OAuth, then use a separate finalization operation. Requires Documents write permission."
154893
+ },
154894
+ {
154895
+ "slug": "CLIO_MANAGE_CREATE_DOCUMENT_TEMPLATE",
154896
+ "name": "Create Document Template",
154897
+ "description": "Upload one non-sensitive file directly to Clio's documented multipart route and create a document template suitable for START_DOCUMENT_FROM_TEMPLATE or GENERATE_DOCUMENT_FROM_TEMPLATE. Requires Documents write permission."
154898
+ },
154899
+ {
154900
+ "slug": "CLIO_MANAGE_CREATE_MATTER",
154901
+ "name": "Create Matter",
154902
+ "description": "Create a Clio matter for a client. Requires Clio's Matters write permission."
154903
+ },
154904
+ {
154905
+ "slug": "CLIO_MANAGE_CREATE_MATTER_FOLDER",
154906
+ "name": "Create Matter Folder",
154907
+ "description": "Create a subfolder inside a Clio Matter. Clio creates each Matter's root folder automatically; this action creates a child folder and always uses the supplied Matter as its parent. Requires Documents write permission."
154908
+ },
154909
+ {
154910
+ "slug": "CLIO_MANAGE_CREATE_MATTER_NOTE",
154911
+ "name": "Create Matter Note",
154912
+ "description": "Create a note associated with a Clio Matter. The action fixes the note type to Matter and intentionally does not support notification subscribers. Requires Notes and Matter access in the Clio developer application."
154913
+ },
154914
+ {
154915
+ "slug": "CLIO_MANAGE_CREATE_TASK",
154916
+ "name": "Create Task",
154917
+ "description": "Create a non-complete Clio task with assignee notifications disabled. To complete it safely, create it as pending and then call UPDATE_TASK with status complete. Requires Clio's Tasks write permission."
154918
+ },
154919
+ {
154920
+ "slug": "CLIO_MANAGE_CREATE_TASK_TEMPLATE_LIST",
154921
+ "name": "Create Non-Empty Task Template List",
154922
+ "description": "Create a Clio task-template list plus one to ten documented task templates, read it back to confirm it is non-empty, and clean up partial creation on failure. Templates are private, non-cascading, plain text, and have no reminders; this does not assign a list to a matter or notify assignees. Requires Tasks write permission."
154923
+ },
154924
+ {
154925
+ "slug": "CLIO_MANAGE_DELETE_ACTIVITY",
154926
+ "name": "Delete Activity",
154927
+ "description": "Permanently delete one Clio time or expense activity by ID. Requires Clio's Activities write permission."
154928
+ },
154929
+ {
154930
+ "slug": "CLIO_MANAGE_DELETE_BILL",
154931
+ "name": "Delete Bill",
154932
+ "description": "Permanently delete an owned Draft or Pending Approval bill after exact ID, number, ETag, state, ownership, and confirmation checks. Clio only accepts bills without recorded payments. Unpaid bills must use Void Bill. Requires Billing write permission."
154933
+ },
154934
+ {
154935
+ "slug": "CLIO_MANAGE_DELETE_CALENDAR",
154936
+ "name": "Delete Calendar",
154937
+ "description": "Permanently delete one manually created Clio calendar after verifying it is an owner-controlled AdhocCalendar. Built-in firm and user calendars are refused. This tool does not check whether the calendar contains entries, and Clio does not document whether deletion preserves, migrates, or deletes them. Requires Calendars write permission."
154938
+ },
154939
+ {
154940
+ "slug": "CLIO_MANAGE_DELETE_CALENDAR_ENTRY",
154941
+ "name": "Delete Calendar Entry",
154942
+ "description": "Permanently delete a non-recurring Clio calendar entry or an explicitly scoped recurring occurrence, future sequence, or series. Fails closed when Contact attendees exist because Clio would email them. Clio DELETE has no atomic ETag guard, so a concurrent attendee change after preflight remains a notification risk for non-recurring or series deletion. Requires Calendars write permission."
154943
+ },
154944
+ {
154945
+ "slug": "CLIO_MANAGE_DELETE_COMMUNICATION",
154946
+ "name": "Delete Communication",
154947
+ "description": "Permanently delete one recorded Clio communication after an exact-ID preflight and explicit confirmation. This does not notify subscribers. Requires Communications write permission."
154948
+ },
154949
+ {
154950
+ "slug": "CLIO_MANAGE_DELETE_CONTACT",
154951
+ "name": "Delete Contact",
154952
+ "description": "Permanently delete one Clio contact by ID. Requires Clio's Contacts write permission."
154953
+ },
154954
+ {
154955
+ "slug": "CLIO_MANAGE_DELETE_DOCUMENT",
154956
+ "name": "Delete Document",
154957
+ "description": "Move a Clio document to trash after an exact ID-and-name preflight and explicit confirmation. Clio permanently deletes trashed documents after 30 days. Requires Documents write permission."
154958
+ },
154959
+ {
154960
+ "slug": "CLIO_MANAGE_DELETE_DOCUMENT_TEMPLATE",
154961
+ "name": "Delete Document Template",
154962
+ "description": "Permanently delete a Clio document template after an exact ID-and-filename preflight and explicit confirmation. Requires Documents write permission."
154963
+ },
154964
+ {
154965
+ "slug": "CLIO_MANAGE_DELETE_FOLDER",
154966
+ "name": "Delete Folder",
154967
+ "description": "Move a non-root, unlocked Clio folder to trash after an exact ID-and-name preflight and explicit confirmation. Trashed folders are permanently deleted after 30 days. Requires Documents write permission."
154968
+ },
154969
+ {
154970
+ "slug": "CLIO_MANAGE_DELETE_MATTER",
154971
+ "name": "Delete Matter",
154972
+ "description": "Permanently delete one Clio matter by ID. Requires Clio's Matters write permission."
154973
+ },
154974
+ {
154975
+ "slug": "CLIO_MANAGE_DELETE_NOTE",
154976
+ "name": "Delete Note",
154977
+ "description": "Permanently delete one Clio note after an exact-ID preflight and explicit confirmation. This does not notify subscribers. Requires Notes write permission."
154978
+ },
154979
+ {
154980
+ "slug": "CLIO_MANAGE_DELETE_TASK",
154981
+ "name": "Delete Task",
154982
+ "description": "Permanently delete one Clio task by ID. Requires Clio's Tasks write permission."
154983
+ },
154984
+ {
154985
+ "slug": "CLIO_MANAGE_DELETE_TASK_TEMPLATE_LIST",
154986
+ "name": "Delete Task Template List",
154987
+ "description": "Permanently delete a Clio task-template list after an exact ID-and-name preflight and explicit confirmation. This does not assign tasks or send notifications. Requires Tasks write permission."
154988
+ },
154989
+ {
154990
+ "slug": "CLIO_MANAGE_DOWNLOAD_DOCUMENT",
154991
+ "name": "Download Document",
154992
+ "description": "Download the latest or a specified Clio document version as a managed file. The runtime follows Clio's 303 with cross-host authorization stripping, so Clio OAuth is never sent to the signed download host. Requires Documents read permission."
154993
+ },
154994
+ {
154995
+ "slug": "CLIO_MANAGE_FIND_BILL",
154996
+ "name": "Find Bill",
154997
+ "description": "Exhaustively find Clio bills by exact client, matter, bill number, and state criteria. Provide client_id, matter_id, or invoice_number; state only narrows that lookup. All supplied criteria are combined with AND; duplicate exact bills are returned as ambiguous rather than selecting one. Requires Billing read permission on the Clio developer application."
154998
+ },
154999
+ {
155000
+ "slug": "CLIO_MANAGE_FIND_COMPANY_CONTACT",
155001
+ "name": "Find Company Contact",
155002
+ "description": "Exhaustively find exact Clio company contacts without choosing an arbitrary duplicate. Requires Contacts read permission."
155003
+ },
155004
+ {
155005
+ "slug": "CLIO_MANAGE_FIND_CONTACT_BY_CUSTOM_FIELD",
155006
+ "name": "Find Contact by Custom Field",
155007
+ "description": "Validate a Clio Contact custom field, exhaustively search its exact typed value, and report duplicate ambiguity. Requires Custom Fields read and Contacts read permissions."
155008
+ },
155009
+ {
155010
+ "slug": "CLIO_MANAGE_FIND_MATTER",
155011
+ "name": "Find Matter",
155012
+ "description": "Find by matter_id alone, or exhaustively search using display_number, description, or client_reference, optionally narrowed by client_id and status. All collection results are exact-filtered; multiple matches are reported as ambiguous. Requires Matters read permission."
155013
+ },
155014
+ {
155015
+ "slug": "CLIO_MANAGE_FIND_MATTER_BY_CUSTOM_FIELD",
155016
+ "name": "Find Matter by Custom Field",
155017
+ "description": "Validate a dynamic Matter custom field, exhaustively scan all exact provider candidates, and report zero, one, or every ambiguous exact match. Requires Custom Fields and Matters read permissions."
155018
+ },
155019
+ {
155020
+ "slug": "CLIO_MANAGE_FIND_NEWEST_MATTER_BY_CLIENT_EMAIL",
155021
+ "name": "Find Newest Matter by Client Email",
155022
+ "description": "Resolve exactly one contact by exact email, exhaust all of that client's matters, and select the greatest created_at with greatest ID as the tie-break. If any candidate lacks a valid created_at, return comparison_incomplete and do not select a newest matter. Requires Contacts and Matters read permissions."
155023
+ },
155024
+ {
155025
+ "slug": "CLIO_MANAGE_FIND_OR_CREATE_COMPANY_CONTACT",
155026
+ "name": "Find or Create Company Contact",
155027
+ "description": "Exhaustively preflight a Clio company identity using email or a complete custom-field ID/value pair, create only when absent, then postflight for races. Requires Contacts write and, when used, Custom Fields read permissions."
155028
+ },
155029
+ {
155030
+ "slug": "CLIO_MANAGE_FIND_OR_CREATE_MATTER",
155031
+ "name": "Find or Create Matter",
155032
+ "description": "Choose either client_id or client_email, not both, plus client_reference or a complete custom-field ID/value pair. Resolve exactly one client, exhaustively find an exact matter identity, create only when absent, then repeat the exhaustive search to detect concurrent duplicates. Requires Matters write and relevant Contacts/Custom Fields access."
155033
+ },
155034
+ {
155035
+ "slug": "CLIO_MANAGE_FIND_OR_CREATE_PERSON_CONTACT",
155036
+ "name": "Find or Create Person Contact",
155037
+ "description": "Exhaustively preflight a Clio person identity using email or a complete custom-field ID/value pair, create only when absent, then postflight for races. Requires Contacts write and, when used, Custom Fields read permissions."
155038
+ },
155039
+ {
155040
+ "slug": "CLIO_MANAGE_FIND_PERSON_CONTACT",
155041
+ "name": "Find Person Contact",
155042
+ "description": "Exhaustively find exact Clio person contacts without choosing an arbitrary duplicate. Requires Contacts read permission."
155043
+ },
155044
+ {
155045
+ "slug": "CLIO_MANAGE_FIND_USER",
155046
+ "name": "Find User",
155047
+ "description": "Find one Clio user using a single selector: user_id, email, or full name. enabled and include_co_counsel apply only to email or name searches. ID uses the documented single-user endpoint; email and name searches exhaust all id-ascending pages and report duplicate exact users as ambiguous. Requires Users read permission on the Clio developer application."
155048
+ },
155049
+ {
155050
+ "slug": "CLIO_MANAGE_GENERATE_DOCUMENT_FROM_TEMPLATE",
155051
+ "name": "Generate Document From Template",
155052
+ "description": "Create a Clio document automation, then poll its documented status endpoint within the caller's bounded interval and timeout. This creates a persistent automation and generated Documents; completed returns those documents, failed or empty returns that terminal outcome, and polling expiry returns still_pending with the automation ID and latest state so callers do not start a duplicate. Clio publishes no polling SLA. Requires Documents read/write access and access to the Matter and template."
155053
+ },
155054
+ {
155055
+ "slug": "CLIO_MANAGE_GET_ACTIVITY",
155056
+ "name": "Get Activity",
155057
+ "description": "Get one Clio time or expense activity by ID, including billing state and its user and matter references."
155058
+ },
155059
+ {
155060
+ "slug": "CLIO_MANAGE_GET_BILL",
155061
+ "name": "Get Bill",
155062
+ "description": "Get one Clio bill with its ETag, lifecycle state, permitted transitions, and concrete financial totals. Requires Billing read permission."
155063
+ },
155064
+ {
155065
+ "slug": "CLIO_MANAGE_GET_CALENDAR",
155066
+ "name": "Get Calendar",
155067
+ "description": "Get one Clio calendar by ID, including its type, permission, visibility, source, and colors. Requires the Calendars read permission selected on the Clio developer application."
155068
+ },
155069
+ {
155070
+ "slug": "CLIO_MANAGE_GET_CALENDAR_ENTRY",
155071
+ "name": "Get Calendar Entry",
155072
+ "description": "Get one Clio calendar entry or expanded recurring occurrence by ID with recurrence, attendee, owner, and matter details. Requires the Calendars read permission selected on the Clio developer application."
155073
+ },
155074
+ {
155075
+ "slug": "CLIO_MANAGE_GET_COMMUNICATION",
155076
+ "name": "Get Communication",
155077
+ "description": "Retrieve one recorded Clio communication. This does not send a message or notify subscribers. Requires Communications read permission."
155078
+ },
155079
+ {
155080
+ "slug": "CLIO_MANAGE_GET_CONTACT",
155081
+ "name": "Get Contact",
155082
+ "description": "Get one Clio person or company by its known ID, including primary and structured email and phone details. Use Search Contacts to discover an ID. Requires Contacts read permission on the Clio developer application."
155083
+ },
155084
+ {
155085
+ "slug": "CLIO_MANAGE_GET_CURRENT_USER",
155086
+ "name": "Get Current User",
155087
+ "description": "Return the authenticated Clio user and role information for identity checks and default user references. Requires the Users read permission selected on the Clio developer application."
155088
+ },
155089
+ {
155090
+ "slug": "CLIO_MANAGE_GET_DOCUMENT",
155091
+ "name": "Get Document",
155092
+ "description": "Get one Clio document and its latest-version metadata by ID. Requires Documents read permission."
155093
+ },
155094
+ {
155095
+ "slug": "CLIO_MANAGE_GET_FOLDER",
155096
+ "name": "Get Folder",
155097
+ "description": "Retrieve one Clio folder by ID. Requires Documents read permission."
155098
+ },
155099
+ {
155100
+ "slug": "CLIO_MANAGE_GET_MATTER",
155101
+ "name": "Get Matter",
155102
+ "description": "Get one Clio matter by ID with lifecycle, client, staffing, practice area, dates, and billing method. Requires read access to Matters."
155103
+ },
155104
+ {
155105
+ "slug": "CLIO_MANAGE_GET_MATTER_CLIENT",
155106
+ "name": "Get Matter Client",
155107
+ "description": "Retrieve the client contact for one Clio matter. Requires Contacts and Matters read permission."
155108
+ },
155109
+ {
155110
+ "slug": "CLIO_MANAGE_GET_NOTE",
155111
+ "name": "Get Note",
155112
+ "description": "Retrieve one Clio matter or contact note. Reading a note does not notify subscribers. Requires Notes read permission."
155113
+ },
155114
+ {
155115
+ "slug": "CLIO_MANAGE_GET_TASK",
155116
+ "name": "Get Task",
155117
+ "description": "Get one Clio task by its known ID, including description, status, due date, priority, assignee, matter, and completion-notification state. Requires read access to Tasks in the Clio developer application."
155118
+ },
155119
+ {
155120
+ "slug": "CLIO_MANAGE_GET_USER",
155121
+ "name": "Get User",
155122
+ "description": "Get one Clio firm user by ID with identity, account role, locale, time zone, and default calendar information. Requires the Users read permission selected on the Clio developer application."
155123
+ },
155124
+ {
155125
+ "slug": "CLIO_MANAGE_LIST_ACTIVITY_DESCRIPTIONS",
155126
+ "name": "List Activity Descriptions",
155127
+ "description": "List selectable Clio activity descriptions and resolved rates for time entries. Requires Activities read permission."
155128
+ },
155129
+ {
155130
+ "slug": "CLIO_MANAGE_LIST_CALENDARS",
155131
+ "name": "List Calendars",
155132
+ "description": "List visible or writable Clio calendars to resolve the owner ID for calendar entries. Requires the Calendars read permission selected on the Clio developer application."
155133
+ },
155134
+ {
155135
+ "slug": "CLIO_MANAGE_LIST_COMMUNICATIONS",
155136
+ "name": "List Communications",
155137
+ "description": "Return one bounded page of recorded Clio email or phone communications. This reads logs and does not send messages or notify subscribers. Requires Communications read permission."
155138
+ },
155139
+ {
155140
+ "slug": "CLIO_MANAGE_LIST_CONTACT_EMAIL_ADDRESSES",
155141
+ "name": "List Contact Email Addresses",
155142
+ "description": "Return one bounded page of email addresses for a Clio contact. Requires Contacts read permission."
155143
+ },
155144
+ {
155145
+ "slug": "CLIO_MANAGE_LIST_CONTACT_PHONE_NUMBERS",
155146
+ "name": "List Contact Phone Numbers",
155147
+ "description": "Return one bounded page of phone numbers for a Clio contact. Requires Contacts read permission."
155148
+ },
155149
+ {
155150
+ "slug": "CLIO_MANAGE_LIST_DOCUMENT_AUTOMATIONS",
155151
+ "name": "List Document Automations",
155152
+ "description": "Return one bounded page of Clio document-generation automations. Requires Documents read permission."
155153
+ },
155154
+ {
155155
+ "slug": "CLIO_MANAGE_LIST_DOCUMENTS",
155156
+ "name": "List Documents",
155157
+ "description": "Return one bounded provider page of Clio documents. Requires Documents read permission."
155158
+ },
155159
+ {
155160
+ "slug": "CLIO_MANAGE_LIST_DOCUMENT_TEMPLATES",
155161
+ "name": "List Document Templates",
155162
+ "description": "List Clio document templates and IDs for document automation. Requires Documents read permission; availability can depend on the Clio plan."
155163
+ },
155164
+ {
155165
+ "slug": "CLIO_MANAGE_LIST_EXPENSE_CATEGORIES",
155166
+ "name": "List Expense Categories",
155167
+ "description": "List selectable Clio expense categories and rates for expense entries. Requires Activities read permission."
155168
+ },
155169
+ {
155170
+ "slug": "CLIO_MANAGE_LIST_FOLDER_CONTENTS",
155171
+ "name": "List Folder Contents",
155172
+ "description": "Return one bounded page of Clio documents and folders, optionally below a parent folder. Requires Documents read permission."
155173
+ },
155174
+ {
155175
+ "slug": "CLIO_MANAGE_LIST_FOLDERS",
155176
+ "name": "List Folders",
155177
+ "description": "Return one bounded page of Clio folders using documented filters. Requires Documents read permission."
155178
+ },
155179
+ {
155180
+ "slug": "CLIO_MANAGE_LIST_GROUPS",
155181
+ "name": "List Groups",
155182
+ "description": "List Clio groups and IDs for matter assignments and user grouping. Requires Groups read permission."
155183
+ },
155184
+ {
155185
+ "slug": "CLIO_MANAGE_LIST_MATTER_CONTACTS",
155186
+ "name": "List Matter Contacts",
155187
+ "description": "Return one bounded page of Clio matter-contact association records, including association ID and ETag, relationship label, is_client, matter reference, and contact details. Use LIST_MATTER_RELATED_CONTACTS for the related-contact relationship view. Requires Contacts and Matters read permissions."
155188
+ },
155189
+ {
155190
+ "slug": "CLIO_MANAGE_LIST_MATTER_PROTECTED_FUNDS",
155191
+ "name": "List Matter Protected Funds",
155192
+ "description": "Return one bounded page of protected funds for a Clio matter. Requires Matters read permission."
155193
+ },
155194
+ {
155195
+ "slug": "CLIO_MANAGE_LIST_MATTER_RELATED_CONTACTS",
155196
+ "name": "List Matter Related Contacts",
155197
+ "description": "Return one bounded page of Clio related-contact relationship records, including relationship ID, contact_id, and whether the contact is also the matter client. Use LIST_MATTER_CONTACTS for matter-contact association labels. Requires Contacts and Matters read permissions."
155198
+ },
155199
+ {
155200
+ "slug": "CLIO_MANAGE_LIST_MATTER_STAGES",
155201
+ "name": "List Matter Stages",
155202
+ "description": "List Clio matter stages and practice-area associations for selecting a matter stage. Requires Matters read permission."
155203
+ },
155204
+ {
155205
+ "slug": "CLIO_MANAGE_LIST_NOTES",
155206
+ "name": "List Notes",
155207
+ "description": "Return one bounded page of Clio matter or contact notes. Reading notes does not notify subscribers. Requires Notes read permission."
155208
+ },
155209
+ {
155210
+ "slug": "CLIO_MANAGE_LIST_PRACTICE_AREAS",
155211
+ "name": "List Practice Areas",
155212
+ "description": "List Clio practice areas and IDs for matter and task-template selection. Requires Matters read permission."
155213
+ },
155214
+ {
155215
+ "slug": "CLIO_MANAGE_LIST_TASK_TEMPLATE_LISTS",
155216
+ "name": "List Task Template Lists",
155217
+ "description": "List Clio task template lists and IDs for assigning templates to matters. Requires Tasks read permission."
155218
+ },
155219
+ {
155220
+ "slug": "CLIO_MANAGE_LIST_USERS",
155221
+ "name": "List Users",
155222
+ "description": "List Clio users available for attorney, staff, task-assignee, and activity-user references. Requires the Users read permission selected on the Clio developer application."
155223
+ },
155224
+ {
155225
+ "slug": "CLIO_MANAGE_PREVIEW_BILL",
155226
+ "name": "Preview Bill",
155227
+ "description": "Render one Clio bill as HTML, cap the response at 2 MB, and offload it as a file instead of returning active HTML inline. This does not change or send the bill. Requires Billing read permission."
155228
+ },
155229
+ {
155230
+ "slug": "CLIO_MANAGE_SAVE_ACTIVITY",
155231
+ "name": "Save Activity",
155232
+ "description": "Deprecated compatibility action. Use CREATE_ACTIVITY when activity_id is omitted and UPDATE_ACTIVITY when it is provided. Preserves the combined Clio time-or-expense create/update behavior. Requires Activities write permission."
155233
+ },
155234
+ {
155235
+ "slug": "CLIO_MANAGE_SAVE_CALENDAR",
155236
+ "name": "Save Calendar",
155237
+ "description": "Deprecated compatibility action. Use CREATE_CALENDAR when calendar_id is omitted and UPDATE_CALENDAR when it is provided. Preserves custom-calendar creation and ETag-safe updates. Requires Calendars write permission."
155238
+ },
155239
+ {
155240
+ "slug": "CLIO_MANAGE_SAVE_CALENDAR_ENTRY",
155241
+ "name": "Save Calendar Entry",
155242
+ "description": "Deprecated compatibility action. Use CREATE_CALENDAR_ENTRY when calendar_entry_id is omitted and UPDATE_CALENDAR_ENTRY when it is provided. Contact attendees are unsupported because Clio always emails them, so updates fail closed when any already exist. Recurring updates require occurrence or series scope; future-series updates are unsupported. Calendar notifications are disabled. Requires Clio's Calendars write permission."
155243
+ },
155244
+ {
155245
+ "slug": "CLIO_MANAGE_SAVE_CONTACT",
155246
+ "name": "Save Contact",
155247
+ "description": "Deprecated compatibility action. Use CREATE_CONTACT when contact_id is omitted and UPDATE_CONTACT when it is provided. Person writes intentionally use first_name/last_name because live Clio rejects the OpenAPI-documented name field for Person. Nested records can be irreversibly deleted."
155248
+ },
155249
+ {
155250
+ "slug": "CLIO_MANAGE_SAVE_MATTER",
155251
+ "name": "Save Matter",
155252
+ "description": "Deprecated compatibility action. Use CREATE_MATTER when matter_id is omitted and UPDATE_MATTER when it is provided. Preserves combined matter create/update behavior. Requires Clio's Matters write permission."
155253
+ },
155254
+ {
155255
+ "slug": "CLIO_MANAGE_SAVE_TASK",
155256
+ "name": "Save Task",
155257
+ "description": "Deprecated compatibility action. Use CREATE_TASK when task_id is omitted and UPDATE_TASK when it is provided. Assignee notifications are disabled on creation and reassignment; completion notifications are disabled and verified before a complete status transition. Requires Clio's Tasks write permission."
155258
+ },
155259
+ {
155260
+ "slug": "CLIO_MANAGE_SEARCH_ACTIVITIES",
155261
+ "name": "Search Activities",
155262
+ "description": "Search and filter Clio activities, including multiple activity IDs, one page at a time. Use Get Activity for one known ID and full billing details. Requires Activities read permission in the Clio developer application."
155263
+ },
155264
+ {
155265
+ "slug": "CLIO_MANAGE_SEARCH_CALENDAR_ENTRIES",
155266
+ "name": "Search Calendar Entries",
155267
+ "description": "Search Clio calendar entries by time window, text, calendar, matter, or ID, one page at a time. Requires read access to the Calendars permission in the Clio developer application."
155268
+ },
155269
+ {
155270
+ "slug": "CLIO_MANAGE_SEARCH_CONTACTS",
155271
+ "name": "Search Contacts",
155272
+ "description": "Search and filter Clio contacts, including multiple contact IDs, one page at a time. Use Get Contact for one known ID and full contact details. Requires Contacts read permission in the Clio developer application."
155273
+ },
155274
+ {
155275
+ "slug": "CLIO_MANAGE_SEARCH_MATTERS",
155276
+ "name": "Search Matters",
155277
+ "description": "Search and filter Clio matters, including multiple matter IDs, one page at a time. Use Get Matter for one known ID and full lifecycle, staffing, and billing details. Requires Matters read permission in the Clio developer application."
155278
+ },
155279
+ {
155280
+ "slug": "CLIO_MANAGE_SEARCH_TASKS",
155281
+ "name": "Search Tasks",
155282
+ "description": "Search and filter Clio tasks, including multiple task IDs, one page at a time. Use Get Task for one known ID and full task details. Requires Tasks read permission in the Clio developer application."
155283
+ },
155284
+ {
155285
+ "slug": "CLIO_MANAGE_START_DOCUMENT_FROM_TEMPLATE",
155286
+ "name": "Start Document From Template",
155287
+ "description": "Start Clio's asynchronous create-document-from-template generation and return the automation ID, current state, and any documents already present. This action does not wait for completion because Clio documents no polling SLA. Check GET /document_automations/{id}.json using Platform Equivalent via proxy, or a future show action, before treating the document as generated. Requires Clio Documents write access and access to the Matter and template."
155288
+ },
155289
+ {
155290
+ "slug": "CLIO_MANAGE_TRANSITION_BILL_STATE",
155291
+ "name": "Transition Bill State",
155292
+ "description": "Irreversibly transition a bill to paid, void, or deleted only after exact identity, ETag, expected current state, available transition, and explicit confirmation checks. Uses Clio's official PATCH bill operation and requires Billing write permission."
155293
+ },
155294
+ {
155295
+ "slug": "CLIO_MANAGE_UPDATE_ACTIVITY",
155296
+ "name": "Update Activity",
155297
+ "description": "Update at least one field on an existing Clio time or expense activity, optionally using its ETag as a concurrency precondition. Posted or billed activities may be immutable. Requires Clio's Activities write permission."
155298
+ },
155299
+ {
155300
+ "slug": "CLIO_MANAGE_UPDATE_BILL",
155301
+ "name": "Update Bill",
155302
+ "description": "Update ordinary bill presentation, financial, tax, discount, or interest fields using the required current ETag. Lifecycle state is deliberately excluded; use Transition Bill State for a confirmed state change. Requires Billing write permission."
155303
+ },
155304
+ {
155305
+ "slug": "CLIO_MANAGE_UPDATE_CALENDAR",
155306
+ "name": "Update Calendar",
155307
+ "description": "Update at least one of an existing Clio calendar's name, color, source, or visibility after reading its current ETag. Requires the Calendars write permission selected on the Clio developer application."
155308
+ },
155309
+ {
155310
+ "slug": "CLIO_MANAGE_UPDATE_CALENDAR_ENTRY",
155311
+ "name": "Update Calendar Entry",
155312
+ "description": "Update at least one field on a Clio calendar entry without sending calendar notifications. Existing contact attendees cause the update to fail closed because Clio always emails them. Recurring updates require occurrence or series scope; future-series updates are unsupported. Requires Clio's Calendars write permission."
155313
+ },
155314
+ {
155315
+ "slug": "CLIO_MANAGE_UPDATE_COMMUNICATION",
155316
+ "name": "Update Communication",
155317
+ "description": "Update a recorded Clio communication using its current ETag, including explicitly confirmed irreversible deletion of external properties. Notification subscribers are intentionally unsupported. Requires Communications write permission."
155318
+ },
155319
+ {
155320
+ "slug": "CLIO_MANAGE_UPDATE_CONTACT",
155321
+ "name": "Update Contact",
155322
+ "description": "Update at least one field on a Clio person or company, including adding or updating nested email and phone records. Setting destroy=true with a nested record ID irreversibly deletes that record. Requires Clio's Contacts write permission."
155323
+ },
155324
+ {
155325
+ "slug": "CLIO_MANAGE_UPDATE_DOCUMENT",
155326
+ "name": "Update Document Metadata",
155327
+ "description": "Update only Clio document metadata with an If-Match ETag. It cannot restore a trashed document, initialize or finalize uploads, create versions, or mutate external properties. HTTP 412 is surfaced without retry. Requires Documents write permission."
155328
+ },
155329
+ {
155330
+ "slug": "CLIO_MANAGE_UPDATE_FOLDER",
155331
+ "name": "Update Folder",
155332
+ "description": "Rename, move, recategorize, or restore a Clio folder, and add, change, or explicitly and irreversibly delete external properties, using its current ETag. Requires Documents write permission."
155333
+ },
155334
+ {
155335
+ "slug": "CLIO_MANAGE_UPDATE_MATTER",
155336
+ "name": "Update Matter",
155337
+ "description": "Update at least one field on an existing Clio matter, optionally using its ETag for concurrency safety. Requires Clio's Matters write permission."
155338
+ },
155339
+ {
155340
+ "slug": "CLIO_MANAGE_UPDATE_NOTE",
155341
+ "name": "Update Note",
155342
+ "description": "Update a Clio note using its current ETag. Notification subscribers are intentionally unsupported. Requires Notes write permission."
155343
+ },
155344
+ {
155345
+ "slug": "CLIO_MANAGE_UPDATE_TASK",
155346
+ "name": "Update Task",
155347
+ "description": "Update at least one field on an existing Clio task. Assignee notifications are disabled on reassignment. Completion notifications are disabled and verified before a complete status transition. Requires Clio's Tasks write permission."
155348
+ },
155349
+ {
155350
+ "slug": "CLIO_MANAGE_VOID_BILL",
155351
+ "name": "Void Bill",
155352
+ "description": "Irreversibly void an Unpaid bill after exact ID, number, ETag, state, and confirmation checks. Clio only accepts bills without recorded payments. Draft and Pending Approval bills must use Delete Bill. Uses Clio's official DELETE bill operation and requires Billing write permission."
155353
+ }
155354
+ ],
155355
+ "triggers": [],
155356
+ "authConfigDetails": [
155357
+ {
155358
+ "mode": "OAUTH2",
155359
+ "name": "clio_manage_oauth2",
155360
+ "fields": {
155361
+ "auth_config_creation": {
155362
+ "required": [
155363
+ {
155364
+ "name": "client_id",
155365
+ "displayName": "Client id",
155366
+ "type": "string",
155367
+ "description": "Client id of the app",
155368
+ "required": true,
155369
+ "default": null
155370
+ },
155371
+ {
155372
+ "name": "client_secret",
155373
+ "displayName": "Client secret",
155374
+ "type": "string",
155375
+ "description": "Client secret of the app",
155376
+ "required": true,
155377
+ "default": null
155378
+ }
155379
+ ],
155380
+ "optional": [
155381
+ {
155382
+ "name": "oauth_redirect_uri",
155383
+ "displayName": "Redirect URI",
155384
+ "type": "string",
155385
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
155386
+ "required": false,
155387
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
155388
+ },
155389
+ {
155390
+ "name": "scopes",
155391
+ "displayName": "Scopes",
155392
+ "type": "string",
155393
+ "description": "Scopes to request from the user, comma separated",
155394
+ "required": false,
155395
+ "default": ""
155396
+ }
155397
+ ]
155398
+ },
155399
+ "connected_account_initiation": {
155400
+ "required": [],
155401
+ "optional": []
155402
+ }
155403
+ }
155404
+ }
155405
+ ]
155406
+ },
155407
{
155408
"slug": "clockify",
155409
"name": "Clockify",
157720
{
157721
"slug": "CLOUDFLARE_MCP_EXECUTE",
157722
"name": "Execute",
154326
- "description": "Execute JavaScript code against the Cloudflare API. First use the 'search' tool to find the right endpoints, then write code using the cloudflare.request() function.\n\nAvailable in your code:\n\ninterface CloudflareRequestOptions {\n method: \"GET\" | \"POST\" | \"PUT\" | \"PATCH\" | \"DELETE\";\n path: string;\n query?: Record<string, string | number | boolean | undefined>;\n body?: unknown;\n contentType?: string; // Custom Content-Type header (defaults to application/json if body is present)\n rawBody?: boolean; // If true, sends body as-is without JSON.stringify\n}\n\ninterface CloudflareResponse<T = unknown> {\n success: boolean;\n status: number;\n result: T;\n errors: Array<{ code: number; message: string }>;\n messages: Array<{ code: number; message: string }>;\n result_info?: {\n page: number;\n per_page: number;\n total_pages: number;\n count: number;\n total_count: number;\n };\n}\n\ndeclare const cloudflare: {\n request<T = unknown>(options: CloudflareRequestOptions): Promise<CloudflareResponse<T>>;\n};\n\ndeclare const accountId: string;\n\n// accountId is pre-set to \"e8a40544a7211334b83bf588bbf7dec1\" (Qa@agent51testing.com's Account) — use it directly in API paths.\n\n\nYour code must be an async arrow function that returns the result.\n\nExample: Worker with bindings (requires multipart/form-data):\nasync () => {\n const code = `addEventListener('fetch', e => e.respondWith(MY_KV.get('key').then(v => new Response(v || 'none'))));`;\n const metadata = { body_part: \"script\", bindings: [{ type: \"kv_namespace\", name: \"MY_KV\", namespace_id: \"your-kv-id\" }] };\n const b = `--F${Date.now()}`;\n const body = [`--${b}`, 'Content-Disposition: form-data; name=\"metadata\"', 'Content-Type: application/json', '', JSON.stringify(metadata), `--${b}`, 'Content-Disposition: form-data; name=\"script\"', 'Content-Type: application/javascript', '', code, `--${b}--`].join(\"\\r\\n\");\n return cloudflare.request({ method: \"PUT\", path: `/accounts/${accountId}/workers/scripts/my-worker`, body, contentType: `multipart/form-data; boundary=${b}`, rawBody: true });\n}"
157723
+ "description": "Execute JavaScript against the Cloudflare API using the authenticated Cloudflare connection. Use CLOUDFLARE_MCP_SEARCH first to identify the correct endpoint, method, parameters, and request body. For account-scoped endpoints, provide the relevant Cloudflare account ID through the account_id input; it is available inside the function as accountId. Never hard-code account identifiers or credentials. The submitted code must be an async arrow function that returns the result of cloudflare.request(...)."
157724
},
157725
{
157726
"slug": "CLOUDFLARE_MCP_SEARCH",
166499
}
166500
]
166501
},
166502
+ {
166503
+ "slug": "craft_mcp",
166504
+ "name": "Craft MCP",
166505
+ "logo": "https://logos.composio.dev/api/craft_mcp",
166506
+ "description": "Craft MCP lets agents search, read, create, update, and delete authorized Craft documents, daily notes, tasks, collections, and structured workspace content.",
166507
+ "category": "model context protocol",
166508
+ "authSchemes": [
166509
+ "DCR_OAUTH"
166510
+ ],
166511
+ "toolCount": 3,
166512
+ "triggerCount": 0,
166513
+ "version": "20260902_00",
166514
+ "tools": [
166515
+ {
166516
+ "slug": "CRAFT_MCP_BLOCKS_REVERT",
166517
+ "name": "Blocks revert",
166518
+ "description": "Reverts a previous mutation if blocks haven't been modified since. Used by widgets for undo/redo functionality."
166519
+ },
166520
+ {
166521
+ "slug": "CRAFT_MCP_CRAFT_READ",
166522
+ "name": "Craft read",
166523
+ "description": "Read/search Craft; batch with semicolons.\nKeywords: find/open/read/search docs/pages/cards/blocks, daily notes, tasks/inbox/logbook, folders/spaces, collections/tables/schema/items/fields/relations, links/URLs/richUrl, images/files/videos, themes/washi.\nCmds:\n folders list [--filter <regex>]\n folders explore-icons <term>\n documents list [--location unsorted|trash|templates|daily_notes | --folder <folderId>]\n documents resolve-link <url> -> rootBlockId for blocks/write commands\n tasks list [--scope active|upcoming|inbox|logbook|document|all] # all = every task block in full-space, not a union of other scopes\n blocks get <rootBlockId> [--depth <depth>] [--format json|markdown]\n blocks get --date today\n blocks explore-themes --type page|fonts|code\n blocks explore-washi\n blocks search-unsplash <query>\n collections list [--document <rootBlockId>]\n collections schema --collection <collectionId>\n collections items-get --collection <collectionId>\n collections views-list --collection <collectionId>\n connection info\n whiteboards elements get --whiteboard <whiteboardId>\n images view --url <image-url>\n search <query> [--location unsorted|trash|templates|daily_notes]\nCommon flags: --offset, --cursor, --filter <regex>, --format json|markdown. Help: \"<entity> <action> --help\". Example batch: folders list; documents list; blocks get ABC-123 --format markdown For Craft links, run 'documents resolve-link <url>' first; use returned rootBlockId for blocks get/write commands, not raw URL documentId."
166524
+ },
166525
+ {
166526
+ "slug": "CRAFT_MCP_CRAFT_WRITE",
166527
+ "name": "Craft write",
166528
+ "description": "Write; batch semicolons. docs blocks daily notes tasks todos folders collections tables schema items links files; add append update rename delete trash move reorder repeat\nCmds:\n folders create --name <name> [--parent <folderId>] [--icon <emoji>]\n documents create --title <requestedTitle> [--destination unsorted|templates | --folder <folderId>]\n tasks add --markdown <text> [--state todo|done|canceled] [--schedule <date>] [--deadline <date>]\n tasks update --id <taskId> [--state done] [--markdown <text>]\n tasks delete --id <taskId>\n blocks add --id <pageId> --markdown <text> [--position start|end]\n blocks add --siblingId <blockId> --markdown <text> [--position before|after]\n blocks update --id <blockId> --markdown <text>\n blocks delete --id <blockId>\n blocks move --id <blockId> --targetId <pageId> [--position start|end]\n collections create --name <name> --title <titleColumn> --<Property> <type> --document <rootBlockId>\n collections rename --collection <collectionId> --name <name>\n collections items-add --collection <collectionId> --<PropertyName> <value>\n collections items-update --collection <collectionId> --id <itemId> --<PropertyName> <value>\n collections items-delete --collection <collectionId> --id <itemId>\n collections views-create/update/delete/set-active --collection <collectionId> ...\n comments add --comments '[{\"blockId\":\"blockId\",\"content\":\"text\"}]'\n whiteboards create [--position <json>]; whiteboards elements add/update/delete --whiteboard <whiteboardId> ...\nMD: MCP command text needs actual newline chars; not to type backslash-n text for rows; \\n\\n=blocks. After + Toggle, rewrite child text as \" - child\"; never plain/flush-left. update:first replaces;rest inserts. Style:--theme-id,--font,--separator,--washi-pattern,--cover-url,--backdrop-type/color(s)/url,--cover-crop. IDs:resolve;rootBlockId!=URL docId. Coll:schema;prop:. Date YYYY-MM-DD/today/tomorrow/yesterday. Ext:<callout>,+ Toggle,> quote. Help:<entity> <action> --help"
166529
+ }
166530
+ ],
166531
+ "triggers": [],
166532
+ "authConfigDetails": [
166533
+ {
166534
+ "mode": "DCR_OAUTH",
166535
+ "name": "craft_mcp_DCR_OAuth",
166536
+ "fields": {
166537
+ "auth_config_creation": {
166538
+ "required": [],
166539
+ "optional": [
166540
+ {
166541
+ "name": "client_id",
166542
+ "displayName": "Client id",
166543
+ "type": "string",
166544
+ "description": "Client id of the app",
166545
+ "required": false,
166546
+ "default": null
166547
+ },
166548
+ {
166549
+ "name": "client_secret",
166550
+ "displayName": "Client secret",
166551
+ "type": "string",
166552
+ "description": "Client secret of the app",
166553
+ "required": false,
166554
+ "default": null
166555
+ },
166556
+ {
166557
+ "name": "oauth_redirect_uri",
166558
+ "displayName": "Redirect URI",
166559
+ "type": "string",
166560
+ "description": "Add this Redirect URL to your app's OAuth allow list.",
166561
+ "required": false,
166562
+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"
166563
+ },
166564
+ {
166565
+ "name": "scopes",
166566
+ "displayName": "Scopes",
166567
+ "type": "string",
166568
+ "description": "Scopes to request from the user, comma separated",
166569
+ "required": false,
166570
+ "default": ""
166571
+ }
166572
+ ]
166573
+ },
166574
+ "connected_account_initiation": {
166575
+ "required": [],
166576
+ "optional": []
166577
+ }
166578
+ }
166579
+ }
166580
+ ]
166581
+ },
166582
{
166583
"slug": "craftmypdf",
166584
"name": "Craftmypdf",
177453
],
177454
"toolCount": 3,
177455
"triggerCount": 0,
173979
- "version": "20260225_01",
177456
+ "version": "20260904_00",
177457
"tools": [
177458
{
177459
"slug": "DEEPWIKI_MCP_ASK_QUESTION",
177460
"name": "Ask question",
173984
- "description": "Ask any question about a GitHub repository and get an AI-powered, context-grounded response.\n\nArgs:\n repoName: GitHub repository or list of repositories (max 10) in owner/repo format\n question: The question to ask about the repository"
177461
+ "description": "Ask any question about a GitHub repository and get an AI-powered, context-grounded response."
177462
},
177463
{
177464
"slug": "DEEPWIKI_MCP_READ_WIKI_CONTENTS",
177465
"name": "Read wiki contents",
173989
- "description": "View documentation about a GitHub repository.\n\nArgs:\n repoName: GitHub repository in owner/repo format (e.g. \"facebook/react\")"
177466
+ "description": "View documentation about a GitHub repository."
177467
},
177468
{
177469
"slug": "DEEPWIKI_MCP_READ_WIKI_STRUCTURE",
177470
"name": "Read wiki structure",
173994
- "description": "Get a list of documentation topics for a GitHub repository.\n\nArgs:\n repoName: GitHub repository in owner/repo format (e.g. \"facebook/react\")"
177471
+ "description": "Get a list of documentation topics for a GitHub repository."
177472
}
177473
],
177474
"triggers": [],
177952
}
177953
]
177954
},
177955
+ {
177956
+ "slug": "descript_mcp",
177957
+ "name": "Descript MCP",
This file is too large to show in full.