Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs: update toolkits, API spec, and meta tools data (#4330)
sdkrelease[bot]80867a09bce1
diff --git a/docs/content/reference/api-reference/api-keys/index.mdx b/docs/content/reference/api-reference/api-keys/index.mdxindex 7c31c2be6..4949d7981 100644--- a/docs/content/reference/api-reference/api-keys/index.mdx+++ b/docs/content/reference/api-reference/api-keys/index.mdx@@ -9,4 +9,4 @@ API key management## Endpoints-<ApiEndpointsTable endpoints={[{"method":"POST","pathV31":"/api/v3.1/api_key_revocation","pathV3":"/api/v3/api_key_revocation","summary":"Publicly revoke leaked Composio API keys","href":"/reference/api-reference/api-keys/postApiKeyRevocation"}]} />+<ApiEndpointsTable endpoints={[{"method":"POST","pathV31":"/api/v3.1/api_key_revocation","pathV3":"/api/v3/api_key_revocation","summary":"Revoke Composio API keys","href":"/reference/api-reference/api-keys/postApiKeyRevocation"}]} />diff --git a/docs/content/reference/api-reference/toolkits/index.mdx b/docs/content/reference/api-reference/toolkits/index.mdxindex e9be190e5..723505149 100644--- a/docs/content/reference/api-reference/toolkits/index.mdx+++ b/docs/content/reference/api-reference/toolkits/index.mdx@@ -25,4 +25,4 @@ To browse toolkits visually, see the [toolkits catalog](/toolkits). For the conc## Endpoints-<ApiEndpointsTable endpoints={[{"method":"DELETE","pathV31":"/api/v3.1/custom/toolkits/{slug}","pathV3":"/api/v3/custom/toolkits/{slug}","summary":"Delete a custom toolkit","href":"/reference/api-reference/toolkits/deleteCustomToolkitsBySlug"},{"method":"POST","pathV31":"/api/v3.1/toolkits/{toolkit_slug}/scopes/recommended","pathV3":"/api/v3/toolkits/{toolkit_slug}/scopes/recommended","summary":"Get required scopes","href":"/reference/api-reference/toolkits/recommendToolkitScopes"},{"method":"GET","pathV31":"/api/v3.1/toolkits/{toolkit_slug}/scopes/grant_context","pathV3":"/api/v3/toolkits/{toolkit_slug}/scopes/grant_context","summary":"List grant_context options","href":"/reference/api-reference/toolkits/recommendToolkitScopesGrantContext"},{"method":"GET","pathV31":"/api/v3.1/toolkits","pathV3":"/api/v3/toolkits","summary":"List available toolkits","href":"/reference/api-reference/toolkits/getToolkits"},{"method":"GET","pathV31":"/api/v3.1/toolkits/categories","pathV3":"/api/v3/toolkits/categories","summary":"List toolkit categories","href":"/reference/api-reference/toolkits/getToolkitsCategories"},{"method":"POST","pathV31":"/api/v3.1/custom/toolkits/upsert","pathV3":"/api/v3/custom/toolkits/upsert","summary":"Upsert a custom toolkit","href":"/reference/api-reference/toolkits/postCustomToolkitsUpsert"},{"method":"POST","pathV31":"/api/v3.1/custom/toolkits/sync","pathV3":"/api/v3/custom/toolkits/sync","summary":"Sync a custom toolkit","href":"/reference/api-reference/toolkits/postCustomToolkitsSync"},{"method":"GET","pathV31":"/api/v3.1/toolkits/{slug}","pathV3":"/api/v3/toolkits/{slug}","summary":"Get toolkit by slug","href":"/reference/api-reference/toolkits/getToolkitsBySlug"},{"method":"POST","pathV31":"/api/v3.1/toolkits/multi","pathV3":"/api/v3/toolkits/multi","summary":"Fetch multiple toolkits","href":"/reference/api-reference/toolkits/postToolkitsMulti"},{"method":"GET","pathV31":"/api/v3.1/toolkits/changelog","pathV3":"/api/v3/toolkits/changelog","summary":"Get toolkits changelog","href":"/reference/api-reference/toolkits/getToolkitsChangelog"}]} />+<ApiEndpointsTable endpoints={[{"method":"DELETE","pathV31":"/api/v3.1/custom/toolkits/{slug}","pathV3":"/api/v3/custom/toolkits/{slug}","summary":"Delete a custom toolkit","href":"/reference/api-reference/toolkits/deleteCustomToolkitsBySlug"},{"method":"POST","pathV31":"/api/v3.1/toolkits/{toolkit_slug}/scopes/recommended","pathV3":"/api/v3/toolkits/{toolkit_slug}/scopes/recommended","summary":"Get required scopes","href":"/reference/api-reference/toolkits/recommendToolkitScopes"},{"method":"GET","pathV31":"/api/v3.1/toolkits/{toolkit_slug}/scopes/grant_context","pathV3":"/api/v3/toolkits/{toolkit_slug}/scopes/grant_context","summary":"List grant contexts","href":"/reference/api-reference/toolkits/recommendToolkitScopesGrantContext"},{"method":"GET","pathV31":"/api/v3.1/toolkits","pathV3":"/api/v3/toolkits","summary":"List available toolkits","href":"/reference/api-reference/toolkits/getToolkits"},{"method":"GET","pathV31":"/api/v3.1/toolkits/categories","pathV3":"/api/v3/toolkits/categories","summary":"List toolkit categories","href":"/reference/api-reference/toolkits/getToolkitsCategories"},{"method":"POST","pathV31":"/api/v3.1/custom/toolkits/upsert","pathV3":"/api/v3/custom/toolkits/upsert","summary":"Upsert a custom toolkit","href":"/reference/api-reference/toolkits/postCustomToolkitsUpsert"},{"method":"POST","pathV31":"/api/v3.1/custom/toolkits/sync","pathV3":"/api/v3/custom/toolkits/sync","summary":"Sync a custom toolkit","href":"/reference/api-reference/toolkits/postCustomToolkitsSync"},{"method":"GET","pathV31":"/api/v3.1/toolkits/{slug}","pathV3":"/api/v3/toolkits/{slug}","summary":"Get toolkit by slug","href":"/reference/api-reference/toolkits/getToolkitsBySlug"},{"method":"POST","pathV31":"/api/v3.1/toolkits/multi","pathV3":"/api/v3/toolkits/multi","summary":"Fetch multiple toolkits","href":"/reference/api-reference/toolkits/postToolkitsMulti"},{"method":"GET","pathV31":"/api/v3.1/toolkits/changelog","pathV3":"/api/v3/toolkits/changelog","summary":"Get toolkits changelog","href":"/reference/api-reference/toolkits/getToolkitsChangelog"}]} />diff --git a/docs/content/reference/api-reference/tools/index.mdx b/docs/content/reference/api-reference/tools/index.mdxindex 4ed3960e5..7bf3f5e7f 100644--- a/docs/content/reference/api-reference/tools/index.mdx+++ b/docs/content/reference/api-reference/tools/index.mdx@@ -52,4 +52,4 @@ Proxy execute is a form of [direct tool execution](/docs/sessions-vs-direct-exec## Endpoints-<ApiEndpointsTable endpoints={[{"method":"GET","pathV31":"/api/v3.1/tools","pathV3":"/api/v3/tools","summary":"List available tools","href":"/reference/api-reference/tools/getTools"},{"method":"GET","pathV31":"/api/v3.1/tools/enum","pathV3":"/api/v3/tools/enum","summary":"Get tool enum list","href":"/reference/api-reference/tools/getToolsEnum"},{"method":"GET","pathV31":"/api/v3.1/tools/{tool_slug}","pathV3":"/api/v3/tools/{tool_slug}","summary":"Get tool by slug","href":"/reference/api-reference/tools/getToolsByToolSlug"},{"method":"POST","pathV31":"/api/v3.1/tools/execute/{tool_slug}","pathV3":"/api/v3/tools/execute/{tool_slug}","summary":"Execute tool","href":"/reference/api-reference/tools/postToolsExecuteByToolSlug"},{"method":"POST","pathV31":"/api/v3.1/tools/execute/{tool_slug}/input","pathV3":"/api/v3/tools/execute/{tool_slug}/input","summary":"Generate tool inputs from natural language","href":"/reference/api-reference/tools/postToolsExecuteByToolSlugInput"},{"method":"POST","pathV31":"/api/v3.1/tools/execute/proxy","pathV3":"/api/v3/tools/execute/proxy","summary":"Execute proxy request","href":"/reference/api-reference/tools/postToolsExecuteProxy"},{"method":"POST","pathV31":"/api/v3.1/tools/scopes/required","pathV3":"/api/v3/tools/scopes/required","summary":"Get required scopes for tools","href":"/reference/api-reference/tools/postToolsScopesRequired"}]} />+<ApiEndpointsTable endpoints={[{"method":"GET","pathV31":"/api/v3.1/tools","pathV3":"/api/v3/tools","summary":"List available tools","href":"/reference/api-reference/tools/getTools"},{"method":"GET","pathV31":"/api/v3.1/tools/enum","pathV3":"/api/v3/tools/enum","summary":"Get tool enum list","href":"/reference/api-reference/tools/getToolsEnum"},{"method":"GET","pathV31":"/api/v3.1/tools/{tool_slug}","pathV3":"/api/v3/tools/{tool_slug}","summary":"Get tool by slug","href":"/reference/api-reference/tools/getToolsByToolSlug"},{"method":"POST","pathV31":"/api/v3.1/tools/execute/{tool_slug}","pathV3":"/api/v3/tools/execute/{tool_slug}","summary":"Execute tool","href":"/reference/api-reference/tools/postToolsExecuteByToolSlug"},{"method":"POST","pathV31":"/api/v3.1/tools/execute/{tool_slug}/input","pathV3":"/api/v3/tools/execute/{tool_slug}/input","summary":"Generate tool inputs from natural language","href":"/reference/api-reference/tools/postToolsExecuteByToolSlugInput"},{"method":"POST","pathV31":"/api/v3.1/tools/execute/proxy","pathV3":"/api/v3/tools/execute/proxy","summary":"Execute proxy request","href":"/reference/api-reference/tools/postToolsExecuteProxy"},{"method":"POST","pathV31":"/api/v3.1/tools/scopes/required","pathV3":"/api/v3/tools/scopes/required","summary":"Get required scopes for tools (DEPRECATED)","href":"/reference/api-reference/tools/postToolsScopesRequired","legacy":true}]} />diff --git a/docs/public/data/toolkits-list.json b/docs/public/data/toolkits-list.jsonindex f27df6207..0324ecffa 100644--- a/docs/public/data/toolkits-list.json+++ b/docs/public/data/toolkits-list.json@@ -149,7 +149,7 @@"logo": "https://logos.composio.dev/api/jira","category": "project management","toolCount": 102,- "triggerCount": 3+ "triggerCount": 17},{"slug": "firecrawl",@@ -389,7 +389,7 @@"logo": "https://logos.composio.dev/api/trello","category": "project management","toolCount": 329,- "triggerCount": 5+ "triggerCount": 20},{"slug": "apollo",@@ -461,7 +461,7 @@"logo": "https://logos.composio.dev/api/stripe","category": "payment processing","toolCount": 432,- "triggerCount": 7+ "triggerCount": 20},{"slug": "klaviyo",@@ -748,7 +748,7 @@"name": "Meta Ads","logo": "https://logos.composio.dev/api/metaads","category": "ads & conversion",- "toolCount": 53,+ "toolCount": 56,"triggerCount": 0},{@@ -764,7 +764,7 @@"name": "Google Super","logo": "https://logos.composio.dev/api/googlesuper","category": "file management & storage",- "toolCount": 467,+ "toolCount": 473,"triggerCount": 20},{@@ -868,7 +868,7 @@"name": "Google Ads","logo": "https://logos.composio.dev/api/googleads","category": "ads & conversion",- "toolCount": 22,+ "toolCount": 28,"triggerCount": 0},{@@ -1092,7 +1092,7 @@"name": "Facebook","logo": "https://logos.composio.dev/api/facebook","category": "social media accounts",- "toolCount": 43,+ "toolCount": 44,"triggerCount": 0},{@@ -1815,6 +1815,14 @@"toolCount": 42,"triggerCount": 0},+ {+ "slug": "twitch",+ "name": "Twitch",+ "logo": "https://logos.composio.dev/api/twitch",+ "category": "video & audio",+ "toolCount": 149,+ "triggerCount": 0+ },{"slug": "datadog","name": "Datadog",@@ -2103,6 +2111,14 @@"toolCount": 10,"triggerCount": 0},+ {+ "slug": "airwallex",+ "name": "Airwallex",+ "logo": "https://logos.composio.dev/api/airwallex",+ "category": "payment processing",+ "toolCount": 7,+ "triggerCount": 0+ },{"slug": "aivoov","name": "Aivoov",@@ -2807,6 +2823,14 @@"toolCount": 26,"triggerCount": 0},+ {+ "slug": "bluepillow",+ "name": "Blue Pillow Hotels & Stays",+ "logo": "https://logos.composio.dev/api/bluepillow",+ "category": "ai agents",+ "toolCount": 8,+ "triggerCount": 0+ },{"slug": "bluebarry","name": "Bluebarry",@@ -2967,6 +2991,14 @@"toolCount": 17,"triggerCount": 0},+ {+ "slug": "braze",+ "name": "Braze",+ "logo": "https://logos.composio.dev/api/braze",+ "category": "marketing automation",+ "toolCount": 119,+ "triggerCount": 0+ },{"slug": "bread_butter","name": "Bread & Butter",@@ -3159,6 +3191,14 @@"toolCount": 38,"triggerCount": 0},+ {+ "slug": "calendly_mcp",+ "name": "Calendly MCP",+ "logo": "https://logos.composio.dev/api/calendly_mcp",+ "category": "model context protocol",+ "toolCount": 36,+ "triggerCount": 0+ },{"slug": "callerapi","name": "Callerapi",@@ -3215,6 +3255,14 @@"toolCount": 14,"triggerCount": 0},+ {+ "slug": "candid_mcp",+ "name": "Candid MCP",+ "logo": "https://logos.composio.dev/api/candid_mcp",+ "category": "model context protocol",+ "toolCount": 6,+ "triggerCount": 0+ },{"slug": "canny","name": "Canny",@@ -3399,6 +3447,14 @@"toolCount": 3,"triggerCount": 0},+ {+ "slug": "chartmogul",+ "name": "ChartMogul",+ "logo": "https://logos.composio.dev/api/chartmogul",+ "category": "analytics",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "chaser","name": "Chaser",@@ -3487,6 +3543,14 @@"toolCount": 14,"triggerCount": 0},+ {+ "slug": "clarify_mcp",+ "name": "Clarify MCP",+ "logo": "https://logos.composio.dev/api/clarify_mcp",+ "category": "model context protocol",+ "toolCount": 46,+ "triggerCount": 0+ },{"slug": "clarity_ai_mcp","name": "Clarity AI MCP",@@ -3503,6 +3567,14 @@"toolCount": 28,"triggerCount": 0},+ {+ "slug": "clay_mcp",+ "name": "Clay MCP",+ "logo": "https://logos.composio.dev/api/clay_mcp",+ "category": "model context protocol",+ "toolCount": 17,+ "triggerCount": 0+ },{"slug": "clearout","name": "Clearout",@@ -3559,6 +3631,14 @@"toolCount": 57,"triggerCount": 0},+ {+ "slug": "clio_manage",+ "name": "Clio Manage (US)",+ "logo": "https://logos.composio.dev/api/clio_manage",+ "category": "crm",+ "toolCount": 99,+ "triggerCount": 0+ },{"slug": "clockify","name": "Clockify",@@ -4007,6 +4087,14 @@"toolCount": 11,"triggerCount": 0},+ {+ "slug": "craft_mcp",+ "name": "Craft MCP",+ "logo": "https://logos.composio.dev/api/craft_mcp",+ "category": "model context protocol",+ "toolCount": 3,+ "triggerCount": 0+ },{"slug": "craftmypdf","name": "Craftmypdf",@@ -4319,6 +4407,14 @@"toolCount": 60,"triggerCount": 0},+ {+ "slug": "descript_mcp",+ "name": "Descript MCP",+ "logo": "https://logos.composio.dev/api/descript_mcp",+ "category": "model context protocol",+ "toolCount": 14,+ "triggerCount": 0+ },{"slug": "desktime","name": "DeskTime",@@ -4380,7 +4476,7 @@"name": "Dice MCP","logo": "https://logos.composio.dev/api/dice_mcp","category": "hr talent & recruitment",- "toolCount": 2,+ "toolCount": 3,"triggerCount": 0},{@@ -4583,6 +4679,14 @@"toolCount": 22,"triggerCount": 0},+ {+ "slug": "domotz_mcp",+ "name": "Domotz MCP",+ "logo": "https://logos.composio.dev/api/domotz_mcp",+ "category": "model context protocol",+ "toolCount": 92,+ "triggerCount": 0+ },{"slug": "donately","name": "Donately",@@ -4855,6 +4959,14 @@"toolCount": 20,"triggerCount": 0},+ {+ "slug": "emailvalidation",+ "name": "Emailvalidation",+ "logo": "https://logos.composio.dev/api/emailvalidation",+ "category": "email",+ "toolCount": 2,+ "triggerCount": 0+ },{"slug": "emelia","name": "Emelia",@@ -4943,6 +5055,14 @@"toolCount": 11,"triggerCount": 0},+ {+ "slug": "era_context_mcp",+ "name": "Era Context MCP",+ "logo": "https://logos.composio.dev/api/era_context_mcp",+ "category": "model context protocol",+ "toolCount": 51,+ "triggerCount": 0+ },{"slug": "eranol","name": "Eranol",@@ -5071,6 +5191,14 @@"toolCount": 4,"triggerCount": 0},+ {+ "slug": "explorium",+ "name": "Explorium",+ "logo": "https://logos.composio.dev/api/explorium",+ "category": "ai sales tools",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "explorium_mcp","name": "Explorium MCP",@@ -5239,6 +5367,14 @@"toolCount": 60,"triggerCount": 0},+ {+ "slug": "finlight",+ "name": "Finlight",+ "logo": "https://logos.composio.dev/api/finlight",+ "category": "news & lifestyle",+ "toolCount": 3,+ "triggerCount": 0+ },{"slug": "finmei","name": "Finmei",@@ -5431,6 +5567,14 @@"toolCount": 20,"triggerCount": 0},+ {+ "slug": "formilla",+ "name": "Formilla",+ "logo": "https://logos.composio.dev/api/formilla",+ "category": "customer support",+ "toolCount": 1,+ "triggerCount": 0+ },{"slug": "fraudlabs_pro","name": "FraudLabs Pro",@@ -5519,6 +5663,14 @@"toolCount": 9,"triggerCount": 0},+ {+ "slug": "geekflare",+ "name": "Geekflare",+ "logo": "https://logos.composio.dev/api/geekflare",+ "category": "developer tools",+ "toolCount": 17,+ "triggerCount": 0+ },{"slug": "gelato","name": "Gelato",@@ -5599,6 +5751,14 @@"toolCount": 22,"triggerCount": 0},+ {+ "slug": "getresponse",+ "name": "GetResponse",+ "logo": "https://logos.composio.dev/api/getresponse",+ "category": "marketing automation",+ "toolCount": 213,+ "triggerCount": 0+ },{"slug": "get_transcribe","name": "GetTranscribe",@@ -5887,6 +6047,14 @@"toolCount": 11,"triggerCount": 0},+ {+ "slug": "grafana_cloud_mcp",+ "name": "Grafana Cloud MCP",+ "logo": "https://logos.composio.dev/api/grafana_cloud_mcp",+ "category": "model context protocol",+ "toolCount": 118,+ "triggerCount": 0+ },{"slug": "grafbase","name": "Grafbase",@@ -6135,6 +6303,14 @@"toolCount": 14,"triggerCount": 0},+ {+ "slug": "higgsfield_mcp",+ "name": "Higgsfield MCP",+ "logo": "https://logos.composio.dev/api/higgsfield_mcp",+ "category": "model context protocol",+ "toolCount": 89,+ "triggerCount": 0+ },{"slug": "highergov","name": "Highergov",@@ -6183,6 +6359,14 @@"toolCount": 10,"triggerCount": 0},+ {+ "slug": "honcho",+ "name": "Honcho",+ "logo": "https://logos.composio.dev/api/honcho",+ "category": "artificial intelligence",+ "toolCount": 16,+ "triggerCount": 0+ },{"slug": "honeybadger","name": "Honeybadger",@@ -6703,6 +6887,14 @@"toolCount": 18,"triggerCount": 0},+ {+ "slug": "jotform_sign",+ "name": "Jotform Sign",+ "logo": "https://logos.composio.dev/api/jotform_sign",+ "category": "signatures",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "jumpcloud","name": "JumpCloud",@@ -7199,6 +7391,14 @@"toolCount": 10,"triggerCount": 0},+ {+ "slug": "longbridge_mcp",+ "name": "Longbridge MCP",+ "logo": "https://logos.composio.dev/api/longbridge_mcp",+ "category": "model context protocol",+ "toolCount": 162,+ "triggerCount": 0+ },{"slug": "loomio","name": "Loomio",@@ -7223,6 +7423,14 @@"toolCount": 58,"triggerCount": 0},+ {+ "slug": "lucid_mcp",+ "name": "Lucid MCP",+ "logo": "https://logos.composio.dev/api/lucid_mcp",+ "category": "model context protocol",+ "toolCount": 35,+ "triggerCount": 0+ },{"slug": "luma_labs","name": "Luma Labs",@@ -7255,6 +7463,14 @@"toolCount": 22,"triggerCount": 0},+ {+ "slug": "magic_patterns_mcp",+ "name": "Magic Patterns MCP",+ "logo": "https://logos.composio.dev/api/magic_patterns_mcp",+ "category": "model context protocol",+ "toolCount": 23,+ "triggerCount": 0+ },{"slug": "magicslides","name": "MagicSlides",@@ -7431,6 +7647,14 @@"toolCount": 3,"triggerCount": 0},+ {+ "slug": "marcopolo_mcp",+ "name": "MarcoPolo MCP",+ "logo": "https://logos.composio.dev/api/marcopolo_mcp",+ "category": "model context protocol",+ "toolCount": 5,+ "triggerCount": 0+ },{"slug": "marketstack","name": "Marketstack",@@ -7575,6 +7799,14 @@"toolCount": 22,"triggerCount": 0},+ {+ "slug": "midpage_mcp",+ "name": "Midpage MCP",+ "logo": "https://logos.composio.dev/api/midpage_mcp",+ "category": "model context protocol",+ "toolCount": 7,+ "triggerCount": 0+ },{"slug": "mighty_networks","name": "Mighty Networks",@@ -8079,6 +8311,14 @@"toolCount": 3,"triggerCount": 0},+ {+ "slug": "octagon_mcp",+ "name": "Octagon MCP",+ "logo": "https://logos.composio.dev/api/octagon_mcp",+ "category": "model context protocol",+ "toolCount": 4,+ "triggerCount": 0+ },{"slug": "odoo","name": "Odoo",@@ -8207,6 +8447,14 @@"toolCount": 7,"triggerCount": 0},+ {+ "slug": "openfunnel_agent_primitives",+ "name": "OpenFunnel Agent Primitives",+ "logo": "https://logos.composio.dev/api/openfunnel_agent_primitives",+ "category": "ai sales tools",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "opengraph_io","name": "OpenGraph.io",@@ -8303,6 +8551,14 @@"toolCount": 8,"triggerCount": 0},+ {+ "slug": "otter_ai_mcp",+ "name": "Otter.ai MCP",+ "logo": "https://logos.composio.dev/api/otter_ai_mcp",+ "category": "model context protocol",+ "toolCount": 3,+ "triggerCount": 0+ },{"slug": "outline","name": "Outline",@@ -8423,6 +8679,14 @@"toolCount": 24,"triggerCount": 0},+ {+ "slug": "particl_mcp",+ "name": "Particl MCP",+ "logo": "https://logos.composio.dev/api/particl_mcp",+ "category": "model context protocol",+ "toolCount": 18,+ "triggerCount": 0+ },{"slug": "passcreator","name": "Passcreator",@@ -8439,6 +8703,14 @@"toolCount": 8,"triggerCount": 0},+ {+ "slug": "paychasers",+ "name": "PayChasers",+ "logo": "https://logos.composio.dev/api/paychasers",+ "category": "payment processing",+ "toolCount": 7,+ "triggerCount": 0+ },{"slug": "payhere","name": "Payhere",@@ -8471,6 +8743,30 @@"toolCount": 112,"triggerCount": 0},+ {+ "slug": "pdf_blocks",+ "name": "PDF Blocks",+ "logo": "https://logos.composio.dev/api/pdf_blocks",+ "category": "documents",+ "toolCount": 17,+ "triggerCount": 0+ },+ {+ "slug": "pdf_munk",+ "name": "PDF Munk",+ "logo": "https://logos.composio.dev/api/pdf_munk",+ "category": "documents",+ "toolCount": 9,+ "triggerCount": 0+ },+ {+ "slug": "pdf_vector",+ "name": "PDF Vector",+ "logo": "https://logos.composio.dev/api/pdf_vector",+ "category": "ai document extraction",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "pdf_api_io","name": "PDF-API.io",@@ -8527,6 +8823,14 @@"toolCount": 9,"triggerCount": 0},+ {+ "slug": "peec_ai_mcp",+ "name": "Peec AI MCP",+ "logo": "https://logos.composio.dev/api/peec_ai_mcp",+ "category": "model context protocol",+ "toolCount": 79,+ "triggerCount": 0+ },{"slug": "peerdom","name": "Peerdom",@@ -8687,6 +8991,14 @@"toolCount": 11,"triggerCount": 0},+ {+ "slug": "plaid_mcp",+ "name": "Plaid MCP",+ "logo": "https://logos.composio.dev/api/plaid_mcp",+ "category": "model context protocol",+ "toolCount": 5,+ "triggerCount": 0+ },{"slug": "plain","name": "Plain",@@ -9247,6 +9559,14 @@"toolCount": 2,"triggerCount": 0},+ {+ "slug": "read_ai_mcp",+ "name": "Read AI MCP",+ "logo": "https://logos.composio.dev/api/read_ai_mcp",+ "category": "model context protocol",+ "toolCount": 4,+ "triggerCount": 0+ },{"slug": "readwise_reader","name": "Readwise Reader",@@ -9420,7 +9740,7 @@"name": "Resend","logo": "https://logos.composio.dev/api/resend","category": "email",- "toolCount": 62,+ "toolCount": 66,"triggerCount": 0},{@@ -9447,6 +9767,14 @@"toolCount": 7,"triggerCount": 0},+ {+ "slug": "retable",+ "name": "Retable",+ "logo": "https://logos.composio.dev/api/retable",+ "category": "spreadsheets",+ "toolCount": 11,+ "triggerCount": 0+ },{"slug": "retailed","name": "Retailed",@@ -9471,14 +9799,6 @@"toolCount": 15,"triggerCount": 0},- {- "slug": "rev_ai",- "name": "Rev AI",- "logo": "https://logos.composio.dev/api/rev_ai",- "category": "artificial intelligence",- "toolCount": 11,- "triggerCount": 0- },{"slug": "rev","name": "Rev AI",@@ -9487,6 +9807,14 @@"toolCount": 36,"triggerCount": 0},+ {+ "slug": "rev_ai",+ "name": "Rev AI",+ "logo": "https://logos.composio.dev/api/rev_ai",+ "category": "artificial intelligence",+ "toolCount": 11,+ "triggerCount": 0+ },{"slug": "revolt","name": "Revolt",@@ -9695,6 +10023,14 @@"toolCount": 27,"triggerCount": 0},+ {+ "slug": "scorecard_mcp",+ "name": "Scorecard MCP",+ "logo": "https://logos.composio.dev/api/scorecard_mcp",+ "category": "model context protocol",+ "toolCount": 2,+ "triggerCount": 0+ },{"slug": "scrape_do","name": "Scrape Do",@@ -10463,14 +10799,6 @@"toolCount": 10,"triggerCount": 0},- {- "slug": "strava",- "name": "Strava",- "logo": "https://logos.composio.dev/api/strava",- "category": "fitness",- "toolCount": 36,- "triggerCount": 0- },{"slug": "streamtime","name": "Streamtime",@@ -10495,6 +10823,14 @@"toolCount": 57,"triggerCount": 0},+ {+ "slug": "stytch_mcp",+ "name": "Stytch MCP",+ "logo": "https://logos.composio.dev/api/stytch_mcp",+ "category": "model context protocol",+ "toolCount": 21,+ "triggerCount": 0+ },{"slug": "suitedash","name": "Suitedash",@@ -10623,6 +10959,14 @@"toolCount": 79,"triggerCount": 0},+ {+ "slug": "tableau",+ "name": "Tableau",+ "logo": "https://logos.composio.dev/api/tableau",+ "category": "analytics",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "taggun","name": "Taggun",@@ -10631,6 +10975,14 @@"toolCount": 14,"triggerCount": 0},+ {+ "slug": "tailscale",+ "name": "Tailscale",+ "logo": "https://logos.composio.dev/api/tailscale",+ "category": "it operations",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "talenthr","name": "Talenthr",@@ -10759,6 +11111,14 @@"toolCount": 29,"triggerCount": 0},+ {+ "slug": "thecompaniesapi",+ "name": "The Companies API",+ "logo": "https://logos.composio.dev/api/thecompaniesapi",+ "category": "business intelligence",+ "toolCount": 10,+ "triggerCount": 0+ },{"slug": "the_odds_api","name": "The Odds API",@@ -10980,7 +11340,7 @@"name": "Trivago MCP","logo": "https://logos.composio.dev/api/trivago_mcp","category": "scheduling & booking",- "toolCount": 2,+ "toolCount": 3,"triggerCount": 0},{@@ -11031,6 +11391,14 @@"toolCount": 107,"triggerCount": 0},+ {+ "slug": "twenty",+ "name": "Twenty",+ "logo": "https://logos.composio.dev/api/twenty",+ "category": "crm",+ "toolCount": 8,+ "triggerCount": 0+ },{"slug": "twittershots","name": "TwitterShots",@@ -11199,6 +11567,14 @@"toolCount": 44,"triggerCount": 0},+ {+ "slug": "vantage_mcp",+ "name": "Vantage MCP",+ "logo": "https://logos.composio.dev/api/vantage_mcp",+ "category": "model context protocol",+ "toolCount": 127,+ "triggerCount": 0+ },{"slug": "vapi","name": "Vapi",@@ -11319,6 +11695,14 @@"toolCount": 11,"triggerCount": 0},+ {+ "slug": "vimeo",+ "name": "Vimeo",+ "logo": "https://logos.composio.dev/api/vimeo",+ "category": "video & audio",+ "toolCount": 50,+ "triggerCount": 0+ },{"slug": "viral_loops","name": "Viral Loops",@@ -11479,6 +11863,14 @@"toolCount": 3,"triggerCount": 0},+ {+ "slug": "wise",+ "name": "Wise",+ "logo": "https://logos.composio.dev/api/wise",+ "category": "payment processing",+ "toolCount": 9,+ "triggerCount": 0+ },{"slug": "wisepops","name": "Wisepops",diff --git a/docs/public/data/toolkits.json b/docs/public/data/toolkits.jsonindex edbee796d..8df401894 100644--- a/docs/public/data/toolkits.json+++ b/docs/public/data/toolkits.json@@ -13,7 +13,7 @@],"toolCount": 63,"triggerCount": 2,- "version": "20260828_00",+ "version": "20260903_00","tools": [{"slug": "GMAIL_ADD_LABEL_TO_EMAIL",@@ -535,7 +535,7 @@],"toolCount": 893,"triggerCount": 20,- "version": "20260831_00",+ "version": "20260902_00","tools": [{"slug": "GITHUB_ABORT_REPOSITORY_MIGRATION",@@ -5170,7 +5170,7 @@],"toolCount": 49,"triggerCount": 7,- "version": "20260826_00",+ "version": "20260902_00","tools": [{"slug": "GOOGLECALENDAR_ACL_DELETE",@@ -5934,7 +5934,7 @@],"toolCount": 53,"triggerCount": 16,- "version": "20260826_00",+ "version": "20260902_00","tools": [{"slug": "GOOGLESHEETS_ADD_SHEET",@@ -8072,7 +8072,7 @@],"toolCount": 305,"triggerCount": 5,- "version": "20260901_00",+ "version": "20260903_00","tools": [{"slug": "OUTLOOK_ACCEPT_EVENT",@@ -10312,7 +10312,7 @@],"toolCount": 90,"triggerCount": 7,- "version": "20260826_00",+ "version": "20260902_00","tools": [{"slug": "GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE",@@ -12540,7 +12540,7 @@],"toolCount": 47,"triggerCount": 12,- "version": "20260819_00",+ "version": "20260908_00","tools": [{"slug": "LINEAR_ARCHIVE_ISSUE",@@ -12619,8 +12619,8 @@},{"slug": "LINEAR_GET_ATTACHMENT",- "name": "Download issue attachments",- "description": "Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension."+ "name": "Download issue files",+ "description": "Downloads a Linear Attachment record or a private upload embedded in issue/comment Markdown; `file_name` must include the correct extension."},{"slug": "LINEAR_GET_COMMENT",@@ -12645,7 +12645,7 @@{"slug": "LINEAR_GET_LINEAR_ISSUE","name": "Get Linear issue",- "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."+ "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."},{"slug": "LINEAR_GET_LINEAR_PROJECT",@@ -12929,7 +12929,7 @@],"toolCount": 26,"triggerCount": 6,- "version": "20260828_00",+ "version": "20260902_00","tools": [{"slug": "AIRTABLE_CREATE_BASE",@@ -13521,8 +13521,8 @@"OAUTH2"],"toolCount": 102,- "triggerCount": 3,- "version": "20260828_00",+ "triggerCount": 17,+ "version": "20260908_00","tools": [{"slug": "JIRA_ADD_ATTACHMENT",@@ -14037,19 +14037,89 @@],"triggers": [{- "slug": "JIRA_NEW_ISSUE_TRIGGER",- "name": "New Issue",- "description": "Fires when a new issue is created in the Jira project you configure.\n\nOnly issues created in that project produce an event."+ "slug": "JIRA_COMMENT_CREATED",+ "name": "Comment Created",+ "description": "Triggers when a comment is posted on a Jira issue. Can deliver comments\non issues the connected account cannot open in Jira itself."+ },+ {+ "slug": "JIRA_COMMENT_DELETED",+ "name": "Comment Deleted",+ "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."+ },+ {+ "slug": "JIRA_COMMENT_UPDATED",+ "name": "Comment Updated",+ "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."+ },+ {+ "slug": "JIRA_ISSUE_CREATED",+ "name": "Issue Created",+ "description": "Triggers when an issue is created in Jira, including a sub-task. Can\ndeliver issues the connected account cannot open in Jira itself."+ },+ {+ "slug": "JIRA_ISSUE_DELETED",+ "name": "Issue Deleted",+ "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."+ },+ {+ "slug": "JIRA_ISSUE_UPDATED",+ "name": "Issue Updated",+ "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."+ },+ {+ "slug": "JIRA_SPRINT_CLOSED",+ "name": "Sprint Closed",+ "description": "Triggers when a sprint is completed and moves into the closed state."+ },+ {+ "slug": "JIRA_SPRINT_CREATED",+ "name": "Sprint Created",+ "description": "Triggers when a sprint is created on a Jira board. Creating a sprint does\nnot start it — watch Sprint Started for that."+ },+ {+ "slug": "JIRA_SPRINT_STARTED",+ "name": "Sprint Started",+ "description": "Triggers when a sprint moves into the active state."},{- "slug": "JIRA_NEW_PROJECT_TRIGGER",- "name": "New Project",- "description": "Triggered when a new project is added in Jira"+ "slug": "JIRA_SPRINT_UPDATED",+ "name": "Sprint Updated",+ "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."},{- "slug": "JIRA_UPDATED_ISSUE_TRIGGER",- "name": "Updated Issue",- "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."+ "slug": "JIRA_VERSION_CREATED",+ "name": "Version Created",+ "description": "Triggers when a project version is created in Jira."+ },+ {+ "slug": "JIRA_VERSION_DELETED",+ "name": "Version Deleted",+ "description": "Triggers when a project version is deleted outright. A version that\ndisappeared because it was merged into another one fires Version Merged\ninstead."+ },+ {+ "slug": "JIRA_VERSION_MERGED",+ "name": "Version Merged",+ "description": "Triggers when a project version is merged into another one, carrying both\nthe version that went away and the one that survived."+ },+ {+ "slug": "JIRA_VERSION_MOVED",+ "name": "Version Moved",+ "description": "Triggers when a project version is reordered within its project's release\nlist."+ },+ {+ "slug": "JIRA_VERSION_RELEASED",+ "name": "Version Released",+ "description": "Triggers when a project version is marked released."+ },+ {+ "slug": "JIRA_VERSION_UNRELEASED",+ "name": "Version Unreleased",+ "description": "Triggers when a released project version is put back to unreleased."+ },+ {+ "slug": "JIRA_VERSION_UPDATED",+ "name": "Version Updated",+ "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."}],"authConfigDetails": [@@ -14211,7 +14281,7 @@],"toolCount": 30,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260903_00","tools": [{"slug": "FIRECRAWL_AGENT_CANCEL",@@ -18468,7 +18538,7 @@],"toolCount": 110,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260903_00","tools": [{"slug": "BITBUCKET_APPROVE_PULL_REQUEST",@@ -19858,7 +19928,7 @@],"toolCount": 22,"triggerCount": 0,- "version": "20260618_00",+ "version": "20260903_00","tools": [{"slug": "COMPOSIO_SEARCH_AMAZON",@@ -23221,7 +23291,7 @@],"toolCount": 17,"triggerCount": 0,- "version": "20260828_00",+ "version": "20260903_00","tools": [{"slug": "SNOWFLAKE_CANCEL_STATEMENT_EXECUTION",@@ -24303,7 +24373,7 @@],"toolCount": 173,"triggerCount": 0,- "version": "20260831_00",+ "version": "20260903_00","tools": [{"slug": "MICROSOFT_TEAMS_ADD_CHAT_MEMBER",@@ -28909,7 +28979,7 @@],"toolCount": 83,"triggerCount": 9,- "version": "20260828_00",+ "version": "20260903_00","tools": [{"slug": "ONE_DRIVE_ADD_WORKBOOK_WORKSHEET",@@ -33812,8 +33882,8 @@"OAUTH1"],"toolCount": 329,- "triggerCount": 5,- "version": "20260812_00",+ "triggerCount": 20,+ "version": "20260908_00","tools": [{"slug": "TRELLO_ADD_BOARDS",@@ -35463,29 +35533,104 @@],"triggers": [{- "slug": "TRELLO_ARCHIVED_CARD_TRIGGER",- "name": "Card Archived Trigger",- "description": "Triggered when a card is archived in the specified board"+ "slug": "TRELLO_ATTACHMENT_ADDED_TO_CARD",+ "name": "Attachment Added To Card",+ "description": "Triggers when a file or link is attached to a card."+ },+ {+ "slug": "TRELLO_ATTACHMENT_REMOVED_FROM_CARD",+ "name": "Attachment Removed From Card",+ "description": "Triggers when an attachment is removed from a card. Trello drops the\nattachment's URL from this event."+ },+ {+ "slug": "TRELLO_BOARD_ADDED_TO_WORKSPACE",+ "name": "Board Added To Workspace",+ "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."+ },+ {+ "slug": "TRELLO_BOARD_LABEL_CREATED",+ "name": "Board Label Created",+ "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."+ },+ {+ "slug": "TRELLO_BOARD_LABEL_DELETED",+ "name": "Board Label Deleted",+ "description": "Triggers when a label is deleted from the board's label set. Trello drops\nthe label's text and colour from this event."+ },+ {+ "slug": "TRELLO_BOARD_LABEL_UPDATED",+ "name": "Board Label Updated",+ "description": "Triggers when a board label changes. `old` carries the previous value of the\nfield that changed."+ },+ {+ "slug": "TRELLO_BOARD_MEMBER_ROLE_CHANGED",+ "name": "Board Member Role Changed",+ "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."+ },+ {+ "slug": "TRELLO_BOARD_REMOVED_FROM_WORKSPACE",+ "name": "Board Removed From Workspace",+ "description": "Triggers when a board leaves the watched Workspace."+ },+ {+ "slug": "TRELLO_BOARD_UPDATED",+ "name": "Board Updated",+ "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."+ },+ {+ "slug": "TRELLO_CARD_COPIED",+ "name": "Card Copied",+ "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."+ },+ {+ "slug": "TRELLO_CARD_CREATED",+ "name": "Card Created",+ "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."+ },+ {+ "slug": "TRELLO_CARD_CREATED_FROM_CHECKLIST_ITEM",+ "name": "Card Created From Checklist Item",+ "description": "Triggers when a checklist item is promoted into a card of its own — a\nsub-task becoming tracked work."+ },+ {+ "slug": "TRELLO_CARD_DELETED",+ "name": "Card Deleted",+ "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."+ },+ {+ "slug": "TRELLO_CARD_MOVED_BETWEEN_LISTS",+ "name": "Card Moved Between Lists",+ "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."+ },+ {+ "slug": "TRELLO_CARD_MOVED_IN_FROM_ANOTHER_BOARD",+ "name": "Card Moved In From Another Board",+ "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."},{- "slug": "TRELLO_NEW_ACTIVITY_TRIGGER",- "name": "New Activity Trigger",- "description": "Triggered when there is activity in Trello."+ "slug": "TRELLO_CARD_MOVED_OUT_TO_ANOTHER_BOARD",+ "name": "Card Moved Out To Another Board",+ "description": "Triggers when a card leaves the watched board for a different one."},{- "slug": "TRELLO_NEW_BOARD_TRIGGER",- "name": "New Board Trigger",- "description": "Triggered when a board is created in the specified workspace"+ "slug": "TRELLO_CARD_UPDATED",+ "name": "Card Updated",+ "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."},{- "slug": "TRELLO_NEW_CARD_TRIGGER",- "name": "New Card Trigger",- "description": "Triggered when a card is created in the specified board"+ "slug": "TRELLO_CARD_VOTE_CHANGED",+ "name": "Card Vote Changed",+ "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."},{- "slug": "TRELLO_UPDATED_CARD_TRIGGER",- "name": "Card Updated Trigger",- "description": "Triggered when a specific card is updated"+ "slug": "TRELLO_CHECKLIST_ADDED_TO_CARD",+ "name": "Checklist Added To Card",+ "description": "Triggers when a checklist is attached to a card."+ },+ {+ "slug": "TRELLO_CHECKLIST_ITEM_ADDED",+ "name": "Checklist Item Added",+ "description": "Triggers when an item is added to a checklist."}],"authConfigDetails": [@@ -40762,8 +40907,8 @@"OAUTH2"],"toolCount": 432,- "triggerCount": 7,- "version": "20260831_00",+ "triggerCount": 20,+ "version": "20260902_00","tools": [{"slug": "STRIPE_ACCEPT_QUOTE",@@ -42928,39 +43073,104 @@],"triggers": [{- "slug": "STRIPE_CHARGE_FAILED_TRIGGER",- "name": "Charge Failed Trigger",- "description": "Triggered when a direct charge fails in Stripe's legacy Charges API"+ "slug": "STRIPE_CHARGE_CAPTURED",+ "name": "Charge Captured",+ "description": "Occurs whenever a previously uncaptured charge is captured."+ },+ {+ "slug": "STRIPE_CHARGE_DISPUTE_CLOSED",+ "name": "Charge Dispute Closed",+ "description": "Occurs when a dispute is closed and the dispute status changes to `lost`, `warning_closed`, or `won`."+ },+ {+ "slug": "STRIPE_CHARGE_DISPUTE_CREATED",+ "name": "Charge Dispute Created",+ "description": "Occurs whenever a customer disputes a charge with their bank."+ },+ {+ "slug": "STRIPE_CHARGE_DISPUTE_UPDATED",+ "name": "Charge Dispute Updated",+ "description": "Occurs when the dispute is updated (usually with evidence)."+ },+ {+ "slug": "STRIPE_CHARGE_FAILED",+ "name": "Charge Failed",+ "description": "Occurs whenever a failed charge attempt occurs."+ },+ {+ "slug": "STRIPE_CHARGE_REFUNDED",+ "name": "Charge Refunded",+ "description": "Occurs whenever a charge is refunded, including partial refunds. Listen to `refund.created` for information about the refund."+ },+ {+ "slug": "STRIPE_CHARGE_REFUND_UPDATED",+ "name": "Charge Refund Updated",+ "description": "Occurs whenever a refund is updated on selected payment methods. For updates on all refunds, listen to `refund.updated` instead."+ },+ {+ "slug": "STRIPE_CHARGE_SUCCEEDED",+ "name": "Charge Succeeded",+ "description": "Occurs whenever a charge is successful."+ },+ {+ "slug": "STRIPE_CHECKOUT_SESSION_ASYNC_PAYMENT_FAILED",+ "name": "Checkout Session Async Payment Failed",+ "description": "Occurs when a payment intent using a delayed payment method fails."+ },+ {+ "slug": "STRIPE_CHECKOUT_SESSION_ASYNC_PAYMENT_SUCCEEDED",+ "name": "Checkout Session Async Payment Succeeded",+ "description": "Occurs when a payment intent using a delayed payment method finally succeeds."+ },+ {+ "slug": "STRIPE_CHECKOUT_SESSION_COMPLETED",+ "name": "Checkout Session Completed",+ "description": "Occurs when a Checkout Session has been successfully completed."+ },+ {+ "slug": "STRIPE_CHECKOUT_SESSION_EXPIRED",+ "name": "Checkout Session Expired",+ "description": "Occurs when a Checkout Session is expired."+ },+ {+ "slug": "STRIPE_CUSTOMER_CREATED",+ "name": "Customer Created",+ "description": "Occurs whenever a new customer is created."+ },+ {+ "slug": "STRIPE_CUSTOMER_DELETED",+ "name": "Customer Deleted",+ "description": "Occurs whenever a customer is deleted."},{- "slug": "STRIPE_CHECKOUT_SESSION_COMPLETED_TRIGGER",- "name": "Checkout Session Completed Trigger",- "description": "Triggered when a checkout session is completed in Stripe"+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_CREATED",+ "name": "Customer Subscription Created",+ "description": "Occurs whenever a customer is signed up for a new plan."},{- "slug": "STRIPE_INVOICE_PAYMENT_SUCCEEDED_TRIGGER",- "name": "Invoice Payment Succeeded Trigger",- "description": "Triggered when an invoice payment is successful in Stripe"+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_DELETED",+ "name": "Customer Subscription Deleted",+ "description": "Occurs whenever a customer's subscription ends."},{- "slug": "STRIPE_PAYMENT_FAILED_TRIGGER",- "name": "Payment Intent Failed Trigger",- "description": "Triggered when a payment intent fails in Stripe"+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_TRIAL_WILL_END",+ "name": "Customer Subscription Trial Will End",+ "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."},{- "slug": "STRIPE_PRODUCT_CREATED_TRIGGER",- "name": "Product Created Trigger",- "description": "Triggered when a product is created in Stripe"+ "slug": "STRIPE_CUSTOMER_SUBSCRIPTION_UPDATED",+ "name": "Customer Subscription Updated",+ "description": "Occurs whenever a subscription changes (e.g., switching from one plan to another, or changing the status from trial to active)."},{- "slug": "STRIPE_SUBSCRIPTION_ADDED_TRIGGER",- "name": "Subscription Added Trigger",- "description": "Triggered when a subscription is added in Stripe"+ "slug": "STRIPE_CUSTOMER_UPDATED",+ "name": "Customer Updated",+ "description": "Occurs whenever any property of a customer changes."},{- "slug": "STRIPE_SUBSCRIPTION_DELETED_TRIGGER",- "name": "Subscription Deleted Trigger",- "description": "Triggered when a subscription is deleted in Stripe"+ "slug": "STRIPE_INVOICE_CREATED",+ "name": "Invoice Created",+ "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."}],"authConfigDetails": [@@ -47222,7 +47432,7 @@],"toolCount": 177,"triggerCount": 0,- "version": "20260819_00",+ "version": "20260903_00","tools": [{"slug": "DROPBOX_ACTIVATE_TEAM_FOLDER",@@ -48929,7 +49139,7 @@],"toolCount": 69,"triggerCount": 20,- "version": "20260828_00",+ "version": "20260903_00","tools": [{"slug": "CONFLUENCE_ADD_CONTENT_LABEL",@@ -60515,7 +60725,7 @@],"toolCount": 452,"triggerCount": 2,- "version": "20260828_00",+ "version": "20260903_00","tools": [{"slug": "ZENDESK_APPLY_ZENDESK_MACRO",@@ -63080,9 +63290,9 @@"OAUTH2","API_KEY"],- "toolCount": 53,+ "toolCount": 56,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260902_00","tools": [{"slug": "METAADS_CREATE_AD",@@ -63139,6 +63349,11 @@"name": "Get Page Accounts","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."},+ {+ "slug": "METAADS_GET_PIXEL_EVENT_STATS",+ "name": "Get Pixel Event Stats",+ "description": "Read recent Pixel event-count and processing statistics, optionally restricted to server events and one event name, to verify aggregate ingestion."+ },{"slug": "METAADS_GET_USER","name": "Get User",@@ -63149,6 +63364,11 @@"name": "Get Video","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."},+ {+ "slug": "METAADS_LIST_AD_ACCOUNT_PIXELS",+ "name": "List Ad Account Pixels",+ "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."+ },{"slug": "METAADS_LIST_AD_CREATIVES","name": "List Ad Creatives",@@ -63334,6 +63554,11 @@"name": "Read Ad Sets","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."},+ {+ "slug": "METAADS_SEND_CONVERSION_EVENTS",+ "name": "Send Conversion Events",+ "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."+ },{"slug": "METAADS_UPDATE_AD_CREATIVE","name": "Update Ad Creative",@@ -63549,9 +63774,9 @@"composioManagedAuthSchemes": ["OAUTH2"],- "toolCount": 467,+ "toolCount": 473,"triggerCount": 20,- "version": "20260828_00",+ "version": "20260903_00","tools": [{"slug": "GOOGLESUPER_ACL_DELETE",@@ -63838,6 +64063,11 @@"name": "Create a new calendar","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."},+ {+ "slug": "GOOGLESUPER_CREATE_CALLOUT_ASSET",+ "name": "Create Callout Asset",+ "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."+ },{"slug": "GOOGLESUPER_CREATE_CHART","name": "Create Chart in Google Sheets",@@ -64488,6 +64718,11 @@"name": "Get contacts","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)."},+ {+ "slug": "GOOGLESUPER_GET_CONVERSION_ACTION_TAG_SNIPPETS",+ "name": "Get Conversion Action Tag Snippets",+ "description": "Retrieve provider-generated website or call conversion tag snippets after creating a conversion action. Markup is returned exactly as Google provides it."+ },{"slug": "GOOGLESUPER_GET_CURRENT_DATE_TIME","name": "Get current date and time",@@ -64678,6 +64913,11 @@"name": "Get Revision","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."},+ {+ "slug": "GOOGLESUPER_GET_RMF_REPORT",+ "name": "Get Required Google Ads Report",+ "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."+ },{"slug": "GOOGLESUPER_GET_ROUTE","name": "Get Route",@@ -64821,7 +65061,7 @@{"slug": "GOOGLESUPER_LIST_ACCESSIBLE_CUSTOMERS","name": "List Accessible Customers",- "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."+ "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."},{"slug": "GOOGLESUPER_LIST_ACCESS_PROPOSALS",@@ -65271,12 +65511,12 @@{"slug": "GOOGLESUPER_MUTATE_ASSETS","name": "Mutate Assets",- "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."+ "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."},{"slug": "GOOGLESUPER_MUTATE_BIDDING_STRATEGIES","name": "Mutate Bidding Strategies",- "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."+ "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."},{"slug": "GOOGLESUPER_MUTATE_CAMPAIGN_ASSETS",@@ -65303,6 +65543,11 @@"name": "Mutate Campaigns","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."},+ {+ "slug": "GOOGLESUPER_MUTATE_CAMPAIGNS_V2",+ "name": "Mutate Campaigns V2",+ "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."+ },{"slug": "GOOGLESUPER_MUTATE_CONDITIONAL_FORMAT_RULES","name": "Mutate conditional format rules",@@ -65313,11 +65558,21 @@"name": "Mutate Conversion Actions","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."},+ {+ "slug": "GOOGLESUPER_MUTATE_CUSTOMER_ASSETS",+ "name": "Mutate Customer Assets",+ "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."+ },{"slug": "GOOGLESUPER_MUTATE_LABELS","name": "Mutate Labels","description": "Create, update, or remove Google Ads labels. Pair this with campaign label mutations to organize campaigns and support filtering."},+ {+ "slug": "GOOGLESUPER_MUTATE_PORTFOLIO_BIDDING_STRATEGIES",+ "name": "Mutate Portfolio Bidding Strategies",+ "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."+ },{"slug": "GOOGLESUPER_NEARBY_SEARCH","name": "Nearby search",@@ -65511,7 +65766,7 @@{"slug": "GOOGLESUPER_SEARCH_STREAM_GAQL","name": "Search Stream GAQL",- "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."+ "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."},{"slug": "GOOGLESUPER_SEND_DRAFT",@@ -66411,7 +66666,7 @@],"toolCount": 16,"triggerCount": 0,- "version": "20260615_00",+ "version": "20260908_00","tools": [{"slug": "TYPEFULLY_CREATE_DRAFT",@@ -67137,7 +67392,7 @@],"toolCount": 105,"triggerCount": 11,- "version": "20260826_00",+ "version": "20260903_00","tools": [{"slug": "ZOOM_ADD_A_MEETING_REGISTRANT",@@ -69265,15 +69520,20 @@"composioManagedAuthSchemes": ["OAUTH2"],- "toolCount": 22,+ "toolCount": 28,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260902_00","tools": [{"slug": "GOOGLEADS_ADD_OR_REMOVE_TO_CUSTOMER_LIST","name": "Add or remove to customer list","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."},+ {+ "slug": "GOOGLEADS_CREATE_CALLOUT_ASSET",+ "name": "Create Callout Asset",+ "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."+ },{"slug": "GOOGLEADS_CREATE_CUSTOMER_LIST","name": "Create customer list",@@ -69289,15 +69549,25 @@"name": "Get campaign by name","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."},+ {+ "slug": "GOOGLEADS_GET_CONVERSION_ACTION_TAG_SNIPPETS",+ "name": "Get Conversion Action Tag Snippets",+ "description": "Retrieve provider-generated website or call conversion tag snippets after creating a conversion action. Markup is returned exactly as Google provides it."+ },{"slug": "GOOGLEADS_GET_CUSTOMER_LISTS","name": "Get customer lists","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."},+ {+ "slug": "GOOGLEADS_GET_RMF_REPORT",+ "name": "Get Required Google Ads Report",+ "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."+ },{"slug": "GOOGLEADS_LIST_ACCESSIBLE_CUSTOMERS","name": "List Accessible Customers",- "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."+ "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."},{"slug": "GOOGLEADS_LIST_SUB_ACCOUNTS",@@ -69332,12 +69602,12 @@{"slug": "GOOGLEADS_MUTATE_ASSETS","name": "Mutate Assets",- "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."+ "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."},{"slug": "GOOGLEADS_MUTATE_BIDDING_STRATEGIES","name": "Mutate Bidding Strategies",- "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."+ "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."},{"slug": "GOOGLEADS_MUTATE_CAMPAIGN_ASSETS",@@ -69364,20 +69634,35 @@"name": "Mutate Campaigns","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."},+ {+ "slug": "GOOGLEADS_MUTATE_CAMPAIGNS_V2",+ "name": "Mutate Campaigns V2",+ "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."+ },{"slug": "GOOGLEADS_MUTATE_CONVERSION_ACTIONS","name": "Mutate Conversion Actions","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."},+ {+ "slug": "GOOGLEADS_MUTATE_CUSTOMER_ASSETS",+ "name": "Mutate Customer Assets",+ "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."+ },{"slug": "GOOGLEADS_MUTATE_LABELS","name": "Mutate Labels","description": "Create, update, or remove Google Ads labels. Pair this with campaign label mutations to organize campaigns and support filtering."},+ {+ "slug": "GOOGLEADS_MUTATE_PORTFOLIO_BIDDING_STRATEGIES",+ "name": "Mutate Portfolio Bidding Strategies",+ "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."+ },{"slug": "GOOGLEADS_SEARCH_STREAM_GAQL","name": "Search Stream GAQL",- "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."+ "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."}],"triggers": [],@@ -69464,7 +69749,7 @@],"toolCount": 368,"triggerCount": 0,- "version": "20260730_00",+ "version": "20260903_00","tools": [{"slug": "PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGER",@@ -72675,7 +72960,7 @@],"toolCount": 98,"triggerCount": 0,- "version": "20260831_00",+ "version": "20260908_00","tools": [{"slug": "SHARE_POINT_ADD_ATTACHMENT_TO_LIST_ITEM",@@ -79687,7 +79972,7 @@],"toolCount": 58,"triggerCount": 0,- "version": "20260819_00",+ "version": "20260903_00","tools": [{"slug": "ZOHO_INVENTORY_ADD_CREDIT_NOTE_COMMENT",@@ -80062,9 +80347,9 @@"composioManagedAuthSchemes": ["OAUTH2"],- "toolCount": 43,+ "toolCount": 44,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260902_00","tools": [{"slug": "FACEBOOK_ASSIGN_PAGE_TASK",@@ -80076,6 +80361,11 @@"name": "Create Comment","description": "Creates a comment on a Facebook post or replies to an existing comment."},+ {+ "slug": "FACEBOOK_CREATE_MULTI_PHOTO_POST",+ "name": "Create Multi-Photo Post",+ "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."+ },{"slug": "FACEBOOK_CREATE_PHOTO_ALBUM","name": "Create Photo Album",@@ -80274,7 +80564,7 @@{"slug": "FACEBOOK_UPLOAD_PHOTOS_BATCH","name": "Upload Photos Batch",- "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."+ "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."},{"slug": "FACEBOOK_UPLOAD_VIDEO",@@ -80918,17 +81208,17 @@],"toolCount": 48,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260903_00","tools": [{"slug": "CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST","name": "Access user specific brand templates list",- "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."+ "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."},{"slug": "CANVA_CREATE_ASSET_UPLOAD_JOB","name": "Create Asset Upload Job",- "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."+ "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."},{"slug": "CANVA_CREATE_CANVA_DESIGN_EXPORT_JOB",@@ -80938,17 +81228,17 @@{"slug": "CANVA_CREATE_CANVA_DESIGN_WITH_OPTIONAL_ASSET","name": "Create canva design with optional asset (Deprecated)",- "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."+ "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."},{"slug": "CANVA_CREATE_COMMENT_REPLY_IN_DESIGN",- "name": "Create comment reply in design",- "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."+ "name": "Create comment reply in design (Deprecated)",+ "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."},{"slug": "CANVA_CREATE_DESIGN_COMMENT_IN_PREVIEW_API",- "name": "Create design comment in preview api",- "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."+ "name": "Create design comment in preview api (Deprecated)",+ "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."},{"slug": "CANVA_CREATE_DESIGN_IMPORT_JOB",@@ -80978,7 +81268,7 @@{"slug": "CANVA_FETCH_ASSET_UPLOAD_JOB_STATUS","name": "Fetch asset upload job status",- "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."+ "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."},{"slug": "CANVA_FETCH_CANVA_CONNECT_SIGNING_PUBLIC_KEYS",@@ -80988,7 +81278,7 @@{"slug": "CANVA_FETCH_CURRENT_USER_DETAILS","name": "Fetch current user details",- "description": "Returns the User ID, Team ID, and display name of the user account associated with the provided access token."+ "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."},{"slug": "CANVA_FETCH_DESIGN_METADATA_AND_ACCESS_INFORMATION",@@ -80998,27 +81288,27 @@{"slug": "CANVA_GET_DESIGN_COMMENT_REPLIES","name": "Get design comment thread replies",- "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."+ "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."},{"slug": "CANVA_GET_DESIGN_COMMENT_REPLY","name": "Get specific design comment reply",- "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."+ "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."},{"slug": "CANVA_GET_DESIGN_EXPORT_JOB_RESULT","name": "Get design export job result",- "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."+ "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."},{"slug": "CANVA_GET_DESIGNS_DESIGNID_COMMENTS_THREADID","name": "Get designs designid comments threadid",- "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."+ "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."},{"slug": "CANVA_GET_DESIGNS_DESIGNID_EXPORT_FORMATS","name": "Get design export formats",- "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."+ "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."},{"slug": "CANVA_GET_URL_ASSET_UPLOADS_JOBID",@@ -81038,7 +81328,7 @@{"slug": "CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB","name": "Initiate canva design autofill job",- "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."+ "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."},{"slug": "CANVA_LIST_DESIGN_PAGES_WITH_PAGINATION",@@ -81048,7 +81338,7 @@{"slug": "CANVA_LIST_FOLDER_ITEMS_BY_TYPE_WITH_SORTING","name": "List folder items by type with sorting",- "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."+ "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."},{"slug": "CANVA_LIST_USER_DESIGNS",@@ -81063,22 +81353,22 @@{"slug": "CANVA_POST_DESIGNS","name": "Create new Canva design",- "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."+ "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."},{"slug": "CANVA_POST_DESIGNS_DESIGNID_COMMENTS","name": "Post designs designid comments",- "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."+ "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."},{"slug": "CANVA_POST_DESIGNS_DESIGNID_COMMENTS_THREADID_REPLIES","name": "Create reply to comment thread",- "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."+ "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."},{"slug": "CANVA_POST_EXPORTS","name": "Start design export job",- "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')."+ "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')."},{"slug": "CANVA_POST_FOLDERS",@@ -81108,17 +81398,17 @@{"slug": "CANVA_RETRIEVE_BRAND_TEMPLATE_DATASET_DEFINITION","name": "Retrieve brand template dataset definition",- "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."+ "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."},{"slug": "CANVA_RETRIEVE_CANVA_ENTERPRISE_BRAND_TEMPLATE_METADATA",- "name": "Retrieve canva enterprise brand template metadata",- "description": "Upcoming update will change brand template IDs; integrations must migrate within 6 months. API use requires Canva Enterprise membership."+ "name": "Retrieve brand template metadata",+ "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."},{"slug": "CANVA_RETRIEVE_DESIGN_AUTOFILL_JOB_STATUS","name": "Retrieve design autofill job status",- "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."+ "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`."},{"slug": "CANVA_RETRIEVE_DESIGN_IMPORT_JOB_STATUS",@@ -81143,7 +81433,7 @@{"slug": "CANVA_REVOKE_OAUTH_TOKENS","name": "Revoke oauth tokens",- "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."+ "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."},{"slug": "CANVA_UPDATE_ASSET_S_NAME_AND_TAGS_BY_ID",@@ -81201,7 +81491,7 @@"type": "string","description": "Scopes to request from the user, comma separated","required": false,- "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"+ "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"}]},@@ -82316,7 +82606,7 @@],"toolCount": 41,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260902_00","tools": [{"slug": "TIMELY_CREATE_CLIENT",@@ -109362,7 +109652,7 @@],"toolCount": 137,"triggerCount": 0,- "version": "20260819_00",+ "version": "20260903_00","tools": [{"slug": "ZOHO_INVOICE_ADD_CREDITNOTE_TO_INVOICES",@@ -110125,7 +110415,7 @@],"toolCount": 121,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260903_00","tools": [{"slug": "STACK_EXCHANGE_CREATE_FILTER",@@ -111037,351 +111327,1212 @@]},{- "slug": "datadog",- "name": "Datadog",- "logo": "https://logos.composio.dev/api/datadog",- "description": "Datadog offers monitoring, observability, and security for cloud-scale applications, unifying metrics, logs, and traces to help teams detect issues and optimize performance",- "category": "server monitoring",+ "slug": "twitch",+ "name": "Twitch",+ "logo": "https://logos.composio.dev/api/twitch",+ "description": "Twitch is a live streaming platform popular with gamers, creators, and communities, offering real-time interaction and monetization through subscriptions and donations",+ "category": "video & audio","authSchemes": ["OAUTH2",- "API_KEY",- "BEARER_TOKEN"+ "S2S_OAUTH2",+ "NO_AUTH"],- "toolCount": 65,+ "composioManagedAuthSchemes": [+ "OAUTH2"+ ],+ "toolCount": 149,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260908_00","tools": [{- "slug": "DATADOG_AGGREGATE_LOGS",- "name": "Aggregate logs",- "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."+ "slug": "TWITCH_ADD_BLOCKED_TERM",+ "name": "Add Blocked Term",+ "description": "Adds a word or phrase to the broadcaster’s list of blocked terms."},{- "slug": "DATADOG_CREATE_DASHBOARD",- "name": "Create Dashboard",- "description": "Create a dashboard in Datadog. Dashboards provide customizable visualizations for monitoring your infrastructure, applications, and business metrics in a unified view."+ "slug": "TWITCH_ADD_CHANNEL_MODERATOR",+ "name": "Add Channel Moderator",+ "description": "Adds a moderator to the broadcaster’s chat room."},{- "slug": "DATADOG_CREATE_DOWNTIME",- "name": "Create downtime",- "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."+ "slug": "TWITCH_ADD_CHANNEL_VIP",+ "name": "Add Channel VIP",+ "description": "Adds the specified user as a VIP in the broadcaster’s channel."},{- "slug": "DATADOG_CREATE_ESCALATION_POLICY",- "name": "Create On-Call escalation policy",- "description": "Creates a Datadog On-Call escalation policy."+ "slug": "TWITCH_ADD_SUSPICIOUS_STATUS_TO_CHAT_USER",+ "name": "Add Suspicious Status to Chat User",+ "description": "Adds a suspicious user status to a chatter on the broadcaster’s channel."},{- "slug": "DATADOG_CREATE_EVENT",- "name": "Create event",- "description": "Creates a new event in Datadog. Events are useful for tracking deployments, outages, configuration changes, and other important occurrences."+ "slug": "TWITCH_ASSIGN_GUEST_STAR_SLOT",+ "name": "Assign Guest Star Slot",+ "description": "BETA Allows a previously invited user to be assigned a slot within the active Guest Star session."},{- "slug": "DATADOG_CREATE_MONITOR",- "name": "Create monitor",- "description": "Creates a new Datadog monitor to track metrics, logs, or other data sources with configurable alerting thresholds and notifications."+ "slug": "TWITCH_BAN_USER",+ "name": "Ban User",+ "description": "Bans a user from participating in a broadcaster’s chat room or puts them in a timeout."},{- "slug": "DATADOG_CREATE_NOTIFICATION_CHANNEL",- "name": "Create On-Call notification channel",- "description": "Creates an On-Call notification channel for a Datadog user."+ "slug": "TWITCH_BLOCK_USER",+ "name": "Block User",+ "description": "Blocks the specified user from interacting with or having contact with the broadcaster."},{- "slug": "DATADOG_CREATE_NOTIFICATION_RULE",- "name": "Create On-Call notification rule",- "description": "Creates an On-Call notification rule for a Datadog user."+ "slug": "TWITCH_CANCEL_A_RAID",+ "name": "Cancel a raid",+ "description": "Cancel a pending raid."},{- "slug": "DATADOG_CREATE_SCHEDULE",- "name": "Create On-Call schedule",- "description": "Creates a Datadog On-Call schedule."+ "slug": "TWITCH_CHECK_AUTOMOD_STATUS",+ "name": "Check AutoMod Status",+ "description": "Checks whether AutoMod would flag the specified message for review."},{- "slug": "DATADOG_CREATE_SLO",- "name": "Create SLO",- "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."+ "slug": "TWITCH_CHECK_USER_SUBSCRIPTION",+ "name": "Check User Subscription",+ "description": "Checks whether the user subscribes to the broadcaster’s channel."},{- "slug": "DATADOG_CREATE_SYNTHETIC_API_TEST",- "name": "Create Synthetic API Test",- "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."+ "slug": "TWITCH_CREATE_CHANNEL_STREAM_SCHEDULE_SEGMENT",+ "name": "Create Channel Stream Schedule Segment",+ "description": "Adds a single or recurring broadcast to the broadcaster’s streaming schedule."},{- "slug": "DATADOG_CREATE_WEBHOOK",- "name": "Create Webhook",- "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."+ "slug": "TWITCH_CREATE_CLIP",+ "name": "Request Clip Creation",+ "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."},{- "slug": "DATADOG_DELETE_DASHBOARD",- "name": "Delete Dashboard",- "description": "Delete a dashboard in Datadog. Permanently removes a dashboard from your organization. This action cannot be undone. Use with caution."+ "slug": "TWITCH_CREATE_CLIP_FROM_VOD",+ "name": "Request Clip Creation From VOD",+ "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."},{- "slug": "DATADOG_DELETE_ESCALATION_POLICY",- "name": "Delete On-Call escalation policy",- "description": "Deletes a Datadog On-Call escalation policy by ID. This action cannot be undone."+ "slug": "TWITCH_CREATE_CONDUITS",+ "name": "Create Conduits",+ "description": "Creates a new conduit."},{- "slug": "DATADOG_DELETE_MONITOR",- "name": "Delete monitor",- "description": "Deletes a Datadog monitor permanently. Use with caution as this action cannot be undone."+ "slug": "TWITCH_CREATE_CUSTOM_REWARDS",+ "name": "Create Custom Rewards",+ "description": "Creates a Custom Reward in the broadcaster’s channel."},{- "slug": "DATADOG_DELETE_NOTIFICATION_CHANNEL",- "name": "Delete On-Call notification channel",- "description": "Deletes an On-Call notification channel for a Datadog user. This action cannot be undone."+ "slug": "TWITCH_CREATE_EVENTSUB_SUBSCRIPTION",+ "name": "Create EventSub Subscription",+ "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."},{- "slug": "DATADOG_DELETE_NOTIFICATION_RULE",- "name": "Delete On-Call notification rule",- "description": "Deletes an On-Call notification rule for a Datadog user. This action cannot be undone."+ "slug": "TWITCH_CREATE_EXTENSION_SECRET",+ "name": "Create Extension Secret",+ "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."},{- "slug": "DATADOG_DELETE_SCHEDULE",- "name": "Delete On-Call schedule",- "description": "Deletes a Datadog On-Call schedule by ID. This action cannot be undone."+ "slug": "TWITCH_CREATE_GUEST_STAR_SESSION",+ "name": "Create Guest Star Session",+ "description": "BETA Programmatically creates a Guest Star session on behalf of the broadcaster."},{- "slug": "DATADOG_GET_DASHBOARD",- "name": "Get Dashboard",- "description": "Get a specific dashboard from Datadog. Retrieves detailed information about a dashboard including its widgets, layout, template variables, and metadata."+ "slug": "TWITCH_CREATE_POLL",+ "name": "Create Poll",+ "description": "Creates a poll that viewers in the broadcaster’s channel can vote on."},{- "slug": "DATADOG_GET_ESCALATION_POLICY",- "name": "Get On-Call escalation policy",- "description": "Retrieves a Datadog On-Call escalation policy by ID."+ "slug": "TWITCH_CREATE_PREDICTION",+ "name": "Create Prediction",+ "description": "Create a Channel Points Prediction."},{- "slug": "DATADOG_GET_MONITOR",- "name": "Get monitor",- "description": "Retrieves detailed information about a specific Datadog monitor, including its current state, configuration, and any active downtimes."+ "slug": "TWITCH_CREATE_STREAM_MARKER",+ "name": "Create Stream Marker",+ "description": "Adds a marker to a live stream."},{- "slug": "DATADOG_GET_NOTIFICATION_CHANNEL",- "name": "Get On-Call notification channel",- "description": "Retrieves an On-Call notification channel for a user by ID."+ "slug": "TWITCH_DELETE_CHANNEL_STREAM_SCHEDULE_SEGMENT",+ "name": "Delete Channel Stream Schedule Segment",+ "description": "Deletes a broadcast from the broadcaster’s streaming schedule."},{- "slug": "DATADOG_GET_NOTIFICATION_RULE",- "name": "Get On-Call notification rule",- "description": "Retrieves an On-Call notification rule for a user by ID."+ "slug": "TWITCH_DELETE_CHAT_MESSAGES",+ "name": "Delete Chat Messages",+ "description": "Removes a single chat message or all chat messages from the broadcaster’s chat room."},{- "slug": "DATADOG_GET_SCHEDULE",- "name": "Get On-Call schedule",- "description": "Retrieves a Datadog On-Call schedule by ID."+ "slug": "TWITCH_DELETE_CONDUIT",+ "name": "Delete Conduit",+ "description": "Deletes a specified conduit."},{- "slug": "DATADOG_GET_SCHEDULED_ON_CALL_USER",- "name": "Get scheduled on-call user",- "description": "Gets the currently scheduled on-call user for a Datadog On-Call schedule."+ "slug": "TWITCH_DELETE_CUSTOM_REWARD",+ "name": "Delete Custom Reward",+ "description": "Deletes a custom reward that the broadcaster created."},{- "slug": "DATADOG_GET_SERVICE_DEPENDENCIES",- "name": "Get Service Dependencies",- "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."+ "slug": "TWITCH_DELETE_EVENTSUB_SUBSCRIPTION",+ "name": "Delete EventSub Subscription",+ "description": "Deletes an EventSub subscription."},{- "slug": "DATADOG_GET_SYNTHETICS_LOCATIONS",- "name": "Get Synthetics Locations",- "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."+ "slug": "TWITCH_DELETE_GUEST_STAR_INVITE",+ "name": "Delete Guest Star Invite",+ "description": "BETA Revokes a previously sent invite for a Guest Star session."},{- "slug": "DATADOG_GET_TAGS",- "name": "Get host tags",- "description": "Retrieves all tags associated with a specific host in Datadog. Useful for understanding host metadata and organizing infrastructure."+ "slug": "TWITCH_DELETE_GUEST_STAR_SLOT",+ "name": "Delete Guest Star Slot",+ "description": "BETA Allows a caller to remove a slot assignment from a user participating in an active Guest Star session."},{- "slug": "DATADOG_GET_TEAM_ON_CALL_USERS",- "name": "Get team on-call users",- "description": "Gets the current on-call users for a Datadog On-Call team."+ "slug": "TWITCH_DELETE_VIDEOS",+ "name": "Delete Videos",+ "description": "Deletes one or more videos."},{- "slug": "DATADOG_GET_TEAM_ROUTING_RULES",- "name": "Get On-Call team routing rules",- "description": "Gets the Datadog On-Call routing rules configured for a team."+ "slug": "TWITCH_END_GUEST_STAR_SESSION",+ "name": "End Guest Star Session",+ "description": "BETA Programmatically ends a Guest Star session on behalf of the broadcaster."},{- "slug": "DATADOG_GET_TRACE_BY_ID",- "name": "Get Trace by ID",- "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."+ "slug": "TWITCH_END_POLL",+ "name": "End Poll",+ "description": "End an active poll."},{- "slug": "DATADOG_GET_USAGE_SUMMARY",- "name": "Get usage summary",- "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."+ "slug": "TWITCH_END_PREDICTION",+ "name": "End Prediction",+ "description": "Locks, resolves, or cancels a Channel Points Prediction."},{- "slug": "DATADOG_LIST_ALL_TAGS",- "name": "List All Tags",- "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."+ "slug": "TWITCH_GET_AD_SCHEDULE",+ "name": "Get Ad Schedule",+ "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."},{- "slug": "DATADOG_LIST_API_KEYS",- "name": "List API Keys",- "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."+ "slug": "TWITCH_GET_ALL_STREAM_TAGS",+ "name": "Get All Stream Tags",+ "description": "Deprecated: this endpoint was retired and returns HTTP 410 Gone. Use GET_CHANNEL_INFORMATION and its tags field instead."},{- "slug": "DATADOG_LIST_APM_SERVICES",- "name": "List APM Services",- "description": "List APM services from Datadog. Application Performance Monitoring (APM) provides deep visibility into your applications, helping you track performance, errors, and dependencies."+ "slug": "TWITCH_GET_AUTHORIZATION_BY_USER",+ "name": "Get Authorization By User",+ "description": "Gets the authorization scopes that the specified user has granted the application."},{- "slug": "DATADOG_LIST_AWS_INTEGRATION",- "name": "List AWS Integration",- "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."+ "slug": "TWITCH_GET_AUTOMOD_SETTINGS",+ "name": "Get AutoMod Settings",+ "description": "Gets the broadcaster’s AutoMod settings."},{- "slug": "DATADOG_LIST_DASHBOARDS",- "name": "List dashboards",- "description": "Lists all Datadog dashboards with basic information. Useful for dashboard management and getting an overview of available dashboards."+ "slug": "TWITCH_GET_BANNED_USERS",+ "name": "Get Banned Users",+ "description": "Gets all users that the broadcaster banned or put in a timeout."},{- "slug": "DATADOG_LIST_EVENTS",- "name": "List events",- "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."+ "slug": "TWITCH_GET_BITS_LEADERBOARD",+ "name": "Get Bits Leaderboard",+ "description": "Gets the Bits leaderboard for the authenticated broadcaster."},{- "slug": "DATADOG_LIST_HOSTS",- "name": "List hosts",- "description": "Lists all hosts in your Datadog infrastructure with detailed information including metrics, tags, and status. Useful for infrastructure monitoring and management."+ "slug": "TWITCH_GET_BLOCKED_TERMS",+ "name": "Get Blocked Terms",+ "description": "Gets the broadcaster’s list of non-private, blocked words or phrases."},{- "slug": "DATADOG_LIST_INCIDENTS",- "name": "List Incidents",- "description": "List incidents from Datadog. Incident Management helps you track, manage, and resolve incidents efficiently with comprehensive timeline and impact tracking."+ "slug": "TWITCH_GET_BROADCASTER_SUBSCRIPTIONS",+ "name": "Get Broadcaster Subscriptions",+ "description": "Gets a list of users that subscribe to the specified broadcaster."},{- "slug": "DATADOG_LIST_LOG_INDEXES",- "name": "List Log Indexes",- "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."+ "slug": "TWITCH_GET_CHANNEL_CHAT_BADGES",+ "name": "Get Channel Chat Badges",+ "description": "Gets the broadcaster’s list of custom chat badges."},{- "slug": "DATADOG_LIST_METRICS",- "name": "List active metrics",- "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."+ "slug": "TWITCH_GET_CHANNEL_EDITORS",+ "name": "Get Channel Editors",+ "description": "Gets the broadcaster’s list editors."},{- "slug": "DATADOG_LIST_MONITORS",- "name": "List monitors",- "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."+ "slug": "TWITCH_GET_CHANNEL_EMOTES",+ "name": "Get Channel Emotes",+ "description": "Gets the broadcaster’s list of custom emotes."},{- "slug": "DATADOG_LIST_NOTIFICATION_CHANNELS",- "name": "List On-Call notification channels",- "description": "Lists the On-Call notification channels configured for a Datadog user."+ "slug": "TWITCH_GET_CHANNEL_FOLLOWERS",+ "name": "Get Channel Followers",+ "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."},{- "slug": "DATADOG_LIST_NOTIFICATION_RULES",- "name": "List On-Call notification rules",- "description": "Lists the On-Call notification rules configured for a Datadog user."+ "slug": "TWITCH_GET_CHANNEL_GUEST_STAR_SETTINGS",+ "name": "Get Channel Guest Star Settings",+ "description": "BETA Gets the channel settings for configuration of the Guest Star feature for a particular host."},{- "slug": "DATADOG_LIST_ROLES",- "name": "List Roles",- "description": "List roles from Datadog organization. Roles define sets of permissions that control what users can do within your Datadog organization."+ "slug": "TWITCH_GET_CHANNEL_ICALENDAR",+ "name": "Get Channel iCalendar",+ "description": "Gets the broadcaster’s streaming schedule as an iCalendar ."},{- "slug": "DATADOG_LIST_SERVICE_CHECKS",- "name": "List service checks",- "description": "Lists service checks from Datadog. Service checks are status checks that track the health of your services and infrastructure components."+ "slug": "TWITCH_GET_CHANNEL_INFORMATION",+ "name": "Get Channel Information",+ "description": "Gets information about one or more channels."},{- "slug": "DATADOG_LIST_SL_OS",- "name": "List SLOs",- "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."+ "slug": "TWITCH_GET_CHANNEL_STREAM_SCHEDULE",+ "name": "Get Channel Stream Schedule",+ "description": "Gets the broadcaster’s streaming schedule."},{- "slug": "DATADOG_LIST_SYNTHETICS",- "name": "List Synthetics Tests",- "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."+ "slug": "TWITCH_GET_CHANNEL_TEAMS",+ "name": "Get Channel Teams",+ "description": "Gets the list of Twitch teams that the broadcaster is a member of."},{- "slug": "DATADOG_LIST_USERS",- "name": "List Users",- "description": "List users from Datadog organization. User management allows you to see team members, their roles, and access levels within your Datadog organization."+ "slug": "TWITCH_GET_CHARITY_CAMPAIGN",+ "name": "Get Charity Campaign",+ "description": "Gets information about the broadcaster’s active charity campaign."},{- "slug": "DATADOG_LIST_WEBHOOKS",- "name": "List Webhooks",- "description": "List webhooks from Datadog. Webhooks allow you to send notifications to external services when monitors trigger, enabling integration with your workflows."+ "slug": "TWITCH_GET_CHARITY_CAMPAIGN_DONATIONS",+ "name": "Get Charity Campaign Donations",+ "description": "Gets the list of donations that users have made to the broadcaster’s active charity campaign."},{- "slug": "DATADOG_MUTE_MONITOR",- "name": "Mute Monitor",- "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."+ "slug": "TWITCH_GET_CHAT_SETTINGS",+ "name": "Get Chat Settings",+ "description": "Gets the broadcaster’s chat settings."},{- "slug": "DATADOG_QUERY_METRICS",- "name": "Query metrics",- "description": "Queries Datadog metrics and returns time series data. Useful for retrieving historical metric data, creating custom dashboards, or building reports."+ "slug": "TWITCH_GET_CHATTERS",+ "name": "Get Chatters",+ "description": "Gets the list of users that are connected to the broadcaster’s chat session."},{- "slug": "DATADOG_SEARCH_LOGS",- "name": "Search logs",- "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."+ "slug": "TWITCH_GET_CHEERMOTES",+ "name": "Get Cheermotes",+ "description": "Gets a list of Cheermotes that users can use to cheer Bits."},{- "slug": "DATADOG_SEARCH_SPANS_ANALYTICS",- "name": "Search Spans Analytics",- "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."+ "slug": "TWITCH_GET_CLIPS",+ "name": "Get Clips",+ "description": "Gets clips selected by exactly one broadcaster ID, game ID, or list of clip IDs."},{- "slug": "DATADOG_SEARCH_TRACES",- "name": "Search Traces",- "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."+ "slug": "TWITCH_GET_CLIPS_DOWNLOAD",+ "name": "Get Clips Download",+ "description": "Provides URLs to download the video file(s) for the specified clips."},{- "slug": "DATADOG_SET_TEAM_ROUTING_RULES",- "name": "Set On-Call team routing rules",- "description": "Replaces (sets) the On-Call routing rules for a Datadog team."+ "slug": "TWITCH_GET_CONDUITS",+ "name": "Get Conduits",+ "description": "Gets the conduits for a client ID."},{- "slug": "DATADOG_SUBMIT_METRICS",- "name": "Submit metrics",- "description": "Submits custom metrics to Datadog. Useful for sending application-specific metrics, business KPIs, or custom performance indicators."+ "slug": "TWITCH_GET_CONDUIT_SHARDS",+ "name": "Get Conduit Shards",+ "description": "Gets a lists of all shards for a conduit."},{- "slug": "DATADOG_UNMUTE_MONITOR",- "name": "Unmute Monitor",- "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."+ "slug": "TWITCH_GET_CONTENT_CLASSIFICATION_LABELS",+ "name": "Get Content Classification Labels",+ "description": "Gets information about Twitch content classification labels."},{- "slug": "DATADOG_UPDATE_DASHBOARD",- "name": "Update Dashboard",- "description": "Update a dashboard in Datadog. Updates an existing dashboard with new configuration, widgets, or layout while preserving its identity and creation metadata."+ "slug": "TWITCH_GET_CREATOR_GOALS",+ "name": "Get Creator Goals",+ "description": "Gets the broadcaster’s list of active goals."},{- "slug": "DATADOG_UPDATE_ESCALATION_POLICY",- "name": "Update On-Call escalation policy",- "description": "Updates a Datadog On-Call escalation policy by ID."+ "slug": "TWITCH_GET_CUSTOM_POWER_UP",+ "name": "Get Custom Power-up",+ "description": "Gets a list of custom Power-ups that the specified broadcaster created."},{- "slug": "DATADOG_UPDATE_HOST_TAGS",- "name": "Update host tags",- "description": "Updates tags for a specific host in Datadog. This replaces all existing tags from the specified source with the new tags provided."+ "slug": "TWITCH_GET_CUSTOM_REWARD",+ "name": "Get Custom Reward",+ "description": "Gets a list of custom rewards that the specified broadcaster created."},{- "slug": "DATADOG_UPDATE_MONITOR",- "name": "Update monitor",- "description": "Updates an existing Datadog monitor with new configuration, thresholds, or notification settings. Only specified fields will be updated."+ "slug": "TWITCH_GET_CUSTOM_REWARD_REDEMPTION",+ "name": "Get Custom Reward Redemption",+ "description": "Gets a list of redemptions for a custom reward."},{- "slug": "DATADOG_UPDATE_NOTIFICATION_RULE",- "name": "Update On-Call notification rule",- "description": "Updates an On-Call notification rule for a user by ID."+ "slug": "TWITCH_GET_DROPS_ENTITLEMENTS",+ "name": "Get Drops Entitlements",+ "description": "Gets an organization’s list of entitlements that have been granted to a game, a user, or both."},{- "slug": "DATADOG_UPDATE_SCHEDULE",- "name": "Update On-Call schedule",- "description": "Updates a Datadog On-Call schedule by ID."+ "slug": "TWITCH_GET_EMOTE_SETS",+ "name": "Get Emote Sets",+ "description": "Gets emotes for one or more specified emote sets."+ },+ {+ "slug": "TWITCH_GET_EVENTSUB_SUBSCRIPTIONS",+ "name": "Get EventSub Subscriptions",+ "description": "Gets a list of EventSub subscriptions that the client in the access token created."+ },+ {+ "slug": "TWITCH_GET_EXTENSION_ANALYTICS",+ "name": "Get Extension Analytics",+ "description": "Gets an analytics report for one or more extensions."+ },+ {+ "slug": "TWITCH_GET_EXTENSION_BITS_PRODUCTS",+ "name": "Get Extension Bits Products",+ "description": "Gets the list of Bits products that belongs to the extension."+ },+ {+ "slug": "TWITCH_GET_EXTENSION_CONFIGURATION_SEGMENT",+ "name": "Get Extension Configuration Segment",+ "description": "Gets the specified configuration segment from the specified extension."+ },+ {+ "slug": "TWITCH_GET_EXTENSION_LIVE_CHANNELS",+ "name": "Get Extension Live Channels",+ "description": "Gets a list of broadcasters that are streaming live and have installed or activated the extension."+ },+ {+ "slug": "TWITCH_GET_EXTENSIONS",+ "name": "Get Extensions",+ "description": "Gets information about an extension."+ },+ {+ "slug": "TWITCH_GET_EXTENSION_SECRETS",+ "name": "Get Extension Secrets",+ "description": "Gets Extension shared-secret metadata with secret content redacted."+ },+ {+ "slug": "TWITCH_GET_EXTENSION_TRANSACTIONS",+ "name": "Get Extension Transactions",+ "description": "Gets an extension’s list of transactions."+ },+ {+ "slug": "TWITCH_GET_FOLLOWED_CHANNELS",+ "name": "Get Followed Channels",+ "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."+ },+ {+ "slug": "TWITCH_GET_FOLLOWED_STREAMS",+ "name": "Get Followed Streams",+ "description": "Gets the list of broadcasters that the user follows and that are streaming live."+ },+ {+ "slug": "TWITCH_GET_GAME_ANALYTICS",+ "name": "Get Game Analytics",+ "description": "Gets an analytics report for one or more games."+ },+ {+ "slug": "TWITCH_GET_GAMES",+ "name": "Get Games",+ "description": "Gets information about specified games."+ },+ {+ "slug": "TWITCH_GET_GLOBAL_CHAT_BADGES",+ "name": "Get Global Chat Badges",+ "description": "Gets Twitch’s list of chat badges."+ },+ {+ "slug": "TWITCH_GET_GLOBAL_EMOTES",+ "name": "Get Global Emotes",+ "description": "Gets all global emotes."+ },+ {+ "slug": "TWITCH_GET_GUEST_STAR_INVITES",+ "name": "Get Guest Star Invites",+ "description": "BETA Provides the caller with a list of pending invites to a Guest Star session."+ },+ {+ "slug": "TWITCH_GET_GUEST_STAR_SESSION",+ "name": "Get Guest Star Session",+ "description": "BETA Gets information about an ongoing Guest Star session for a particular channel."+ },+ {+ "slug": "TWITCH_GET_HYPE_TRAIN_STATUS",+ "name": "Get Hype Train Status",+ "description": "Gets the status of a Hype Train for the specified broadcaster."+ },+ {+ "slug": "TWITCH_GET_MODERATED_CHANNELS",+ "name": "Get Moderated Channels",+ "description": "Gets a list of channels that the specified user has moderator privileges in."+ },+ {+ "slug": "TWITCH_GET_MODERATORS",+ "name": "Get Moderators",+ "description": "Gets all users allowed to moderate the broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_GET_PINNED_CHAT_MESSAGE",+ "name": "Get Pinned Chat Message",+ "description": "Gets the currently pinned message for the broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_GET_POLLS",+ "name": "Get Polls",+ "description": "Gets a list of polls that the broadcaster created."+ },+ {+ "slug": "TWITCH_GET_PREDICTIONS",+ "name": "Get Predictions",+ "description": "Gets a list of Channel Points Predictions that the broadcaster created."+ },+ {+ "slug": "TWITCH_GET_RELEASED_EXTENSIONS",+ "name": "Get Released Extensions",+ "description": "Gets information about a released extension."+ },+ {+ "slug": "TWITCH_GET_SHARED_CHAT_SESSION",+ "name": "Get Shared Chat Session",+ "description": "Retrieves the active shared chat session for a channel."+ },+ {+ "slug": "TWITCH_GET_SHIELD_MODE_STATUS",+ "name": "Get Shield Mode Status",+ "description": "Gets the broadcaster’s Shield Mode activation status."+ },+ {+ "slug": "TWITCH_GET_STREAM_KEY",+ "name": "Get Sensitive Stream Key",+ "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."+ },+ {+ "slug": "TWITCH_GET_STREAM_MARKERS",+ "name": "Get Stream Markers",+ "description": "Gets markers from either a user's most recent stream or one specified VOD; provide exactly one selector."+ },+ {+ "slug": "TWITCH_GET_STREAMS",+ "name": "Get Streams",+ "description": "Gets a list of all streams."+ },+ {+ "slug": "TWITCH_GET_STREAM_TAGS",+ "name": "Get Stream Tags",+ "description": "Deprecated: this endpoint was retired and returns HTTP 410 Gone. Use GET_CHANNEL_INFORMATION and its tags field instead."+ },+ {+ "slug": "TWITCH_GET_TEAMS",+ "name": "Get Teams",+ "description": "Gets one Twitch team by exactly one team name or team ID."+ },+ {+ "slug": "TWITCH_GET_TOP_GAMES",+ "name": "Get Top Games",+ "description": "Gets games and categories ranked by current viewer count on Twitch."+ },+ {+ "slug": "TWITCH_GET_UNBAN_REQUESTS",+ "name": "Get Unban Requests",+ "description": "Gets a list of unban requests for a broadcaster’s channel."+ },+ {+ "slug": "TWITCH_GET_USER_ACTIVE_EXTENSIONS",+ "name": "Get User Active Extensions",+ "description": "Gets the active extensions that the broadcaster has installed for each configuration."+ },+ {+ "slug": "TWITCH_GET_USER_BLOCK_LIST",+ "name": "Get User Block List",+ "description": "Gets the list of users that the broadcaster has blocked."+ },+ {+ "slug": "TWITCH_GET_USER_CHAT_COLOR",+ "name": "Get User Chat Color",+ "description": "Gets the color used for the user’s name in chat."+ },+ {+ "slug": "TWITCH_GET_USER_EMOTES",+ "name": "Get User Emotes",+ "description": "Retrieves emotes available to the user across all channels."+ },+ {+ "slug": "TWITCH_GET_USER_EXTENSIONS",+ "name": "Get User Extensions",+ "description": "Gets a list of all extensions (both active and inactive) that the broadcaster has installed."+ },+ {+ "slug": "TWITCH_GET_USERS",+ "name": "Get Users",+ "description": "Gets information about one or more users. With no id or login selectors, returns the user represented by the access token."+ },+ {+ "slug": "TWITCH_GET_VIDEOS",+ "name": "Get Videos",+ "description": "Gets published videos selected by exactly one list of video IDs, broadcaster ID, or game ID."+ },+ {+ "slug": "TWITCH_GET_VIPS",+ "name": "Get VIPs",+ "description": "Gets a list of the broadcaster’s VIPs."+ },+ {+ "slug": "TWITCH_MANAGE_HELD_AUTOMOD_MESSAGES",+ "name": "Allow or Deny Held AutoMod Message",+ "description": "Allows or denies one message that AutoMod held for review."+ },+ {+ "slug": "TWITCH_MODIFY_CHANNEL_INFORMATION",+ "name": "Modify Channel Information",+ "description": "Updates a channel’s properties."+ },+ {+ "slug": "TWITCH_PIN_CHAT_MESSAGE",+ "name": "Pin Chat Message",+ "description": "Pins a chat message to the specified broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_REMOVE_BLOCKED_TERM",+ "name": "Remove Blocked Term",+ "description": "Removes the word or phrase from the broadcaster’s list of blocked terms."+ },+ {+ "slug": "TWITCH_REMOVE_CHANNEL_MODERATOR",+ "name": "Remove Channel Moderator",+ "description": "Removes a moderator from the broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_REMOVE_CHANNEL_VIP",+ "name": "Remove Channel VIP",+ "description": "Removes the specified user as a VIP in the broadcaster’s channel."+ },+ {+ "slug": "TWITCH_REMOVE_SUSPICIOUS_STATUS_FROM_CHAT_USER",+ "name": "Remove Suspicious Status From Chat User",+ "description": "Remove a suspicious user status from a chatter on broadcaster’s channel."+ },+ {+ "slug": "TWITCH_RESOLVE_UNBAN_REQUESTS",+ "name": "Resolve Unban Requests",+ "description": "Resolves an unban request by approving or denying it."+ },+ {+ "slug": "TWITCH_SEARCH_CATEGORIES",+ "name": "Search Categories",+ "description": "Gets the games or categories that match the specified query."+ },+ {+ "slug": "TWITCH_SEARCH_CHANNELS",+ "name": "Search Channels",+ "description": "Gets the channels that match the specified query and have streamed content within the past 6 months."+ },+ {+ "slug": "TWITCH_SEND_A_SHOUTOUT",+ "name": "Send a Shoutout",+ "description": "Sends a Shoutout to the specified broadcaster."+ },+ {+ "slug": "TWITCH_SEND_CHAT_ANNOUNCEMENT",+ "name": "Send Chat Announcement",+ "description": "Sends an announcement to the broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_SEND_CHAT_MESSAGE",+ "name": "Send Chat Message",+ "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."+ },+ {+ "slug": "TWITCH_SEND_EXTENSION_CHAT_MESSAGE",+ "name": "Send Extension Chat Message",+ "description": "Sends a message to the specified broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_SEND_EXTENSION_PUBSUB_MESSAGE",+ "name": "Send Extension PubSub Message",+ "description": "Sends a message to one or more viewers."+ },+ {+ "slug": "TWITCH_SEND_GUEST_STAR_INVITE",+ "name": "Send Guest Star Invite",+ "description": "BETA Sends an invite to a specified guest on behalf of the broadcaster for a Guest Star session in progress."+ },+ {+ "slug": "TWITCH_SEND_WHISPER",+ "name": "Send Whisper",+ "description": "Sends a whisper message to the specified user."+ },+ {+ "slug": "TWITCH_SET_EXTENSION_CONFIGURATION_SEGMENT",+ "name": "Set Extension Configuration Segment",+ "description": "Creates or replaces an Extension configuration segment; omitting content deletes the segment."+ },+ {+ "slug": "TWITCH_SET_EXTENSION_REQUIRED_CONFIGURATION",+ "name": "Set Extension Required Configuration",+ "description": "Updates the extension’s required_configuration string."+ },+ {+ "slug": "TWITCH_SNOOZE_NEXT_AD",+ "name": "Snooze Next Ad",+ "description": "Pushes back the timestamp of the upcoming automatic mid-roll ad by 5 minutes."+ },+ {+ "slug": "TWITCH_START_A_RAID",+ "name": "Start a raid",+ "description": "Raid another channel by sending the broadcaster’s viewers to the targeted channel."+ },+ {+ "slug": "TWITCH_START_COMMERCIAL",+ "name": "Start Commercial",+ "description": "Starts a commercial on the specified channel."+ },+ {+ "slug": "TWITCH_UNBAN_USER",+ "name": "Unban User",+ "description": "Removes the ban or timeout that was placed on the specified user."+ },+ {+ "slug": "TWITCH_UNBLOCK_USER",+ "name": "Unblock User",+ "description": "Removes the user from the broadcaster’s list of blocked users."+ },+ {+ "slug": "TWITCH_UNPIN_CHAT_MESSAGE",+ "name": "Unpin Chat Message",+ "description": "Unpins a pinned chat message from the broadcaster’s chat room."+ },+ {+ "slug": "TWITCH_UPDATE_AUTOMOD_SETTINGS",+ "name": "Update AutoMod Settings",+ "description": "Updates the broadcaster’s AutoMod settings."+ },+ {+ "slug": "TWITCH_UPDATE_CHANNEL_GUEST_STAR_SETTINGS",+ "name": "Update Channel Guest Star Settings",+ "description": "BETA Updates Guest Star channel settings; regenerating browser sources immediately invalidates all previously configured browser sources."+ },+ {+ "slug": "TWITCH_UPDATE_CHANNEL_STREAM_SCHEDULE",+ "name": "Update Channel Stream Schedule",+ "description": "Updates the broadcaster’s schedule settings, such as scheduling a vacation."+ },+ {+ "slug": "TWITCH_UPDATE_CHANNEL_STREAM_SCHEDULE_SEGMENT",+ "name": "Update Channel Stream Schedule Segment",+ "description": "Updates a scheduled broadcast segment. Changes to a recurring segment apply to every segment in its series."+ },+ {+ "slug": "TWITCH_UPDATE_CHAT_SETTINGS",+ "name": "Update Chat Settings",+ "description": "Updates the broadcaster’s chat settings."+ },+ {+ "slug": "TWITCH_UPDATE_CONDUITS",+ "name": "Update Conduits",+ "description": "Updates a conduit’s shard count."+ },+ {+ "slug": "TWITCH_UPDATE_CONDUIT_SHARDS",+ "name": "Update Conduit Shards",+ "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."+ },+ {+ "slug": "TWITCH_UPDATE_CUSTOM_REWARD",+ "name": "Update Custom Reward",+ "description": "Updates a custom reward."+ },+ {+ "slug": "TWITCH_UPDATE_DROPS_ENTITLEMENTS",+ "name": "Update Drops Entitlements",+ "description": "Updates the Drop entitlement’s fulfillment status."+ },+ {+ "slug": "TWITCH_UPDATE_EXTENSION_BITS_PRODUCT",+ "name": "Update Extension Bits Product",+ "description": "Adds or updates a Bits product that the extension created."+ },+ {+ "slug": "TWITCH_UPDATE_GUEST_STAR_SLOT",+ "name": "Update Guest Star Slot",+ "description": "BETA Allows a user to update the assigned slot for a particular user within the active Guest Star session."+ },+ {+ "slug": "TWITCH_UPDATE_GUEST_STAR_SLOT_SETTINGS",+ "name": "Update Guest Star Slot Settings",+ "description": "BETA Allows a user to update slot settings for a particular guest within a Guest Star session."+ },+ {+ "slug": "TWITCH_UPDATE_PINNED_CHAT_MESSAGE",+ "name": "Update Pinned Chat Message",+ "description": "Updates the duration of a pinned chat message."+ },+ {+ "slug": "TWITCH_UPDATE_REDEMPTION_STATUS",+ "name": "Update Redemption Status",+ "description": "Updates a redemption’s status."+ },+ {+ "slug": "TWITCH_UPDATE_SHIELD_MODE_STATUS",+ "name": "Update Shield Mode Status",+ "description": "Activates or deactivates the broadcaster’s Shield Mode."+ },+ {+ "slug": "TWITCH_UPDATE_USER",+ "name": "Update User",+ "description": "Updates the user’s information."+ },+ {+ "slug": "TWITCH_UPDATE_USER_CHAT_COLOR",+ "name": "Update User Chat Color",+ "description": "Updates the color used for the user’s name in chat."+ },+ {+ "slug": "TWITCH_UPDATE_USER_EXTENSIONS",+ "name": "Update User Extensions",+ "description": "Updates an installed extension’s information."+ },+ {+ "slug": "TWITCH_WARN_CHAT_USER",+ "name": "Warn Chat User",+ "description": "Warns a user in the specified broadcaster’s chat room, preventing them from chat interaction until the warning is acknowledged."}],"triggers": [],"authConfigDetails": [+ {+ "mode": "NO_AUTH",+ "name": "twitch_no_auth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ },{"mode": "OAUTH2",- "name": "datadog_oauth2",+ "name": "twitch_oauth2",+ "fields": {+ "auth_config_creation": {+ "required": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": true,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": true,+ "default": null+ }+ ],+ "optional": [+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": ""+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ },+ {+ "mode": "S2S_OAUTH2",+ "name": "twitch_app_oauth2",+ "fields": {+ "auth_config_creation": {+ "required": [+ {+ "name": "client_id",+ "displayName": "Twitch Application Client ID",+ "type": "string",+ "description": "The Client ID shown for your application in the Twitch Developer Console under Applications > Manage.",+ "required": true,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Twitch Application Client Secret",+ "type": "string",+ "description": "The client secret generated for the same application in the Twitch Developer Console under Applications > Manage. Keep this value secret.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },+ {+ "slug": "datadog",+ "name": "Datadog",+ "logo": "https://logos.composio.dev/api/datadog",+ "description": "Datadog offers monitoring, observability, and security for cloud-scale applications, unifying metrics, logs, and traces to help teams detect issues and optimize performance",+ "category": "server monitoring",+ "authSchemes": [+ "OAUTH2",+ "API_KEY",+ "BEARER_TOKEN"+ ],+ "toolCount": 65,+ "triggerCount": 0,+ "version": "20260826_00",+ "tools": [+ {+ "slug": "DATADOG_AGGREGATE_LOGS",+ "name": "Aggregate logs",+ "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."+ },+ {+ "slug": "DATADOG_CREATE_DASHBOARD",+ "name": "Create Dashboard",+ "description": "Create a dashboard in Datadog. Dashboards provide customizable visualizations for monitoring your infrastructure, applications, and business metrics in a unified view."+ },+ {+ "slug": "DATADOG_CREATE_DOWNTIME",+ "name": "Create downtime",+ "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."+ },+ {+ "slug": "DATADOG_CREATE_ESCALATION_POLICY",+ "name": "Create On-Call escalation policy",+ "description": "Creates a Datadog On-Call escalation policy."+ },+ {+ "slug": "DATADOG_CREATE_EVENT",+ "name": "Create event",+ "description": "Creates a new event in Datadog. Events are useful for tracking deployments, outages, configuration changes, and other important occurrences."+ },+ {+ "slug": "DATADOG_CREATE_MONITOR",+ "name": "Create monitor",+ "description": "Creates a new Datadog monitor to track metrics, logs, or other data sources with configurable alerting thresholds and notifications."+ },+ {+ "slug": "DATADOG_CREATE_NOTIFICATION_CHANNEL",+ "name": "Create On-Call notification channel",+ "description": "Creates an On-Call notification channel for a Datadog user."+ },+ {+ "slug": "DATADOG_CREATE_NOTIFICATION_RULE",+ "name": "Create On-Call notification rule",+ "description": "Creates an On-Call notification rule for a Datadog user."+ },+ {+ "slug": "DATADOG_CREATE_SCHEDULE",+ "name": "Create On-Call schedule",+ "description": "Creates a Datadog On-Call schedule."+ },+ {+ "slug": "DATADOG_CREATE_SLO",+ "name": "Create SLO",+ "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."+ },+ {+ "slug": "DATADOG_CREATE_SYNTHETIC_API_TEST",+ "name": "Create Synthetic API Test",+ "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."+ },+ {+ "slug": "DATADOG_CREATE_WEBHOOK",+ "name": "Create Webhook",+ "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."+ },+ {+ "slug": "DATADOG_DELETE_DASHBOARD",+ "name": "Delete Dashboard",+ "description": "Delete a dashboard in Datadog. Permanently removes a dashboard from your organization. This action cannot be undone. Use with caution."+ },+ {+ "slug": "DATADOG_DELETE_ESCALATION_POLICY",+ "name": "Delete On-Call escalation policy",+ "description": "Deletes a Datadog On-Call escalation policy by ID. This action cannot be undone."+ },+ {+ "slug": "DATADOG_DELETE_MONITOR",+ "name": "Delete monitor",+ "description": "Deletes a Datadog monitor permanently. Use with caution as this action cannot be undone."+ },+ {+ "slug": "DATADOG_DELETE_NOTIFICATION_CHANNEL",+ "name": "Delete On-Call notification channel",+ "description": "Deletes an On-Call notification channel for a Datadog user. This action cannot be undone."+ },+ {+ "slug": "DATADOG_DELETE_NOTIFICATION_RULE",+ "name": "Delete On-Call notification rule",+ "description": "Deletes an On-Call notification rule for a Datadog user. This action cannot be undone."+ },+ {+ "slug": "DATADOG_DELETE_SCHEDULE",+ "name": "Delete On-Call schedule",+ "description": "Deletes a Datadog On-Call schedule by ID. This action cannot be undone."+ },+ {+ "slug": "DATADOG_GET_DASHBOARD",+ "name": "Get Dashboard",+ "description": "Get a specific dashboard from Datadog. Retrieves detailed information about a dashboard including its widgets, layout, template variables, and metadata."+ },+ {+ "slug": "DATADOG_GET_ESCALATION_POLICY",+ "name": "Get On-Call escalation policy",+ "description": "Retrieves a Datadog On-Call escalation policy by ID."+ },+ {+ "slug": "DATADOG_GET_MONITOR",+ "name": "Get monitor",+ "description": "Retrieves detailed information about a specific Datadog monitor, including its current state, configuration, and any active downtimes."+ },+ {+ "slug": "DATADOG_GET_NOTIFICATION_CHANNEL",+ "name": "Get On-Call notification channel",+ "description": "Retrieves an On-Call notification channel for a user by ID."+ },+ {+ "slug": "DATADOG_GET_NOTIFICATION_RULE",+ "name": "Get On-Call notification rule",+ "description": "Retrieves an On-Call notification rule for a user by ID."+ },+ {+ "slug": "DATADOG_GET_SCHEDULE",+ "name": "Get On-Call schedule",+ "description": "Retrieves a Datadog On-Call schedule by ID."+ },+ {+ "slug": "DATADOG_GET_SCHEDULED_ON_CALL_USER",+ "name": "Get scheduled on-call user",+ "description": "Gets the currently scheduled on-call user for a Datadog On-Call schedule."+ },+ {+ "slug": "DATADOG_GET_SERVICE_DEPENDENCIES",+ "name": "Get Service Dependencies",+ "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."+ },+ {+ "slug": "DATADOG_GET_SYNTHETICS_LOCATIONS",+ "name": "Get Synthetics Locations",+ "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."+ },+ {+ "slug": "DATADOG_GET_TAGS",+ "name": "Get host tags",+ "description": "Retrieves all tags associated with a specific host in Datadog. Useful for understanding host metadata and organizing infrastructure."+ },+ {+ "slug": "DATADOG_GET_TEAM_ON_CALL_USERS",+ "name": "Get team on-call users",+ "description": "Gets the current on-call users for a Datadog On-Call team."+ },+ {+ "slug": "DATADOG_GET_TEAM_ROUTING_RULES",+ "name": "Get On-Call team routing rules",+ "description": "Gets the Datadog On-Call routing rules configured for a team."+ },+ {+ "slug": "DATADOG_GET_TRACE_BY_ID",+ "name": "Get Trace by ID",+ "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."+ },+ {+ "slug": "DATADOG_GET_USAGE_SUMMARY",+ "name": "Get usage summary",+ "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."+ },+ {+ "slug": "DATADOG_LIST_ALL_TAGS",+ "name": "List All Tags",+ "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."+ },+ {+ "slug": "DATADOG_LIST_API_KEYS",+ "name": "List API Keys",+ "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."+ },+ {+ "slug": "DATADOG_LIST_APM_SERVICES",+ "name": "List APM Services",+ "description": "List APM services from Datadog. Application Performance Monitoring (APM) provides deep visibility into your applications, helping you track performance, errors, and dependencies."+ },+ {+ "slug": "DATADOG_LIST_AWS_INTEGRATION",+ "name": "List AWS Integration",+ "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."+ },+ {+ "slug": "DATADOG_LIST_DASHBOARDS",+ "name": "List dashboards",+ "description": "Lists all Datadog dashboards with basic information. Useful for dashboard management and getting an overview of available dashboards."+ },+ {+ "slug": "DATADOG_LIST_EVENTS",+ "name": "List events",+ "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."+ },+ {+ "slug": "DATADOG_LIST_HOSTS",+ "name": "List hosts",+ "description": "Lists all hosts in your Datadog infrastructure with detailed information including metrics, tags, and status. Useful for infrastructure monitoring and management."+ },+ {+ "slug": "DATADOG_LIST_INCIDENTS",+ "name": "List Incidents",+ "description": "List incidents from Datadog. Incident Management helps you track, manage, and resolve incidents efficiently with comprehensive timeline and impact tracking."+ },+ {+ "slug": "DATADOG_LIST_LOG_INDEXES",+ "name": "List Log Indexes",+ "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."+ },+ {+ "slug": "DATADOG_LIST_METRICS",+ "name": "List active metrics",+ "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."+ },+ {+ "slug": "DATADOG_LIST_MONITORS",+ "name": "List monitors",+ "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."+ },+ {+ "slug": "DATADOG_LIST_NOTIFICATION_CHANNELS",+ "name": "List On-Call notification channels",+ "description": "Lists the On-Call notification channels configured for a Datadog user."+ },+ {+ "slug": "DATADOG_LIST_NOTIFICATION_RULES",+ "name": "List On-Call notification rules",+ "description": "Lists the On-Call notification rules configured for a Datadog user."+ },+ {+ "slug": "DATADOG_LIST_ROLES",+ "name": "List Roles",+ "description": "List roles from Datadog organization. Roles define sets of permissions that control what users can do within your Datadog organization."+ },+ {+ "slug": "DATADOG_LIST_SERVICE_CHECKS",+ "name": "List service checks",+ "description": "Lists service checks from Datadog. Service checks are status checks that track the health of your services and infrastructure components."+ },+ {+ "slug": "DATADOG_LIST_SL_OS",+ "name": "List SLOs",+ "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."+ },+ {+ "slug": "DATADOG_LIST_SYNTHETICS",+ "name": "List Synthetics Tests",+ "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."+ },+ {+ "slug": "DATADOG_LIST_USERS",+ "name": "List Users",+ "description": "List users from Datadog organization. User management allows you to see team members, their roles, and access levels within your Datadog organization."+ },+ {+ "slug": "DATADOG_LIST_WEBHOOKS",+ "name": "List Webhooks",+ "description": "List webhooks from Datadog. Webhooks allow you to send notifications to external services when monitors trigger, enabling integration with your workflows."+ },+ {+ "slug": "DATADOG_MUTE_MONITOR",+ "name": "Mute Monitor",+ "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."+ },+ {+ "slug": "DATADOG_QUERY_METRICS",+ "name": "Query metrics",+ "description": "Queries Datadog metrics and returns time series data. Useful for retrieving historical metric data, creating custom dashboards, or building reports."+ },+ {+ "slug": "DATADOG_SEARCH_LOGS",+ "name": "Search logs",+ "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."+ },+ {+ "slug": "DATADOG_SEARCH_SPANS_ANALYTICS",+ "name": "Search Spans Analytics",+ "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."+ },+ {+ "slug": "DATADOG_SEARCH_TRACES",+ "name": "Search Traces",+ "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."+ },+ {+ "slug": "DATADOG_SET_TEAM_ROUTING_RULES",+ "name": "Set On-Call team routing rules",+ "description": "Replaces (sets) the On-Call routing rules for a Datadog team."+ },+ {+ "slug": "DATADOG_SUBMIT_METRICS",+ "name": "Submit metrics",+ "description": "Submits custom metrics to Datadog. Useful for sending application-specific metrics, business KPIs, or custom performance indicators."+ },+ {+ "slug": "DATADOG_UNMUTE_MONITOR",+ "name": "Unmute Monitor",+ "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."+ },+ {+ "slug": "DATADOG_UPDATE_DASHBOARD",+ "name": "Update Dashboard",+ "description": "Update a dashboard in Datadog. Updates an existing dashboard with new configuration, widgets, or layout while preserving its identity and creation metadata."+ },+ {+ "slug": "DATADOG_UPDATE_ESCALATION_POLICY",+ "name": "Update On-Call escalation policy",+ "description": "Updates a Datadog On-Call escalation policy by ID."+ },+ {+ "slug": "DATADOG_UPDATE_HOST_TAGS",+ "name": "Update host tags",+ "description": "Updates tags for a specific host in Datadog. This replaces all existing tags from the specified source with the new tags provided."+ },+ {+ "slug": "DATADOG_UPDATE_MONITOR",+ "name": "Update monitor",+ "description": "Updates an existing Datadog monitor with new configuration, thresholds, or notification settings. Only specified fields will be updated."+ },+ {+ "slug": "DATADOG_UPDATE_NOTIFICATION_RULE",+ "name": "Update On-Call notification rule",+ "description": "Updates an On-Call notification rule for a user by ID."+ },+ {+ "slug": "DATADOG_UPDATE_SCHEDULE",+ "name": "Update On-Call schedule",+ "description": "Updates a Datadog On-Call schedule by ID."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "OAUTH2",+ "name": "datadog_oauth2","fields": {"auth_config_creation": {"required": [@@ -112083,7 +113234,7 @@],"toolCount": 3,"triggerCount": 0,- "version": "20260615_00",+ "version": "20260908_00","tools": [{"slug": "ABSTRACT_EMAIL_REPUTATION_API",@@ -117537,6 +118688,90 @@}]},+ {+ "slug": "airwallex",+ "name": "Airwallex",+ "logo": "https://logos.composio.dev/api/airwallex",+ "description": "Airwallex provides business accounts, payments, payouts, foreign exchange, cards, and financial operations through a unified global financial platform.",+ "category": "payment processing",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 7,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "AIRWALLEX_GET_CURRENT_ACCOUNT",+ "name": "Get Current Account",+ "description": "Retrieve identity, status, and profile details for the connected Airwallex account."+ },+ {+ "slug": "AIRWALLEX_GET_CURRENT_BALANCES",+ "name": "Get Current Balances",+ "description": "Return available, pending, reserved, prepayment, and total balances by currency for an Airwallex account type."+ },+ {+ "slug": "AIRWALLEX_GET_SUPPORTED_CONVERSION_CURRENCIES",+ "name": "Get Supported Conversion Currencies",+ "description": "Return the connected client's currencies supported for buying and selling in conversions."+ },+ {+ "slug": "AIRWALLEX_LIST_BENEFICIARIES",+ "name": "List Beneficiaries",+ "description": "List beneficiaries, optionally filtered by identity, bank account, entity type, or creation date. Returns one page and a cursor for continuation."+ },+ {+ "slug": "AIRWALLEX_LIST_CONVERSIONS",+ "name": "List Conversions",+ "description": "List recent currency conversions, optionally filtered by currencies, request ID, status, or creation time. Returns one page and a continuation cursor."+ },+ {+ "slug": "AIRWALLEX_LIST_GLOBAL_ACCOUNTS",+ "name": "List Global Accounts",+ "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."+ },+ {+ "slug": "AIRWALLEX_LIST_TRANSFERS",+ "name": "List Transfers",+ "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."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "airwallex_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "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.",+ "required": true,+ "default": null+ },+ {+ "name": "generic_id",+ "displayName": "Client ID",+ "type": "string",+ "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.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "aivoov","name": "Aivoov",@@ -117594,12 +118829,12 @@],"toolCount": 10,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{"slug": "AIWYN_TAX_MCP_CALCULATE_TAX","name": "Calculate tax",- "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."+ "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."},{"slug": "AIWYN_TAX_MCP_CHECK_TAX",@@ -117629,7 +118864,7 @@{"slug": "AIWYN_TAX_MCP_TAX_NAMESPACES","name": "Tax namespaces",- "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."+ "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."},{"slug": "AIWYN_TAX_MCP_TAX_NAMESPACE_SCHEMA",@@ -122417,7 +123652,7 @@],"toolCount": 113,"triggerCount": 0,- "version": "20260821_00",+ "version": "20260902_00","tools": [{"slug": "APIFY_ACT_BUILDS_POST",@@ -133965,6 +135200,87 @@}]},+ {+ "slug": "bluepillow",+ "name": "Blue Pillow Hotels & Stays",+ "logo": "https://logos.composio.dev/api/bluepillow",+ "description": "Blue Pillow provides AI agents with hotel and stay discovery, live offer comparison, recommendations, validation, and tracked booking handoff.",+ "category": "ai agents",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 8,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "BLUEPILLOW_CREATE_BOOKING_HANDOFF",+ "name": "Create Booking Handoff",+ "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."+ },+ {+ "slug": "BLUEPILLOW_DISCOVER_DESTINATIONS_NEAR",+ "name": "Discover Destinations Near Coordinates",+ "description": "Find cities, neighborhoods, airports, or points of interest near geographic coordinates."+ },+ {+ "slug": "BLUEPILLOW_GET_PROPERTY",+ "name": "Get Property",+ "description": "Get canonical details and optional review enrichments for one property; use search or hotel recommendation for live availability."+ },+ {+ "slug": "BLUEPILLOW_RECOMMEND_OFFER_FOR_PROPERTY",+ "name": "Recommend Offer for Property",+ "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."+ },+ {+ "slug": "BLUEPILLOW_RECOMMEND_STAY",+ "name": "Recommend Stay",+ "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."+ },+ {+ "slug": "BLUEPILLOW_RESOLVE_DESTINATION",+ "name": "Resolve Destination",+ "description": "Resolve a place name into destination IDs for stay search, including ambiguity and confidence information."+ },+ {+ "slug": "BLUEPILLOW_SEARCH_STAYS",+ "name": "Search Stays",+ "description": "Search one page of ranked live stay inventory with availability, prices, OTA offers, and an opaque cursor for more results."+ },+ {+ "slug": "BLUEPILLOW_VALIDATE_OFFER",+ "name": "Validate Offer",+ "description": "Re-price a previously seen EUR offer and report whether it remains valid within the provider's two-percent tolerance."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "bluepillow_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "B2A API Key",+ "type": "string",+ "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.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "bluebarry","name": "Bluebarry",@@ -137087,6 +138403,650 @@}]},+ {+ "slug": "braze",+ "name": "Braze",+ "logo": "https://logos.composio.dev/api/braze",+ "description": "Braze is a customer engagement platform for managing user data, messaging, campaigns, analytics, catalogs, templates, and workspace automation.",+ "category": "marketing automation",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 119,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "BRAZE_BLOCKLIST_EMAILS",+ "name": "Blocklist Emails",+ "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."+ },+ {+ "slug": "BRAZE_CANCEL_SEGMENT_EXPORTS",+ "name": "Cancel Segment Exports",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CAMPAIGN_TRIGGER_SCHEDULE",+ "name": "Schedule Campaign Trigger",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CANVAS_TRIGGER_SCHEDULE",+ "name": "Schedule Canvas Trigger",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CATALOG",+ "name": "Create Catalog",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CATALOG_FIELDS",+ "name": "Create Catalog Fields",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CATALOG_ITEM",+ "name": "Create Catalog Item",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CATALOG_ITEMS",+ "name": "Create Multiple Catalog Items",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CATALOG_SELECTION",+ "name": "Create Catalog Selection",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_CONTENT_BLOCK",+ "name": "Create Content Block",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_EMAIL_TEMPLATE",+ "name": "Create Email Template",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_MEDIA_LIBRARY_ASSET",+ "name": "Create Media Library Asset",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_MESSAGE_SCHEDULE",+ "name": "Create Message Schedule",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_PREFERENCE_CENTER",+ "name": "Create Preference Center",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_SDK_AUTHENTICATION_KEY",+ "name": "Create SDK Authentication Key",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_SEND_ID",+ "name": "Create Send ID",+ "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."+ },+ {+ "slug": "BRAZE_CREATE_USER_ALIASES",+ "name": "Create User Aliases",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CAMPAIGN_TRIGGER_SCHEDULE",+ "name": "Delete Campaign Trigger Schedule",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CANVAS_TRIGGER_SCHEDULE",+ "name": "Delete Canvas Trigger Schedule",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CATALOG",+ "name": "Delete Catalog",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CATALOG_FIELD",+ "name": "Delete Catalog Field",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CATALOG_ITEM",+ "name": "Delete Catalog Item",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CATALOG_ITEMS",+ "name": "Delete Multiple Catalog Items",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_CATALOG_SELECTION",+ "name": "Delete Catalog Selection",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_MESSAGE_SCHEDULE",+ "name": "Delete Message Schedule",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_SDK_AUTHENTICATION_KEY",+ "name": "Delete SDK Authentication Key",+ "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."+ },+ {+ "slug": "BRAZE_DELETE_USERS",+ "name": "Delete Users",+ "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."+ },+ {+ "slug": "BRAZE_DUPLICATE_CAMPAIGN",+ "name": "Duplicate Campaign",+ "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."+ },+ {+ "slug": "BRAZE_DUPLICATE_CANVAS",+ "name": "Duplicate Canvas",+ "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."+ },+ {+ "slug": "BRAZE_END_LIVE_ACTIVITY",+ "name": "End Live Activity",+ "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."+ },+ {+ "slug": "BRAZE_EXPORT_GLOBAL_CONTROL_GROUP_USERS",+ "name": "Export Global Control Group Users",+ "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."+ },+ {+ "slug": "BRAZE_EXPORT_SEGMENT_USERS",+ "name": "Export Segment Users",+ "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."+ },+ {+ "slug": "BRAZE_EXPORT_USERS_BY_IDENTIFIERS",+ "name": "Export Users by Identifiers",+ "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."+ },+ {+ "slug": "BRAZE_GENERATE_PREFERENCE_CENTER_URL",+ "name": "Generate Preference Center URL",+ "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."+ },+ {+ "slug": "BRAZE_GET_CAMPAIGN",+ "name": "Get Campaign",+ "description": "Return configuration and delivery details for one campaign identified by its Braze campaign ID."+ },+ {+ "slug": "BRAZE_GET_CAMPAIGN_ANALYTICS",+ "name": "Get Campaign Analytics",+ "description": "Get up to 100 daily campaign analytics points. Dashboard and Currents aggregation definitions can differ."+ },+ {+ "slug": "BRAZE_GET_CAMPAIGN_TRANSLATION_SOURCE",+ "name": "Get Campaign Translation Source",+ "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."+ },+ {+ "slug": "BRAZE_GET_CANVAS",+ "name": "Get Canvas",+ "description": "Return configuration and step details for one Canvas identified by its Braze Canvas ID."+ },+ {+ "slug": "BRAZE_GET_CANVAS_ANALYTICS",+ "name": "Get Canvas Analytics",+ "description": "Export Canvas daily time-series analytics with optional variant, step, and deleted-step breakdowns. Dashboard and Currents definitions can differ."+ },+ {+ "slug": "BRAZE_GET_CANVAS_ANALYTICS_SUMMARY",+ "name": "Get Canvas Analytics Summary",+ "description": "Export Canvas analytics rollups with optional variant, step, and deleted-step breakdowns. Braze normalizes range timestamps to midnight in the company time zone."+ },+ {+ "slug": "BRAZE_GET_CANVAS_TRANSLATION_SOURCE",+ "name": "Get Canvas Translation Source",+ "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."+ },+ {+ "slug": "BRAZE_GET_CATALOG_ITEM",+ "name": "Get Catalog Item",+ "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."+ },+ {+ "slug": "BRAZE_GET_CONTENT_BLOCK",+ "name": "Get Content Block",+ "description": "Return one persisted Braze Content Block by API identifier, optionally with its current campaign and Canvas inclusion records."+ },+ {+ "slug": "BRAZE_GET_CONTENT_BLOCK_TRANSLATION_SOURCE",+ "name": "Get Content Block Translation Source",+ "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."+ },+ {+ "slug": "BRAZE_GET_CUSTOM_EVENT_ANALYTICS",+ "name": "Get Custom Event Analytics",+ "description": "Get 1 to 100 daily or hourly occurrence counts for one custom event, optionally filtered by app and analytics-enabled segment."+ },+ {+ "slug": "BRAZE_GET_EMAIL_TEMPLATE",+ "name": "Get Email Template",+ "description": "Return one stored HTML email template by API identifier. Braze does not accept drag-and-drop-editor templates on this endpoint."+ },+ {+ "slug": "BRAZE_GET_EMAIL_TEMPLATE_TRANSLATION_SOURCE",+ "name": "Get Email Template Translation Source",+ "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."+ },+ {+ "slug": "BRAZE_GET_PREFERENCE_CENTER",+ "name": "Get Preference Center",+ "description": "Get persisted HTML, state, options, identifiers, and timestamps for one Braze preference center. Limited to 1,000 requests/minute per workspace."+ },+ {+ "slug": "BRAZE_GET_PURCHASE_SERIES",+ "name": "Get Purchase Series",+ "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."+ },+ {+ "slug": "BRAZE_GET_SEGMENT",+ "name": "Get Segment",+ "description": "Return Braze's documented configuration details for one segment identified by its segment API identifier."+ },+ {+ "slug": "BRAZE_GET_SEGMENT_ANALYTICS",+ "name": "Get Segment Analytics",+ "description": "Get up to 100 daily estimated segment-size points. Export and count segment users when an exact size is required."+ },+ {+ "slug": "BRAZE_GET_SEND_ANALYTICS",+ "name": "Get Send Analytics",+ "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."+ },+ {+ "slug": "BRAZE_GET_SESSION_ANALYTICS",+ "name": "Get Session Analytics",+ "description": "Get 1 to 100 daily or hourly session-count points, optionally filtered by app and analytics-enabled segment."+ },+ {+ "slug": "BRAZE_GET_SUBSCRIPTION_GROUP_STATUS",+ "name": "Get Subscription Group Status",+ "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."+ },+ {+ "slug": "BRAZE_GET_USER_KPI_SERIES",+ "name": "Get User KPI Series",+ "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."+ },+ {+ "slug": "BRAZE_GET_WEBHOOK_TEMPLATE_TRANSLATION_SOURCE",+ "name": "Get Webhook Template Translation Source",+ "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."+ },+ {+ "slug": "BRAZE_IDENTIFY_USERS",+ "name": "Identify Users",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CAMPAIGNS",+ "name": "List Campaigns",+ "description": "Return one page of Braze campaigns for discovery, optionally including archived campaigns and filtering by last edit time."+ },+ {+ "slug": "BRAZE_LIST_CAMPAIGN_TRANSLATIONS",+ "name": "List Campaign Translations",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CANVASES",+ "name": "List Canvases",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CANVAS_TRANSLATIONS",+ "name": "List Canvas Translations",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CATALOG_ITEMS",+ "name": "List Catalog Items",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CATALOGS",+ "name": "List Catalogs",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CLOUD_DATA_INGESTION_INTEGRATIONS",+ "name": "List Cloud Data Ingestion Integrations",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CLOUD_DATA_INGESTION_SYNC_STATUSES",+ "name": "List Cloud Data Ingestion Sync Statuses",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CONTENT_BLOCKS",+ "name": "List Content Blocks",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CONTENT_BLOCK_TRANSLATIONS",+ "name": "List Content Block Translations",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CUSTOM_ATTRIBUTES",+ "name": "List Custom Attributes",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CUSTOM_EVENT_NAMES",+ "name": "List Custom Event Names",+ "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."+ },+ {+ "slug": "BRAZE_LIST_CUSTOM_EVENTS",+ "name": "List Custom Events",+ "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."+ },+ {+ "slug": "BRAZE_LIST_EMAIL_TEMPLATE_LOCALE_TRANSLATIONS",+ "name": "List Email Template Locale Translations",+ "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."+ },+ {+ "slug": "BRAZE_LIST_EMAIL_TEMPLATES",+ "name": "List Email Templates",+ "description": "Return one offset-based page of stored HTML email templates. Drag-and-drop templates are excluded; omit offset on the first call."+ },+ {+ "slug": "BRAZE_LIST_EMAIL_TEMPLATE_TRANSLATIONS",+ "name": "List Email Template Translations",+ "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."+ },+ {+ "slug": "BRAZE_LIST_HARD_BOUNCED_EMAILS",+ "name": "List Hard Bounced Emails",+ "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."+ },+ {+ "slug": "BRAZE_LIST_INVALID_PHONE_NUMBERS",+ "name": "List Invalid Phone Numbers",+ "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."+ },+ {+ "slug": "BRAZE_LIST_PREFERENCE_CENTERS",+ "name": "List Preference Centers",+ "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."+ },+ {+ "slug": "BRAZE_LIST_PURCHASE_PRODUCTS",+ "name": "List Purchase Products",+ "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."+ },+ {+ "slug": "BRAZE_LIST_SCHEDULED_BROADCASTS",+ "name": "List Scheduled Broadcasts",+ "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."+ },+ {+ "slug": "BRAZE_LIST_SDK_AUTHENTICATION_KEYS",+ "name": "List SDK Authentication Keys",+ "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."+ },+ {+ "slug": "BRAZE_LIST_SEGMENTS",+ "name": "List Segments",+ "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."+ },+ {+ "slug": "BRAZE_LIST_UNSUBSCRIBED_EMAILS",+ "name": "List Unsubscribed Emails",+ "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."+ },+ {+ "slug": "BRAZE_LIST_USER_SUBSCRIPTION_GROUPS",+ "name": "List User Subscription Groups",+ "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."+ },+ {+ "slug": "BRAZE_LIST_WEBHOOK_TEMPLATE_TRANSLATIONS",+ "name": "List Webhook Template Translations",+ "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."+ },+ {+ "slug": "BRAZE_MERGE_USERS",+ "name": "Merge Users",+ "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."+ },+ {+ "slug": "BRAZE_REMOVE_EXTERNAL_IDS",+ "name": "Remove Deprecated External IDs",+ "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."+ },+ {+ "slug": "BRAZE_REMOVE_HARD_BOUNCED_EMAILS",+ "name": "Remove Hard Bounced Emails",+ "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."+ },+ {+ "slug": "BRAZE_REMOVE_INVALID_PHONE_NUMBERS",+ "name": "Remove Invalid Phone Numbers",+ "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."+ },+ {+ "slug": "BRAZE_REMOVE_SPAM_EMAILS",+ "name": "Remove Emails From Spam List",+ "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."+ },+ {+ "slug": "BRAZE_RENAME_EXTERNAL_IDS",+ "name": "Rename External IDs",+ "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."+ },+ {+ "slug": "BRAZE_REPLACE_CATALOG_ITEM",+ "name": "Replace Catalog Item",+ "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."+ },+ {+ "slug": "BRAZE_REPLACE_CATALOG_ITEMS",+ "name": "Replace Multiple Catalog Items",+ "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."+ },+ {+ "slug": "BRAZE_REPLACE_MEDIA_LIBRARY_ASSET_FILE",+ "name": "Replace Media Library Asset File",+ "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."+ },+ {+ "slug": "BRAZE_SEND_CAMPAIGN_TRIGGER",+ "name": "Send Campaign Trigger",+ "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."+ },+ {+ "slug": "BRAZE_SEND_CANVAS_TRIGGER",+ "name": "Send Canvas Trigger",+ "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."+ },+ {+ "slug": "BRAZE_SEND_MESSAGES",+ "name": "Send API-Only Messages",+ "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."+ },+ {+ "slug": "BRAZE_SEND_TRANSACTIONAL_CAMPAIGN",+ "name": "Send Transactional Campaign",+ "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."+ },+ {+ "slug": "BRAZE_SET_EMAIL_SUBSCRIPTION_STATUS",+ "name": "Set Global Email Subscription Status",+ "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."+ },+ {+ "slug": "BRAZE_SET_PRIMARY_SDK_AUTHENTICATION_KEY",+ "name": "Set Primary SDK Authentication Key",+ "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."+ },+ {+ "slug": "BRAZE_SET_SUBSCRIPTION_GROUP_STATUS",+ "name": "Set Subscription Group Status",+ "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."+ },+ {+ "slug": "BRAZE_SET_SUBSCRIPTION_GROUP_STATUSES",+ "name": "Set Subscription Group Statuses",+ "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."+ },+ {+ "slug": "BRAZE_START_LIVE_ACTIVITY",+ "name": "Start Live Activity",+ "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."+ },+ {+ "slug": "BRAZE_TRACK_USERS",+ "name": "Create and Update Users",+ "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."+ },+ {+ "slug": "BRAZE_TRIGGER_CLOUD_DATA_INGESTION_SYNC",+ "name": "Trigger Cloud Data Ingestion Sync",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CAMPAIGN_TRANSLATIONS",+ "name": "Update Campaign Translations",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CAMPAIGN_TRIGGER_SCHEDULE",+ "name": "Update Campaign Trigger Schedule",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CANVAS_TRANSLATIONS",+ "name": "Update Canvas Translations",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CANVAS_TRIGGER_SCHEDULE",+ "name": "Update Canvas Trigger Schedule",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CATALOG_ITEM",+ "name": "Update Catalog Item",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CATALOG_ITEMS",+ "name": "Update Multiple Catalog Items",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CONTENT_BLOCK",+ "name": "Update Content Block",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_CONTENT_BLOCK_TRANSLATIONS",+ "name": "Update Content Block Translations",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_EMAIL_TEMPLATE",+ "name": "Update Email Template",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_EMAIL_TEMPLATE_TRANSLATIONS",+ "name": "Update Email Template Translations",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_LIVE_ACTIVITY",+ "name": "Update Live Activity",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_MESSAGE_SCHEDULE",+ "name": "Update Message Schedule",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_PREFERENCE_CENTER",+ "name": "Update Preference Center",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_PUSH_CREDENTIALS",+ "name": "Update Push Credentials",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_USER_ALIASES",+ "name": "Update User Aliases",+ "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."+ },+ {+ "slug": "BRAZE_UPDATE_WEBHOOK_TEMPLATE_TRANSLATIONS",+ "name": "Update Webhook Template Translations",+ "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."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "braze_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "full",+ "displayName": "REST Endpoint",+ "type": "string",+ "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.",+ "required": true,+ "default": null+ },+ {+ "name": "generic_api_key",+ "displayName": "REST API Key",+ "type": "string",+ "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.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "bread_butter","name": "Bread & Butter",@@ -140656,6 +142616,251 @@}]},+ {+ "slug": "calendly_mcp",+ "name": "Calendly MCP",+ "logo": "https://logos.composio.dev/api/calendly_mcp",+ "description": "Calendly MCP lets agents manage event types and availability, find open times, generate scheduling links, book meetings, and cancel scheduled events.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 36,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "CALENDLY_MCP_AVAILABILITY_GET_USER_AVAILABILITY_SCHEDULE",+ "name": "Availability-get user availability schedule",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_AVAILABILITY_LIST_USER_AVAILABILITY_SCHEDULES",+ "name": "Availability-list user availability schedules",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_AVAILABILITY_LIST_USER_BUSY_TIMES",+ "name": "Availability-list user busy times",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_CREATE_EVENT_TYPE",+ "name": "Event types-create event type",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_GET_EVENT_TYPE",+ "name": "Event types-get event type",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPE_AVAILABILITY_SCHEDULE",+ "name": "Event types-list event type availability schedule",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPE_AVAILABLE_TIMES",+ "name": "Event types-list event type available times",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_LIST_EVENT_TYPES",+ "name": "Event types-list event types",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_UPDATE_EVENT_TYPE",+ "name": "Event types-update event type",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_EVENT_TYPES_UPDATE_EVENT_TYPE_AVAILABILITY_SCHEDULE",+ "name": "Event types-update event type availability schedule",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_LIST_CALENDLY_SKILLS",+ "name": "List calendly skills",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_LOAD_CALENDLY_SKILL",+ "name": "Load calendly skill",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_LOCATIONS_LIST_USER_MEETING_LOCATIONS",+ "name": "Locations-list user meeting locations",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_CANCEL_EVENT",+ "name": "Meetings-cancel event",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_CREATE_INVITEE",+ "name": "Meetings-create invitee",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_CREATE_INVITEE_NO_SHOW",+ "name": "Meetings-create invitee no show",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_DELETE_INVITEE_NO_SHOW",+ "name": "Meetings-delete invitee no show",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_GET_EVENT",+ "name": "Meetings-get event",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_GET_EVENT_INVITEE",+ "name": "Meetings-get event invitee",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_GET_INVITEE_NO_SHOW",+ "name": "Meetings-get invitee no show",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_LIST_EVENT_INVITEES",+ "name": "Meetings-list event invitees",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_MEETINGS_LIST_EVENTS",+ "name": "Meetings-list events",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_ORGANIZATIONS_CREATE_ORGANIZATION_INVITATION",+ "name": "Organizations-create organization invitation",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_ORGANIZATIONS_GET_ORGANIZATION",+ "name": "Organizations-get organization",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_ORGANIZATIONS_GET_ORGANIZATION_MEMBERSHIP",+ "name": "Organizations-get organization membership",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_ORGANIZATIONS_LIST_ORGANIZATION_INVITATIONS",+ "name": "Organizations-list organization invitations",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_ORGANIZATIONS_LIST_ORGANIZATION_MEMBERSHIPS",+ "name": "Organizations-list organization memberships",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_ORGANIZATIONS_REVOKE_ORGANIZATION_INVITATION",+ "name": "Organizations-revoke organization invitation",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_ROUTING_FORMS_GET_ROUTING_FORM",+ "name": "Routing forms-get routing form",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_ROUTING_FORMS_GET_ROUTING_FORM_SUBMISSION",+ "name": "Routing forms-get routing form submission",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_ROUTING_FORMS_LIST_ROUTING_FORMS",+ "name": "Routing forms-list routing forms",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_ROUTING_FORMS_LIST_ROUTING_FORM_SUBMISSIONS",+ "name": "Routing forms-list routing form submissions",+ "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`."+ },+ {+ "slug": "CALENDLY_MCP_SCHEDULING_LINKS_CREATE_SINGLE_USE_SCHEDULING_LINK",+ "name": "Scheduling links-create single use scheduling link",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_SHARES_CREATE_SHARE",+ "name": "Shares-create share",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_USERS_GET_CURRENT_USER",+ "name": "Users-get current user",+ "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."+ },+ {+ "slug": "CALENDLY_MCP_USERS_GET_USER",+ "name": "Users-get user",+ "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."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "calendly_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": ""+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "callerapi","name": "Callerapi",@@ -141533,6 +143738,101 @@}]},+ {+ "slug": "candid_mcp",+ "name": "Candid MCP",+ "logo": "https://logos.composio.dev/api/candid_mcp",+ "description": "Candid MCP lets agents research nonprofit organizations, funders, funding opportunities, social-sector knowledge, and related news using Candid data.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 6,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "CANDID_MCP_CURRENT_DATE",+ "name": "Current date",+ "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"+ },+ {+ "slug": "CANDID_MCP_IDENTIFY_LOCATIONS",+ "name": "Identify locations",+ "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."+ },+ {+ "slug": "CANDID_MCP_IDENTIFY_MENTIONED_ORGANIZATIONS",+ "name": "Identify mentioned organizations",+ "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"+ },+ {+ "slug": "CANDID_MCP_KNOWLEDGE_RESOURCES",+ "name": "Knowledge resources",+ "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]"+ },+ {+ "slug": "CANDID_MCP_SEARCH_ORGANIZATIONS",+ "name": "Search organizations",+ "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"+ },+ {+ "slug": "CANDID_MCP_TAXONOMY_TERMS",+ "name": "Taxonomy terms",+ "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."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "candid_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,claudeai"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "canny","name": "Canny",@@ -146647,6 +148947,97 @@}]},+ {+ "slug": "chartmogul",+ "name": "ChartMogul",+ "logo": "https://logos.composio.dev/api/chartmogul",+ "description": "ChartMogul is a subscription analytics and revenue data platform for managing customers, billing data, metrics, and sales opportunities.",+ "category": "analytics",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "CHARTMOGUL_CREATE_CUSTOMER",+ "name": "Create Customer",+ "description": "Create a customer under a ChartMogul data source using a caller-owned external ID and optional profile or lead details."+ },+ {+ "slug": "CHARTMOGUL_DELETE_CUSTOMER",+ "name": "Delete Customer",+ "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."+ },+ {+ "slug": "CHARTMOGUL_GET_ACCOUNT",+ "name": "Get Account",+ "description": "Return the connected ChartMogul account's identity, reporting currency, time zone, week start, and optionally selected churn and refund settings."+ },+ {+ "slug": "CHARTMOGUL_GET_CUSTOMER",+ "name": "Get Customer",+ "description": "Return one customer and its identifiers, lifecycle status, revenue values, ownership, location, and attributes by ChartMogul UUID."+ },+ {+ "slug": "CHARTMOGUL_GET_KEY_METRICS",+ "name": "Get Key Metrics",+ "description": "Return all key subscription metrics and current summaries for a date range, optionally grouped by interval and filtered by countries or plans."+ },+ {+ "slug": "CHARTMOGUL_LIST_ACTIVITIES",+ "name": "List Activities",+ "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."+ },+ {+ "slug": "CHARTMOGUL_LIST_CUSTOMERS",+ "name": "List Customers",+ "description": "Return one page of customers filtered by source, identifier, email, status, or billing system."+ },+ {+ "slug": "CHARTMOGUL_LIST_PLANS",+ "name": "List Plans",+ "description": "Return one page of subscription plans, optionally filtered by source, external ID, or billing system."+ },+ {+ "slug": "CHARTMOGUL_LIST_SOURCES",+ "name": "List Sources",+ "description": "Return the account's billing data sources, optionally filtered by name or system and with selected source settings included."+ },+ {+ "slug": "CHARTMOGUL_UPDATE_CUSTOMER",+ "name": "Update Customer",+ "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."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "chartmogul_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "Read & Write API Key",+ "type": "string",+ "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.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "chaser","name": "Chaser",@@ -149495,6 +151886,301 @@}]},+ {+ "slug": "clarify_mcp",+ "name": "Clarify MCP",+ "logo": "https://logos.composio.dev/api/clarify_mcp",+ "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.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 46,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "CLARIFY_MCP_ADD_COMMENT",+ "name": "Add-comment",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_CAMPAIGN",+ "name": "Create-campaign",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_CREATE_EMAIL_DRAFT",+ "name": "Create-email-draft",+ "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)."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_AGENT",+ "name": "Create-or-update-agent",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_ARTIFACT",+ "name": "Create-or-update-artifact",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_CALENDAR_EVENT",+ "name": "Create-or-update-calendar-event",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_CUSTOM_OBJECT",+ "name": "Create-or-update-custom-object",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_FIELDS",+ "name": "Create-or-update-fields",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_LIST",+ "name": "Create-or-update-list",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_RECORDS",+ "name": "Create-or-update-records",+ "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: \"[email protected]\", 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."+ },+ {+ "slug": "CLARIFY_MCP_CREATE_OR_UPDATE_WORKFLOW",+ "name": "Create-or-update-workflow",+ "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\": \"[email protected]\",\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."+ },+ {+ "slug": "CLARIFY_MCP_DELETE_AGENT",+ "name": "Delete-agent",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_DELETE_ARTIFACT",+ "name": "Delete-artifact",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_DELETE_CALENDAR_EVENT",+ "name": "Delete-calendar-event",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_DELETE_CAMPAIGN",+ "name": "Delete-campaign",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_DELETE_CUSTOM_OBJECT",+ "name": "Delete-custom-object",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_DELETE_FIELDS",+ "name": "Delete-fields",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_DELETE_LIST",+ "name": "Delete-list",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_DELETE_RECORDS",+ "name": "Delete-records",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_DELETE_WORKFLOW",+ "name": "Delete-workflow",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_FIND_LEADS",+ "name": "Find-leads",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_AGENT_RUNS",+ "name": "Get-agent-runs",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_AGENTS",+ "name": "Get-agents",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_GET_ARTIFACT_COMPONENT_DOC",+ "name": "Get-artifact-component-doc",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_ARTIFACT_SOURCE",+ "name": "Get-artifact-source",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_CALENDAR_EVENTS",+ "name": "Get-calendar-events",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_CAMPAIGN_RECIPIENTS",+ "name": "Get-campaign-recipients",+ "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>"+ },+ {+ "slug": "CLARIFY_MCP_GET_CAMPAIGNS",+ "name": "Get-campaigns",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_CURRENT_USER",+ "name": "Get-current-user",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_GET_LISTS",+ "name": "Get-lists",+ "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\")"+ },+ {+ "slug": "CLARIFY_MCP_GET_RECORDS",+ "name": "Get-records",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_SCHEMA",+ "name": "Get-schema",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_GET_WORKFLOW_RUNS",+ "name": "Get-workflow-runs",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_GET_WORKFLOWS",+ "name": "Get-workflows",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_IMPORT_LEADS",+ "name": "Import-leads",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_IMPORT_MEETING_TRANSCRIPT",+ "name": "Import-meeting-transcript",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_MANAGE_ACCESS",+ "name": "Manage-access",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_MERGE_RECORDS",+ "name": "Merge-records",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_QUERY_ANALYTICS",+ "name": "Query-analytics",+ "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>"+ },+ {+ "slug": "CLARIFY_MCP_QUERY_DATA",+ "name": "Query-data",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_READ_CONTEXT",+ "name": "Read-context",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_RESPOND_TO_CALENDAR_EVENT",+ "name": "Respond-to-calendar-event",+ "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)."+ },+ {+ "slug": "CLARIFY_MCP_RUN_WORKFLOW",+ "name": "Run-workflow",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_SEND_EMAIL",+ "name": "Send-email",+ "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"+ },+ {+ "slug": "CLARIFY_MCP_SUBMIT_FEEDBACK",+ "name": "Submit-feedback",+ "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."+ },+ {+ "slug": "CLARIFY_MCP_UPDATE_CAMPAIGN",+ "name": "Update-campaign",+ "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"+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "clarify_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "email,offline_access,openid,profile"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "clarity_ai_mcp","name": "Clarity AI MCP",@@ -149746,6 +152432,156 @@}]},+ {+ "slug": "clay_mcp",+ "name": "Clay MCP",+ "logo": "https://logos.composio.dev/api/clay_mcp",+ "description": "Clay MCP lets agents research companies and contacts, run enrichment providers and Clay functions, and return enriched prospect data for authorized workspaces.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 17,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "CLAY_MCP_ADD_COMPANY_DATA_POINTS",+ "name": "Add-company-data-points",+ "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."+ },+ {+ "slug": "CLAY_MCP_ADD_CONTACT_DATA_POINTS",+ "name": "Add-contact-data-points",+ "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."+ },+ {+ "slug": "CLAY_MCP_ASK_QUESTION_ABOUT_ACCOUNTS",+ "name": "Ask-question-about-accounts",+ "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"+ },+ {+ "slug": "CLAY_MCP_FIND_AND_ENRICH_COMPANY",+ "name": "Find-and-enrich-company",+ "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."+ },+ {+ "slug": "CLAY_MCP_FIND_AND_ENRICH_CONTACTS_AT_COMPANY",+ "name": "Find-and-enrich-contacts-at-company",+ "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"+ },+ {+ "slug": "CLAY_MCP_FIND_AND_ENRICH_LIST_OF_CONTACTS",+ "name": "Find-and-enrich-list-of-contacts",+ "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."+ },+ {+ "slug": "CLAY_MCP_GET_CREDITS_AVAILABLE",+ "name": "Get-credits-available",+ "description": "Check if credits are available for the workspace. Returns hasWorkspaceCredits, hasSalesRepCredits, and (when credit budgets are enabled) hasBudgetCredits."+ },+ {+ "slug": "CLAY_MCP_GET_CURRENT_WORKSPACE",+ "name": "Get-current-workspace",+ "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."+ },+ {+ "slug": "CLAY_MCP_GET_SUBROUTINE_INPUT_OPTIONS",+ "name": "Get subroutine input options",+ "description": "Fetch the available dropdown options for a subroutine input that has a configured options source."+ },+ {+ "slug": "CLAY_MCP_GET_TASK",+ "name": "Get-task",+ "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."+ },+ {+ "slug": "CLAY_MCP_GET_TASK_CONTEXT",+ "name": "Get-task-context",+ "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."+ },+ {+ "slug": "CLAY_MCP_LIST_SUBROUTINES",+ "name": "List subroutines",+ "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."+ },+ {+ "slug": "CLAY_MCP_QUERY_OBJECTS",+ "name": "Query-objects",+ "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"+ },+ {+ "slug": "CLAY_MCP_RUN_SUBROUTINE",+ "name": "Run subroutine",+ "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."+ },+ {+ "slug": "CLAY_MCP_RUN_SUBROUTINE_DIRECT",+ "name": "Run subroutine direct",+ "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.\""+ },+ {+ "slug": "CLAY_MCP_RUN_SUBROUTINE_NO_MAPPING",+ "name": "Run subroutine no mapping",+ "description": "Run a custom subroutine on search entities. The backend automatically generates the field mapping."+ },+ {+ "slug": "CLAY_MCP_TRACK_EVENT",+ "name": "Track-event",+ "description": "Track an analytics event with optional properties."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "clay_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "mcp"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "clearout","name": "Clearout",@@ -152007,6 +154843,567 @@}]},+ {+ "slug": "clio_manage",+ "name": "Clio Manage (US)",+ "logo": "https://logos.composio.dev/api/clio_manage",+ "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.",+ "category": "crm",+ "authSchemes": [+ "OAUTH2"+ ],+ "toolCount": 99,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "CLIO_MANAGE_ASSIGN_TASK_TEMPLATE_LIST",+ "name": "Assign Task Template List",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_ACTIVITY",+ "name": "Create Activity",+ "description": "Create a Clio time or expense activity. Requires Clio's Activities write permission."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_CALENDAR",+ "name": "Create Calendar",+ "description": "Create a Clio custom calendar. Requires the Calendars write permission selected on the Clio developer application."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_CALENDAR_ENTRY",+ "name": "Create Calendar Entry",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_COMMUNICATION",+ "name": "Create Communication",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_CONTACT",+ "name": "Create Contact",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_DOCUMENT",+ "name": "Create Document Upload Initiation",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_DOCUMENT_TEMPLATE",+ "name": "Create Document Template",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_MATTER",+ "name": "Create Matter",+ "description": "Create a Clio matter for a client. Requires Clio's Matters write permission."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_MATTER_FOLDER",+ "name": "Create Matter Folder",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_MATTER_NOTE",+ "name": "Create Matter Note",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_TASK",+ "name": "Create Task",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_CREATE_TASK_TEMPLATE_LIST",+ "name": "Create Non-Empty Task Template List",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_ACTIVITY",+ "name": "Delete Activity",+ "description": "Permanently delete one Clio time or expense activity by ID. Requires Clio's Activities write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_BILL",+ "name": "Delete Bill",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_CALENDAR",+ "name": "Delete Calendar",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_CALENDAR_ENTRY",+ "name": "Delete Calendar Entry",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_COMMUNICATION",+ "name": "Delete Communication",+ "description": "Permanently delete one recorded Clio communication after an exact-ID preflight and explicit confirmation. This does not notify subscribers. Requires Communications write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_CONTACT",+ "name": "Delete Contact",+ "description": "Permanently delete one Clio contact by ID. Requires Clio's Contacts write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_DOCUMENT",+ "name": "Delete Document",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_DOCUMENT_TEMPLATE",+ "name": "Delete Document Template",+ "description": "Permanently delete a Clio document template after an exact ID-and-filename preflight and explicit confirmation. Requires Documents write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_FOLDER",+ "name": "Delete Folder",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_MATTER",+ "name": "Delete Matter",+ "description": "Permanently delete one Clio matter by ID. Requires Clio's Matters write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_NOTE",+ "name": "Delete Note",+ "description": "Permanently delete one Clio note after an exact-ID preflight and explicit confirmation. This does not notify subscribers. Requires Notes write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_TASK",+ "name": "Delete Task",+ "description": "Permanently delete one Clio task by ID. Requires Clio's Tasks write permission."+ },+ {+ "slug": "CLIO_MANAGE_DELETE_TASK_TEMPLATE_LIST",+ "name": "Delete Task Template List",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_DOWNLOAD_DOCUMENT",+ "name": "Download Document",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_BILL",+ "name": "Find Bill",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_COMPANY_CONTACT",+ "name": "Find Company Contact",+ "description": "Exhaustively find exact Clio company contacts without choosing an arbitrary duplicate. Requires Contacts read permission."+ },+ {+ "slug": "CLIO_MANAGE_FIND_CONTACT_BY_CUSTOM_FIELD",+ "name": "Find Contact by Custom Field",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_MATTER",+ "name": "Find Matter",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_MATTER_BY_CUSTOM_FIELD",+ "name": "Find Matter by Custom Field",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_NEWEST_MATTER_BY_CLIENT_EMAIL",+ "name": "Find Newest Matter by Client Email",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_OR_CREATE_COMPANY_CONTACT",+ "name": "Find or Create Company Contact",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_OR_CREATE_MATTER",+ "name": "Find or Create Matter",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_OR_CREATE_PERSON_CONTACT",+ "name": "Find or Create Person Contact",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_FIND_PERSON_CONTACT",+ "name": "Find Person Contact",+ "description": "Exhaustively find exact Clio person contacts without choosing an arbitrary duplicate. Requires Contacts read permission."+ },+ {+ "slug": "CLIO_MANAGE_FIND_USER",+ "name": "Find User",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GENERATE_DOCUMENT_FROM_TEMPLATE",+ "name": "Generate Document From Template",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GET_ACTIVITY",+ "name": "Get Activity",+ "description": "Get one Clio time or expense activity by ID, including billing state and its user and matter references."+ },+ {+ "slug": "CLIO_MANAGE_GET_BILL",+ "name": "Get Bill",+ "description": "Get one Clio bill with its ETag, lifecycle state, permitted transitions, and concrete financial totals. Requires Billing read permission."+ },+ {+ "slug": "CLIO_MANAGE_GET_CALENDAR",+ "name": "Get Calendar",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GET_CALENDAR_ENTRY",+ "name": "Get Calendar Entry",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GET_COMMUNICATION",+ "name": "Get Communication",+ "description": "Retrieve one recorded Clio communication. This does not send a message or notify subscribers. Requires Communications read permission."+ },+ {+ "slug": "CLIO_MANAGE_GET_CONTACT",+ "name": "Get Contact",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GET_CURRENT_USER",+ "name": "Get Current User",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GET_DOCUMENT",+ "name": "Get Document",+ "description": "Get one Clio document and its latest-version metadata by ID. Requires Documents read permission."+ },+ {+ "slug": "CLIO_MANAGE_GET_FOLDER",+ "name": "Get Folder",+ "description": "Retrieve one Clio folder by ID. Requires Documents read permission."+ },+ {+ "slug": "CLIO_MANAGE_GET_MATTER",+ "name": "Get Matter",+ "description": "Get one Clio matter by ID with lifecycle, client, staffing, practice area, dates, and billing method. Requires read access to Matters."+ },+ {+ "slug": "CLIO_MANAGE_GET_MATTER_CLIENT",+ "name": "Get Matter Client",+ "description": "Retrieve the client contact for one Clio matter. Requires Contacts and Matters read permission."+ },+ {+ "slug": "CLIO_MANAGE_GET_NOTE",+ "name": "Get Note",+ "description": "Retrieve one Clio matter or contact note. Reading a note does not notify subscribers. Requires Notes read permission."+ },+ {+ "slug": "CLIO_MANAGE_GET_TASK",+ "name": "Get Task",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_GET_USER",+ "name": "Get User",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_LIST_ACTIVITY_DESCRIPTIONS",+ "name": "List Activity Descriptions",+ "description": "List selectable Clio activity descriptions and resolved rates for time entries. Requires Activities read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_CALENDARS",+ "name": "List Calendars",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_LIST_COMMUNICATIONS",+ "name": "List Communications",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_LIST_CONTACT_EMAIL_ADDRESSES",+ "name": "List Contact Email Addresses",+ "description": "Return one bounded page of email addresses for a Clio contact. Requires Contacts read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_CONTACT_PHONE_NUMBERS",+ "name": "List Contact Phone Numbers",+ "description": "Return one bounded page of phone numbers for a Clio contact. Requires Contacts read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_DOCUMENT_AUTOMATIONS",+ "name": "List Document Automations",+ "description": "Return one bounded page of Clio document-generation automations. Requires Documents read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_DOCUMENTS",+ "name": "List Documents",+ "description": "Return one bounded provider page of Clio documents. Requires Documents read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_DOCUMENT_TEMPLATES",+ "name": "List Document Templates",+ "description": "List Clio document templates and IDs for document automation. Requires Documents read permission; availability can depend on the Clio plan."+ },+ {+ "slug": "CLIO_MANAGE_LIST_EXPENSE_CATEGORIES",+ "name": "List Expense Categories",+ "description": "List selectable Clio expense categories and rates for expense entries. Requires Activities read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_FOLDER_CONTENTS",+ "name": "List Folder Contents",+ "description": "Return one bounded page of Clio documents and folders, optionally below a parent folder. Requires Documents read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_FOLDERS",+ "name": "List Folders",+ "description": "Return one bounded page of Clio folders using documented filters. Requires Documents read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_GROUPS",+ "name": "List Groups",+ "description": "List Clio groups and IDs for matter assignments and user grouping. Requires Groups read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_MATTER_CONTACTS",+ "name": "List Matter Contacts",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_LIST_MATTER_PROTECTED_FUNDS",+ "name": "List Matter Protected Funds",+ "description": "Return one bounded page of protected funds for a Clio matter. Requires Matters read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_MATTER_RELATED_CONTACTS",+ "name": "List Matter Related Contacts",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_LIST_MATTER_STAGES",+ "name": "List Matter Stages",+ "description": "List Clio matter stages and practice-area associations for selecting a matter stage. Requires Matters read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_NOTES",+ "name": "List Notes",+ "description": "Return one bounded page of Clio matter or contact notes. Reading notes does not notify subscribers. Requires Notes read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_PRACTICE_AREAS",+ "name": "List Practice Areas",+ "description": "List Clio practice areas and IDs for matter and task-template selection. Requires Matters read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_TASK_TEMPLATE_LISTS",+ "name": "List Task Template Lists",+ "description": "List Clio task template lists and IDs for assigning templates to matters. Requires Tasks read permission."+ },+ {+ "slug": "CLIO_MANAGE_LIST_USERS",+ "name": "List Users",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_PREVIEW_BILL",+ "name": "Preview Bill",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SAVE_ACTIVITY",+ "name": "Save Activity",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SAVE_CALENDAR",+ "name": "Save Calendar",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SAVE_CALENDAR_ENTRY",+ "name": "Save Calendar Entry",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SAVE_CONTACT",+ "name": "Save Contact",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SAVE_MATTER",+ "name": "Save Matter",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SAVE_TASK",+ "name": "Save Task",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SEARCH_ACTIVITIES",+ "name": "Search Activities",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SEARCH_CALENDAR_ENTRIES",+ "name": "Search Calendar Entries",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SEARCH_CONTACTS",+ "name": "Search Contacts",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SEARCH_MATTERS",+ "name": "Search Matters",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_SEARCH_TASKS",+ "name": "Search Tasks",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_START_DOCUMENT_FROM_TEMPLATE",+ "name": "Start Document From Template",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_TRANSITION_BILL_STATE",+ "name": "Transition Bill State",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_ACTIVITY",+ "name": "Update Activity",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_BILL",+ "name": "Update Bill",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_CALENDAR",+ "name": "Update Calendar",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_CALENDAR_ENTRY",+ "name": "Update Calendar Entry",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_COMMUNICATION",+ "name": "Update Communication",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_CONTACT",+ "name": "Update Contact",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_DOCUMENT",+ "name": "Update Document Metadata",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_FOLDER",+ "name": "Update Folder",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_MATTER",+ "name": "Update Matter",+ "description": "Update at least one field on an existing Clio matter, optionally using its ETag for concurrency safety. Requires Clio's Matters write permission."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_NOTE",+ "name": "Update Note",+ "description": "Update a Clio note using its current ETag. Notification subscribers are intentionally unsupported. Requires Notes write permission."+ },+ {+ "slug": "CLIO_MANAGE_UPDATE_TASK",+ "name": "Update Task",+ "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."+ },+ {+ "slug": "CLIO_MANAGE_VOID_BILL",+ "name": "Void Bill",+ "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."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "OAUTH2",+ "name": "clio_manage_oauth2",+ "fields": {+ "auth_config_creation": {+ "required": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": true,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": true,+ "default": null+ }+ ],+ "optional": [+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": ""+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "clockify","name": "Clockify",@@ -154323,7 +157720,7 @@{"slug": "CLOUDFLARE_MCP_EXECUTE","name": "Execute",- "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\" ([email protected]'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}"+ "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(...)."},{"slug": "CLOUDFLARE_MCP_SEARCH",@@ -163102,6 +166499,86 @@}]},+ {+ "slug": "craft_mcp",+ "name": "Craft MCP",+ "logo": "https://logos.composio.dev/api/craft_mcp",+ "description": "Craft MCP lets agents search, read, create, update, and delete authorized Craft documents, daily notes, tasks, collections, and structured workspace content.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 3,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "CRAFT_MCP_BLOCKS_REVERT",+ "name": "Blocks revert",+ "description": "Reverts a previous mutation if blocks haven't been modified since. Used by widgets for undo/redo functionality."+ },+ {+ "slug": "CRAFT_MCP_CRAFT_READ",+ "name": "Craft read",+ "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."+ },+ {+ "slug": "CRAFT_MCP_CRAFT_WRITE",+ "name": "Craft write",+ "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"+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "craft_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": ""+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "craftmypdf","name": "Craftmypdf",@@ -173976,22 +177453,22 @@],"toolCount": 3,"triggerCount": 0,- "version": "20260225_01",+ "version": "20260904_00","tools": [{"slug": "DEEPWIKI_MCP_ASK_QUESTION","name": "Ask question",- "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"+ "description": "Ask any question about a GitHub repository and get an AI-powered, context-grounded response."},{"slug": "DEEPWIKI_MCP_READ_WIKI_CONTENTS","name": "Read wiki contents",- "description": "View documentation about a GitHub repository.\n\nArgs:\n repoName: GitHub repository in owner/repo format (e.g. \"facebook/react\")"+ "description": "View documentation about a GitHub repository."},{"slug": "DEEPWIKI_MCP_READ_WIKI_STRUCTURE","name": "Read wiki structure",- "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\")"+ "description": "Get a list of documentation topics for a GitHub repository."}],"triggers": [],@@ -174475,6 +177952,141 @@}]},+ {+ "slug": "descript_mcp",+ "name": "Descript MCP",+ "logo": "https://logos.composio.dev/api/descript_mcp",+ "description": "Descript MCP lets agents import media, run project-agent workflows, and inspect or manage authorized processing jobs in Descript.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 14,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "DESCRIPT_MCP_CANCEL_JOB",+ "name": "Cancel job",+ "description": "Cancel a queued or running job."+ },+ {+ "slug": "DESCRIPT_MCP_EXPORT_TIMELINE",+ "name": "Export timeline",+ "description": "Export a project composition as a timeline file for import into another DAW/NLE (Premiere, DaVinci Resolve, Final Cut Pro, Pro Tools, Logic, Audition, Reaper). Media files are never bundled — only the timeline/XML/EDL file itself.\n\nReturns immediately with a job_id. Use the wait_for_job tool with the returned job_id to wait for completion; when the job finishes, its result carries a time-limited download_url (valid until download_url_expires_at). Always display the download_url to the user so they can download the file directly. Large exports can take several minutes, so polling avoids connection timeouts.\n\nFormats: edl (Samplitude/Reaper), sesx (Adobe Audition), fcp (Final Cut Pro X .fcpxml), premiere (Premiere Pro XML), davinci_resolve (DaVinci Resolve XML), aaf (Pro Tools/Logic, binary)."+ },+ {+ "slug": "DESCRIPT_MCP_EXPORT_TRANSCRIPT",+ "name": "Export transcript",+ "description": "Export a project composition as a transcript document. Formats: txt, markdown, html, rtf, srt. Returns the exported content directly in the response."+ },+ {+ "slug": "DESCRIPT_MCP_GET_DRIVE_INFO",+ "name": "Get drive info",+ "description": "Returns the drive (workspace) connected to the current session, including its ID and name. Use this to confirm which drive your requests will operate on."+ },+ {+ "slug": "DESCRIPT_MCP_GET_PROJECT",+ "name": "Get project",+ "description": "Get a detailed project summary including all media files, compositions, and existing publishes. Returns the project's id, name, drive_id, created_at, updated_at, folder_path (if in a folder), a map of media files (keyed by display path) with type and duration, a list of compositions with id, name, duration, and media type, and a list of existing publishes with share_url, access_level, media_type, and publish time. Use this to inspect a project's contents before editing or importing media, or to retrieve existing share URLs without triggering a republish."+ },+ {+ "slug": "DESCRIPT_MCP_IMPORT_DRIVE_MEDIA",+ "name": "Import drive media",+ "description": "Import media files into the drive media library (not into a project). Use this when the user wants to add files to their media library without creating or editing a project. Supports URL imports and direct file uploads.\n\nDIRECT FILE UPLOAD: Instead of a url, provide content_type (MIME type) and file_size (bytes). The response includes upload_urls — a map of media key → { upload_url, asset_id, artifact_id }. PUT each file to its upload_url with header Content-Type: application/octet-stream.\n\nReturns immediately with a job_id and drive_id. Please use the wait_for_job tool with the returned job_id to wait for the job to complete."+ },+ {+ "slug": "DESCRIPT_MCP_IMPORT_MEDIA",+ "name": "Import media",+ "description": "Import media into a Descript project via URLs (direct links, Google Drive, Dropbox) or direct file upload. Pass URLs as-is. Pass empty add_media ({}) with project_name to create an empty project.\n\nADDING TO COMPOSITION: When creating a new project, include add_compositions so imported media appears on the timeline — this is the expected default. Only omit add_compositions for new projects when the user explicitly asks to import without adding to the composition. When importing into an existing project, omit add_compositions unless the user requests it, to avoid disrupting existing edits. To append media to an EXISTING composition, use update_compositions (composition_id + append_clips) instead of add_compositions.\n\nDIRECT FILE UPLOAD: Instead of a url, provide content_type (MIME type) and file_size (bytes). The response includes upload_urls — a map of media key → { upload_url, asset_id, artifact_id }. PUT each file to its upload_url with header Content-Type: application/octet-stream. The uploaded file size must match the file_size declared in the request.\n\nReturns immediately with a job_id, project_id, and project_url. Always display the project_url to the user so they can open the project in Descript. Please use the wait_for_job tool with the returned job_id to wait for the job to complete."+ },+ {+ "slug": "DESCRIPT_MCP_LIST_FOLDERS",+ "name": "List folders",+ "description": "List folders in the drive. Returns each folder's full path from the drive root. By default lists root-level folders. Pass parent_path to list child folders of a specific parent. Use this to browse the folder hierarchy before filtering projects by folder_path."+ },+ {+ "slug": "DESCRIPT_MCP_LIST_JOBS",+ "name": "List jobs",+ "description": "List recent jobs, optionally filtered by project or type. Job states: queued, running, stopped (check result.status), cancelled."+ },+ {+ "slug": "DESCRIPT_MCP_LIST_PROJECTS",+ "name": "List projects",+ "description": "List projects accessible to the authenticated user. Returns each project's id, name, created_at, updated_at, and folder_path (if the project is inside a folder). Use this to discover project IDs before editing or importing media. Supports cursor-based pagination — pass the next_cursor from a previous response's pagination field to fetch the next page."+ },+ {+ "slug": "DESCRIPT_MCP_PROMPT_PROJECT_AGENT",+ "name": "Prompt project agent",+ "description": "Agent Underlord, Descript's built-in AI editor, queries, creates, and edits Descript projects using natural language. Refer to it as Agent Underlord when telling the user what is doing the editing, since that is the name they see in the Descript app. Use project_id for existing projects, project_name to create new ones. Returns immediately with a job_id, project_id, and project_url. Always display the project_url to the user so they can open the project in Descript. Please use the wait_for_job tool with the returned job_id to wait for the job to complete. The response includes a conversation_id — pass it back on subsequent calls to the same project to continue the conversation with full context."+ },+ {+ "slug": "DESCRIPT_MCP_PUBLISH_PROJECT",+ "name": "Publish project",+ "description": "Publish a Descript project composition as video or audio, producing a shareable URL. Requires a project_id. Optionally specify a composition_id (defaults to the first composition). Publishing the same composition again automatically reuses the previous share URL, overwriting its content; Video and Audio publishes of the same composition get separate share URLs. If the composition has no video content: omitting media_type publishes it as audio (the result reports media_type=\"Audio\"), while explicitly requesting media_type=\"Video\" fails with a 422. Returns immediately with a job_id. Please use the wait_for_job tool with the returned job_id to wait for the job to complete. When the job completes, always display the share_url and download_url from the result to the user."+ },+ {+ "slug": "DESCRIPT_MCP_REPORT_UPLOAD_STATUS",+ "name": "Report upload status",+ "description": "Report that a specific direct upload failed, was aborted, or was abandoned so the import job stops waiting on just that file (other files keep uploading). Use this after a PUT to an upload_url errors (\"failed\"), the user cancels an in-flight upload (\"aborted\"), or a file will never be uploaded (\"abandoned\", e.g. the upload UI was dismissed). media_id is the key from the import request's add_media / upload_urls map."+ },+ {+ "slug": "DESCRIPT_MCP_WAIT_FOR_JOB",+ "name": "Wait for job",+ "description": "Wait for a job to complete. Polls for completion by default (840s) and streams progress updates. Set wait_seconds to 0 to return immediately without waiting. Job states: queued, running, stopped, cancelled. A stopped job has a result object — check result.status for \"success\" or \"error\". These jobs routinely run for many minutes, so a long wait is normal rather than a stall. If the job is still going when the wait window elapses, the call still succeeds and returns a non-terminal job_state with wait_status \"still_running\". That is not a failure — call wait_for_job again with the same job_id and keep calling until job_state is \"stopped\" or \"cancelled\". While the job is running, progress.label contains a human-readable status (e.g. \"Editing script\", \"Searching web\") — display this to the user so they can see what the agent is doing. The response includes project_url — when a composition ID is available in the result, the URL includes a composition short ID suffix so it opens directly to the right composition. Always display project_url to the user. A completed export_timeline job returns a time-limited result.download_url (valid until result.download_url_expires_at); always display this URL to the user so they can download the file directly. For prompt_project_agent jobs, the completed result includes result.conversation_id — save it and pass it back as conversation_id on the next prompt_project_agent call to the same project to continue the conversation."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "descript_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,phone,offline_access"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "desktime","name": "DeskTime",@@ -175309,19 +178921,24 @@"authSchemes": ["NO_AUTH"],- "toolCount": 2,+ "toolCount": 3,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{- "slug": "DICE_MCP_GET_CANDIDATE",- "name": "Get candidate",- "description": "Retrieve a Dice candidate's profile by candidate ID. Returns career info, skills, ideal job preferences, company preferences, and education.\n\nUse this tool when you already have a candidateId and need that candidate's profile details.\nDO NOT use for: searching/discovering candidates by keyword (use a candidate search tool instead), or for job listings.\n\nArgs:\n candidate_id: The unique identifier of the candidate to retrieve (required)\n\nReturns:\n CandidateResult: Contains:\n - data: CandidateData with candidateId, profileTitle, careerInfo (years of experience,\n work authorization, employment history, resume), skills, idealJob, companyPreference,\n and education\n\nRaises:\n Exception: If API call fails, the candidate is not found, or input validation errors occur\n"+ "slug": "DICE_MCP_GET_COMPANY",+ "name": "Get company",+ "description": "Retrieve the name and description of the company behind a job, by job ID.\n\nUse this tool when users want more detail about a company than search_jobs/get_job_details\nreturn (e.g. after finding a job and wanting to know more about the company that posted it).\nDO NOT use for: searching/discovering companies or jobs by keyword (use search_jobs instead).\n\nLLM USAGE INSTRUCTIONS:\n- The typical flow is: search_jobs to find jobs -> user picks one -> offer to look up the\n company -> if the user agrees, call this tool with that same job_id (the same guid used\n for get_job_details; no separate lookup step is needed first).\n- Do not call this automatically right after get_job_details; ask the user first unless\n they already explicitly asked for company details.\n- Not every company has published an employer branding profile, and some profiles are\n marked not visible by the company. When that happens this tool does NOT raise — it\n returns a Company with `message` set and empty name/desc. Relay that message to the\n user (e.g. \"Looks like that company hasn't published a public profile.\") rather than\n treating it as an error.\n\nArgs:\n job_id: The unique identifier of the job whose company to look up (required). This\n must be the job's `guid` field from a search_jobs result, NOT its `id` field —\n `id` is a different, internal identifier that this tool does not accept.\n\nReturns:\n Company: Contains:\n - name: The company name (empty if message is set)\n - desc: The company description (empty if message is set)\n - message: Set instead of name/desc when there is no visible company profile\n to show; None when name/desc are populated\n\nRaises:\n Exception: If the job is not found, an API call itself fails (network error,\n non-200 response, GraphQL errors), or input validation errors occur\n"+ },+ {+ "slug": "DICE_MCP_GET_JOB_DETAILS",+ "name": "Get job details",+ "description": "Retrieve a job's full description and associated skills by job ID.\n\nUse this tool when users want more detail about a specific job than search_jobs returns\n(e.g. after finding a job via search_jobs and wanting its full description and skills list).\nDO NOT use for: searching/discovering jobs by keyword (use search_jobs instead).\n\nLLM USAGE INSTRUCTIONS:\n- Only call this after the user has picked out a specific job from search_jobs results\n (or otherwise supplied a job's guid directly) — do not call it speculatively for every\n search result.\n- After returning job details, do NOT automatically call get_company. Instead, offer to\n look up the company (e.g. \"Want me to pull up more info on the company?\") and only call\n get_company, passing this same job_id, if the user says yes.\n\nArgs:\n job_id: The unique identifier of the job to retrieve (required). This must be the\n job's `guid` field from a search_jobs result, NOT its `id` field — `id` is a\n different, internal identifier that this tool does not accept.\n\nReturns:\n JobDetails: Contains:\n - description: The full job description\n - skills: List of Skill objects associated with the job\n\nRaises:\n Exception: If the API call fails, the job is not found, or input validation errors occur\n"},{"slug": "DICE_MCP_SEARCH_JOBS","name": "Search jobs",- "description": "Search for job listings by keyword, location, and filters. Returns job details, company info, and application links.\n\nUse this tool when users want to find jobs, search employment opportunities, or explore job openings.\nDO NOT use for: applying to jobs, submitting applications, or making employment decisions.\n\nLLM USAGE INSTRUCTIONS:\n- ALWAYS provide the keyword parameter (required)\n- When presenting results to users, include BOTH the job details URL (detailsPageUrl)\n AND the company page URL (companyPageUrl) for each job\n- Use location to find geographically relevant positions\n- Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work)\n- Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days)\n- Default jobs_per_page is reasonable, increase for comprehensive searches\n\nIMPORTANT - AI DISCLOSURE REQUIREMENT:\nWhen presenting job search results to users, you MUST include an appropriate disclosure\nthat these results were retrieved using AI assistance. Example disclosure language:\n\"These job listings were found using AI-powered search. Please review all job details\ncarefully and verify information directly with employers before applying.\"\n\nThis tool provides job listing data only. Final employment decisions should always\ninvolve human judgment and direct review of complete job postings.\n\nArgs:\n keyword: The job keyword or title to search for (required)\n location: Geographic location for the job search (city, state, country)\n radius: Search radius from the specified location (minimum 1.0)\n radius_unit: Unit for search radius. Options: 'mi', 'km', 'miles', 'kilometers'\n jobs_per_page: Number of jobs to return per page (1-100, default handled by API)\n page_number: Page number for pagination (1-based, default is 1)\n posted_date: Filter by posting date. Options: 'ONE' (1 day), 'THREE' (3 days), 'SEVEN' (7 days)\n workplace_types: Workplace arrangements. Options: 'Remote', 'On-Site', 'Hybrid'\n employment_types: Employment types. Options: 'FULLTIME', 'CONTRACTS', 'PARTTIME', 'THIRD_PARTY'\n employer_types: Employer types. Options: 'Direct Hire', 'Recruiter', 'Other'\n willing_to_sponsor: Filter for employers willing to sponsor work authorization (boolean)\n easy_apply: Filter for jobs with easy application process (boolean)\n fields: Specific fields to include in response (optional, returns all fields by default)\n\nReturns:\n JobSearchResult: Contains:\n - data: List of JobDisplayFields with job details including:\n * detailsPageUrl: Direct link to full job posting\n * companyPageUrl: Link to company profile page\n * title, summary, salary, location, employmentType, etc.\n - meta: Search metadata with pagination info and facet results\n - _links: Pagination navigation links\n\nRaises:\n Exception: If API call fails or input validation errors occur\n"+ "description": "Search for job listings by keyword, location, and filters. Returns job details, company info, and application links.\n\nUse this tool when users want to find jobs, search employment opportunities, or explore job openings.\nDO NOT use for: applying to jobs, submitting applications, or making employment decisions.\n\nLLM USAGE INSTRUCTIONS:\n- ALWAYS provide the keyword parameter (required)\n- When presenting results to users, include BOTH the job details URL (detailsPageUrl)\n AND the company page URL (companyPageUrl) for each job\n- Use location to find geographically relevant positions\n- Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work)\n- Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days)\n- Default jobs_per_page is reasonable, increase for comprehensive searches\n- Use company_name to scope results to a specific employer\n- Use sort='datePosted' when the user wants the newest listings instead of the most relevant\n- Use facets to get aggregate counts (e.g., how many results are remote vs on-site) without paging through all results\n- After presenting results, do NOT automatically call get_job_details for every job returned.\n Wait for the user to indicate which specific job(s) they're interested in, then pass that\n job's guid to get_job_details.\n\nIMPORTANT - AI DISCLOSURE REQUIREMENT:\nWhen presenting job search results to users, you MUST include an appropriate disclosure\nthat these results were retrieved using AI assistance. Example disclosure language:\n\"These job listings were found using AI-powered search. Please review all job details\ncarefully and verify information directly with employers before applying.\"\n\nThis tool provides job listing data only. Final employment decisions should always\ninvolve human judgment and direct review of complete job postings.\n\nArgs:\n keyword: The job keyword or title to search for (required)\n location: Geographic location for the job search (city, state, country)\n radius: Search radius from the specified location (minimum 1, requires radius_unit)\n radius_unit: Unit for search radius. Options: 'mi', 'km' (requires radius)\n jobs_per_page: Number of jobs to return per page (1-100, defaults to 5)\n page_number: Page number for pagination (1-based, default is 1)\n sort: Sort order for results. Options: 'relevance', 'datePosted' (defaults to relevance)\n posted_date: Filter by posting date. Options: 'ONE' (1 day), 'THREE' (3 days), 'SEVEN' (7 days)\n workplace_types: Workplace arrangements. Options: 'Remote', 'On-Site', 'Hybrid'\n employment_types: Employment types. Options: 'FULLTIME', 'CONTRACTS', 'PARTTIME', 'THIRD_PARTY', 'INTERNSHIP'\n employer_types: Employer types. Options: 'Direct Hire', 'Recruiter', 'Other'\n willing_to_sponsor: Filter for employers willing to sponsor work authorization (boolean)\n easy_apply: Filter for jobs with easy application process (boolean)\n company_name: Filter by company name\n fields: Specific fields to include in response (optional, returns all exposed fields by default)\n facets: Facet dimensions to aggregate (optional). Options: 'employmentType', 'postedDate',\n 'workFromHomeAvailability', 'workplaceTypes', 'employerType', 'easyApply', 'isRemote',\n 'willingToSponsor'\n\nReturns:\n JobSearchResult: Contains:\n - data: List of JobDisplayFields with job details including:\n * guid: The job's identifier to pass as job_id to get_job_details for the full\n description and skills list (NOT the `id` field, which is a different, internal\n identifier not accepted by get_job_details)\n * detailsPageUrl: Direct link to full job posting\n * companyPageUrl: Link to company profile page\n * title, summary, salary, location, employmentType, etc.\n - metadata: Search metadata with pagination info and facet results\n\nRaises:\n Exception: If API call fails or input validation errors occur\n"}],"triggers": [],@@ -179153,6 +182770,507 @@}]},+ {+ "slug": "domotz_mcp",+ "name": "Domotz MCP",+ "logo": "https://logos.composio.dev/api/domotz_mcp",+ "description": "Domotz MCP lets agents inspect and manage authorized network-monitoring data, devices, alerts, sites, and IT operations through Domotz.",+ "category": "model context protocol",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 92,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "DOMOTZ_MCP_APPLY_DEVICE_PROFILE",+ "name": "Apply device profile",+ "description": "Applies a device profile (a saved bundle of sensors, and optionally credentials) to one or more devices. Apply runs as a background job — the tool blocks for up to `poll_timeout_seconds` (default 60s, max 120s) waiting for completion. If the job finishes within that window, per-device results are returned. If it times out, a partial state is returned; you can wait and call this tool again with the same arguments — apply is idempotent in REPLACE mode. IMPORTANT: a successful call does NOT mean every requested device was configured. Report the apply as complete only when `applied_count` covers every requested device; any other count being non-zero means it is not. Consult `retryable` rather than your own judgement before calling again. Devices on collectors you lack the Device Management permission on are skipped: they come back with result WITHHELD and an explanation. Whenever the apply is dispatched, every requested device carries exactly one verdict in `per_device` — OK, FAIL, WITHHELD, NOT_APPLIED (the job did not cover it), UNKNOWN (outcome undeterminable) or PENDING — and the per-verdict counts add up to the devices you asked for. Sometimes no job is created at all — `job_status` is NOT_STARTED, `retryable` is false and calling again cannot change the outcome; the cause varies (every device withheld, no devices matched, the profile has no modules), so relay the `message` instead of assuming a permission problem. `other_issues` carries anything the backend reported about something other than a device; it is normally empty, and a non-empty one is worth relaying rather than ignoring. If the profile contains credential modules, applying it WILL OVERWRITE existing credentials on the targeted devices (the confirmation prompt discloses this when relevant). For applying alert rules to devices, use `bind_alert_rule_to_device` instead. Devices named in `failed_device_ids` carry no reason for their failure; WITHHELD devices, and devices affected by a job that failed or was cancelled as a whole, do carry one. Input-validation and dispatch errors return an `error` with a `message` and `retryable`, and no per-device detail."+ },+ {+ "slug": "DOMOTZ_MCP_ATTACH_DRIVER",+ "name": "Attach driver",+ "description": "Attach a driver to a device. THIS IS A LIVE OPERATION: the backend runs the driver's `validate()` action against the device during attach and, once the binding is persisted, the scheduler will trigger the real (non-dry-run) actions (`get_status` for GENERIC, `backup` for CONFIGURATION_MANAGEMENT) on the device's sample period.\n\nPRECONDITION: execute_driver must have returned outcome=success for every mandatory action (validate + get-status for GENERIC, validate + backup for CONFIGURATION_MANAGEMENT) against this (driver_id, collector_id, device_id) tuple. Because the driver is not yet attached, those execute_driver calls run in dry-run mode automatically and persist nothing — they exist precisely to catch failures before this attach. Skipping them and relying on attach_driver's implicit validate() alone hides failures of get_status / backup until the next scheduled run.\n\nProvide `params` as a list of {name, value} pairs matching the driver's PARAMETER SCHEMA (the inputs declared on the driver — NOT for credentials). The tool resolves names to internal parameter IDs before dispatch (unknown names are rejected). Sample period defaults to the driver's minimum; that's not configurable in this beta. To remove the binding later use `detach_driver`; to delete the driver everywhere use `delete_driver`.\n\n`credentials` (SEPARATE top-level argument — DO NOT put inside `params`): `{username: str, password: str, store?: bool}`. Used for the validate() call that runs during attach. On a successful attach, the backend's result reporter persists these credentials in the credential store AND seeds the device's purpose row (CUSTOM_DRIVER_MANAGEMENT for GENERIC drivers, CONFIGURATION_MANAGEMENT for CM drivers). After that, `set_device_credential(purpose=...)` works for rotation.\nFor CONFIGURATION_MANAGEMENT drivers on devices that don't already have a CM purpose row, you MUST pass `credentials` here — calling set_device_credential first will fail with 412 (scope missing).\nCommon LLM mistake: passing credentials as an entry in `params` like `{name: 'credentials', value: {username, password}}`. That goes to the driver's parameter list and is NOT used for authentication. The tool rejects this shape with WRONG_FIELD_SHAPE so you can resubmit with the top-level `credentials` arg.\n\nIf the driver is already attached, returns result=ALREADY_ATTACHED with the existing binding_id. If the backend rejects the attach for another reason (e.g. driver validation error), returns result=CONFLICT with the error details. If the driver's validate() action fails, returns result=VALIDATION_FAILED with the driver error and a remediation hint."+ },+ {+ "slug": "DOMOTZ_MCP_ATTACH_SENSOR",+ "name": "Attach sensor",+ "description": "Attach a sensor to a device. `sensor_spec.kind` selects the variant: `overlay` applies a preconfigured sensor (use `list_preconfigured_sensors` to discover `overlay_id`, optional `selected_fields` to subset its fields); `tcp_port` monitors a TCP port on the device (`port` 1..65535); `custom_oid` defines a per-device custom SNMP-OID sensor — required: `oid` (dotted notation, e.g. `1.3.6.1.2.1.1.3.0`), `name` (short identifier), `value_type` (1|STRING, 2|NUMERIC, 3|ENUM — accepted as int id or label), `description` (human-readable text); optional: `custom_name`. Each `custom_oid` call creates a new per-device sensor entity — the same OID attached to multiple devices yields independent sensors. Sensor limits per collector apply; duplicate `overlay` attachments return a structured FAIL with a clear reason. No detach in this beta — remove via the UI."+ },+ {+ "slug": "DOMOTZ_MCP_BIND_ALERT_RULE_TO_COLLECTOR",+ "name": "Bind alert rule to collector",+ "description": "Bind an existing alert rule to a collector. Use this for collector-scoped metrics such as agent_status or agent_performance/*. Already-bound combinations return status=ALREADY_BOUND rather than an error (idempotent retry-safe). Use after create_alert_rule (with the returned id) or after picking an existing rule from list_alert_rules. Before binding, call get_collector_alert_rule_bindings to verify the rule is not already bound to this collector."+ },+ {+ "slug": "DOMOTZ_MCP_BIND_ALERT_RULE_TO_DEVICE",+ "name": "Bind alert rule to device",+ "description": "Bind an existing alert rule to a specific device. The system will then watch every variable on that device whose metric matches the rule and raise incidents when the rule's condition is met. Use after create_alert_rule (with the returned id) or after picking an existing rule from list_alert_rules. Before binding, call get_device_alert_rule_bindings to verify the rule is not already bound to this device (binding-level dedupe). For variable-level dedupe — checking whether a suitable rule already exists for a specific variable — use list_variable_alert_rule_candidates before creating a new rule. Already-bound combinations return status=ALREADY_BOUND rather than an error (idempotent retry-safe). SENSOR CHECK: verify device has sensor data for the metric before binding (see alert_rule_id parameter). ICMP CAVEAT: latency/packet-loss rules require ICMP — check device_performance for 100% packet_loss_percent before binding, as many devices (firewalls, hardened hosts) block ICMP. BINARY METRIC: bind only one rule per binary metric (device_status, heartbeat) per device to avoid duplicate incidents."+ },+ {+ "slug": "DOMOTZ_MCP_BIND_COLLECTOR_TO_ORGANIZATION",+ "name": "Bind collector to organization",+ "description": "Bind a Collector to an Organization (addressed by its internal `id`). A Collector can belong to one Organization at a time. Reversible via unbind_collector_from_organization."+ },+ {+ "slug": "DOMOTZ_MCP_BIND_TAGS",+ "name": "Bind tags",+ "description": "Bind tags to a device or to a collector, setting which tags it carries. Pass `device_id` to tag a device (with the `collector_id` that monitors it), or omit `device_id` to tag the collector itself. This REPLACES the target's whole tag set - send every tag it should end up with, not just the new one, or the omitted tags are removed. Read the current set first from search_devices / search_collectors (field custom_tags), and use `list_tags` for the catalog of valid ids. An empty `tag_ids` removes every tag from the target. The tags themselves are never deleted - use `delete_tag` for that. Tagging a device requires the manage_devices permission on its collector; tagging a collector requires manage_configuration."+ },+ {+ "slug": "DOMOTZ_MCP_COLLECTOR_DISCOVERY_STATUS",+ "name": "Collector discovery status",+ "description": "Returns the discovery dashboard data for a collector, including initial discovery progress, device statistics, collector issues, and device categories. Use this after a collector comes online to monitor network discovery."+ },+ {+ "slug": "DOMOTZ_MCP_COLLECTOR_OVERVIEW",+ "name": "Collector overview",+ "description": "Fetch a high-level overview of a collector including its identity, health status, software version, uptime/downtime intervals, device counts, security issues, speed test results, and IP conflict status. Pass `lookback` (in days, 1-90, default 7) to widen or narrow the uptime window. Note: when the collector is OFFLINE, live fields populated by the collector (speed test, IP conflict) coalesce to null — null means 'no recent push' rather than 'never ran'. Counters and uptime stay populated server-side. Use as the first call to understand the overall state of a collector before diving deeper."+ },+ {+ "slug": "DOMOTZ_MCP_COMPARE_CONFIG_BACKUP",+ "name": "Compare config backup",+ "description": "Compares two configuration backup snapshots of the same device. `config_type` selects which side(s) to compare: `running` (default), `startup`, or `both`. Returns a unified diff (LCS) when both sides are <= 5000 lines; falls back to a set-based added / removed listing otherwise. When MD5s match, `diff_strategy` is `md5_match` and the summary is empty. `max_diff_lines` (default 200) caps the returned `diff_text`."+ },+ {+ "slug": "DOMOTZ_MCP_CREATE_ALERT_RULE",+ "name": "Create alert rule",+ "description": "Create an alert rule. The rule fires when the named metric matches the given condition against the provided operands. `function` accepts a name (e.g. 'GREATER_THAN', 'LESS_THAN', 'RANGE') or a numeric function_id (e.g. '2'). Call `list_metric_functions` first to discover valid functions and their required operand count for the chosen metric. severity must be one of: Critical / High / Warning / Info. channel_ids must list at least one notification channel — a rule without channels notifies no one (use `list_communication_channels` to discover valid IDs). The rule's `metric` is IMMUTABLE after creation: changing the target metric requires deleting the rule via the UI and creating a new one. After creation, use `bind_alert_rule_to_device` to bind the rule to specific devices or variables."+ },+ {+ "slug": "DOMOTZ_MCP_CREATE_CONTACT",+ "name": "Create contact",+ "description": "Add a Contact to the Organization with the given internal `id`. `name` and `email` are required; `mobile_phone` and `phone` are optional. Returns the new contact_id. Contacts belong to a single Organization."+ },+ {+ "slug": "DOMOTZ_MCP_CREATE_ORGANIZATION",+ "name": "Create organization",+ "description": "Create a new Organization for the calling account. Returns the new internal `id`. `organization_id` is an optional caller-defined reference (e.g. a CRM id); it is stored as-is and is not used to address the organization. Reversible via delete_organization. Requires MCP access on the account."+ },+ {+ "slug": "DOMOTZ_MCP_CREATE_TAG",+ "name": "Create tag",+ "description": "Create a new user-defined tag. `color` is cosmetic and user-visible: do not pick one yourself -- ask the user which colour they want, and omit the parameter when you cannot ask (omitted means gray). Valid values are in the `color` enum, and `update_tag` can recolour later without affecting any bindings. The new tag becomes immediately usable as a filter in search_devices / search_collectors, as an assignable id in `bind_tags`, and can be renamed or recoloured with `update_tag`. Reversible with delete_tag. For MSP accounts the tag namespace is account-wide. Requires the manage_device_tags permission; callers without it receive a permission error."+ },+ {+ "slug": "DOMOTZ_MCP_CYCLE_OUTLET_POWER",+ "name": "Cycle outlet power",+ "description": "Power-cycle a single outlet on a host device (PoE switch / PDU). The powered device will experience a brief outage while the outlet turns OFF and back ON. Although the outlet itself returns to its prior ON state, the device may suffer config corruption or data loss during the cycle — treat as a recovery action of last resort. The cycle is dispatched asynchronously (HTTP 202): the response confirms dispatch, not completion. Source `host_device_id` and `outlet_id` from the `power_source` block returned by `device_inventory` for the powered device; that block is present only when the device is on a managed PoE switch or PDU and is the indicator that power-cycling is supported. Re-query `device_inventory` afterwards to inspect `power_source.link_freshness`."+ },+ {+ "slug": "DOMOTZ_MCP_DELETE_ALERT_RULE",+ "name": "Delete alert rule",+ "description": "Delete an alert rule by ID. Irreversible — the rule and all its device/collector/variable bindings are removed. Use `list_alert_rules` to discover valid IDs. Idempotent: deleting a non-existent rule returns status=NOT_FOUND (no error)."+ },+ {+ "slug": "DOMOTZ_MCP_DELETE_CONTACT",+ "name": "Delete contact",+ "description": "Permanently delete a Contact from the Organization with the given internal `id`. This cannot be undone."+ },+ {+ "slug": "DOMOTZ_MCP_DELETE_DEVICE",+ "name": "Delete device",+ "description": "PERMANENTLY delete one or more device records from a collector: the device and its history are removed entirely. This is IRREVERSIBLE - deleted devices cannot be recovered (though a device may be rediscovered later if it is still present on the network). Accepts a single device_id (int) or a list of device_ids (list[int]) for bulk deletion - all devices must belong to the same collector. Devices that no longer exist are reported as not-found and skipped (no error). Use `search_devices` to find device_ids before deleting."+ },+ {+ "slug": "DOMOTZ_MCP_DELETE_DRIVER",+ "name": "Delete driver",+ "description": "Permanently delete a driver from the account. This is IRREVERSIBLE: the driver disappears for every device it was attached to, all existing bindings are removed, and the scheduler stops running it everywhere. Persisted metrics and configuration backups produced before deletion remain in their respective stores — only the driver definition and its bindings are removed. ALWAYS confirm with the user before calling; in particular, list the devices that currently have the driver attached so the user understands the blast radius. Use `get_driver_catalog` for the driver catalog and `list_device_drivers` per device to enumerate bindings. If the intent is just to stop running the driver on ONE device, use `detach_driver` instead."+ },+ {+ "slug": "DOMOTZ_MCP_DELETE_ORGANIZATION",+ "name": "Delete organization",+ "description": "Permanently delete an Organization. Any Collectors bound to it are unlinked (not deleted). Fails if it is the account's only Organization. This cannot be undone."+ },+ {+ "slug": "DOMOTZ_MCP_DELETE_TAG",+ "name": "Delete tag",+ "description": "Delete a user-defined tag by ID. Irreversible — the tag is removed and unbound from every device and collector it was assigned to. Use `list_tags` to discover valid IDs. Idempotent: deleting a non-existent tag returns status=NOT_FOUND (no error). Fails with `TAG_IN_USE` if the tag is still referenced by one or more custom filters; the response lists the blocking filters so the caller can edit or remove them first. Requires the manage_device_tags permission."+ },+ {+ "slug": "DOMOTZ_MCP_DETACH_DRIVER",+ "name": "Detach driver",+ "description": "Remove the binding between a driver and a device on the given collector. The driver itself stays in the account and remains attached to other devices — only THIS device's binding is removed. The scheduler will stop running the driver on this device; any metrics already emitted are preserved. CONFIGURATION_MANAGEMENT drivers: previously persisted backups remain in storage and the device's CONFIGURATION_MANAGEMENT purpose row stays in the credential store (rotate or delete credentials via set_device_credential / UI if needed). To delete the driver everywhere instead, use `delete_driver`. Pass device_id+collector_id+driver_id; if no binding exists, the tool returns result=NOT_ATTACHED (idempotent — safe to call repeatedly)."+ },+ {+ "slug": "DOMOTZ_MCP_DETACH_SENSOR",+ "name": "Detach sensor",+ "description": "Detach a preconfigured (overlay) sensor from a device. Irreversible — the overlay link is removed and the sensor stops collecting. Use `list_device_sensors` to discover the `overlay_id` for currently attached overlay sensors. Only overlay (preconfigured) sensors can be detached via MCP: TCP-port sensors and custom OID sensors must be removed via the UI in this beta. Idempotent: detaching a non-attached overlay returns status=NOT_FOUND (no error)."+ },+ {+ "slug": "DOMOTZ_MCP_DEVICE_INVENTORY",+ "name": "Device inventory",+ "description": "Returns detailed information about a single device: identity, status, capabilities, protocol coverage, attached sensors/drivers/profiles, OS info, location, power source, and end-of-life (EOL) status for firmware, software, and hardware. Includes `collector_id` and `collector_name` — the numeric id (and display name) of the collector that monitors this device; needed for any subsequent metric tool call. The `power_source` section (when present) carries `host_device_id`, `outlet_id`, `outlet_type`, `link_source`, `link_freshness`, `available_power_actions` and, when no action is available, `power_actions_unavailable_reason`. `available_power_actions` lists what `set_device_power` accepts for this device right now (`on`, `off`, `cycle`, `software_reboot`); use `host_device_id` + `outlet_id` only for the older `cycle_outlet_power`. The `protocol` field describes how the device is represented: 'ip' (a standard network device with its own IP address); 'grouped' (a device that merges multiple network interfaces (NICs) on the same physical host into one logical device - it is online if any of its member interfaces is online, and the member interfaces are represented by this single grouped device); 'logical' (a manually-managed placeholder device with no IP - its status is set manually, not auto-monitored). Use for questions about what a device is, its hardware/software, installed services, where it is, how it is powered, or whether it has reached end-of-life. When presenting results, always refer to devices by name, not just by ID."+ },+ {+ "slug": "DOMOTZ_MCP_DEVICE_PERFORMANCE",+ "name": "Device performance",+ "description": "Fetch device performance metrics including round-trip delay, packet loss, uptime, SNMP sensor values, and disk usage over the last 7 days. Use for questions about device health, availability, resource utilization, or network performance."+ },+ {+ "slug": "DOMOTZ_MCP_EXECUTE_DRIVER",+ "name": "Execute driver",+ "description": "Run an action of a driver against a device. The tool auto-selects mode based on whether the driver is attached to the device:\n - NOT attached → DRY-RUN. The action runs on the device (real network, real credentials) but nothing is persisted: no metric stored, no backup row created, no binding made. Use this to smoke-test newly created drivers BEFORE attach_driver. Response includes `mode: 'dry-run'`.\n - ATTACHED → LIVE. Standard execution against the existing binding. Results are persisted by the scheduler/backend as usual. Response includes `mode: 'live'`. The binding must have `code_is_valid: true` and `status: ENABLED`.\n\nREQUIRED authoring workflow:\n save_driver → set_device_credential (if needed) → execute_driver (validate) → execute_driver (get-status | backup) → confirm both outcome=success → attach_driver. The first two execute_driver calls auto-run as dry-run because no binding exists yet. After attach_driver, future execute_driver calls run live.\n\n`action_id` values: `validate`, `get-status`, `backup`, `restore`, `custom-N`. For GENERIC drivers dry-run `validate` then `get-status`; for CONFIGURATION_MANAGEMENT dry-run `validate` then `backup`. `params` is a list of {name, value} pairs; types are derived from the driver's parameter schema.\n\n`credentials` (SEPARATE top-level argument — DO NOT put inside `params`): pass `{username: str, password: str, store?: bool}` to use ad-hoc credentials for this single execution instead of (or in addition to) any credentials previously saved via `set_device_credential`. Useful in the dry-run loop to try a credential without persisting it. `store` defaults to false in dry-run, true in live mode — set explicitly to override. Passwords are redacted in audit logs.\nCommon LLM mistake: passing credentials as an entry in `params` like `{name: 'credentials', value: {username, password}}`. That goes to the driver's parameter list and is IGNORED by the authentication path — the call then fails with INVALID_CODE/PRECONDITION because no real credentials reached the sandbox. The tool rejects this shape with WRONG_FIELD_SHAPE so you can resubmit with the top-level `credentials` arg.\n\nLogs are capped at 100 lines.\n\nDRY-RUN OUTPUT: when `mode: 'dry-run'`, the response also surfaces what the driver WOULD emit, so you can verify before attaching: `metrics` (GENERIC metric table), `variables` (legacy scalar variables), `tables`, and `backup` (CONFIGURATION_MANAGEMENT `running`/`startup`, each truncated to 4000 chars with a `*_truncated: true` flag). These keys appear only when present and only in dry-run; live runs persist results and omit them."+ },+ {+ "slug": "DOMOTZ_MCP_GET_ACCOUNT_INFO",+ "name": "Get account info",+ "description": "Returns identity and account context for the currently authenticated user: user ID, email, billing state, trial end date, whether the user is the account owner, and whether RBAC is enabled. For freemium users, also includes current device usage and limits. Use this as the first call to understand who you are acting as and what account capabilities are available."+ },+ {+ "slug": "DOMOTZ_MCP_GET_AUDIT_LOG_FILTERS",+ "name": "Get audit log filters",+ "description": "Return the set of values available for filtering Domotz audit logs: the operation categories (each with its operation types), source applications, target entities, actor entities, and outcome statuses currently present in the data. Use this to discover valid arguments for `search_audit_logs` before searching."+ },+ {+ "slug": "DOMOTZ_MCP_GET_COLLECTOR_ALERT_RULE_BINDINGS",+ "name": "Get collector alert rule bindings",+ "description": "List alert rules bound to a specific collector, including bindings at the collector level and bindings to variables owned by that collector. Use to see which alert rules are active on a collector and which metrics they target."+ },+ {+ "slug": "DOMOTZ_MCP_GET_COLLECTOR_CAPABILITIES",+ "name": "Get collector capabilities",+ "description": "Inspect what the customer's Collector can actually run. Without `driver_id`, returns the Collector's current sandbox module version plus the full supported / unsupported `D.*` symbol lists. With `driver_id`, returns a compatibility diff for that specific driver against this Collector, including a `compatible` flag and any `missing_features`. Use this BEFORE `attach_driver` / `execute_driver` to warn the customer when the Collector is behind on the sandbox version the driver requires — execute will otherwise fail with HTTP 412 inside execute_driver."+ },+ {+ "slug": "DOMOTZ_MCP_GET_COLLECTOR_CREDENTIAL_COVERAGE",+ "name": "Get collector credential coverage",+ "description": "Collector-wide credential audit. Returns only credential STATUS and metadata (integration status, SNMP reading sub-status). Does NOT return passwords, private keys, or SNMP community strings. Returns every visible device on the collector (including those with `has_working_credentials: false` so missing-credential gaps are visible) along with its enabled integration purposes — SNMP_MANAGEMENT, OS_MONITORING, CONFIGURATION_MANAGEMENT, ONVIF_CAMERA, DEVICE_MANAGEMENT — and whether each purpose's credentials are working (`UNLOCKED`) or not yet validated (`LOCKED`). SNMP_MANAGEMENT integrations include `snmp_reading_status` (CHECKING / NOT_FOUND / NOT_READING_DATA / READING_DATA) when available. `has_working_credentials` is true only when at least one purpose has valid, working credentials. Status mapping to `get_device_credentials`: UNLOCKED = AUTHENTICATED; LOCKED = any of REQUIRED / PENDING / WRONG_CREDENTIALS / NO_AUTHENTICATION. For per-protocol credential drill-down on a specific device (SSH/HTTP/etc.), use `get_device_credentials`."+ },+ {+ "slug": "DOMOTZ_MCP_GET_CONFIG_BACKUP_ENTRY",+ "name": "Get config backup entry",+ "description": "Returns a single configuration backup snapshot's text for a device. `config_type` selects which block to return: `running`, `startup`, or `both` (default). When running and startup configs are identical, `configs_match` is true and only the `running` block is populated for `both`. Each block carries `text` plus `line_count`, `truncated`, and `returned_lines` so the caller knows whether it was capped. `max_lines` (default 1000) caps each block independently — large enterprise configs can exceed this; raise the cap if a fuller view is needed."+ },+ {+ "slug": "DOMOTZ_MCP_GET_CONFIG_BACKUP_STATUS",+ "name": "Get config backup status",+ "description": "Lists devices on a collector that have configuration backup ('config backup') enabled, with the active backup driver, mode (READ_WRITE / READ_ONLY / AVAILABLE / INSUFFICIENT_PRIVILEGE / ERROR), status (ENABLED / DISABLED), failed-inspection count, and last inspection time. Devices without a detected backup driver are simply absent — this is not an error. Driver values include CISCO_IOS, CISCO_SG30X, CISCO_CBS, LUXUL_SMBSTAX, WATCHGUARD_FIREWARE_OS, WATCHGUARD_FIREWARE_OS_TFTP, FORTIGATE, FORTIGATE_TFTP, JUN_OS, HP_ARUBA_OS, HP_ARUBA_OS_AP, HP_ARUBA_OS_CX, HP_ARUBA_OS_SWITCH, SONICWALL, MIKROTIK, NETGEAR_OS_SWITCH, DELL_OS_SWITCH."+ },+ {+ "slug": "DOMOTZ_MCP_GET_CREATE_TAG_FORM",+ "name": "Get create tag form",+ "description": "Shows an interactive form to create a new custom tag, with a name field and a color picker. Use this tool when the user asks to create a new tag. If the user already stated the tag name or the color, pass them as the \"name\" and \"color\" arguments so they are pre-selected and the user does not have to enter them twice. Leave an argument out when the user did not mention it: the color then defaults to gray. This tool only creates a tag; it does NOT apply it to devices or collectors, and does NOT list or search existing tags."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DEVICE_ALERT_RULE_BINDINGS",+ "name": "Get device alert rule bindings",+ "description": "List alert rules bound to a specific device, including device-level bindings and bindings to variables owned by that device. Requires both collector_id and device_id. Use to see which alert rules are active on a device and which metrics they target. Call before bind_alert_rule_to_device to verify the rule is not already bound."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DEVICE_ALERTS",+ "name": "Get device alerts",+ "description": "Retrieve alert and monitoring configuration status for a specific device. Returns whether shared alerts are configured, event/alert rule counts, alert rule IDs, and setup integrations. Requires a device_id."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DEVICE_CREDENTIALS",+ "name": "Get device credentials",+ "description": "Per-device credential status drill-down. Returns only credential STATUS and metadata (authentication status, SNMP version, public-key fingerprint, timestamps). Does NOT return passwords, private keys, or SNMP community strings. Covers SNMP version + reachability status, and per-protocol access keys (SSH / TELNET / HTTP / HTTPS / WINRM / ONVIF) with their authentication status and (where available) public-key fingerprint. Status enums — `snmp.status`: CHECKING / NOT_FOUND / NOT_READING_DATA / READING_DATA; `access_keys[].authentication_status`: AUTHENTICATED / REQUIRED / PENDING / WRONG_CREDENTIALS / NO_AUTHENTICATION. `snmp` is null when no SNMP data exists. Status mapping to `get_collector_credential_coverage`: AUTHENTICATED = UNLOCKED; any of REQUIRED / PENDING / WRONG_CREDENTIALS / NO_AUTHENTICATION = LOCKED. For collector-wide credential gap analysis, use `get_collector_credential_coverage`."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DEVICE_HISTORY",+ "name": "Get device history",+ "description": "Returns the per-device History / Event Log for a single device: the chronological stream of events the device generated, most recent first. Events include availability transitions (`UP`/`DOWN`), `IP_CONFLICT_DETECTION` / `IP_CONFLICT_RESOLUTION`, `CREATED`, `IP_CHANGE`, `CONFIGURATION_CHANGE`, `CONFIGURATION_MISALIGNMENT`. Each entry carries a `timestamp` (ISO 8601) and an `event` name; when the backend recorded extra context (e.g. the IP or MAC address involved) it is returned in a `details` object. Requires `collector_id` and `device_id`. Optional `event_type` filters to a single event name from the fixed set above (case-insensitive). Optional `from`/`to` accept ISO 8601 timestamps and bound the time window; the backend caps a query at 31 days. If neither is given, the most recent events are returned; if only one is given the window defaults to 7 days. This is the device-level event stream, distinct from get_device_alerts (monitoring-profile alert configuration) and search_alerts (fired incidents)."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DEVICE_INTERFACES",+ "name": "Get device interfaces",+ "description": "Lists the SNMP-collected interfaces on a device. Returns id as a string (= ifIndex, pass directly to `get_interface_traffic.interface_ids`), name, alias, description, admin/operational status (IF-MIB enums: up/down/testing/unknown/dormant/notPresent/lowerLayerDown), high-speed (Mbps), type (human-readable IANA ifType label, e.g. 'ethernetCsmacd', 'ieee80211', 'tunnel', 'ieee8023adLag'), and per-interface error/discard counters. Devices without SNMP credentials yield an empty result. `max_interfaces` (default 100) caps the returned list; when truncated, `truncated: true` and `total_count` indicate that more exist."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DEVICE_METRICS",+ "name": "Get device metrics",+ "description": "Fetch summarised time-series analytics for one or more named metrics on a device within a time range. `metric_names` is capped at 15 per call and the total variables analysed across all metrics is capped at 30 (each metric can fan out to multiple variables, each analysed independently by the time-series analysis backend). Numeric variables are returned under `variables` with full analytics; text variables (e.g. status strings, hostnames, firmware versions) are returned under `text_variables` with `latest`, `count`, and `distinct_values` instead — they have no statistical analysis, so `include_anomalies` and `include_change_points` are ignored for them. `view=summary` (default) returns scalar stats only ({min, max, avg, latest, count, std, trend_slope, seasonality}); `view=timeseries` adds bucketed time/values arrays per variable, trimmed to `max_datapoints` (default 50). `include_anomalies` adds rolling-MAD anomaly points. `include_change_points` adds PELT segment break-points. `from`/`to` accept ISO 8601 timestamps; default window is the last 7 days (the time-series analysis backend needs a multi-day baseline for anomalies and change-points). Source `metric_names` from `list_collector_metrics` or `list_device_sensors`."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DRIVER_CATALOG",+ "name": "Get driver catalog",+ "description": "Lists the account-wide catalog of drivers available for attaching and executing on devices. Each entry returns the `id` (use as `driver_id` in `attach_driver` / `execute_driver`), `name`, `description`, `type`, `minimal_sample_period`, `last_saved_time`, and a `parameters` array describing each input (`name`, `label`, `value_type`, default `value`) — empty when the driver declares none. `code_is_valid: false` ⇒ the driver will fail at execute time and should not be attached. `credentials_required: true` ⇒ the device must have credentials configured before the driver can run; if absent, attach will fail."+ },+ {+ "slug": "DOMOTZ_MCP_GET_DRIVER_TEMPLATE",+ "name": "Get driver template",+ "description": "Fetch a single driver template, including its full JS code body and requirement metadata (`requirements.sandbox_version`, etc.). Use the returned `code` as the starting point for `inspect_driver` and `save_driver`."+ },+ {+ "slug": "DOMOTZ_MCP_GET_INTERFACE_TRAFFIC",+ "name": "Get interface traffic",+ "description": "Returns traffic counters for one or more device interfaces over a time range. Octets are reported in bps (per-period delta). `interface_ids` accepts strings or integers (pass the `id` values returned by `get_device_interfaces` directly); capped at 5 per call. `view=summary` (default) returns avg/max bps and total errors/discards; `view=timeseries` adds downsampled time/values arrays per interface, capped at `max_datapoints` (default 50) and limited to in/out octets unless `include_error_series=true`. `from`/`to` accept ISO 8601 timestamps; default window is the last 24 hours."+ },+ {+ "slug": "DOMOTZ_MCP_GET_NETWORK_CONFIGURATION",+ "name": "Get network configuration",+ "description": "Fetch what a collector actually scans, to answer 'why isn't this device discovered?'. Read-only. Returns:\n- `discovery_settings`: the three flags bounding the scan. `broadcast_discovery` is the decisive one: ON means the collector sweeps its subnets and picks up devices as they connect; OFF means it only probes the IPs already known to the cloud plus the forced ones, so a new device is never found and a known device that changes IP via DHCP just goes offline (ONVIF, SSDP/UPnP and mDNS discovery stop too; external hosts keep being probed). `scan_all_interface_ips` OFF means only the FIRST address of each network interface defines a subnet to scan, so secondary addresses and VLAN sub-interfaces are never scanned - the usual cause on a multi-homed collector. `dhcp_device_discovery` ON reports devices seen asking for a DHCP lease but never answering a scan (they appear with no IP); it needs the collector to sit in the same broadcast domain.\n- `interfaces`: `attached` are the interfaces the collector is physically attached to - the subnet of each is scanned with ARP ping at layer 2, and `vlan_id` is the VLAN it is tagged with (null when untagged), so the VLANs the collector sits on are the non-null ones. `routed` mirrors the routed networks below.\n- `routed_networks`: subnets NOT reachable at layer 2, only through a router, so they are scanned without ARP ping and answered at layer 3 only. `scan_probes` is the probe set nmap runs for that network (ICMP echo/timestamp, TCP SYN or TCP ACK on given ports); null means the collector's default set, which is ICMP echo only - `advanced_discovery` is what adds the extra TCP probes. Those extra probes are one collector-wide configuration copied onto every network with the flag on, so `scan_probes` is identical across them - the per-network choice is only whether they apply. Devices found this way carry a synthetic MAC starting `CS:TM:` followed by the IP in hex. Public ranges cannot be routed networks.\n- `external_hosts`: single monitored addresses, the equivalent of a /32 routed network; they accept a hostname or an IP and may be public, and appear with a `EX:TN:` MAC. `external_host_scan_policy` is the ICMP/TCP probe set deciding whether they are up - one value for ALL external hosts of the collector, not per host.\n- `ip_scan_policy`: subsets of addresses to scan (layer 2 and layer 3 alike) - forced IPs or IP ranges, used to monitor specific addresses instead of whole subnets.\n- `interfaces_policy`: `policy` plus `rules`, patterns on the interface name where `*` is a wildcard. With `deny`, a matching interface is NOT scanned (no rule = every interface is scanned, the default); with `allow`, ONLY matching interfaces are scanned (no rule = nothing is scanned at all).\n- `unavailable`: sections whose backend read failed. They are returned empty as a fallback, so an empty section listed here means 'not read', NOT 'nothing configured' - never diagnose from it.\nTypical causes of a missing device: broadcast_discovery off, a subnet that needs a routed network, an interface excluded by the interfaces policy, or an address outside the IP scan policy."+ },+ {+ "slug": "DOMOTZ_MCP_GET_ORGANIZATION",+ "name": "Get organization",+ "description": "Get the full details of a single Organization by its internal `id`: name, `organization_id` (the caller-facing reference), its Contacts, and the ids of the Collectors bound to it. Use search_organizations or list_organizations first to resolve a name or organization_id to an `id`."+ },+ {+ "slug": "DOMOTZ_MCP_GET_SNMP_CREDENTIALS_FORM",+ "name": "Get snmp credentials form",+ "description": "Shows an interactive form to set or update SNMP credentials on a specific device.Only use this tool when the user explicitly asks to set, update, or change SNMP credentials for a deviceDo NOT use for listing, searching, or querying devices or collectors."+ },+ {+ "slug": "DOMOTZ_MCP_GET_UPTIME",+ "name": "Get uptime",+ "description": "Returns uptime stats for a collector or device over a time range: total uptime percentage, online_seconds, total_seconds, and the list of downtime intervals. If `device_id` is omitted the response covers collector uptime; if provided, it covers device uptime (with `agent_uptime` showing how much of that range the collector itself was online). The backend caps individual queries at 31 days; obi splits longer ranges into 31-day chunks (parallel) and merges them, with an obi-side ceiling of 90 days. `from`/`to` accept ISO 8601; default window is the last 7 days."+ },+ {+ "slug": "DOMOTZ_MCP_INSPECT_DRIVER",+ "name": "Inspect driver",+ "description": "Static analysis of a driver's JS against the Domotz sandbox. Two modes: pass `code`+`type` to analyze a DRAFT statelessly (nothing persisted — use this in the authoring loop while iterating), OR pass `driver_id` to inspect a SAVED driver (returns its stored `code`, code analysis, `code_is_valid`, `required_features`, and its declared `parameters`). Provide exactly one mode — not both, not neither. Returns `is_valid`, the list of analyzer errors, and a summary of which `D.*` APIs the code references. When an error points at a `D.*` symbol you don't recognize, read the per-symbol doc at MCP resource `domotz://sandbox/api/{symbol}` for signature, params, and examples (or `domotz://sandbox/api/catalog` for the full surface). Once `is_valid` is true, call `save_driver` to persist."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_ALERT_RULES",+ "name": "List alert rules",+ "description": "Lists alert rule definitions in the account. Each rule defines a condition and threshold that, when matched, fires an alert. This tool returns the rule definitions (id, name, metric, function, operands, severity, attached devices/collectors). It does NOT return fired alerts — use `search_alerts` for those. Optional `entity` filter narrows to rules attached to devices (`device`) or collectors (`collector`). The `linked_entities` field shows where the rule is currently attached. `channel_ids` are not returned for existing rules — they're only available at rule creation time. Feeds `create_alert_rule` and `bind_alert_rule_to_device`."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_COLLECTOR_METRICS",+ "name": "List collector metrics",+ "description": "Enumerate the metrics available on a collector — speed-test thresholds, IP-conflict status, collector uptime, security-issues counts, and the rest of the collector-scoped metric catalog. Use this to discover what can be alerted on at the collector level. Use the returned `metric` values as input to alert rule creation."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_COMMUNICATION_CHANNELS",+ "name": "List communication channels",+ "description": "List the user's notification channels (email, webhook, Slack, etc.). Each channel has an id, endpoint, description, and type. Use to discover channel_ids before creating an alert rule via create_alert_rule (channel_ids is a required parameter)."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_CONFIG_BACKUP_HISTORY",+ "name": "List config backup history",+ "description": "Lists configuration backup snapshots for a device on a collector, newest first. When `running_md5` differs from `startup_md5` the device has unsaved changes (running config diverges from what would persist across reboot). `label` is user-mutable; `source` (user / custom_driver / internal_driver) records who took the snapshot. Use `next_before` as the `before` cursor to fetch the next page. `snapshot_timestamp` is the chain identifier consumed by `get_config_backup_entry` and `compare_config_backup`."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_DEVICE_DRIVERS",+ "name": "List device drivers",+ "description": "Lists drivers currently attached to a device. Each binding returns the driver identity, the binding status, parameter values (with secrets pre-masked), and the list of executable actions (e.g. `validate`, `get-status`, `backup`, `restore`, `custom-N`) — pass an action's `action_id` to `execute_driver`. `status: DISABLED` ⇒ the binding cannot be executed even when `code_is_valid: true`; re-enable via the UI before retrying. Empty `actions[]` ⇒ the driver is not executable."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_DEVICE_METRICS",+ "name": "List device metrics",+ "description": "List everything monitorable on a device. Returns the metric catalog (what CAN be alerted on — always populated, even at discovery time). Pass metric (prefix match) to also include the live variable instances for that metric, with variable_id needed for variable-level binding. When metric is omitted, only the metric catalog is returned — use this to browse what's available before drilling into a specific metric's variables. Follow up with list_metric_functions to discover valid thresholds for a metric, and list_variable_alert_rule_candidates to check whether a suitable alert rule already exists."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_DEVICE_PROFILES",+ "name": "List device profiles",+ "description": "Lists device profiles in the account. A device profile bundles sensor definitions and credentials that can be applied to one or more devices. Use the returned `id` with `apply_device_profile`. The optional `view` parameter selects detail level: `summary` (default) returns module metadata only; `full` includes the per-module configuration JSON (~5x larger payload). Module types include SNMP_PRECONFIGURED_SENSOR, SNMP_CUSTOM_OID, TCP_SENSOR, CREDENTIAL, CUSTOM_TAG, INFO, SHARED_ALERT. `has_credentials` is true when the profile applies credentials (applying it will overwrite credentials on targeted devices)."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_DEVICE_SENSORS",+ "name": "List device sensors",+ "description": "Lists the sensors currently attached to a device, merged across CUSTOM_OID, TCP, CUSTOM_DRIVER, and PRECONFIGURED kinds. Every entry carries `kind`. CUSTOM_OID entries carry `id`, `name`, `oid`, `description`, `value_type`, `category`, `custom_name` — created via `attach_sensor(sensor_spec={kind:'custom_oid', ...})`. TCP entries carry `name`, `port`, `service`, `status`, `last_update`. CUSTOM_DRIVER entries carry `id` and `driver_name` (drivers, distinct from custom OIDs). PRECONFIGURED entries carry `id`, `name`, and `category` (overlays from `list_preconfigured_sensors`). Sibling tools: `device_inventory` for sensor counts only, `get_device_metrics` for time-series data, `list_preconfigured_sensors` for the account-wide overlay catalog."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_DEVICE_TYPES",+ "name": "List device types",+ "description": "Returns the device-type catalog used to classify devices (router, switch, AP, server, etc.). Stable across calls within an API version. Each entry has an `id` (used as the `type_id` filter in `search_devices`) and a user-facing `label`. Use to discover valid type filters before constructing a search."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_DRIVER_TEMPLATES",+ "name": "List driver templates",+ "description": "List shared driver templates the account can start from. Each entry returns `id` (use as `template_id` in `get_driver_template` and `save_driver`), `name`, `category`, `type`, and `version`. Templates are read-only starters; creating a driver from a template still produces a new, account-owned driver."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_METRIC_FUNCTIONS",+ "name": "List metric functions",+ "description": "List the evaluation functions (e.g. GREATER_THAN, LESS_THAN, RANGE, CHANGED) available for a given metric name. Each function describes the comparison used to evaluate incoming variable values. Use to discover which threshold functions can be applied when creating or describing an alert rule."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_ORGANIZATIONS",+ "name": "List organizations",+ "description": "List the account's Organizations with their Contacts and bound Collector ids. Each result carries the internal `id` (use it to address an organization) and the caller-facing `organization_id`. Optional filters (applied server-side): `name` (case-insensitive substring), `organization_id` (exact), `collector_id` (only the organization the collector is bound to). Sort by `name` (default) or `id`."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_PRECONFIGURED_SENSORS",+ "name": "List preconfigured sensors",+ "description": "Returns the account-wide catalog of preconfigured sensors available to attach via `attach_sensor(sensor_spec={kind: 'overlay', overlay_id: ...})`. When `device_ids` is provided, each sensor includes a per-device `attached` flag indicating whether it is already attached to that device. Custom sensors (category=CUSTOM) are excluded. Sorted by `supported_device_count` descending — most-applicable first. Companion to `attach_sensor`. Distinct from `list_device_sensors` (per-device attached) and `get_device_metrics` (time-series data for a device)."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_TAGS",+ "name": "List tags",+ "description": "Returns the account-wide catalog of user-defined tags applied to devices and collectors. Each entry includes id, name, color, and the count of devices and collectors currently using it. For MSP accounts the tag namespace is account-wide (shared across organizations). Use to discover valid tag IDs before filtering in search_devices / search_collectors, assigning tags with `bind_tags`, or editing a tag with `update_tag`."+ },+ {+ "slug": "DOMOTZ_MCP_LIST_VARIABLE_ALERT_RULE_CANDIDATES",+ "name": "List variable alert rule candidates",+ "description": "List alert rules that could be bound to a specific device variable. Each candidate includes an 'attached' flag: true means the rule is already bound to this variable, false means it could be bound. Use this right before creating a new alert rule, to reuse an existing one when possible."+ },+ {+ "slug": "DOMOTZ_MCP_MANAGE_EXTERNAL_HOSTS",+ "name": "Manage external hosts",+ "description": "Add or remove an external host on a collector. An external host is a single address - a public or remote IP, or a hostname/FQDN - monitored as one device (the equivalent of a /32 routed network); public addresses are allowed here, unlike routed networks.\n- action='add': needs `host` (IP or hostname) and `name`. Optionally `device_type_id` (see `list_device_types`; defaults to the generic type). Returns the new `device_id`.\n- action='remove': needs `device_id`. DESTRUCTIVE and irreversible: it deletes the device record and its history. Get the id from `get_network_configuration` (external_hosts). Only external hosts can be removed here - an id that is not one is refused, use `delete_device` for a regular device.\nHow external hosts are probed (the ICMP/TCP probe set deciding whether they are up) is NOT settable here: it is a single collector-wide value shared by every external host, so it cannot be changed for one of them. Read it with `get_network_configuration` (`external_host_scan_policy`) and change it from the web app.\nAdding an external host consumes the account's external-host and managed-device allowance; the backend rejects the call when either is exhausted."+ },+ {+ "slug": "DOMOTZ_MCP_MANAGE_IP_SCAN_POLICY",+ "name": "Manage ip scan policy",+ "description": "Manage the collector's forced IP scan policy: extra addresses the collector must probe on top of what it discovers by itself. Use it for a device that never answers a normal discovery scan (silent host, outside the interface's own subnet, ignores ARP/ICMP broadcast) so the collector keeps polling that address explicitly.\nThis is an INCLUDE-only list: there is no way to exclude an address here - to reduce what gets scanned use `set_interfaces_policy`.\n- kind='ip', action='set': `ip_addresses` REPLACES the whole forced address list. Read the current one with `get_network_configuration` and send it back with your additions, or you will drop the others.\n- kind='ip', action='remove': removes the single `ip_address`.\n- kind='range', action='set': `ip_ranges` (list of {'start': ..., 'end': ...}) REPLACES the whole forced range list. start must be lower than end.\n- kind='range', action='remove': removes the single range identified by `ip_range_id`.\nOnly IPv4. Public addresses are refused unless the account is allowed to use them, and the whole feature is plan-gated - the backend answers 403 when it is not enabled."+ },+ {+ "slug": "DOMOTZ_MCP_MANAGE_ROUTED_NETWORKS",+ "name": "Manage routed networks",+ "description": "Add, update or remove a routed network on a collector. A routed network is a subnet the collector cannot reach at layer 2 (no ARP), only through a router, so it is probed at layer 3 only; devices found there appear with a synthetic MAC address. Use it to monitor a subnet that lives behind a router.\n- action='add': needs `address`, `subnet_mask` and `name`. `subnet_mask` takes a dotted quad ('255.255.255.0') or a prefix length ('24'); it must be /24 or narrower, the range must be private (public ranges are rejected) and must not overlap an existing routed network nor one of the collector's own attached subnets.\n- action='update': needs `routed_network_id` plus the full new `address`/`subnet_mask`/`name` - it replaces, it does not patch. `advanced_discovery` is part of that replace: omit it and the network keeps the value it has now, pass it to change it.\n- action='remove': needs `routed_network_id`. DESTRUCTIVE: it also deletes every device discovered inside that subnet, with its history.\n`advanced_discovery` (add/update) widens the probe set from ICMP echo only to ICMP plus a few TCP probes, finding devices that drop ICMP but answer TCP, at the cost of a slower and noisier scan. The flag is the only per-network choice: which probes 'advanced' means is one collector-wide configuration, identical for every routed network that has the flag on, and it cannot be changed from here - read it in `get_network_configuration` (`scan_probes`).\nRead the current routed networks and their ids with `get_network_configuration` first."+ },+ {+ "slug": "DOMOTZ_MCP_NETWORK_TOPOLOGY",+ "name": "Network topology",+ "description": "Returns the network topology discovered by a single collector: device-to-device links and per-outlet (port) details. `view` controls detail level — `summary` returns infrastructure-only counts (~10 nodes), `standard` (default) returns full nodes and edges, `full` adds an upstream dependency map plus the inferred root (gateway). `max_links` (default 200) caps the returned edges; when truncated, `truncated: true` and `total_links` indicate that more exist. Use to understand network structure, identify single points of failure, or trace upstream paths."+ },+ {+ "slug": "DOMOTZ_MCP_RESOLVE_ALERT",+ "name": "Resolve alert",+ "description": "Permanently resolve one or more alert incidents. Resolution is IRREVERSIBLE — once resolved an incident cannot be re-opened. Domotz has no intermediate 'acknowledged-but-not-fixed' state; this tool transitions TRIGGERED / TRIGGERED_NO_AUTOMATIC incidents to RESOLVED. Bulk resolution is supported in a single call (pass an array of `unique_ids`). The optional `note` is captured in the audit trail. Source the UUIDs from `search_alerts.alerts[].unique_id`."+ },+ {+ "slug": "DOMOTZ_MCP_SAVE_DRIVER",+ "name": "Save driver",+ "description": "Create or update a driver on the account. Omit `driver_id` to CREATE a new driver (requires `name`, `code`, `type`); pass `driver_id` to UPDATE an existing one (only `code`, `description`, `timeout` are mutable — `name`/`type` are immutable here and rejected with `FIELD_NOT_ALLOWED`, change them in the UI). Account-scoped: no `collector_id` here — capability checks happen later via `get_collector_capabilities` or at execute time. On success returns `driver_id`, `code_is_valid`, and `required_features` (the `D.*` APIs the driver uses, useful for warning the customer if the target Collector lacks them), plus `result` (`CREATED` or `UPDATED`). On create, a name clash returns `result=NAME_CONFLICT`; on update, an unknown id returns `result=NOT_FOUND`. Iterate on `inspect_driver` until the code is valid before saving. Optional fields: `description`, `timeout` (0-120s), `credentials_required`, `template_id` (create only — start from a shared template).\n\n`credentials_required` (CRITICAL — getting this wrong silently breaks the driver): controls whether the sandbox receives the device's persisted credentials when the driver runs.\n - Set TRUE if the JS code uses ANY of: `D.device.username()`, `D.device.password()`, `D.device.credentials`, `D.device.sendSSHCommand`, `D.device.sendSSHShellSequence`, `D.device.sendWinRMCommand`, `D.device.sendTelnetCommand`, or HTTP options with `auth: 'basic'` and no inline username/password.\n - Set FALSE if the driver only makes anonymous HTTP calls, public-community SNMP reads, or passes inline credentials sourced from driver parameters (not from the device's stored creds).\n - If omitted, this tool auto-infers from the code (in BOTH create and update-with-`code`) by scanning for the patterns above and includes `credentials_required_auto_inferred: true` in the response so you can verify. Override explicitly when the heuristic is wrong (e.g. the code uses encrypted creds via custom params, or credentials are passed inline at execute time only).\nWhy it matters: with `credentials_required=false`, the backend strips `device.device_access_keys` before dispatch — the driver runs but every credential-bearing call sees empty values and fails non-obviously (auth errors, empty username in SSH, etc).\n\nChoosing `type` (create only) — REQUIRED decision before writing any code:\n - `GENERIC`: monitor observable values over time (CPU, temperature, link state, counters, port up/down, service health). Implements validate() + get_status(). Returns metrics via `D.success([D.createMetric({uid, label, value, unit?}), ...])` — ALWAYS use `D.createMetric` as the first pick. `D.createVariable` (and `D.device.createVariable`) are the legacy fallback, used ONLY when the target Collector lacks `SandboxCapabilityMetrics` — confirm via `get_collector_capabilities` before emitting createVariable. Do NOT use GENERIC to capture device configuration text.\n - `CONFIGURATION_MANAGEMENT`: snapshot the device's configuration (switch/router running-config and startup-config, firewall rules, AP config). Implements validate() + backup(). Returns config blobs via `D.success(D.createBackup({running, startup}))`. Do NOT use this type to emit metrics.\n Decision rule: is the output numeric/state values to chart over time, or a text blob representing device config? Metrics → GENERIC. Config text → CONFIGURATION_MANAGEMENT.\n\nBEFORE writing code, read MCP resources `domotz://sandbox/types` (driver type contracts with `purpose`, `when_to_use`, `output_shape`, and example use cases per type), `domotz://sandbox/skeleton/{driver_type}` (minimal valid starter with inline intent comments), and `domotz://sandbox/api/catalog` (every `D.*` symbol with signature, params, min sandbox version, and examples). Each `D.*` symbol is also readable individually via `domotz://sandbox/api/{symbol}`."+ },+ {+ "slug": "DOMOTZ_MCP_SEARCH_ALERTS",+ "name": "Search alerts",+ "description": "Search alert history with filters. Returns both active and historical alerts. Each result carries the `unique_id` UUID (the chain identifier into `resolve_alert(unique_ids=[...])`), the `status`, `severity`, `triggered_at`/`closed_at`, the `trigger_function_repr` + `trigger_value` that fired the rule, and a `context` block with device/collector/profile snapshots. status ∈ TRIGGERED / TRIGGERED_NO_AUTOMATIC / CLOSED / RESOLVED — open alerts are TRIGGERED ∪ TRIGGERED_NO_AUTOMATIC. Default sort: triggered_at descending. Pass `unique_ids=[…]` to fetch specific incidents by UUID (exact match) — use this when you already know which incident(s) you want, instead of filtering by device/time and hunting through the result page."+ },+ {+ "slug": "DOMOTZ_MCP_SEARCH_AUDIT_LOGS",+ "name": "Search audit logs",+ "description": "Search Domotz audit logs for the caller's organization. Filter by time range, operation type/category, target entity, actor, outcome status, and source application. Timestamps may be ISO 8601 strings (e.g. '2026-06-12T10:00:00Z') or integer epoch seconds. Valid `target_entity_type` values: USER, COLLECTOR, DEVICE, DEVICE_PROFILE, USER_CREDENTIALS, ALERT_RULE, ALERT, CUSTOM_FILTER, CUSTOM_TAG (the monitoring appliance is a 'COLLECTOR'). Results are sorted by event_timestamp descending by default."+ },+ {+ "slug": "DOMOTZ_MCP_SEARCH_COLLECTORS",+ "name": "Search collectors",+ "description": "Search and list Domotz collectors with filtering and pagination (zero-based: first page is page=0). filter_by keys: name, collector_id, status (ONLINE/OFFLINE), health_status (HEALTHY/ISSUES/DOWN), organization_id, tag_ids (list, AND-ed), ip_prefix, owner_name, text_match (fuzzy across name/vendor/IP/owner). Returns data in three detail levels: 'summary' (id, name, status, ip, organization), 'standard' (default - adds tags, counters, platform, mac), 'detailed' (all available fields including licence, monitoring mode, software version). Use this tool to discover which collectors exist and their current state."+ },+ {+ "slug": "DOMOTZ_MCP_SEARCH_DEVICES",+ "name": "Search devices",+ "description": "Cross-account device search with filters and pagination (zero-based: first page is page=0). Supports filtering by text_match, name, ip_mac, vendor, model, collector_ids, status (ONLINE/OFFLINE), type_ids, tag_ids, organization_id, serial, room, zone, credential_types, credential_status, importance (important or not important), monitoring_state (device managed or device unmanaged), and device_id. Note: ONLINE includes devices within the heartbeat grace period; OFFLINE means the device has been unreachable past the grace period. Returns data in three detail levels: 'summary' (id, name, status, ip, collector_id, type), 'standard' (default - adds mac, vendor, model, importance, tags, organization, first_seen), 'detailed' (all fields including serial_number, zone, credentials/alerts/snmp flags). The 'detailed' view includes a `protocol` field describing how a device is represented: 'ip' (a standard network device with its own IP address); 'grouped' (a device that merges multiple network interfaces (NICs) on the same physical host into one logical device - it is online if any of its member interfaces is online, and the member interfaces are represented by this single grouped device); 'logical' (a manually-managed placeholder device with no IP - its status is set manually, not auto-monitored). Use this tool to discover and filter devices across your network. When presenting results, always refer to devices by name, not just by ID."+ },+ {+ "slug": "DOMOTZ_MCP_SEARCH_ORGANIZATIONS",+ "name": "Search organizations",+ "description": "List and filter the organizations visible to the calling user. The discovery entry-point for multi-tenant workflows: resolve an organization name to an `id` before scoping subsequent calls (e.g., `search_collectors`, `search_devices`). MSP accounts typically have many organizations; single-org accounts return a single result. `with_offline_collectors_only` narrows to organizations with at least one offline collector. The chain: `search_organizations` → `search_collectors` → `search_devices`."+ },+ {+ "slug": "DOMOTZ_MCP_SET_COLLECTOR_DEFAULT_SNMP_CREDENTIALS",+ "name": "Set collector default snmp credentials",+ "description": "Set the collector's DEFAULT SNMP credentials — the ones used for devices that have no SNMP credentials of their own. Devices already configured keep theirs: to change one of those use `set_device_credential`. `credential_spec.version` selects the family: V1/V2 require `community` (optional `write_community`); V3_NO_AUTH requires `username`; V3_AUTH_NO_PRIV adds `authentication_protocol` + `authentication_key`; V3_AUTH_PRIV adds `encryption_protocol` + `encryption_key`. Protocol names carry hyphens: MD5 / SHA / SHA-224 / SHA-256 / SHA-384 / SHA-512 for authentication, DES / AES / AES-256B / AES-256R for encryption. OVERWRITES any default previously set on the collector. The feature is licensed: on plans without it the tool returns `error=FEATURE_NOT_AVAILABLE`. Never include the community string or any key in a user-visible message. Use `collector_overview` to read back which version is configured (secrets are never returned)."+ },+ {+ "slug": "DOMOTZ_MCP_SET_DEVICE_CREDENTIAL",+ "name": "Set device credential",+ "description": "Set or overwrite a device credential. `credential_spec.kind` selects the credential family. Access keys (SSH / HTTP / HTTPS / TELNET / WINRM / ONVIF) require {username, password} and accept optional `purpose` (DEVICE_MANAGEMENT default, also CONFIGURATION_MANAGEMENT / CUSTOM_DRIVER_MANAGEMENT / OS_MANAGEMENT). When purpose=CUSTOM_DRIVER_MANAGEMENT you MUST also pass `driver_id`. SNMP variants: SNMPv1/SNMPv2 require `community` (optional `write_community`); SNMPv3_NO_AUTH requires `username`; SNMPv3_AUTH_NO_PRIV adds `authentication_protocol` + `authentication_key`; SNMPv3_AUTH_PRIV adds `encryption_protocol` + `encryption_key`. OVERWRITES the existing credential of the same kind/purpose. Validation is asynchronous on the collector — re-fetch with `get_device_credentials` after a few seconds. If the collector is unreachable the call returns `result=CREDENTIALS_SAVED_VALIDATION_TIMEOUT` — credentials are saved, retry later. Never include secrets in any user-visible message. For SNMP credentials specifically, when the client renders HTML UI (Claude Desktop, Claude.ai web), prefer `get_snmp_credentials_form` for a guided form-based flow; this tool remains the canonical text alternative."+ },+ {+ "slug": "DOMOTZ_MCP_SET_DEVICE_POWER",+ "name": "Set device power",+ "description": "Change the power state of a device: turn it `on`, hold it `off`, `cycle` it, or issue a `software_reboot`. `on`/`off`/`cycle` act on the outlet of the PoE switch or PDU the device is plugged into; `software_reboot` is a management command sent to the device itself. Unlike `cycle`, an `off` is durable — the device stays powered off until an explicit `on`, so a Power Off / wait / Power On sequence is two calls. The call is asynchronous (HTTP 202): the response confirms DISPATCH, not completion — re-query `device_inventory` or `get_uptime` to confirm the outcome. obi pre-checks the device's power capabilities and returns NOT_SUPPORTED with a `reason` instead of dispatching when the requested action is unavailable. Address the device by its own `device_id`: the host device and outlet are resolved for you."+ },+ {+ "slug": "DOMOTZ_MCP_SET_INTERFACES_POLICY",+ "name": "Set interfaces policy",+ "description": "Set which of the collector's own network interfaces take part in discovery, by name. Rules are interface-name patterns where `*` is the only wildcard (e.g. 'eth0', 'docker*', 'br-*'); matching is case-insensitive. This REPLACES the current policy - send the full set of rules you want, not a delta.\n- policy='deny' with rules: every interface is scanned EXCEPT the ones matching. This is how you stop the collector scanning a noisy or irrelevant interface (a container bridge, a VPN tunnel).\n- policy='deny' with no rules: the default - every interface is scanned.\n- policy='allow' with rules: ONLY matching interfaces are scanned.\n- policy='allow' with no rules: nothing at all is scanned, so no device is discovered or monitored on any subnet. Rejected here as it is almost never intended.\nAt most 10 rules, each at most 20 characters. Use `get_network_configuration` first: it lists the collector's actual interface names and the policy in force."+ },+ {+ "slug": "DOMOTZ_MCP_SNOOZE_COLLECTOR_ALERTS",+ "name": "Snooze collector alerts",+ "description": "Snooze (temporarily mute) all alerting for a collector for a maintenance window. Equivalent to 'Snooze Agent Alerts' in the UI: alerting is suppressed now and automatically resumes when the window ends. Specify the window with EITHER `until` (an absolute ISO 8601 timestamp, e.g. '2026-07-01T18:30:00Z') OR `duration_minutes` (a relative number of minutes from now) - provide exactly one. Snoozing is a collector-level maintenance window and applies to the whole collector (individual devices cannot be snoozed); use `unsnooze_collector_alerts` to resume alerting before the window ends."+ },+ {+ "slug": "DOMOTZ_MCP_SUBMIT_FEEDBACK",+ "name": "Submit feedback",+ "description": "Submit feedback about a gap in available MCP tools or data. Use this ONLY when you searched for a tool but could not find one, got incomplete results from an existing tool, or a tool was missing a needed parameter. Required: what_i_needed, what_i_tried, gap_type. gap_type must be one of: missing_tool, incomplete_results, missing_parameter, wrong_format, other."+ },+ {+ "slug": "DOMOTZ_MCP_UNBIND_ALERT_RULE_FROM_COLLECTOR",+ "name": "Unbind alert rule from collector",+ "description": "Unbind an alert rule from a collector. Removes the bindings of all of the collector's variables to the rule — the rule definition itself stays. Use after `bind_alert_rule_to_collector` or to clean up a rule that is no longer relevant for the collector. Idempotent: unbinding a rule that is not bound returns status=NOT_FOUND (no error)."+ },+ {+ "slug": "DOMOTZ_MCP_UNBIND_ALERT_RULE_FROM_DEVICE",+ "name": "Unbind alert rule from device",+ "description": "Unbind an alert rule from a device. Removes the bindings of all of the device's variables to the rule — the rule definition itself stays. Use after `bind_alert_rule_to_device` or to clean up a rule that is no longer relevant for the device. Idempotent: unbinding a rule that is not bound returns status=NOT_FOUND (no error)."+ },+ {+ "slug": "DOMOTZ_MCP_UNBIND_COLLECTOR_FROM_ORGANIZATION",+ "name": "Unbind collector from organization",+ "description": "Unbind a Collector from an Organization (addressed by its internal `id`). The Collector is not deleted, only detached from the Organization."+ },+ {+ "slug": "DOMOTZ_MCP_UNSNOOZE_COLLECTOR_ALERTS",+ "name": "Unsnooze collector alerts",+ "description": "Resume alerting on a collector immediately, cancelling any active snooze/maintenance window set by `snooze_collector_alerts`. Safe to call even if the collector is not currently snoozed."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_ALERT_RULE",+ "name": "Update alert rule",+ "description": "Update an existing alert rule in place, preserving its device/collector/variable bindings and alert history (unlike deleting and recreating). Only the fields you pass are changed; omitted fields keep their current value. Editable fields: `name`, `severity` (Critical / High / Warning / Info), `function` (a name like 'GREATER_THAN' or a numeric function_id), `operands`, `operands_unit`, and `channel_ids` (the full set of notification channels the rule should use; channels not listed are detached, so an empty list is rejected). When changing `function`, call `list_metric_functions` first to confirm the valid functions and their required operand count. The rule's target `metric` is IMMUTABLE and cannot be changed here: retarget by deleting the rule and creating a new one. Use `list_alert_rules` to discover valid IDs. Updating a non-existent rule returns status=NOT_FOUND (no error)."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_COLLECTOR_METADATA",+ "name": "Update collector metadata",+ "description": "Update editable metadata on a collector (the on-site monitoring agent). Editable fields: `name` (the collector's display name), `time_zone` (an IANA time zone such as 'Europe/Rome'), and the postal address fields `address` (street address), `city`, `state`, `country`, `post_code`. This is a partial update: only the fields you pass are changed, the rest are left untouched. Pass at least one field -- empty calls are rejected. Use `search_collectors` to find the `collector_id`."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_COLLECTOR_MONITORING_SETTINGS",+ "name": "Update collector monitoring settings",+ "description": "Update how the collector monitors, as opposed to what it monitors. This is a partial update: only the fields you pass are changed. Pass at least one — empty calls are rejected. `sensor_hourly_frequency` is how many readings per hour every sensor on the collector takes, SNMP sensors included. It is READINGS PER HOUR, not minutes, and only the five cadences the product supports are accepted — users and the web app talk in minutes, so convert: 2 = every 30 minutes, 4 = every 15 minutes, 6 = every 10 minutes, 12 = every 5 minutes, 30 = every 2 minutes. The licence caps the maximum: above it the tool returns `error=FREQUENCY_EXCEEDED` and nothing is changed — lower the value or tell the user their plan does not allow that cadence. Read the current value back with `collector_overview`."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_CONTACT",+ "name": "Update contact",+ "description": "Update a Contact on the Organization with the given internal `id`. `name` and `email` are required (the full contact is replaced); `mobile_phone` and `phone` are optional."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_DEVICE_METADATA",+ "name": "Update device metadata",+ "description": "Update editable metadata fields on a device: `name`, `importance` (important or not important), `zone`, `room`, `serial`, `notes` (max 256 chars). To clear a field, pass the sentinel value `\"__clear__\"` (passing an empty string also works but may be dropped by some clients). Tags can be managed with `add_tag_ids` / `remove_tag_ids`. Per-field outcomes are reported in the response so partial successes are visible. Pass at least one field — empty calls are rejected."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_DEVICE_MONITORING_STATE",+ "name": "Update device monitoring state",+ "description": "Manage or unmanage one or more devices by changing their monitoring state. This is the ONLY way to manage or unmanage devices. When the user asks to 'manage', 'start monitoring', 'add to monitoring', or 'enable monitoring' for devices, use this tool with monitoring_state='managed'. When they ask to 'unmanage', 'stop monitoring', 'remove from monitoring', or 'disable monitoring', use monitoring_state='unmanaged'. Accepts a single device_id (int) or a list of device_ids (list[int]) for bulk operations — all devices must belong to the same collector. Managed devices consume a licence slot and are actively monitored (alerts, uptime tracking, etc.); unmanaged devices are visible in the network inventory but not actively monitored. IMPORTANT: monitoring_state (managed/unmanaged) is NOT the same as importance (important/not important). They are independent properties. 'not important' means low-priority, 'unmanaged' means not monitored at all. When the result is LIMIT_EXCEEDED and a checkout_url is present, always ask the user if they want to see the upgrade link — do not silently discard it. Fails with LOCATION_BASED_LICENSING when the collector uses location-based licensing (all devices are automatically monitored). Use `search_devices` to check the current monitoring_state before calling this tool."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_ORGANIZATION",+ "name": "Update organization",+ "description": "Update an existing Organization by its internal `id`. Only the fields you pass are changed (omit a field to leave it untouched). Updating just the name will not clear the organization_id. `organization_id` is the caller-facing reference (organa's external_reference)."+ },+ {+ "slug": "DOMOTZ_MCP_UPDATE_TAG",+ "name": "Update tag",+ "description": "Rename an existing user-defined tag, change its colour, or both. This is a partial update: omit a field to leave it untouched, and pass at least one -- empty calls are rejected. `color` is cosmetic and user-visible, so change it only when the user asked for a specific colour; valid values are in the `color` enum. Devices and collectors already carrying the tag keep it; only its name and colour change. A name already used by another tag returns ALREADY_EXISTS. Use `list_tags` to discover valid IDs. Requires the manage_device_tags permission."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "domotz_mcp_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "Domotz MCP API Key",+ "type": "string",+ "description": "Your Domotz MCP API key",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "donately","name": "Donately",@@ -181641,7 +185759,7 @@],"toolCount": 27,"triggerCount": 0,- "version": "20260615_00",+ "version": "20260908_00","tools": [{"slug": "E2B_CONNECT_SANDBOX",@@ -184434,6 +188552,57 @@}]},+ {+ "slug": "emailvalidation",+ "name": "Emailvalidation",+ "logo": "https://logos.composio.dev/api/emailvalidation",+ "description": "Validate individual email addresses for deliverability and quality signals, and inspect account quota usage through emailvalidation.io's complete REST API surface.",+ "category": "email",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 2,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "EMAILVALIDATION_GET_ACCOUNT_QUOTA_STATUS",+ "name": "Get Account Quota Status",+ "description": "Return the connected emailvalidation.io account ID and current monthly and grace credit totals, usage, and remaining balances. This status check does not consume validation credits or count against the API rate limit."+ },+ {+ "slug": "EMAILVALIDATION_VALIDATE_EMAIL_ADDRESS",+ "name": "Validate Email Address",+ "description": "Validate one email address and return deliverability, format, mailbox, domain, role-address, disposable-address, and quality signals. Each successful validation costs one account credit. Catch-all detection is optional, disabled by default, and requires a Small or higher plan; requesting it on an unsupported plan can still consume one credit."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "emailvalidation_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Your live emailvalidation.io API key. Sign in at https://app.emailvalidation.io/dashboard and copy the key shown on the Dashboard. Keep this value secret.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "emelia","name": "Emelia",@@ -186166,6 +190335,326 @@}]},+ {+ "slug": "era_context_mcp",+ "name": "Era Context MCP",+ "logo": "https://logos.composio.dev/api/era_context_mcp",+ "description": "Era Context MCP lets agents access authorized financial context and perform supported banking, brokerage, social, resource, and billing workflows through Era.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 51,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "ERA_CONTEXT_MCP_ACCOUNTS__CHECK_ACCOUNT_BALANCE",+ "name": "Accounts check account balance",+ "description": "Get the current and available balance for a specific account, including credit limit if applicable. Requires an account_group_key from accounts__list_financial_accounts. Use when the user asks about a specific account's balance rather than all accounts."+ },+ {+ "slug": "ERA_CONTEXT_MCP_ACCOUNTS__LIST_FINANCIAL_ACCOUNTS",+ "name": "Accounts list financial accounts",+ "description": "List all linked bank accounts, credit cards, and investment accounts with current and available balances. Use this when the user asks about their accounts, which banks they use, or when you need an account_group_key to pass to other tools like accounts__check_account_balance or transactions__list_transactions. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too."+ },+ {+ "slug": "ERA_CONTEXT_MCP_ACCOUNTS__MANAGE_ACCOUNT",+ "name": "Accounts manage account",+ "description": "Manage financial accounts in the user's universe — both manually tracked accounts and accounts synced from a connected banking provider. Actions: 'create' a new manual account (manual only), 'update' to change account properties (account_name is account-type-agnostic; account_type/institution_name/account_number_mask are manual-only), 'delete' to soft-delete a manual account (manual only), 'set_balance' to record a balance snapshot (manual only). On update, supplying 'account_name' writes a user-supplied display-name override that applies on top of any institution-supplied name and works for any account type — manual or connected. Supplying 'clear_account_name=true' removes the override, reverting to the institution-supplied name. The two are mutually exclusive. The account_type enum in the schema lists all valid types. Use accounts__list_financial_accounts to obtain the account_group_key for existing accounts."+ },+ {+ "slug": "ERA_CONTEXT_MCP_ACCOUNTS__SET_ACCOUNT_VISIBILITY",+ "name": "Accounts set account visibility",+ "description": "Set the visibility of a single financial account. Pass visible=true to show an account or visible=false to hide it. Hidden accounts are excluded from analytics and summaries. Use accounts__list_financial_accounts (with include_hidden=true) to get the account_group_key. Accounts excluded by tier enforcement (tier_excluded) cannot be toggled — the user must use the swap operation or upgrade their plan via billing__list_plans. Showing an account when the user is at their tier limit is also blocked — use swap instead."+ },+ {+ "slug": "ERA_CONTEXT_MCP_ACCOUNTS__TOGGLE_BALANCE_BACKFILL",+ "name": "Accounts toggle balance backfill",+ "description": "Toggle balance backfill for an account group. When enabled, balances are derived from cumulative transaction history rather than relying solely on explicit balance snapshots. This is useful for accounts that have transaction data but lack balance snapshots (e.g., CSV-imported accounts). This feature is only supported for manual accounts. Use accounts__list_financial_accounts to obtain the account_group_key."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__CANCEL_SUBSCRIPTION",+ "name": "Billing cancel subscription",+ "description": "Initiate subscription cancellation. This is a three-path retention gate. Step 1: Call WITHOUT a confirmation_key — the tool returns a retention offer with a 50% discount coupon for the next billing cycle and a confirmation key. Present this offer to the user. Step 2a: If the user accepts the discount, call AGAIN WITH the confirmation_key AND accept_offer=true — the tool applies the coupon to their subscription and returns the outcome. Step 2b: If the user declines, call AGAIN WITH the confirmation_key AND accept_offer=false (or omit accept_offer) — the tool returns the billing page URL where the user can complete cancellation manually. This tool does NOT cancel the subscription directly. Requires billing-write permission."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__GET_CURRENT_PLAN",+ "name": "Billing get current plan",+ "description": "Get the user's current subscription plan, tier, usage against meter limits, and what the next tier up would unlock. Use for questions like 'what plan am I on?', 'how many API calls do I have left?', or 'what am I paying for?'. Call billing__list_plans if the user wants to compare all available tiers. The response distinguishes a scheduled full cancellation from a genuine tier downgrade via is_cancellation_pending — a downgrade also sets a pending tier but is not a cancellation. When is_cancellation_pending is true, call billing__uncancel_subscription to offer the user the winback path and keep their subscription active."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__LIST_PAYMENTS",+ "name": "Billing list payments",+ "description": "List the user's past invoices — what they were charged, when, for which service period, and whether each was paid. Use for 'what have I been charged?', 'when was I last billed?', or 'show me my receipts'. Amounts are in minor currency units (cents for USD). Pagination is forward-only and cursor-based, not page-numbered: pass the previous response's next_cursor back as cursor to get the next page, and stop when next_cursor is null (has_more is false). There is no total count and no way to jump to a page or go backwards — never invent a cursor value. This tool returns no invoice PDF or hosted invoice link, by design. If the user wants the actual document, send them to the billing portal, which authenticates them first."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__LIST_PLANS",+ "name": "Billing list plans",+ "description": "List all available subscription plans with pricing, billing periods, feature comparisons relative to the user's current tier, and free trial eligibility. Use for questions like 'what plans are available?', 'how much does the automate plan cost?', or 'can I get a free trial?'. Returns each tier marked as upgrade, current, or downgrade. After the user picks a plan, call billing__upgrade to subscribe or change tiers directly. billing__preview_subscription_change and billing__confirm_subscription_change require an organize-tier-or-above subscription and preview then confirm the exact prorated cost of a change for an existing subscriber — call billing__upgrade instead if the user has no active subscription yet."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__LIST_SUBSCRIPTIONS",+ "name": "Billing list subscriptions",+ "description": "List what the user is actually being charged for right now, read live from Stripe, broken down by individual line item. Use for 'what am I paying for?', 'when does my subscription renew?', 'how much is my add-on?', or 'am I being charged twice?'. Each subscription carries one or more items, and price, billing period and renewal date are per ITEM, not per subscription: a plan item and an add-on item on the same subscription can bill on different cadences and renew on different dates, so answer renewal questions from the specific item's current_period_end and never from another item's. A user may also hold more than one subscription; when the list has more than one entry, say so plainly rather than describing only the first. An item with kind 'legacy' is on a price predating the current catalog: report its name and amount as given and do not offer to change its billing period. Call billing__list_payments for past invoices rather than inferring them from this response."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__UNCANCEL_SUBSCRIPTION",+ "name": "Billing uncancel subscription",+ "description": "Un-cancel a subscription that Stripe holds a scheduled cancellation for, in either of the two mutually exclusive expressions Stripe stores one in: the cancel_at_period_end flag, or a concrete cancel_at instant with that flag false. Clears the scheduled cancellation and optionally applies a 50% off winback coupon for the next billing cycle. The user must have an active subscription that is currently scheduled to stop renewing. Returns the current tier and whether the coupon was applied. Requires billing-write permission."+ },+ {+ "slug": "ERA_CONTEXT_MCP_BILLING__UPGRADE",+ "name": "Billing upgrade",+ "description": "Start a subscription upgrade or plan change. Returns either a confirmation that the change was applied immediately (for existing subscribers changing tiers) or a secure checkout URL the user must visit to complete payment. Use when the user says 'I want to upgrade to automate', 'switch me to the yearly plan', or 'subscribe to organize'. Call billing__upgrade directly to subscribe for the first time or change tiers immediately; existing subscribers who already have an organize-tier-or-above subscription can instead call billing__preview_subscription_change first to show the prorated price before confirming with billing__confirm_subscription_change. Requires billing-write permission. After presenting a checkout URL to the user, consider polling billing__get_current_plan after 1-2 minutes to verify the upgrade completed."+ },+ {+ "slug": "ERA_CONTEXT_MCP_CONNECTIONS__CONNECT_BANK_ACCOUNT",+ "name": "Connections connect bank account",+ "description": "Initiate a bank account connection flow. Opens a secure connection page that the user interacts with to link their bank account. Optionally accepts a connection_id to reconnect an existing connection that has become stale or requires re-authentication. Also accepts an assistant_name (your name, e.g. 'Claude') to personalize the experience. Use this when the user wants to connect a new bank account or fix a broken connection."+ },+ {+ "slug": "ERA_CONTEXT_MCP_CONNECTIONS__DISCONNECT_INSTITUTION",+ "name": "Connections disconnect institution",+ "description": "Permanently disconnect a bank institution. This is a DESTRUCTIVE, IRREVERSIBLE operation that severs the link to the financial institution and stops all future data syncs. All accounts associated with this connection will be soft-deleted and excluded from analytics. Use connections__list_connections to identify the connection_id for the institution. After disconnecting, use connections__connect_bank_account to reconnect where the provider supports reconnecting (some connection types can't be reconnected on demand — the disconnect response says which)."+ },+ {+ "slug": "ERA_CONTEXT_MCP_CONNECTIONS__LIST_CONNECTIONS",+ "name": "Connections list connections",+ "description": "List every one of the user's bank connections with an honest, provider-agnostic status for each: whether it is healthy, syncing with no data yet, needs reconnecting, is currently disconnected, or one of several other narrower states — see each row's state for the exact one. This is the discover hop of the connection recovery loop — call this first to get each connection's connection_id, then act on a specific connection with connections__trigger_connection_resync, connections__connect_bank_account, or connections__disconnect_institution. Unlike accounts__list_financial_accounts, this tool's subject is the connection roster itself, not the accounts beneath it — use it to answer \"what banks are connected and are any of them broken?\" rather than \"what accounts do I have?\""+ },+ {+ "slug": "ERA_CONTEXT_MCP_CONNECTIONS__SET_PROACTIVE_SYNC_MODE",+ "name": "Connections set proactive sync mode",+ "description": "Record whether Era may proactively ask a bank connection's provider for fresh data on its own schedule. Set mode='disabled' when the user wants Era to stop reaching out to that bank between their own requests; set mode='enabled' to allow it again. This does NOT stop the connection: webhook updates, reconciliation and reads of data the provider already holds continue either way, and an on-demand refresh the user asks for is always honoured. The instruction is recorded for any connection the user owns — including one whose provider is never proactively contacted, and one whose plan does not include the proactive lane — so it survives a plan change and takes effect if the situation changes. Use connections__list_connections to obtain the connection_id. The response reports what was recorded AND whether it changes anything today, so say that back to the user rather than implying an effect that will not occur."+ },+ {+ "slug": "ERA_CONTEXT_MCP_CONNECTIONS__TRIGGER_CONNECTION_RESYNC",+ "name": "Connections trigger connection resync",+ "description": "Trigger an on-demand data resync for a bank connection. This fetches the latest transaction and balance data from supported banks — most major institutions support on-demand refresh, though it may take a few minutes for data to arrive. Possible outcomes: (1) resync queued successfully — check back shortly for updated data, (2) the bank requires the user to re-authenticate first — a widget link is returned that the user must open in the app to authenticate before the latest data can be fetched, (3) user's plan does not include on-demand resync (available on Automate tier or with Fast-Lane Data Sync add-on; use billing__list_plans to explore upgrade options), (4) data was already refreshed recently — next refresh available after the indicated time, (5) connection not found or not owned by the user. Use connections__list_connections to obtain the connection_id."+ },+ {+ "slug": "ERA_CONTEXT_MCP_HELP__GET_HELP",+ "name": "Help get help",+ "description": "Get contextual help and onboarding guidance for Era Context. Use when the user asks how to use the platform, what capabilities are available, how to get started, how to connect accounts, what they can ask, or questions about privacy or troubleshooting. Returns authoritative help content — prefer this over generating answers from memory."+ },+ {+ "slug": "ERA_CONTEXT_MCP_INSIGHTS__ANALYZE_SPENDING",+ "name": "Insights analyze spending",+ "description": "Break down spending by category, merchant, account, week, or month. Each group carries amount, percent of total, and transaction count. group_by 'category', 'merchant' or 'account' returns the top_n highest-spending groups, highest first. 'week' and 'month' ignore top_n and return one group per period that has spending, oldest first, never truncated. A gap in the series means no spending in that period, not an omitted group. A wide range returns many groups; narrow the period to bound the response. Week and month groups carry period_start and period_end: the dates covered, clamped to the requested range. Read those dates, not the label, when the span matters. The first and last group are commonly partial. A week label is a 7-day block counted from January 1, not an ISO week. period.start is the first date the response covers: the requested start date whenever the request names one, and — for 'all_time', or a custom range starting 0001-01-01, which name none — the date of the earliest transaction matching this call. It is omitted whenever no such date is available: beside empty groups the empty_state envelope explains why; beside non-empty groups the bound was unavailable, never that nothing matched. Divide total_spending by the span from period.start to period.end only for 'week' or 'month', where every matching transaction is in some group. With 'category', 'merchant' or 'account', total_spending sums only the groups RETURNED, not everything matched. Dividing it understates the rate; use group_by='month' or 'week' instead. Drill from a category into its merchants with category_key. Use it for questions like 'where is my money going?'. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_INSIGHTS__COMPARE_SPENDING_PERIODS",+ "name": "Insights compare spending periods",+ "description": "Compare spending between any two time periods side-by-side with pre-computed deltas and percentage changes. Group comparisons by category, merchant, or total. Use for questions like 'am I spending more this month than last?', 'how do my grocery costs compare to last year?', or 'which categories increased the most?'. Automatically warns about partial periods to prevent misleading comparisons. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_INSIGHTS__FORECAST_SPENDING",+ "name": "Insights forecast spending",+ "description": "Estimate how much the user will spend by the end of the current period based on their spending pace so far. Returns: projected end-of-period total, daily spending rate, category-level breakdown with projections, and expected upcoming recurring charges (subscriptions, bills). Use for questions like 'how much will I spend this month?', 'am I on track with my budget?', or 'what recurring charges are coming up?'. The projection is based on current spending patterns and known recurring items — it is an estimate, not a guarantee. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_INSIGHTS__GET_CASH_FLOW",+ "name": "Insights get cash flow",+ "description": "Analyze income, spending, and net cash flow over multiple weeks or months (up to 12 periods) with computed averages. Use for trend questions like 'am I saving more than last quarter?', 'how has my spending changed?', or 'what's my average monthly income?'. Returns pre-computed averages so you can narrate trends directly without doing math. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_INSIGHTS__GET_DAILY_CATEGORY_SPENDING",+ "name": "Insights get daily category spending",+ "description": "Get a per-day, per-category spending breakdown for a calendar month. Returns one row per day-and-category combination with the spending amount, transaction count, and the user's category display name, plus month totals. Use for spending-calendar drill-downs and questions like 'which categories did I spend on each day this month?' or 'break down my daily spending by category'. For per-day totals of spending, income, and bills use insights__get_daily_financial_summary; for ranked category totals over a period use insights__analyze_spending. For the current month, totals apply a same-day rolling cutoff: rows dated after today are still returned but excluded from total_amount and transaction_count. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_INSIGHTS__GET_DAILY_FINANCIAL_SUMMARY",+ "name": "Insights get daily financial summary",+ "description": "Get daily financial calendar for a month. Returns spending, income, bills/recurrences, and net per day, plus month totals and prior-month comparisons. Totals are broken down per currency (keyed by ISO-4217 code in totals_by_currency and each day's by_currency): a user's accounts may span several currencies, which are reported separately and never summed together. Use for calendar heatmaps, daily budgets, cash flow analysis, or questions like 'what did I earn and spend each day this month?'. These are aggregate daily totals, not a row-level transaction list, so they are not subject to the free-plan history window that limits transactions__list_transactions/transactions__search_transactions — a queried month's totals reflect all of that month's activity regardless of plan. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__CONFIRM_OR_REJECT_INFERENCE",+ "name": "Knowledge confirm or reject inference",+ "description": "Confirm or reject a fact that was inferred by the system. Use 'confirm' when the user agrees with an inferred assertion (upgrades confidence to 'confirmed'). Use 'reject' when the user disagrees -- optionally provide a corrected_value with the user's actual answer. Call knowledge__get_financial_context_and_overview first to see inferred assertions that need confirmation."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__DEFER_QUESTION",+ "name": "Knowledge defer question",+ "description": "Skip or snooze an onboarding question. Use 'skip' when the user declines to answer a question (it may be re-surfaced later by the flow engine). Use 'snooze' when the user wants to defer the question for a specific number of days. Call knowledge__get_pending_questions first to discover available question slugs."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__FORGET",+ "name": "Knowledge forget",+ "description": "Retract or delete a previously recorded fact about the user. Use this when the user asks to forget or remove a specific piece of information. The assertion is marked as retracted (not physically deleted) so it appears in the audit history. Call knowledge__get_financial_context_and_overview first to find the slug of the fact to retract."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__GET_FINANCIAL_CONTEXT_AND_OVERVIEW",+ "name": "Knowledge get financial context and overview",+ "description": "Load the user's profile, complete financial snapshot (all account balances, net worth, this month vs. last month income/spending/net, top 5 spending categories), known facts, goals, preferences, and personalization state — all in one call. Typically the first tool called in a session to establish user context. Returns a personalization.guidance_quality field: when not 'ready', personalization.questions_to_unlock_better_guidance contains onboarding questions that improve guidance quality. For additional questions, call knowledge__get_pending_questions. Facts whose structured value carries \"$type\": \"lookup\", \"lookupTarget\": \"connected-accounts\" record the user's intent to source that value from their connected accounts; resolve the current amount against the accounts and totals_by_type arrays in this same response rather than surfacing the raw directive string. Related tools: insights__analyze_spending, transactions__search_transactions, insights__compare_spending_periods for deeper financial analysis. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__GET_PENDING_QUESTIONS",+ "name": "Knowledge get pending questions",+ "description": "Get the next onboarding questions to ask the user. Returns an ordered list of pending questions with each question's slug, display text, answer type, category, constraints, and a suggested_presentation field. Inspect suggested_presentation to decide how to present each question: when 'conversational', ask in natural language -- for single-select and country types, consider using your client's native question/picker tool (e.g., AskUserQuestion) for a better user experience. When 'embedded_ui', call knowledge__show_question_ui to present a visual input control (best for numeric, date, money, multi-select, compound, and scale types). After the user answers, record it via knowledge__remember. Tip: you can offer to extract answers from documents or images the user shares (pay stubs, tax forms, statements), or from facts you already know — not every question needs to be asked directly."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__RECALL_HISTORY",+ "name": "Knowledge recall history",+ "description": "Get the version history of a specific fact about the user. Returns all versions of the assertion including supersessions, retractions, and confirmations. Use this when the user asks how a fact has changed over time or to audit the history of a specific piece of information. Call knowledge__get_financial_context_and_overview first to find assertion slugs."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__REMEMBER",+ "name": "Knowledge remember",+ "description": "Record a fact, preference, goal, or observation about the user. Persistent across sessions and shared with all connected agents. Two modes: (1) prompted -- supply the slug and answer from knowledge__get_pending_questions; category is auto-derived. (2) Ambient -- supply a descriptive slug and category for facts discovered in conversation. Populate exactly one typed value field matching the answer_type, or set use_connected_accounts to source the value from the user's connected financial data."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__RESET_PACK_QUESTIONS",+ "name": "Knowledge reset pack questions",+ "description": "Warning: this cannot be undone — only call when you have high confidence the user wants to reset and re-surface all previously skipped or snoozed questions. This operation reverts all Skipped and Snoozed question states back to Pending so they will be re-surfaced by the flow engine. It does not delete any stored facts or assertions — only the skip/snooze state is reset. Call knowledge__get_pending_questions after a successful reset to obtain the newly re-surfaced questions."+ },+ {+ "slug": "ERA_CONTEXT_MCP_KNOWLEDGE__SHOW_QUESTION_UI",+ "name": "Knowledge show question ui",+ "description": "Present an onboarding question using a visual input control (slider, date picker, multi-select checklist, etc.). Best for answer types that benefit from structured widgets: numeric, date, money, multi-select, compound, and scale. Requires a client that supports MCP Apps embedded UI rendering. If your client is a CLI or terminal without embedded UI support, present the question conversationally or use your client's native question/picker tool instead. Call knowledge__get_pending_questions first to discover available question slugs and check each question's suggested_presentation field. Use this tool when suggested_presentation is 'embedded_ui'. For simple answer types (text, boolean, single-select, country, region), record the answer directly via knowledge__remember."+ },+ {+ "slug": "ERA_CONTEXT_MCP_NURTURE__GET_MY_STATUS",+ "name": "Nurture get my status",+ "description": "Get the caller's own nurture (lifecycle email) campaign enrollment status — which campaigns they are currently enrolled in, their progress through each, and whether they have unsubscribed. Use for questions like 'what emails am I signed up for?' or 'am I subscribed to X?'. Call nurture__set_subscription to change the subscription state for a specific campaign."+ },+ {+ "slug": "ERA_CONTEXT_MCP_NURTURE__SET_SUBSCRIPTION",+ "name": "Nurture set subscription",+ "description": "Subscribe the caller to, or unsubscribe them from, a nurture (lifecycle email) campaign. Takes effect immediately — no confirmation step, and always reversible by calling this tool again with the opposite value. Unsubscribing from a campaign the caller was never enrolled in is a safe no-op. Call nurture__get_my_status first to see the caller's current campaigns and subscription state."+ },+ {+ "slug": "ERA_CONTEXT_MCP_REFERRAL__GET_DASHBOARD_SSO",+ "name": "Referral get dashboard sso",+ "description": "Get a single-use SSO magic link to open the user's Rewardful affiliate dashboard. The link expires after approximately 1 minute and can only be used once. Use when the user wants to view detailed referral reporting, commission history, or manage their affiliate settings."+ },+ {+ "slug": "ERA_CONTEXT_MCP_REFERRAL__GET_REFERRAL_LINK",+ "name": "Referral get referral link",+ "description": "Get the user's referral link if they are enrolled in the referral program. Returns the shareable referral URL and affiliate ID for enrolled users, or indicates the user is not yet enrolled. Users must join the referral program before a link is available."+ },+ {+ "slug": "ERA_CONTEXT_MCP_REFERRAL__GET_REFERRAL_STATS",+ "name": "Referral get referral stats",+ "description": "Get the user's referral performance statistics: visitors, conversions, earned commissions, and pending commissions. Use when the user asks about referral earnings, conversion rates, or how their referrals are performing."+ },+ {+ "slug": "ERA_CONTEXT_MCP_REFERRAL__JOIN_REFERRAL_PROGRAM",+ "name": "Referral join referral program",+ "description": "Join the referral program by creating a Rewardful affiliate for the authenticated user. Returns the shareable referral URL and affiliate ID on success. Use when the user wants to start referring others and earning commissions."+ },+ {+ "slug": "ERA_CONTEXT_MCP_REFERRAL__SWITCH_REFERRAL_CAMPAIGN",+ "name": "Referral switch referral campaign",+ "description": "Move the user's referral programme onto a different track. Rewardful allows one affiliate per email, so this reassigns their existing affiliate rather than creating a second one — the user must already have joined (referral__join_referral_program) or this returns an error. Two destinations accept members: 'friends-family-usd' pays a fixed reward for each friend who subscribes, in the currency that user is billed in, and 'creator' pays 30% recurring commission for 12 months on each referred subscription. Naming 'friends-family-usd' selects the track only — the server assigns the campaign paying the user's own settled currency and the response reports the slug actually assigned, so read the currency off the result rather than off the request. Any other slug, including a campaign the deployment has retired, is refused with the list of destinations that would have worked."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__IMPORT_CSV_TRANSACTIONS",+ "name": "Transactions import csv transactions",+ "description": "Import transactions from inline CSV text into a manual account. Supports auto-detection of common formats or explicit format hints. Partial-success semantics: rows that fail validation are reported individually. Set preview_only=true to validate without importing. PROTOCOL — before calling, do the categorisation work up front so the CSV you submit is already aligned with the user's category landscape: (1) call accounts__list_financial_accounts to obtain the account_group_key for the target manual account; (2) call transactions__list_spending_categories to enumerate the user's effective categories — both system and custom (Origin=\"user\"); (3) inspect the source CSV header to see whether it carries a category column; (4) when you write the CSV content into csv_content, set the Category column on each row to text that maps cleanly onto the categories surfaced in step 2. Composing the CSV deliberately at submission time keeps the import deterministic and avoids a follow-up cleanup pass. A plan may limit reads to a rolling recent window of history. When that limit applies to this caller, a transaction dated before the window is still stored and syncs normally — the write is never blocked, delayed, or rejected by the window. It simply will not appear in transactions__list_transactions/transactions__search_transactions results until the plan is upgraded or the date rolls back into the window. The response signals when this applies to a specific transaction and, whenever the window could be confirmed, leads that signal with the date visible history starts — relay that date rather than only the fact of exclusion."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__LIST_RECURRING_CHARGES",+ "name": "Transactions list recurring charges",+ "description": "List detected recurring transactions — subscriptions (Netflix, Spotify), bills (rent, utilities), and regular income (salary, freelance) — with estimated monthly amounts, frequency, and last-seen date. Includes monthly totals by type. Use for questions like 'what subscriptions am I paying for?', 'how much are my fixed monthly expenses?', or 'what’s my regular income?'. This is detected pattern metadata (the FirstSeen/LastSeen dates that identify a recurrence), not a row-level transaction list, so it is not subject to the free-plan history window that limits transactions__list_transactions/transactions__search_transactions. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__LIST_SPENDING_CATEGORIES",+ "name": "Transactions list spending categories",+ "description": "List all available spending categories organized in a parent/child hierarchy (e.g., 'Daily living' contains 'Groceries', 'Dining out', etc.). Each category has a unique key (the key field) that you MUST use when assigning categories via transactions__update_transactions or transactions__manage_automation_rules. Call this tool first whenever you need to categorize a transaction or create a rule with a set_category action — do not guess category keys."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__LIST_TRANSACTIONS",+ "name": "Transactions list transactions",+ "description": "List recent transactions with pagination, optionally filtered by account and date range. Returns merchant name, amount, category, and pending status for each transaction. Best for browsing recent activity or getting a chronological view. For targeted lookups (e.g. 'find my Amazon charges'), prefer transactions__search_transactions instead. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. A plan may limit reads to a rolling recent window of history; when that limit applies to this caller, older transactions outside the window are not returned even when explicitly requested by date. The response signals whenever the window clamped the results (history_window_applied) and then carries the date visible history starts (history_window_floor_date), how far back matching activity actually exists (history_window_earliest_date), and how many older transactions were withheld (history_window_hidden_count) — lead with the dates when relaying this, so the user learns how far their history really goes rather than only that some rows are missing. The earliest date and the count are each omitted when unknown (absent is NOT zero), and both are scoped to THIS request's own filters (account, category, search, date range), i.e. what was withheld from THIS query, not an account-wide total. So an empty or shortened result set does not necessarily mean no matching transactions ever existed — upgrading the plan reveals full history immediately. When the window clamped results AND the caller's plan was confirmed, the response also carries a structured upgrade affordance (history_window_upsell) naming the plan that unlocks the hidden history and the tool to call to upgrade — relay it to offer the user a concrete next step. If the plan could not be confirmed at read time (a transient fail-closed clamp that may have affected a paid caller), history_window_upsell is omitted; the response instead carries a warning that the history window could not be confirmed and to retry shortly — relay that caveat and do NOT attribute the clamp to the caller's plan. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__MANAGE_AUTOMATION_RULES",+ "name": "Transactions manage automation rules",+ "description": "Create and manage automation rules that automatically organize the user's transactions. Transaction-scope rules evaluate filters against each individual transaction as it arrives. Pattern-scope rules evaluate a pattern specification against a time-windowed batch of transactions to detect cross-transaction patterns such as transfers, recurring charges, spending anomalies, and frequency thresholds. Transaction-scope rules watch for transactions matching conditions you define (by merchant name, amount, category, tags, transaction type, date, or combinations using and/or/not logic) and then perform actions like assigning a category, adding/removing tags, renaming the merchant, hiding the transaction, flagging for review, updating the description, or marking as a transfer. Pattern-scope rules require a pattern_spec object and window_days parameter. Library pattern rules (like Transfer Detection, Recurring Detection, and Anomaly Detection) are created automatically and cannot be deleted, but you can enable, disable, or tune their behavior via user_overrides on update. Use the preview action to test filters or pattern specs against historical data before committing. BEFORE creating rules: call transactions__list_spending_categories to get category keys for set_category actions, and call transactions__manage_transaction_tags with list_tags to get tag keys for tag-related actions or filters. AFTER creating rules: the user's existing transactions are updated immediately by default (apply_retroactively defaults to true), and all future matching transactions will be processed automatically."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__MANAGE_CATEGORIES",+ "name": "Transactions manage categories",+ "description": "Create, rename, hide, unhide, delete, or merge spending categories. Display mutations (rename, emoji, description, spending type) of system categories are free on all plans. Custom category limits per plan — Context Basic (free): 2, Context Organize: 10, Context Automate: 50, Context Optimize: 100, Context Operate: 300. Use transactions__list_spending_categories first to get current category keys. When creating a category, provide a URL-safe slug (lowercase, hyphens allowed, 2-50 chars) and a parent category key under which to place it."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__MANAGE_MANUAL_TRANSACTION",+ "name": "Transactions manage manual transaction",+ "description": "Batch-manage transactions on a manually tracked account. Send an array of operations (create, update, delete) in a single call — ideal for bulk imports. All operations share one account_group_key and are processed sequentially with partial-success semantics. Set preview_only=true to validate without writing. Use accounts__list_financial_accounts to obtain the account_group_key, and transactions__list_transactions to obtain the transaction_group_key. Before creating transactions, call transactions__list_spending_categories to obtain a valid category_key (fcat_xxx format). A plan may limit reads to a rolling recent window of history. When that limit applies to this caller, a transaction dated before the window is still stored and syncs normally — the write is never blocked, delayed, or rejected by the window. It simply will not appear in transactions__list_transactions/transactions__search_transactions results until the plan is upgraded or the date rolls back into the window. The response signals when this applies to a specific transaction and, whenever the window could be confirmed, leads that signal with the date visible history starts — relay that date rather than only the fact of exclusion."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__MANAGE_TRANSACTION_TAGS",+ "name": "Transactions manage transaction tags",+ "description": "Create, list, update, or delete tags, and attach or detach them from transactions. Tags are custom labels the user attaches to transactions for organizing expenses by project, trip, goal, or any personal grouping (e.g., 'Vacation 2026', 'Tax Deductible', 'Side Project'). Use this tool when the user wants to create a new tag, see existing tags, or tag specific transactions. After creating a tag, attach it to specific transactions with the 'assign_tags' action (and detach with 'remove_tags'), or set up a rule to auto-tag matching transactions using transactions__manage_automation_rules."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__MANAGE_TRANSFER_LINKS",+ "name": "Transactions manage transfer links",+ "description": "List, confirm, or reject detected transfer links between the user's accounts. Transfer links are automatically detected when matching debit/credit transactions appear across different accounts (exact or near-match amounts within 3%). Use 'list' to see all detected transfers. Use 'confirm' when the user verifies a detected transfer is correct (upgrades confidence to 100%). Use 'reject' when a detected transfer is a false positive (removes the link and prevents re-detection). Transfer-tagged transactions are automatically excluded from spending and income analytics to prevent double-counting."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__SEARCH_TRANSACTIONS",+ "name": "Transactions search transactions",+ "description": "Search and filter transactions by merchant name, description, amount range, date range, and direction (debit/credit). Returns matching transactions with total count and sum — no arithmetic needed. Use for targeted questions like 'how much did I spend at Starbucks?', 'what was that $50 charge?', or 'show me all refunds this month'. Supports free-text search so exact merchant names are not required — but free-text does NOT match category names. To filter by category, first call transactions__list_spending_categories to resolve the category to its fcat_* key, then pass that key as category_key (set include_children=true to also include its subcategories). For browsing recent activity chronologically, prefer transactions__list_transactions instead. Results include only posted/settled transactions; pending (authorization-hold) transactions are excluded. A plan may limit reads to a rolling recent window of history; when that limit applies to this caller, older transactions outside the window are not returned even when explicitly requested by date. The response signals whenever the window clamped the results (history_window_applied) and then carries the date visible history starts (history_window_floor_date), how far back matching activity actually exists (history_window_earliest_date), and how many older transactions were withheld (history_window_hidden_count) — lead with the dates when relaying this, so the user learns how far their history really goes rather than only that some rows are missing. The earliest date and the count are each omitted when unknown (absent is NOT zero), and both are scoped to THIS request's own filters (account, category, search, date range), i.e. what was withheld from THIS query, not an account-wide total. So an empty or shortened result set does not necessarily mean no matching transactions ever existed — upgrading the plan reveals full history immediately. When the window clamped results AND the caller's plan was confirmed, the response also carries a structured upgrade affordance (history_window_upsell) naming the plan that unlocks the hidden history and the tool to call to upgrade — relay it to offer the user a concrete next step. If the plan could not be confirmed at read time (a transient fail-closed clamp that may have affected a paid caller), history_window_upsell is omitted; the response instead carries a warning that the history window could not be confirmed and to retry shortly — relay that caveat and do NOT attribute the clamp to the caller's plan. When a result — or a section of it — is empty, the response carries an empty_state envelope (kind, reason, next_step; multi-section responses instead use section-scoped variants such as accounts_empty_state) giving the authoritative reason it is empty and the recovery action. Read that envelope for the reason rather than inferring one — do not assume data is still syncing or settling. The response may also carry a top-level warnings array flagging data-health caveats (e.g. a connection to reconnect, or an unconfirmed check to retry); relay those caveats too. Session context from knowledge__get_financial_context_and_overview enriches these results with the user's profile, goals, and preferences."+ },+ {+ "slug": "ERA_CONTEXT_MCP_TRANSACTIONS__UPDATE_TRANSACTIONS",+ "name": "Transactions update transactions",+ "description": "Update the category, merchant name, description, or review status on one or more transactions. The user's changes take priority over automatically detected values. BEFORE calling: use transactions__list_transactions or transactions__search_transactions to get transaction IDs, and call transactions__list_spending_categories to get valid category keys if changing the category. Use the clear_ options to undo a previous manual change and revert to the original value. For bulk automatic updates based on conditions, use transactions__manage_automation_rules instead."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "era_context_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "mcp:discovery,mcp:tools-basic,mcp:tools-write,mcp:billing-write,mcp:resources-read,offline_access,banking:read,banking:write,brokerage:read,brokerage:write,social:read,social:write"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "eranol","name": "Eranol",@@ -188886,7 +193375,7 @@],"toolCount": 54,"triggerCount": 0,- "version": "20260828_00",+ "version": "20260908_00","tools": [{"slug": "EXCEL_ADD_CHART",@@ -189320,6 +193809,97 @@}]},+ {+ "slug": "explorium",+ "name": "Explorium",+ "logo": "https://logos.composio.dev/api/explorium",+ "description": "Explorium AgentSource provides company and prospect discovery, matching, enrichment, research, and usage management through its REST API.",+ "category": "ai sales tools",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "EXPLORIUM_AUTOCOMPLETE_FILTER_VALUES",+ "name": "Autocomplete Filter Values",+ "description": "Find normalized values for Explorium business and prospect search filters, including company names, job titles, industries, locations, skills, and interests. Live trial calls consumed zero credits."+ },+ {+ "slug": "EXPLORIUM_ENRICH_BUSINESS_FIRMOGRAPHICS",+ "name": "Enrich Business Firmographics",+ "description": "Enrich 1-50 Explorium business IDs with company firmographics. This call is credit-metered: a live trial probe charged exactly one credit for one submitted business. Check EXPLORIUM_GET_CREDIT_BALANCE first; the response reports the actual credit usage for the call."+ },+ {+ "slug": "EXPLORIUM_GET_AUDIENCE_STATS",+ "name": "Get Audience Stats",+ "description": "Return aggregate distributions and total counts for either a business or prospect filter set before fetching records. Empty business filters were live-tested at zero credits; usage is still reported."+ },+ {+ "slug": "EXPLORIUM_GET_CREDIT_BALANCE",+ "name": "Get Credit Balance",+ "description": "Return the connected Explorium company's allocated and remaining credits and trial or paid account type. Use before full searches, enrichments, or other potentially metered calls."+ },+ {+ "slug": "EXPLORIUM_GET_JOB_STATUS",+ "name": "Get Job Status",+ "description": "Get detailed status, timing, credit usage, errors, and downloadable CSV result metadata for one existing Explorium job. Invalid IDs may produce a provider 500 instead of 404."+ },+ {+ "slug": "EXPLORIUM_LIST_JOBS",+ "name": "List Jobs",+ "description": "List existing Explorium asynchronous jobs, optionally filtered by lifecycle status, and return their IDs for detailed monitoring. This does not create or cancel jobs."+ },+ {+ "slug": "EXPLORIUM_MATCH_BUSINESSES",+ "name": "Match Businesses",+ "description": "Resolve 1-50 business names, domains, URLs, or LinkedIn URLs to Explorium business IDs while preserving input order. The provider reports credit usage for every call; a one-record trial call consumed zero credits."+ },+ {+ "slug": "EXPLORIUM_MATCH_PROSPECTS",+ "name": "Match Prospects",+ "description": "Resolve 1-50 people from names, employers, email, phone, LinkedIn URL, or Explorium business ID to prospect IDs while preserving input order. A live one-record trial call used zero credits; returned usage is included."+ },+ {+ "slug": "EXPLORIUM_SEARCH_BUSINESSES",+ "name": "Search Businesses",+ "description": "Search Explorium businesses with structured filters and cursor pagination. Preview mode is the zero-credit default observed on the trial account; full mode may consume credits, so check EXPLORIUM_GET_CREDIT_BALANCE first."+ },+ {+ "slug": "EXPLORIUM_SEARCH_PROSPECTS",+ "name": "Search Prospects",+ "description": "Search Explorium prospects with strict person and employer filters, returning one cursor-paginated page. Preview is the zero-credit default observed on the trial account; full mode may consume credits."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "explorium_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "AgentSource API Key",+ "type": "string",+ "description": "Your company-level AgentSource API key. In the Explorium Admin Portal at https://admin.explorium.ai, open Access & Authentication, then Getting Your API Key, and copy the key. Explorium shares one key among company users and uses it for billing, so keep it secret.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "explorium_mcp","name": "Explorium MCP",@@ -192650,6 +197230,62 @@}]},+ {+ "slug": "finlight",+ "name": "Finlight",+ "logo": "https://logos.composio.dev/api/finlight",+ "description": "Search Finlight's financial news, retrieve articles by link, and list source metadata through its complete v2 REST API surface.",+ "category": "news & lifestyle",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 3,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "FINLIGHT_GET_ARTICLE_BY_LINK",+ "name": "Get Article by Link",+ "description": "Retrieve one Finlight-indexed article by its original URL. Optional full content and company entities are plan-gated and may be silently absent even when the request succeeds."+ },+ {+ "slug": "FINLIGHT_LIST_SOURCES",+ "name": "List Sources",+ "description": "List all news source domains visible to the connected Finlight account, including default-source status, origin country, and supported languages."+ },+ {+ "slug": "FINLIGHT_SEARCH_ARTICLES",+ "name": "Search Articles",+ "description": "Search Finlight's indexed financial news using text, market, source, geography, category, language, and date filters. Returns one page at a time. Availability, recency, content, and entity enrichment depend on the connected plan and may be silently omitted."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "finlight_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Your Finlight API key. Sign in at https://app.finlight.me, open the API Keys section of the dashboard, and copy an active key. Finlight sends this secret in the X-API-KEY header for REST requests.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "finmei","name": "Finmei",@@ -196758,6 +201394,52 @@}]},+ {+ "slug": "formilla",+ "name": "Formilla",+ "logo": "https://logos.composio.dev/api/formilla",+ "description": "Create or update customer contacts through Formilla's Secure Token REST API for live chat and marketing automation workflows.",+ "category": "customer support",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 1,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "FORMILLA_UPSERT_CONTACT",+ "name": "Upsert Contact",+ "description": "Create a Formilla contact or overwrite supplied fields on an existing contact matched by user ID first, then email. Returns no contact data, ID, or create-versus-update result."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "formilla_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "Secure Token",+ "type": "string",+ "description": "Log in to Formilla as the Account Owner, open Settings > Security, enable REST API Enabled, and copy the generated Secure Token. If needed, use Create New Token on that page; generating a replacement invalidates the token used by existing integrations. This is not the JavaScript Secure Key or the Zapier API key.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "fraudlabs_pro","name": "FraudLabs Pro",@@ -198356,6 +203038,132 @@}]},+ {+ "slug": "geekflare",+ "name": "Geekflare",+ "logo": "https://logos.composio.dev/api/geekflare",+ "description": "Geekflare provides APIs for web scraping, search, website testing, DNS and network diagnostics, and security scans.",+ "category": "developer tools",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 17,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "GEEKFLARE_CAPTURE_SCREENSHOT",+ "name": "Capture Website Screenshot",+ "description": "Capture a webpage or selected element as PNG, JPEG, or WebP with viewport and rendering controls. This is credit-heavy at 5 credits per successful run; proxy_country uses the paid Premium Proxy add-on and additional credits."+ },+ {+ "slug": "GEEKFLARE_CHECK_BROKEN_LINKS",+ "name": "Check Broken Links",+ "description": "Scan one webpage for links that return errors. Costs 2 credits; proxy_country uses the paid Premium Proxy add-on."+ },+ {+ "slug": "GEEKFLARE_CHECK_DNSSEC",+ "name": "Check DNSSEC",+ "description": "Check whether DNSSEC is enabled and validating for a domain, including DNSKEY and RRSIG records. Observed Free cost is 1 credit."+ },+ {+ "slug": "GEEKFLARE_CHECK_MIXED_CONTENT",+ "name": "Check Mixed Content",+ "description": "Scan an HTTPS page for insecure HTTP images, scripts, stylesheets, and other mixed content. Observed Free cost is 2 credits; proxy_country uses the paid Premium Proxy add-on."+ },+ {+ "slug": "GEEKFLARE_CHECK_SITE_STATUS",+ "name": "Check Site Status",+ "description": "Check whether a website is reachable and return the target site's HTTP status. Costs 1 credit; proxy_country uses the paid Premium Proxy add-on."+ },+ {+ "slug": "GEEKFLARE_CONVERT_URL_TO_PDF",+ "name": "Convert URL to PDF",+ "description": "Render a webpage into a downloadable PDF with paper, orientation, margin, and scale controls. This is credit-heavy at 5 credits per successful run; proxy_country uses the paid Premium Proxy add-on and additional credits."+ },+ {+ "slug": "GEEKFLARE_LOOKUP_DNS_RECORDS",+ "name": "Look Up DNS Records",+ "description": "Retrieve A, AAAA, CNAME, MX, CAA, NS, SOA, SRV, and TXT records for a domain. Costs 1 credit per successful run."+ },+ {+ "slug": "GEEKFLARE_MEASURE_LOAD_TIME",+ "name": "Measure Page Load Time",+ "description": "Measure browser page-load time from Geekflare's default location for 1 credit. Optionally compare additional countries, but setting target_countries is credit-heavy and costs 8 credits total for the run. proxy_country uses the paid Premium Proxy add-on."+ },+ {+ "slug": "GEEKFLARE_PING_HOST",+ "name": "Ping Host",+ "description": "Send ICMP pings to a domain or IP address and return latency, packet-loss, and round-trip statistics. Costs 2 credits per successful run."+ },+ {+ "slug": "GEEKFLARE_RUN_LIGHTHOUSE_AUDIT",+ "name": "Run Lighthouse Audit",+ "description": "Run a Google Lighthouse audit for performance, SEO, accessibility, and best practices. This credit-heavy endpoint costs 10 credits per successful run; proxy_country uses the paid Premium Proxy add-on and additional credits."+ },+ {+ "slug": "GEEKFLARE_RUN_MTR",+ "name": "Run MTR Network Diagnostic",+ "description": "Run MTR to report packet loss and latency at each network hop between Geekflare and a target. Observed Free cost is 2 credits; proxy_country uses the paid Premium Proxy add-on."+ },+ {+ "slug": "GEEKFLARE_SCAN_OPEN_PORTS",+ "name": "Scan Open Ports",+ "description": "Scan a domain or IP address for open TCP ports using a common-port set, custom ranges, or Geekflare's default top 100 ports. Costs 2 credits per successful run."+ },+ {+ "slug": "GEEKFLARE_SCAN_TLS",+ "name": "Scan TLS Configuration",+ "description": "Inspect a domain's TLS protocols, cipher suites, and certificate details. Costs 1 credit per successful run."+ },+ {+ "slug": "GEEKFLARE_SCRAPE_PAGE_METADATA",+ "name": "Scrape Page Metadata",+ "description": "Extract meta tags, Open Graph fields, Twitter Card fields, canonical URLs, and images from a webpage. Base cost is 2 credits per successful run; proxy_country opts into the paid Premium Proxy add-on and additional credits."+ },+ {+ "slug": "GEEKFLARE_SCRAPE_WEBPAGE",+ "name": "Scrape Webpage",+ "description": "Fetch webpage content as HTML, Markdown, JSON, or text, with optional browser rendering, selector extraction, and AI analysis. Base cost is 1 credit; ai_prompt adds 6 credits, and proxy modes use the paid Premium Proxy add-on."+ },+ {+ "slug": "GEEKFLARE_SEARCH_INTERNET",+ "name": "Search the Internet",+ "description": "Search web pages, news, or images with domain, category, location, and time filters. A base search costs 2 credits. Scraping result URLs and synthesizing a grounded answer are opt-in, credit-heavy enhancements and default off."+ },+ {+ "slug": "GEEKFLARE_TRACE_REDIRECTS",+ "name": "Trace URL Redirects",+ "description": "Trace every redirect hop, status code, and final destination for a URL. Costs 1 credit; proxy_country uses the paid Premium Proxy add-on."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "geekflare_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Your Geekflare API key. Sign in at https://dash.geekflare.com/ and copy the API key generated for your account or workspace. Geekflare currently provides one active key per account, so keep it secret.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "gelato","name": "Gelato",@@ -198474,7 +203282,7 @@],"toolCount": 8,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260902_00","tools": [{"slug": "GEMINI_COUNT_TOKENS",@@ -199251,6 +204059,1161 @@}]},+ {+ "slug": "getresponse",+ "name": "GetResponse",+ "logo": "https://logos.composio.dev/api/getresponse",+ "description": "Manage GetResponse email marketing, contacts, campaigns, automation, ecommerce, and account resources.",+ "category": "marketing automation",+ "authSchemes": [+ "API_KEY",+ "OAUTH2"+ ],+ "toolCount": 213,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "GETRESPONSE_CANCEL_AB_TEST",+ "name": "Cancel A/B test",+ "description": "Schedule cancellation of an A/B test."+ },+ {+ "slug": "GETRESPONSE_CANCEL_NEWSLETTER_SEND",+ "name": "Cancel sending the newsletter",+ "description": "Cancel newsletter sending and turn the newsletter into a draft."+ },+ {+ "slug": "GETRESPONSE_CREATE_ADDRESS",+ "name": "Create address",+ "description": "Create an address in the connected GetResponse account."+ },+ {+ "slug": "GETRESPONSE_CREATE_AND_SEND_NEWSLETTER",+ "name": "Create and send newsletter",+ "description": "Create a newsletter and immediately queue delivery, or schedule it when send_settings.sendOn is supplied. GetResponse limits this endpoint to 256 calls per day."+ },+ {+ "slug": "GETRESPONSE_CREATE_AUTORESPONDER",+ "name": "Create autoresponder",+ "description": "Create an autoresponder that automatically delivers its message when the configured trigger and timing conditions are met."+ },+ {+ "slug": "GETRESPONSE_CREATE_CAMPAIGN",+ "name": "Create campaign",+ "description": "Create a campaign (contact list); configured double opt-in can automatically send confirmation emails, and subscription notifications can alert configured recipients."+ },+ {+ "slug": "GETRESPONSE_CREATE_CART",+ "name": "Create cart",+ "description": "Create a cart with its selected product variants."+ },+ {+ "slug": "GETRESPONSE_CREATE_CATEGORY",+ "name": "Create category",+ "description": "Create a shop category; setting is_default makes it the shop's default category and changes the previous default."+ },+ {+ "slug": "GETRESPONSE_CREATE_CONTACT",+ "name": "Create a new contact",+ "description": "Submit a contact for asynchronous creation in a campaign. GetResponse returns no contact ID; use LIST_CONTACTS with the email filter to find the contact after processing."+ },+ {+ "slug": "GETRESPONSE_CREATE_CONTACTS_BATCH",+ "name": "Create multiple contacts at once",+ "description": "Submit multiple contacts for asynchronous creation in one campaign. GetResponse returns no contact IDs; use LIST_CONTACTS after processing to find accepted contacts."+ },+ {+ "slug": "GETRESPONSE_CREATE_CUSTOM_EVENT",+ "name": "Create a custom event",+ "description": "Create a custom event definition with typed attributes."+ },+ {+ "slug": "GETRESPONSE_CREATE_CUSTOM_FIELD",+ "name": "Create a custom field",+ "description": "Create a custom field definition."+ },+ {+ "slug": "GETRESPONSE_CREATE_CUSTOM_REPORT",+ "name": "Create the custom report",+ "description": "Schedule a one-time custom report. Requires a paid custom-reports entitlement, and available report types depend on the pricing plan."+ },+ {+ "slug": "GETRESPONSE_CREATE_FILE",+ "name": "Create a file",+ "description": "Create a File Library file from base64-encoded content."+ },+ {+ "slug": "GETRESPONSE_CREATE_FOLDER",+ "name": "Create a folder",+ "description": "Create a File Library folder."+ },+ {+ "slug": "GETRESPONSE_CREATE_FROM_ADDRESS",+ "name": "Create 'From' address",+ "description": "Create a GetResponse sender name and email address."+ },+ {+ "slug": "GETRESPONSE_CREATE_IMPORT",+ "name": "Create a contact import",+ "description": "Start an asynchronous contact import into a campaign."+ },+ {+ "slug": "GETRESPONSE_CREATE_META_FIELD",+ "name": "Create meta field",+ "description": "Create a meta field in a shop."+ },+ {+ "slug": "GETRESPONSE_CREATE_NEWSLETTER_DRAFT",+ "name": "Create newsletter draft",+ "description": "Create a newsletter draft without sending or scheduling delivery. GetResponse requires send_settings but stores the message as a draft."+ },+ {+ "slug": "GETRESPONSE_CREATE_ORDER",+ "name": "Create order",+ "description": "Create an ecommerce order and trigger matching Make a purchase workflows unless additional_flags is skipAutomation."+ },+ {+ "slug": "GETRESPONSE_CREATE_PREDEFINED_FIELD",+ "name": "Create a predefined field",+ "description": "Create a campaign-specific predefined field in GetResponse."+ },+ {+ "slug": "GETRESPONSE_CREATE_PRODUCT",+ "name": "Create product",+ "description": "Create a product and its nested ecommerce data in a shop."+ },+ {+ "slug": "GETRESPONSE_CREATE_PRODUCT_VARIANT",+ "name": "Create product variant",+ "description": "Create a product variant with images, meta fields, and taxes."+ },+ {+ "slug": "GETRESPONSE_CREATE_RSS_NEWSLETTER",+ "name": "Create RSS newsletter",+ "description": "Create and configure an RSS-to-email newsletter, which can deliver new feed content when enabled. Requires the RSS email-marketing entitlement."+ },+ {+ "slug": "GETRESPONSE_CREATE_SAVED_CONTACT_SEARCH",+ "name": "Create search contacts",+ "description": "Create a saved contact search from condition sections."+ },+ {+ "slug": "GETRESPONSE_CREATE_SHOP",+ "name": "Create shop",+ "description": "Create an ecommerce shop."+ },+ {+ "slug": "GETRESPONSE_CREATE_SUBJECT_AB_TEST",+ "name": "Create a subject A/B test",+ "description": "Create a subject-line A/B test with two to five variants and start or schedule delivery to its selected recipients."+ },+ {+ "slug": "GETRESPONSE_CREATE_SUPPRESSION",+ "name": "Create a suppression list",+ "description": "Create a new suppression list."+ },+ {+ "slug": "GETRESPONSE_CREATE_TAG",+ "name": "Add a new tag",+ "description": "Add a new tag."+ },+ {+ "slug": "GETRESPONSE_CREATE_TAX",+ "name": "Create tax",+ "description": "Create a tax for a shop."+ },+ {+ "slug": "GETRESPONSE_CREATE_TRANSACTIONAL_EMAIL_TEMPLATE",+ "name": "Create transactional email template",+ "description": "Create a reusable transactional email template."+ },+ {+ "slug": "GETRESPONSE_DELETE_AB_TEST",+ "name": "Delete A/B test",+ "description": "Delete an A/B test."+ },+ {+ "slug": "GETRESPONSE_DELETE_ADDRESS",+ "name": "Delete address",+ "description": "Delete an existing GetResponse account address."+ },+ {+ "slug": "GETRESPONSE_DELETE_AUTORESPONDER",+ "name": "Delete autoresponder",+ "description": "Permanently delete an autoresponder."+ },+ {+ "slug": "GETRESPONSE_DELETE_CART",+ "name": "Delete cart",+ "description": "Delete a cart from a shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_CATEGORY",+ "name": "Delete category",+ "description": "Delete a category from a shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_CONTACT",+ "name": "Delete a contact by contact ID",+ "description": "Permanently remove a contact; when message_id is supplied, record the removal as an unsubscribe from that message, optionally with the source IP address."+ },+ {+ "slug": "GETRESPONSE_DELETE_CUSTOM_EVENT",+ "name": "Delete a custom event",+ "description": "Delete a custom event definition by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_CUSTOM_FIELD",+ "name": "Delete a custom field",+ "description": "Delete a custom field definition by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_FILE",+ "name": "Delete file by file ID",+ "description": "Permanently delete a File Library file by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_FOLDER",+ "name": "Delete folder by folder ID",+ "description": "Permanently delete a File Library folder by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_FROM_ADDRESS",+ "name": "Delete 'From' address",+ "description": "Delete a GetResponse 'From' address, optionally replacing its references with another address."+ },+ {+ "slug": "GETRESPONSE_DELETE_META_FIELD",+ "name": "Delete meta field",+ "description": "Delete a meta field from a shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_NEWSLETTER",+ "name": "Delete newsletter",+ "description": "Delete a newsletter by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_ORDER",+ "name": "Delete order",+ "description": "Delete an order from a shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_PREDEFINED_FIELD",+ "name": "Delete a predefined field",+ "description": "Delete an existing GetResponse predefined field."+ },+ {+ "slug": "GETRESPONSE_DELETE_PRODUCT",+ "name": "Delete product",+ "description": "Delete a product from a shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_PRODUCT_VARIANT",+ "name": "Delete product variant",+ "description": "Delete a product variant."+ },+ {+ "slug": "GETRESPONSE_DELETE_RSS_NEWSLETTER",+ "name": "Delete RSS newsletter",+ "description": "Permanently delete an RSS newsletter."+ },+ {+ "slug": "GETRESPONSE_DELETE_SAVED_CONTACT_SEARCH",+ "name": "Delete search contacts",+ "description": "Delete a saved contact search."+ },+ {+ "slug": "GETRESPONSE_DELETE_SHOP",+ "name": "Delete shop",+ "description": "Delete an ecommerce shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_SUPPRESSION",+ "name": "Delete a suppression list",+ "description": "Delete a suppression list by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_TAG",+ "name": "Delete tag by ID",+ "description": "Delete a tag by ID."+ },+ {+ "slug": "GETRESPONSE_DELETE_TAX",+ "name": "Delete tax by ID",+ "description": "Delete a tax from a shop."+ },+ {+ "slug": "GETRESPONSE_DELETE_TRANSACTIONAL_EMAIL_TEMPLATE",+ "name": "Delete transactional email template",+ "description": "Permanently delete a transactional email template."+ },+ {+ "slug": "GETRESPONSE_DISABLE_CALLBACKS",+ "name": "Disable callbacks",+ "description": "Disable all account-wide callbacks. Returns success=true for HTTP 204."+ },+ {+ "slug": "GETRESPONSE_GET_AB_TEST",+ "name": "Get a single A/B test",+ "description": "Get a single A/B test by ID."+ },+ {+ "slug": "GETRESPONSE_GET_ACCOUNT",+ "name": "Account information",+ "description": "Return information about the connected GetResponse account."+ },+ {+ "slug": "GETRESPONSE_GET_ACCOUNT_BADGE",+ "name": "Current status of your GetResponse badge",+ "description": "Return the current GetResponse badge status."+ },+ {+ "slug": "GETRESPONSE_GET_ACCOUNT_BILLING",+ "name": "Billing information",+ "description": "Return billing, plan, allowance, payment, and add-on information."+ },+ {+ "slug": "GETRESPONSE_GET_ACCOUNT_BLOCKLIST",+ "name": "Returns account blocklist masks",+ "description": "Returns account blocklist masks."+ },+ {+ "slug": "GETRESPONSE_GET_ADDRESS",+ "name": "Get an address by ID",+ "description": "Get one GetResponse account address by its ID."+ },+ {+ "slug": "GETRESPONSE_GET_AUTORESPONDER",+ "name": "Get autoresponder",+ "description": "Get one autoresponder and its delivery and trigger settings."+ },+ {+ "slug": "GETRESPONSE_GET_AUTORESPONDER_STATISTICS",+ "name": "Get autoresponder statistics",+ "description": "Return one page of delivery statistics for one autoresponder."+ },+ {+ "slug": "GETRESPONSE_GET_AUTORESPONDER_THUMBNAIL",+ "name": "Get autoresponder thumbnail",+ "description": "Download an autoresponder thumbnail image."+ },+ {+ "slug": "GETRESPONSE_GET_CALLBACK_CONFIGURATION",+ "name": "Get callbacks configuration",+ "description": "Return whether account-wide callbacks are configured, plus their URL and enabled event types when configured."+ },+ {+ "slug": "GETRESPONSE_GET_CAMPAIGN",+ "name": "Get campaign",+ "description": "Get a campaign (contact list) by its campaign ID."+ },+ {+ "slug": "GETRESPONSE_GET_CAMPAIGN_BLOCKLIST",+ "name": "Get campaign blocklist",+ "description": "Return the blocklist masks configured for a campaign (contact list)."+ },+ {+ "slug": "GETRESPONSE_GET_CAMPAIGN_STATISTICS",+ "name": "Get campaign statistics",+ "description": "Get one of six campaign metrics: subscriber origins, locations, list size, subscriptions, removals, or subscription-removal balance."+ },+ {+ "slug": "GETRESPONSE_GET_CAMPAIGN_STATISTICS_SUMMARY",+ "name": "Get campaign statistics summary",+ "description": "Get subscriber, newsletter, trigger, landing-page, and webform totals by campaign."+ },+ {+ "slug": "GETRESPONSE_GET_CART",+ "name": "Get cart by ID",+ "description": "Get a cart and its selected variants by ID."+ },+ {+ "slug": "GETRESPONSE_GET_CATEGORY",+ "name": "Get a single category by ID",+ "description": "Get a category by shop ID and category ID."+ },+ {+ "slug": "GETRESPONSE_GET_CLICK_TRACK",+ "name": "Get click tracked link details",+ "description": "Get click tracked link details by click-track ID."+ },+ {+ "slug": "GETRESPONSE_GET_CONTACT",+ "name": "Get contact details by contact ID",+ "description": "Get contact details by contact ID."+ },+ {+ "slug": "GETRESPONSE_GET_CUSTOM_EVENT",+ "name": "Get a custom event by ID",+ "description": "Get a custom event definition by ID."+ },+ {+ "slug": "GETRESPONSE_GET_CUSTOM_FIELD",+ "name": "Get a custom field",+ "description": "Get a custom field definition by ID."+ },+ {+ "slug": "GETRESPONSE_GET_CUSTOM_REPORT",+ "name": "Get a single custom report by ID",+ "description": "Get custom report status and generated files by ID. Requires a paid plan with custom reports."+ },+ {+ "slug": "GETRESPONSE_GET_ECOMMERCE_PERFORMANCE",+ "name": "Get the ecommerce general performance statistics",+ "description": "Get aggregate ecommerce order and revenue performance statistics."+ },+ {+ "slug": "GETRESPONSE_GET_ECOMMERCE_REVENUE_STATISTICS",+ "name": "Get the ecommerce revenue statistics",+ "description": "Get ecommerce revenue and order statistics over time."+ },+ {+ "slug": "GETRESPONSE_GET_FILE",+ "name": "Get file by ID",+ "description": "Get File Library metadata and direct URLs for one file by ID."+ },+ {+ "slug": "GETRESPONSE_GET_FILE_LIBRARY_QUOTA",+ "name": "Get storage space information",+ "description": "Get the File Library storage limit and current usage in bytes."+ },+ {+ "slug": "GETRESPONSE_GET_FORM",+ "name": "Get form by ID",+ "description": "Get a resource from GetResponse's standalone modern Forms product by form ID. This is distinct from the Forms and Popups resource family and requires the relevant paid plan or add-on."+ },+ {+ "slug": "GETRESPONSE_GET_FORM_OR_POPUP",+ "name": "Get a single form or popup by ID",+ "description": "Get a resource from GetResponse's combined Forms and Popups product family by popup ID; use GET_FORM for the separate standalone modern Forms family."+ },+ {+ "slug": "GETRESPONSE_GET_FORM_OR_POPUP_PERFORMANCE",+ "name": "Get statistics for a single form or popup",+ "description": "Get performance statistics for an existing form or popup. Availability depends on the account plan."+ },+ {+ "slug": "GETRESPONSE_GET_FROM_ADDRESS",+ "name": "Get a single 'From' address by ID",+ "description": "Get a single GetResponse 'From' address by its ID."+ },+ {+ "slug": "GETRESPONSE_GET_GDPR_FIELD",+ "name": "Get GDPR field details",+ "description": "Get a GetResponse GDPR field and its latest consent-text version."+ },+ {+ "slug": "GETRESPONSE_GET_IMPORT",+ "name": "Get an import by ID",+ "description": "Get import details and processing statistics by ID."+ },+ {+ "slug": "GETRESPONSE_GET_LANDING_PAGE",+ "name": "Get a single landing page by ID",+ "description": "Get a current landing page by ID."+ },+ {+ "slug": "GETRESPONSE_GET_LANDING_PAGE_PERFORMANCE",+ "name": "Get details for landing page statistics",+ "description": "Get performance statistics for an existing landing page. Availability depends on the account plan."+ },+ {+ "slug": "GETRESPONSE_GET_LEGACY_FORM",+ "name": "Get Legacy Form by ID",+ "description": "Get a legacy form by ID."+ },+ {+ "slug": "GETRESPONSE_GET_LEGACY_LANDING_PAGE",+ "name": "Get single landing page by ID",+ "description": "Get a legacy landing page by ID."+ },+ {+ "slug": "GETRESPONSE_GET_META_FIELD",+ "name": "Get the meta field by ID",+ "description": "Get a meta field by shop ID and meta field ID."+ },+ {+ "slug": "GETRESPONSE_GET_NEWSLETTER",+ "name": "Get a single newsletter",+ "description": "Get a single newsletter by its ID."+ },+ {+ "slug": "GETRESPONSE_GET_NEWSLETTER_STATISTICS",+ "name": "Get newsletter statistics",+ "description": "Return one page of statistics for a newsletter and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_GET_NEWSLETTER_THUMBNAIL",+ "name": "Get newsletter thumbnail",+ "description": "Download a newsletter thumbnail with its provider content type."+ },+ {+ "slug": "GETRESPONSE_GET_ORDER",+ "name": "Get a single order by ID",+ "description": "Get one ecommerce order by its shop and order IDs."+ },+ {+ "slug": "GETRESPONSE_GET_PREDEFINED_FIELD",+ "name": "Get a predefined field by ID",+ "description": "Get detailed information about one GetResponse predefined field."+ },+ {+ "slug": "GETRESPONSE_GET_PRODUCT",+ "name": "Get a single product by ID",+ "description": "Get a product and its nested ecommerce data by ID."+ },+ {+ "slug": "GETRESPONSE_GET_PRODUCT_VARIANT",+ "name": "Get a single product variant by ID",+ "description": "Get a product variant and its nested ecommerce data by ID."+ },+ {+ "slug": "GETRESPONSE_GET_RSS_NEWSLETTER",+ "name": "Get RSS newsletter by ID",+ "description": "Get one RSS newsletter and its delivery configuration."+ },+ {+ "slug": "GETRESPONSE_GET_RSS_NEWSLETTER_STATISTICS",+ "name": "Get RSS newsletter statistics by ID",+ "description": "Return one page of delivery statistics for one RSS newsletter."+ },+ {+ "slug": "GETRESPONSE_GET_SAVED_CONTACT_SEARCH",+ "name": "Get search contacts by contact ID",+ "description": "Get a saved contact search by ID."+ },+ {+ "slug": "GETRESPONSE_GET_SENDING_LIMITS",+ "name": "Send limits",+ "description": "Return the connected account's email sending allowances and usage."+ },+ {+ "slug": "GETRESPONSE_GET_SHOP",+ "name": "Get a single shop by ID",+ "description": "Get an ecommerce shop by ID."+ },+ {+ "slug": "GETRESPONSE_GET_SMS_AUTOMATION_MESSAGE",+ "name": "Get a single automated SMS message by its ID",+ "description": "Get an automated SMS message. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_GET_SMS_MESSAGE",+ "name": "Get a single SMS message by its ID",+ "description": "Get an SMS message. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_GET_SMS_STATISTICS",+ "name": "Get details for the SMS message statistics",+ "description": "Get SMS message statistics. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_GET_SUBJECT_AB_TEST",+ "name": "Get a single subject A/B test",+ "description": "Get a single subject A/B test by ID."+ },+ {+ "slug": "GETRESPONSE_GET_SUPPRESSION",+ "name": "Get a suppression list by ID",+ "description": "Get a suppression list by ID."+ },+ {+ "slug": "GETRESPONSE_GET_TAG",+ "name": "Get tag by ID",+ "description": "Get a tag by ID."+ },+ {+ "slug": "GETRESPONSE_GET_TAX",+ "name": "Get a single tax by ID",+ "description": "Get a tax by shop ID and tax ID."+ },+ {+ "slug": "GETRESPONSE_GET_TRACKING",+ "name": "Get tracking JavaScript code snippets",+ "description": "Get the JavaScript snippets used to track purchases, abandoned carts, and visited URLs."+ },+ {+ "slug": "GETRESPONSE_GET_TRANSACTIONAL_EMAIL",+ "name": "Get transactional email details by transactional email ID",+ "description": "Get transactional email details by ID. Requires a paid transactional-email plan or add-on."+ },+ {+ "slug": "GETRESPONSE_GET_TRANSACTIONAL_EMAIL_STATISTICS",+ "name": "Get the overall statistics of transactional emails",+ "description": "Get aggregate transactional email statistics. Requires a paid transactional-email plan or add-on."+ },+ {+ "slug": "GETRESPONSE_GET_TRANSACTIONAL_EMAIL_TEMPLATE",+ "name": "Get a single template by ID",+ "description": "Get a transactional email template by ID."+ },+ {+ "slug": "GETRESPONSE_GET_WEBINAR",+ "name": "Get a webinar by ID",+ "description": "Get a webinar by ID."+ },+ {+ "slug": "GETRESPONSE_GET_WEBSITE",+ "name": "Get a single Website by ID",+ "description": "Get a website by ID."+ },+ {+ "slug": "GETRESPONSE_GET_WEBSITE_PERFORMANCE",+ "name": "Get details for website statistics",+ "description": "Get performance statistics for an existing website. Availability depends on the account plan."+ },+ {+ "slug": "GETRESPONSE_GET_WORKFLOW",+ "name": "Get a workflow by ID",+ "description": "Get a workflow and its subscriber statistics by ID."+ },+ {+ "slug": "GETRESPONSE_LIST_AB_TESTS",+ "name": "List A/B tests",+ "description": "Return one page of A/B tests and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_ACCOUNT_LOGINS",+ "name": "History of logins",+ "description": "Return one page of account login history and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_ADDRESSES",+ "name": "Get a list of addresses",+ "description": "Return one filtered page of GetResponse addresses and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_AUTORESPONDERS",+ "name": "List autoresponders",+ "description": "Return one filtered page of autoresponders and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_AUTORESPONDER_STATISTICS",+ "name": "List autoresponder statistics",+ "description": "Return one filtered page of statistics across autoresponders. Provide an autoresponder or campaign ID filter."+ },+ {+ "slug": "GETRESPONSE_LIST_CAMPAIGN_CONTACTS",+ "name": "Get contacts from a single campaign",+ "description": "List the contacts directly related to one campaign using the campaign-membership endpoint, with relationship-specific filters and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CAMPAIGNS",+ "name": "List campaigns",+ "description": "Return one page of GetResponse campaigns (contact lists), with filters and sorting."+ },+ {+ "slug": "GETRESPONSE_LIST_CARTS",+ "name": "Get shop carts",+ "description": "Get one page of shop carts and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CATEGORIES",+ "name": "Get the shop categories list",+ "description": "Get one page of shop categories and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CLICK_TRACKS",+ "name": "List click tracked links",+ "description": "Return one page of click tracked links and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CONTACT_ACTIVITIES",+ "name": "Get a list of contact activities",+ "description": "Get one page of contact activities and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CONTACT_CONSENTS",+ "name": "Get contact's consent fields",+ "description": "Get the consent fields assigned to a contact."+ },+ {+ "slug": "GETRESPONSE_LIST_CONTACTS",+ "name": "Get contact list",+ "description": "Get one page of contacts and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CUSTOM_EVENTS",+ "name": "List custom events",+ "description": "Return one filtered page of custom event definitions and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CUSTOM_FIELDS",+ "name": "Get a list of custom fields",+ "description": "Get one page of custom field definitions and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_CUSTOM_REPORTS",+ "name": "Get a list of custom reports",+ "description": "Get one page of custom reports. Requires a paid plan with the custom-reports entitlement."+ },+ {+ "slug": "GETRESPONSE_LIST_FACEBOOK_PIXELS",+ "name": "Get the list of Facebook Pixels",+ "description": "List Facebook Pixels assigned to the connected GetResponse account."+ },+ {+ "slug": "GETRESPONSE_LIST_FILES",+ "name": "Get the list of files",+ "description": "Return one page of File Library files with filters and sorting."+ },+ {+ "slug": "GETRESPONSE_LIST_FOLDERS",+ "name": "Get the list of folders",+ "description": "Return one page of File Library folders with filters and sorting."+ },+ {+ "slug": "GETRESPONSE_LIST_FORMS",+ "name": "Get the list of forms",+ "description": "Return one filtered page of modern forms and a continuation cursor. This endpoint requires the relevant paid GetResponse plan or add-on."+ },+ {+ "slug": "GETRESPONSE_LIST_FORMS_AND_POPUPS",+ "name": "List forms and popups",+ "description": "Return one filtered page of forms and popups and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_FORM_VARIANTS",+ "name": "Get the list of form variants (A/B tests)",+ "description": "Get all A/B test variants for a modern form. This endpoint requires the relevant paid GetResponse plan or add-on."+ },+ {+ "slug": "GETRESPONSE_LIST_FROM_ADDRESSES",+ "name": "Get the list of 'From' addresses",+ "description": "Return one filtered page of GetResponse 'From' addresses and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_GDPR_FIELDS",+ "name": "Get the GDPR fields list",+ "description": "Return one page of GetResponse GDPR fields and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_IMAGES",+ "name": "Get images list",+ "description": "Return one page of GetResponse Multimedia images."+ },+ {+ "slug": "GETRESPONSE_LIST_IMPORTS",+ "name": "List imports",+ "description": "Return one filtered page of contact imports and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_INDUSTRIES",+ "name": "List of Industry Tags",+ "description": "Return one page of industry tags and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_LANDING_PAGES",+ "name": "Get the list of landing pages",+ "description": "Return one filtered page of current landing pages and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_LEGACY_FORMS",+ "name": "Get Legacy Forms",+ "description": "Return one filtered page of legacy forms and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_LEGACY_LANDING_PAGES",+ "name": "Get a list of landing pages",+ "description": "Return one filtered page of legacy landing pages and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_META_FIELDS",+ "name": "Get the shop meta fields",+ "description": "Get one page of shop meta fields and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_NEWSLETTERS",+ "name": "List newsletters",+ "description": "Return one page of newsletters and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_NEWSLETTER_STATISTICS",+ "name": "List newsletter statistics",+ "description": "Return one page of total newsletter statistics and a continuation cursor. Provide a newsletter or campaign ID filter."+ },+ {+ "slug": "GETRESPONSE_LIST_ORDERS",+ "name": "Get the list of orders",+ "description": "Get one page of orders and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_PREDEFINED_FIELDS",+ "name": "Get the predefined fields list",+ "description": "Return one filtered page of GetResponse predefined fields and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_PRODUCTS",+ "name": "Get a product list",+ "description": "Get one page of products and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_PRODUCT_VARIANTS",+ "name": "Get a list of product variants",+ "description": "Get one page of product variants and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_RSS_NEWSLETTERS",+ "name": "List RSS newsletters",+ "description": "Return one filtered page of RSS newsletters and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_RSS_NEWSLETTER_STATISTICS",+ "name": "List RSS newsletter statistics",+ "description": "Return one filtered page of statistics across RSS newsletters. Provide an RSS newsletter or campaign ID filter."+ },+ {+ "slug": "GETRESPONSE_LIST_SAVED_CONTACT_SEARCHES",+ "name": "List saved contact searches",+ "description": "Get one page of saved contact searches and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_SAVED_SEARCH_CONTACTS",+ "name": "Get contacts by search contacts ID",+ "description": "Get one page of contacts matching a saved contact search."+ },+ {+ "slug": "GETRESPONSE_LIST_SHOPS",+ "name": "Get a list of shops",+ "description": "Get one page of shops and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_SMS_AUTOMATION_MESSAGES",+ "name": "Get the list of automated SMS messages",+ "description": "Return one page of automated SMS messages. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_LIST_SMS_MESSAGES",+ "name": "Get the list of SMS messages",+ "description": "Return one page of SMS messages. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_LIST_SMS_SENDER_NAMES",+ "name": "Get a list of SMS sender names",+ "description": "Get SMS sender names. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_LIST_SUBJECT_AB_TESTS",+ "name": "List subject A/B tests",+ "description": "Return one page of subject A/B tests and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_SUBSCRIPTION_CONFIRMATION_TEMPLATES",+ "name": "List subscription confirmation templates",+ "description": "List unpaginated body or subject templates for subscription-confirmation emails in one language."+ },+ {+ "slug": "GETRESPONSE_LIST_SUPPRESSIONS",+ "name": "Get suppression lists",+ "description": "Get one page of suppression lists and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_TAGS",+ "name": "Get the list of tags",+ "description": "Get one page of tags and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_TAXES",+ "name": "Get a list of taxes",+ "description": "Get one page of taxes for a shop and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_TIMEZONES",+ "name": "List of timezones",+ "description": "List timezones in the connected account's language context."+ },+ {+ "slug": "GETRESPONSE_LIST_TRANSACTIONAL_EMAILS",+ "name": "Get the list of transactional emails",+ "description": "Get one page of transactional email history. Requires a paid transactional-email plan or add-on."+ },+ {+ "slug": "GETRESPONSE_LIST_TRANSACTIONAL_EMAIL_TEMPLATES",+ "name": "Get the list of transactional email templates",+ "description": "Get one page of transactional email templates and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_WEBINARS",+ "name": "List webinars",+ "description": "Return one filtered page of webinars and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_WEBSITES",+ "name": "Get the list of websites",+ "description": "Return one filtered page of websites and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_LIST_WORKFLOWS",+ "name": "List workflows",+ "description": "Return one page of workflows and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_SEARCH_CONTACTS",+ "name": "Search contacts using conditions",+ "description": "Search contacts using supplied conditions without creating or changing a saved search. Returns one page and a continuation cursor."+ },+ {+ "slug": "GETRESPONSE_SELECT_SUBJECT_AB_TEST_WINNER",+ "name": "Choose A/B test winner",+ "description": "Choose the winning message variant for a subject A/B test."+ },+ {+ "slug": "GETRESPONSE_SEND_NEWSLETTER_DRAFT",+ "name": "Send newsletter draft",+ "description": "Send an existing newsletter draft using the supplied recipient and delivery settings."+ },+ {+ "slug": "GETRESPONSE_SEND_SMS",+ "name": "Send an SMS message",+ "description": "Immediately send an SMS to selected GetResponse contacts or imported phone numbers. Requires a paid SMS plan or add-on."+ },+ {+ "slug": "GETRESPONSE_SEND_TRANSACTIONAL_EMAIL",+ "name": "Send transactional email",+ "description": "Send a direct or template-based transactional email. Requires a paid transactional-email plan or add-on."+ },+ {+ "slug": "GETRESPONSE_SET_DEFAULT_FROM_ADDRESS",+ "name": "Set a 'From' address as default",+ "description": "Set an existing GetResponse 'From' address as the account default."+ },+ {+ "slug": "GETRESPONSE_TRIGGER_CUSTOM_EVENT",+ "name": "Trigger a custom event",+ "description": "Trigger an existing custom event for a contact. This may start connected automation workflows."+ },+ {+ "slug": "GETRESPONSE_UPDATE_ACCOUNT",+ "name": "Update account",+ "description": "Update supplied profile fields on the connected GetResponse account. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_ACCOUNT_BADGE",+ "name": "Turn on/off the GetResponse Badge",+ "description": "Enable or disable the selected GetResponse account badge type."+ },+ {+ "slug": "GETRESPONSE_UPDATE_ACCOUNT_BLOCKLIST",+ "name": "Update account blocklist",+ "description": "Update the account-wide blocklist. Omit additional_flags to replace all masks; use add or delete for incremental changes, optionally combined with noResponse."+ },+ {+ "slug": "GETRESPONSE_UPDATE_ADDRESS",+ "name": "Update address",+ "description": "Update only the supplied fields of an existing GetResponse address. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_AUTORESPONDER",+ "name": "Update autoresponder",+ "description": "Update an autoresponder's content, status, delivery timing, or trigger settings. Setting status to 'enabled' can send messages when its trigger conditions are met. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CALLBACK_CONFIGURATION",+ "name": "Enable or update callbacks configuration",+ "description": "Enable or update the account-wide callback URL and event subscriptions. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CAMPAIGN",+ "name": "Update campaign",+ "description": "Update a GetResponse campaign (contact list) and its confirmation or profile settings."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CAMPAIGN_BLOCKLIST",+ "name": "Update campaign blocklist",+ "description": "Add, delete, or replace blocklist masks for a campaign (contact list)."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CART",+ "name": "Update cart",+ "description": "Update a cart and its selected variants. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CATEGORY",+ "name": "Update category",+ "description": "Update a category's supplied fields. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CONTACT",+ "name": "Update contact details",+ "description": "Update contact details; supplied tags and custom fields replace existing values, and changing campaign moves the contact and its history. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CUSTOM_EVENT",+ "name": "Update a custom event",+ "description": "Update a custom event definition and its attributes."+ },+ {+ "slug": "GETRESPONSE_UPDATE_CUSTOM_FIELD",+ "name": "Update a custom field",+ "description": "Update a custom field definition's visibility and assigned values."+ },+ {+ "slug": "GETRESPONSE_UPDATE_META_FIELD",+ "name": "Update meta field",+ "description": "Update a meta field's supplied fields. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_ORDER",+ "name": "Update order",+ "description": "Update the supplied fields of an ecommerce order. Provide at least one mutable body field; additional_flags alone does not update the order."+ },+ {+ "slug": "GETRESPONSE_UPDATE_PREDEFINED_FIELD",+ "name": "Update a predefined field",+ "description": "Update the value of an existing GetResponse predefined field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_PRODUCT",+ "name": "Update product",+ "description": "Update a product and its nested ecommerce data. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_PRODUCT_VARIANT",+ "name": "Update product variant",+ "description": "Update a product variant and its nested ecommerce data. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_RSS_NEWSLETTER",+ "name": "Update RSS newsletter",+ "description": "Update an RSS newsletter's content, status, delivery, or audience settings. Setting status to 'enabled' can send messages according to its delivery schedule. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_SAVED_CONTACT_SEARCH",+ "name": "Update search contacts",+ "description": "Replace a saved contact search's name and condition sections."+ },+ {+ "slug": "GETRESPONSE_UPDATE_SHOP",+ "name": "Update shop",+ "description": "Update a shop's supplied fields. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_SUPPRESSION",+ "name": "Update a suppression list by ID",+ "description": "Replace a suppression list's masks and optionally rename it. The complete masks list is required; pass an empty list to remove all masks."+ },+ {+ "slug": "GETRESPONSE_UPDATE_TAX",+ "name": "Update tax",+ "description": "Update a tax's supplied fields. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_TRANSACTIONAL_EMAIL_TEMPLATE",+ "name": "Update transactional email template",+ "description": "Update the subject or content of a transactional email template. Provide at least one mutable field."+ },+ {+ "slug": "GETRESPONSE_UPDATE_WORKFLOW",+ "name": "Update a workflow",+ "description": "Set a workflow to active, inactive, or incomplete (draft)."+ },+ {+ "slug": "GETRESPONSE_UPLOAD_IMAGE",+ "name": "Upload image",+ "description": "Upload an image file to GetResponse Multimedia."+ },+ {+ "slug": "GETRESPONSE_UPSERT_CONTACT_CUSTOM_FIELDS",+ "name": "Upsert the custom fields of a contact",+ "description": "Add or update a contact's custom fields without removing other assigned custom fields."+ },+ {+ "slug": "GETRESPONSE_UPSERT_CONTACT_TAGS",+ "name": "Upsert the tags of a contact",+ "description": "Add tags to a contact without unassigning the contact's existing tags."+ },+ {+ "slug": "GETRESPONSE_UPSERT_META_FIELDS",+ "name": "Upsert product meta fields",+ "description": "Assign meta fields to a product without removing existing assignments."+ },+ {+ "slug": "GETRESPONSE_UPSERT_PRODUCT_CATEGORIES",+ "name": "Upsert product categories",+ "description": "Assign categories to a product and optionally set its default category without removing existing assignments."+ },+ {+ "slug": "GETRESPONSE_UPSERT_SAVED_SEARCH_CONTACT_CUSTOM_FIELDS",+ "name": "Upsert custom fields by search contacts",+ "description": "Submit an asynchronous request to add or update custom fields for contacts matching a saved contact search. A successful response confirms acceptance, not completion."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "OAUTH2",+ "name": "getresponse_oauth",+ "fields": {+ "auth_config_creation": {+ "required": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": true,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": true,+ "default": null+ }+ ],+ "optional": [+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": ""+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ },+ {+ "mode": "API_KEY",+ "name": "getresponse_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Your GetResponse API key from https://app.getresponse.com/api",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "get_transcribe","name": "GetTranscribe",@@ -206681,6 +212644,661 @@}]},+ {+ "slug": "grafana_cloud_mcp",+ "name": "Grafana Cloud MCP",+ "logo": "https://logos.composio.dev/api/grafana_cloud_mcp",+ "description": "Grafana Cloud MCP lets agents query metrics, logs, traces, dashboards, datasources, alerts, incidents, and related observability resources in an authorized Grafana Cloud stack.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 118,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "GRAFANA_CLOUD_MCP_ADD_ACTIVITY_TO_INCIDENT",+ "name": "Add activity to incident",+ "description": "Add a note (userNote activity) to an existing incident's timeline using its ID. The note body can include URLs which will be attached as context. Use this to add context to an incident."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_AGENTS",+ "name": "Agento11y manage agents",+ "description": "Read the agent catalog of Grafana Agent Observability (the grafana-agento11y-app plugin): which agents send telemetry, what their system prompts and tools are, how their prompt versions evolved, and how each version scored.\n\nThe catalog is derived from ingested telemetry, not from a registration step: an agent exists here once its generations have been seen. It answers \"what is this agent\" while agento11y_manage_conversations and agento11y_manage_generations answer \"what did it do\".\n\nOperations:\n- 'list': agents in this tenant, newest activity first. Each row carries the latest effective version, first and latest seen times, generation and version counts, tool count, a system prompt prefix, and token_estimate. Paginated via limit and cursor\n- 'get': one agent version in full: the complete system prompt, every tool with its JSON schema, and the models it ran on. Returns the latest version unless 'version' is set\n- 'list_versions': the version history of one agent, one row per effective version with its seen window, generation count, tool count, and token_estimate. Paginated\n- 'list_version_scores': evaluation score aggregates per version, with per-evaluator score_key, pass and fail counts, and mean_score. Use it to compare how versions scored\n\nVersions: an effective version is always 'sha256:<64 lowercase hex>', and only that form is accepted by 'get'; a declared version such as '1.4.2' is reported in the declared_version fields but cannot be looked up. The plugin derives the effective version from the first of these the telemetry carries: the version the SDK reported, a hash of the declared version, a hash of the system prompt. Adding, removing, or editing a tool never mints a new version. Editing the prompt mints one only for an agent that reports neither its own effective version nor a declared version, so an agent that declares '1.4.2' keeps one effective version across prompt edits.\n\nResponse size: 'get' returns the whole system prompt plus every tool schema, which can be tens of thousands of tokens. Check token_estimate.total from 'list' or 'list_versions' before fetching, and prefer the system_prompt_prefix in those rows when a prefix is enough.\n\nCross-referencing: pass an agent name from 'list' to agento11y_manage_conversations as the search filter agent = \"<name>\" to find what that agent actually did.\n\nPagination: when a response carries next_cursor, call the same operation again with cursor set to it. For 'list', also repeat the same name_prefix, start_time, and end_time using absolute RFC3339 times; the cursor is bound to those filters and a relative value such as now-7d or 7d re-resolves and is rejected.\n\nPermissions: every operation is a read and needs grafana-agento11y-app.data:read (Agento11y Editor or Admin). This tool performs no writes.\n\nWhen to use:\n- Discovering which agent names exist before filtering conversations or generations by agent\n- Reading the system prompt or tool inventory an agent ran with, or how they changed between versions\n- Checking whether a new prompt version scores worse than the previous one\n\nWhen NOT to use:\n- Reading individual conversations, generations, or their scores (use agento11y_manage_conversations and agento11y_manage_generations)\n- Inspecting evaluators or the rules that schedule them (use agento11y_manage_evaluators and agento11y_manage_eval_rules)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_CONVERSATIONS",+ "name": "Agento11y manage conversations",+ "description": "List, search, and fetch LLM conversations from Grafana Agent Observability (the grafana-agento11y-app plugin).\n\nOperations:\n- 'list': recent conversations (lightweight; id, title, generation count, timestamps), paginated via limit and cursor\n- 'search': search conversations by filter expression and time range; results include models, agents, error counts, rating and eval summaries, and trace IDs\n- 'get': one conversation by ID with all its generations, including full prompts and outputs (can be large)\n\nFilter syntax for 'search': key operator value, with the value in double quotes; multiple filters are separated by spaces and combined with AND.\nFilter keys (trace): model, provider, agent, agent.version, status, error.type, error.category, duration, tool.name, operation, namespace, cluster, service\nFilter keys (metadata): generation_count, eval.passed, eval.evaluator_id, eval.score_key, eval.score\nOperators: =, !=, >, <, >=, <=, =~ (regex)\nExample: status = \"error\" agent = \"claude-code\"\n\nPagination: when a response has next_cursor, fetch the next page by calling the same operation again with cursor set to next_cursor. For 'search', also repeat the same filters, start_time, and end_time as the first call, using absolute RFC3339 times; relative ranges like now-24h shift between calls and the cursor will be rejected.\n\nWhen to use:\n- Debugging an AI application: find failing or low-rated conversations, then inspect their generations\n- Reviewing evaluation results and user ratings across conversations\n\nWhen NOT to use:\n- Fetching a single generation or its evaluation scores (use agento11y_manage_generations)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_EVAL_COLLECTIONS",+ "name": "Agento11y manage eval collections",+ "description": "Manage the curated conversations of Grafana Agent Observability (the grafana-agento11y-app plugin): bookmark conversations as saved conversations and group them into collections.\n\nTwo linked resources:\n- A saved conversation (/eval/saved-conversations) is a bookmark on one conversation, keyed by a saved_id you choose. It gives that conversation a stable ID, a name, and tags a collection can reference. It does not preserve the conversation: retention deletes the bookmark and its collection memberships together with the conversation it points at.\n- A collection (/eval/collections) is a named group of saved conversations, used as the source material for offline evaluation. Collections hold saved conversations, never raw conversation IDs, so a conversation must already be bookmarked before a collection accepts it.\n\nOperations:\n- 'list_saved_conversations': bookmarked conversations in this tenant, filterable by source ('telemetry' for bookmarked production traffic, 'manual' for hand-built ones). Also reports total_count for the whole filtered set, not just the page\n- 'get_saved_conversation': one bookmark by ID\n- 'list_collections_for_saved_conversation': the collections one bookmark belongs to (unpaginated)\n- 'list_collections': collections in this tenant, each with its member_count\n- 'get_collection': one collection by ID\n- 'list_collection_members': the saved conversations in a collection\n- 'save_conversation': bookmark a live conversation by conversation_id. saved_id is optional and defaults to 'saved-<conversation_id>'; a conversation can only be saved once, so a repeat returns 409 naming the existing saved_id\n- 'delete_saved_conversation': delete a bookmark by saved_id. Idempotent, and it also removes the bookmark from every collection it belonged to, with no separate membership cleanup. On a source='manual' bookmark the backend goes further and deletes the underlying conversation and its generations, so the content itself is gone\n- 'create_collection': create an empty collection from a name and optional description. The response carries the server-assigned collection_id needed by the membership operations\n- 'update_collection': patch a collection's name or description. Omitted fields are left unchanged, and an explicitly empty description clears it\n- 'delete_collection': delete a collection and its memberships in one transaction. Idempotent, and the saved conversations themselves are kept\n- 'add_collection_members': add saved_ids to a collection. Every ID must already be a saved conversation (a missing one returns 400 naming it), and re-adding an existing member is a no-op\n- 'remove_collection_member': drop one saved conversation from a collection. Idempotent, and the bookmark itself is kept\n\nIdentifiers: saved_id is caller-chosen and accepts letters, digits, '_', '.', ':', and '-' (looser than the evaluator and rule IDs, which reject hyphens). collection_id is a UUID assigned by the server when a collection is created; it cannot be chosen.\n\nList rows are already enriched: every saved conversation in 'list_saved_conversations' and 'list_collection_members' embeds the collections it belongs to plus generation_count, total_tokens, agent_names, models, model_providers, and tags. Read those fields instead of calling 'list_collections_for_saved_conversation' per row, which is one request per result. An absent collections field means the row was not enriched; an empty array means the row genuinely belongs to no collection.\n\nPagination: when a response carries next_cursor, call the same operation again with cursor set to it. Echo the value back exactly; never construct or increment one. 'list_saved_conversations' returns an opaque numeric value while 'list_collections' and 'list_collection_members' return the last row ID, so a cursor from one operation passed to another fails or silently skips rows. Keep the same source filter across pages.\n\nPermissions: reads need grafana-agento11y-app.data:read (Agento11y Editor or Admin). Every write needs grafana-agento11y-app.eval:write, granted only by the Agento11y Admin role; an Editor token gets 403.\n\nWhen to use:\n- Reading what is already curated: which collections exist, how large they are, and what is in them\n- Turning a triaged failure into a regression collection: 'save_conversation', then 'create_collection' or 'add_collection_members'\n- Bookmarking a conversation found via agento11y_manage_conversations so a collection can reference it by a stable ID\n- Collection hygiene: renaming a collection, or removing a conversation that no longer belongs in it\n\nWhen NOT to use:\n- Searching or reading live conversations and generations (use agento11y_manage_conversations and agento11y_manage_generations)\n- Inspecting evaluators or the rules that schedule them (use agento11y_manage_evaluators and agento11y_manage_eval_rules)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_EVAL_RULES",+ "name": "Agento11y manage eval rules",+ "description": "Manage the evaluation rules and guards of Grafana Agent Observability (the grafana-agento11y-app plugin): the configuration that decides when evaluators run.\n\nTwo different resources with different runtime behavior:\n- Eval rules (/eval/rules) are asynchronous. A rule selects production traffic (selector, match filters, sample_rate) and schedules its evaluator_ids to score matching generations after the fact. Rules only observe; they never change a request.\n- Guards (/eval/hook-rules; there is no /eval/guards path) run inline on the request path and can deny it, redact content, or block tool calls. A guard is inert until the agent application calls the hooks endpoint (POST /eval/hooks:evaluate) itself: a stored guard on its own changes nothing.\n\nOperations:\n- 'list_rules': asynchronous eval rules in this tenant (paginated)\n- 'get_rule': one eval rule by ID\n- 'list_guards': guards, read from /eval/hook-rules (paginated)\n- 'get_guard': one guard by ID\n- 'create_rule': create an asynchronous eval rule from an inline 'definition'\n- 'update_rule': patch an existing rule; send only the fields to change (rule_id is taken from the 'rule_id' parameter and must not appear in the definition)\n- 'delete_rule': delete a rule by ID\n- 'preview_rule': dry-run a selector, match, and sample_rate against recent traffic and return how many generations would match and be sampled, plus example generations. Run this before creating a rule that spends judge tokens\n- 'create_guard': create an inline guard (stored as a hook rule)\n- 'update_guard': full replace of a guard (PUT, not PATCH) — omitted fields reset to server defaults, so send the complete definition, normally a 'get_guard' result with your edits applied\n- 'delete_guard': delete a guard by ID\n\nIdentifiers (rule_id) accept only letters, digits, '_', and '.'; hyphens are rejected by the API. Rule selectors: user_visible_turn, all_assistant_generations, tool_call_steps, errored_generations, conversation (guards also accept 'all'). Match keys are arrays and include agent_name, agent_version, operation_name, model.provider, model.name, mode, error.type, error.category, and tags.<key>. Pagination: when a response carries next_cursor, call the same operation again with cursor set to it.\n\nPermissions: reads need grafana-agento11y-app.data:read (Agento11y Editor or Admin). Every write, plus 'preview_rule' (which persists nothing), needs grafana-agento11y-app.eval:write, granted only by the Agento11y Admin role; an Editor token gets 403.\n\nWhen to use:\n- A score names an evaluator and you need to know which rule scheduled it and on what traffic\n- Auditing which guards are live and whether they warn or deny\n- Binding a new evaluator to production traffic with 'create_rule', after checking the blast radius with 'preview_rule'\n- Adding a guard, or promoting one from warn to deny after watching its false-positive rate\n\nWhen NOT to use:\n- Inspecting what an evaluator checks, or the template it came from (use agento11y_manage_evaluators)\n- Listing conversations, generations, or scores (use agento11y_manage_conversations and agento11y_manage_generations)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_EVALUATORS",+ "name": "Agento11y manage evaluators",+ "description": "Manage the evaluator catalog of Grafana Agent Observability (the grafana-agento11y-app plugin): read evaluators, evaluator templates, and the judge model catalog, and create, test, or delete evaluators.\n\nAn evaluator is a scoring function (kind: llm_judge, json_schema, regex, or heuristic) that scores generations. The scores returned by agento11y_manage_generations operation 'scores' name the evaluator that produced them. Templates are versioned starting points for evaluators. Judge providers and models are the LLM backends an llm_judge evaluator can use.\n\nOperations:\n- 'list_evaluators': evaluators in this tenant (paginated)\n- 'get_evaluator': one evaluator by ID, with its kind, config, and output_keys\n- 'list_templates': evaluator templates, filterable by scope ('global' for built-ins, 'tenant' for locally created ones)\n- 'get_template': one template with its config, output_keys, and version list\n- 'list_template_versions': version history of a template, each version with its config and output_keys\n- 'list_judge_providers': judge providers configured on this stack\n- 'list_judge_models': judge models, optionally filtered by provider\n- 'upsert_evaluator': create or update an evaluator from an inline 'definition'. POST is create-or-update keyed on definition.evaluator_id; there is no separate update operation, and re-using an existing 'version' returns 409, so bump the version to change an evaluator\n- 'delete_evaluator': soft-delete an evaluator by ID. Rules and guards that reference it keep the reference and silently stop producing scores, so check agento11y_manage_eval_rules first\n- 'fork_template': derive a new evaluator from a template in one call. Prefer this over copying 'get_template' output into 'upsert_evaluator', which the API rejects\n- 'test_evaluator': run an inline evaluator definition against one generation and return its scores without persisting anything. Useful for tuning a judge config before 'upsert_evaluator'\n\nIdentifiers (evaluator_id, template_id) accept only letters, digits, '_', and '.'; hyphens are rejected by the API. Template operations need a stack with the evaluator template store configured and return 404 otherwise. Pagination: when a response carries next_cursor, call the same operation again with cursor set to it.\n\nPermissions: reads need grafana-agento11y-app.data:read (Agento11y Editor or Admin). Every write, plus 'test_evaluator' (which persists nothing), needs grafana-agento11y-app.eval:write, granted only by the Agento11y Admin role; an Editor token gets 403.\n\nWhen to use:\n- A score from agento11y_manage_generations names an evaluator and you need to see what it checks\n- Inspecting a template before deriving an evaluator from it\n- Tuning an llm_judge config against a real generation with 'test_evaluator' before storing it\n- Creating an evaluator so a rule or guard can reference it\n\nWhen NOT to use:\n- Finding which rule scheduled an evaluator, or which guard enforces it (use agento11y_manage_eval_rules)\n- Listing conversations, generations, or scores (use agento11y_manage_conversations and agento11y_manage_generations)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_EXPERIMENTS",+ "name": "Agento11y manage experiments",+ "description": "Manage the offline experiments of Grafana Agent Observability (the grafana-agento11y-app plugin), their trials, and their scores.\n\nAn experiment is one offline run of an agent over a test suite. Each test case in the suite produces one or more trials, each trial is scored by the experiment's evaluators, and the experiment reports a pass rate. Experiments are created by SDK runners, not from here.\n\nOperations:\n- 'list': experiments in this tenant, filterable by suite_id, status, source, created_by, tag, and a created_at or completed_at window. Each row carries the same result summary as 'get', so finding the experiment that regressed needs no second call\n- 'get': one experiment with its result summary: pass rate, average final score, total cost and tokens\n- 'get_report': the per-test-case breakdown, trimmed by row_limit. The test case input and expected values, the score records, and the artifact records are dropped because those fields have no size bound; each trial keeps its error message, a score_count, an artifact_count, and the IDs the drill-downs take\n- 'list_trials': one experiment's trials, paginated. Prefer this over 'get_report' on a large suite. It reports no cost or token counts: only the report path fills those in\n- 'list_scores': every score in one experiment, paginated\n- 'get_trial': one trial in full, including the test case snapshot with its input and expected values\n- 'list_trial_scores': one trial's scores, with the explanation each judge wrote\n- 'list_trial_artifacts': one trial's artifact metadata, with a content_ref rather than the bytes\n- 'list_facets': the distinct suites, owners, and tags across every experiment in the tenant, for building a 'list' filter. Only source, from, and to narrow it; it rejects a filter it would otherwise have to ignore\n- 'update': patch an experiment's name, description, tags, or metadata. Only the experiment's created_by may patch it, so patching an experiment someone else started answers 401\n- 'cancel': stop a running experiment. It checks no owner, so any caller with the write permission can stop any experiment. An experiment that already finished is left alone: the call answers 200 and returns it unchanged instead of failing, so read the status on the result rather than assume a run was stopped\n\nSize: 'get_report' is fetched whole before it is trimmed, and a response above 10 MiB fails the call rather than arriving truncated.\n\nPagination: when a response carries next_cursor, call the same operation again with cursor set to it, repeating the first page's filters with absolute RFC3339 times. A relative bound such as now-7d re-resolves between calls and moves the window the cursor was issued against, so it is rejected alongside a cursor.\n\nPermissions: reads need grafana-agento11y-app.data:read (Agento11y Editor or Admin). Both writes need grafana-agento11y-app.eval:write, granted only by the Agento11y Admin role; an Editor token gets 403.\n\nWhen to use:\n- Finding the last experiment for a suite after a suspected regression: 'list' by suite_id, then read the pass rate off the row\n- Finding which test cases an experiment failed on, then reading one failing trial in full\n- Labelling an experiment after triage, so 'list' by tag finds it later\n- Stopping an experiment that is burning judge tokens on a broken candidate\n\nWhen NOT to use:\n- Reading scores on live production traffic (use agento11y_manage_generations and agento11y_manage_conversations)\n- Inspecting the test cases a suite defines, or editing them (use agento11y_manage_test_suites)\n- Inspecting what an evaluator checks (use agento11y_manage_evaluators)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_GENERATIONS",+ "name": "Agento11y manage generations",+ "description": "Fetch a single LLM generation and its evaluation scores from Grafana Agent Observability (the grafana-agento11y-app plugin).\n\nOperations:\n- 'get': full generation detail by ID, including prompt, output, model, and usage (can be large)\n- 'scores': evaluation scores for a generation (evaluator, score key, score type, value, passed, explanation)\n\nWhen to use:\n- Drilling into one generation found via agento11y_manage_conversations\n- Checking why an evaluation passed or failed for a specific generation\n\nWhen NOT to use:\n- Searching or listing conversations (use agento11y_manage_conversations)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_AGENTO11Y_MANAGE_TEST_SUITES",+ "name": "Agento11y manage test suites",+ "description": "Manage the test suites of Grafana Agent Observability (the grafana-agento11y-app plugin), their versions, and their test cases.\n\nA test suite is the input side of an offline experiment: a named set of test cases that an SDK runner replays against an agent. Suites are versioned, and a test case belongs to one version rather than to the suite, so every test case operation takes both suite_id and version.\n\nA version is either a draft or published. A draft accepts test case edits; publishing freezes it and makes it the suite's latest_version, which is the version a runner picks up. A suite has at most one draft at a time.\n\nOperations:\n- 'list_suites': the test suites in this tenant, newest first. The rows carry no version history\n- 'get_suite': one suite with its full version history under versions\n- 'list_test_cases': the test cases of one suite version, oldest first, paginated\n- 'get_test_case': one test case in full, with its free-form input and expected values\n- 'create_suite': a new empty suite. It has no version yet, so follow it with 'create_draft_version'\n- 'update_suite': patch a suite's name, description, or tags\n- 'create_draft_version': open a new editable version. A suite that already has a draft answers 409\n- 'publish_version': freeze a draft. There is no unpublish; a published version answers 409 to a second publish and to every test case edit, so changing a published suite means a new draft\n- 'upsert_test_case': write a whole test case into a draft version. It replaces the stored case rather than merging into it, so a field left out is cleared; read the case with 'get_test_case' first and send it back complete\n- 'delete_test_case': remove one test case from a draft version. Deleting a test case that is already gone answers 404\n\nPagination: when a response carries next_cursor, call the same operation again with cursor set to it.\n\nPermissions: reads need grafana-agento11y-app.data:read (Agento11y Editor or Admin). Every write needs grafana-agento11y-app.eval:write, granted only by the Agento11y Admin role; an Editor token gets 403.\n\nWhen to use:\n- Reading the test cases at the version an experiment used, after it reported a failing case\n- Adding a regression case to a suite, then publishing the draft so the next experiment picks it up\n- Correcting a test case whose expected value was wrong\n\nWhen NOT to use:\n- Reading how a suite scored, or the trials, scores, and artifacts behind it (use agento11y_manage_experiments)\n- Changing what an evaluator checks (use agento11y_manage_evaluators)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_ALERTING_MANAGE_ROUTING",+ "name": "Alerting manage routing",+ "description": "Manage Grafana alerting routing configuration, including notification policies, contact points and time intervals.\n\nNotification policies define how alerts are grouped, routed, and which contact points receive them.\nTime intervals define active/mute periods for alert notifications.\n\nWhen to use:\n- Understanding how alerts are routed to contact points/receivers\n- Debugging why an alert went to a specific receiver\n- Checking grouping, timing, or mute interval settings\n\nWhen NOT to use:\n- Checking alert rule configuration or state (use alerting_manage_rules)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_ALERTING_MANAGE_RULES",+ "name": "Alerting manage rules",+ "description": "Manage Grafana alert rules with full CRUD capabilities and filtering.\n\nWhen to use:\n- Understanding why an alert is or isn't firing\n- Auditing alert rule configuration (queries, conditions, labels, notification settings)\n- Finding alert rules by state, folder, group, or name\n- Creating, updating, or deleting alert rules\n- Comparing rule versions to see what changed\n\nWhen NOT to use:\n- Checking how alerts are routed to receivers (use alerting_manage_routing)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_ALERTING_MANAGE_SILENCES",+ "name": "Alerting manage silences",+ "description": "Manage Grafana alerting silences. A silence temporarily suppresses notifications for alerts whose labels match a set of matchers, without changing the alert rules themselves.\n\nOperations:\n- 'list': list existing silences. Optionally filter by rule_uid (matches the __alert_rule_uid__ label) or by matchers.\n- 'get': retrieve a single silence by silence_id.\n- 'create': create a new silence. Requires matchers, starts_at, ends_at (RFC3339) and comment.\n- 'update': modify an existing silence by silence_id. Requires matchers, starts_at, ends_at and comment. The id is only kept when the posted matchers and starts_at match the stored ones, so pass back the starts_at returned by 'get'; otherwise Alertmanager expires the old silence and returns a new id.\n- 'delete': expire/remove a silence by silence_id.\n\nWhen to use:\n- Muting noisy or expected alerts during maintenance windows\n- Inspecting or cleaning up existing silences\n\nWhen NOT to use:\n- Changing alert rule configuration or state (use alerting_manage_rules)\n- Changing how alerts are routed to receivers (use alerting_manage_routing)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_ANALYZE_LOKI_LABELS",+ "name": "Analyze loki labels",+ "description": "Audits a Loki label strategy and optionally diagnoses query performance. Returns per-label verdicts, missing base labels, normalisation issues, and a recommended set. Pass datasourceUid for live cardinality or labels for static scoring; both may be combined."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_ASK_ASSISTANT",+ "name": "Ask assistant",+ "description": "Send a message to Grafana Assistant and wait for the full text reply. The assistant may use tools, metrics, logs, and other stack context—broader than firing one isolated data-source query.\n\nUse for open-ended questions, triage, or anything that needs assistant reasoning and tool use, in addition to the more targeted MCP tools.\n\n**Multi-turn:** pass contextId from a previous ask_assistant result to continue the same conversation.\n\n**Time:** complex tasks can take several minutes; the call blocks until the reply is done or the request times out. Consider running this tool as a background task if able."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CHECK_DATASOURCES_HEALTH",+ "name": "Check datasources health",+ "description": "Check datasource health. Filter by type or UIDs; omit both to check all."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CREATE_ANNOTATION",+ "name": "Create annotation",+ "description": "Create a new annotation on a dashboard or panel. Set format to 'graphite' and provide 'what' for Graphite-format annotations."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CREATE_DATASOURCE",+ "name": "Create datasource",+ "description": "Create a datasource. If type is ambiguous, call search_plugin_information first; install the plugin if needed. IMPORTANT: always call this tool twice. First call: provide only the type — the tool returns a field schema. After receiving the schema, you MUST ask the user for every required field value explicitly; do not infer or use defaults without user confirmation. Second call: provide the type, the display name in the top-level name argument, schemaReviewed=true, and the fields map populated with values confirmed by the user. Never handle credentials — remind the user to rotate any detected. Returns UID, health check, and a config page link. "+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CREATE_FOLDER",+ "name": "Create folder",+ "description": "Create a Grafana folder. Provide a title and optional UID. Returns the created folder."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CREATE_INCIDENT",+ "name": "Create incident",+ "description": "Create a new Grafana incident. Requires title, severity, and room prefix. Allows setting status and labels. This tool should be used judiciously and sparingly, and only after confirmation from the user, as it may notify or alarm lots of people."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CREATE_INVESTIGATION",+ "name": "Create investigation",+ "description": "Start a Grafana Assistant investigation: an agentic, multi-step root-cause analysis across the stack's metrics, logs, traces, dashboards, and alerts.\n\nProvide a natural-language instruction describing what to investigate. Optionally set a title, share with teams via teamNames, or pick an agent profile via agentProfileId.\n\nThe investigation runs asynchronously: this returns investigationId and chatId immediately; poll get_investigation for lifecycle state and results."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_CREATE_SNAPSHOT",+ "name": "Create snapshot",+ "description": "Create a Grafana snapshot from a full dashboard payload. Supports optional expiration and external snapshot fields."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_DELETE_SNAPSHOT",+ "name": "Delete snapshot",+ "description": "Delete a Grafana snapshot by snapshot key."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_DESCRIBE_ATHENA_TABLE",+ "name": "Describe athena table",+ "description": "Get column names for an Athena table. Use after list_athena_tables. NEXT: Use query_athena with discovered column names."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_DESCRIBE_CLICKHOUSE_TABLE",+ "name": "Describe clickhouse table",+ "description": "Get column schema for a ClickHouse table. Pass the database from list_clickhouse_tables results. NEXT: Use query_clickhouse with discovered column names."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_DESCRIBE_INFRASTRUCTURE",+ "name": "Describe infrastructure",+ "description": "Start here when users ask about their infrastructure, services, or architecture. Returns pre-built summaries of service groups including topology, metrics, deployment, dependencies, and datasource UIDs.\n\nInfrastructure memories are generated by scanning Prometheus metric datasources to discover services, then using AI to summarize each service group. Memories are organized by service group (e.g. \"Payment System\", \"Inventory\"). Each group has chunks covering: overview, metrics, deployment, dependencies, logs, and — when code search finds relevant repos — a code & repositories chunk describing the source repos, languages, and deployment/configuration evidence found in the code. Results also include datasource UIDs for metrics (Prometheus), logs (Loki), and traces (Tempo) — use these to query the right datasource in follow-up tool calls. Individual services/components (e.g. \"cortex-gw\") are listed inside their parent group's overview chunk — use the exact component name in keywords to find the right group.\n\nUses hybrid search (semanticQuery for meaning + keywords for lexical matching). keywords is critical for finding specific sub-components within groups.\n\nBatch queries: pass an array of queries (max 3) to explore multiple service groups or angles in a single call. Results from all queries are merged and deduplicated by group name, so overlapping matches won't be returned twice. Prefer batching related angles over multiple sequential calls.\n\nIMPORTANT: semanticQuery must be a single short question with the group/component name — e.g. \"What metrics does checkout-service expose?\". Do NOT append generic terms like \"architecture, components, dependencies, telemetry\" — these match every document. keywords must use the exact service/component name (e.g. \"cortex-gw\").\n\nExamples:\n- User asks \"What's my infrastructure like?\" → queries: [{semanticQuery: \"What services are running?\", keywords: \"service\"}]\n- User asks \"Tell me about the checkout system\" → queries: [{semanticQuery: \"How does checkout-service work?\", keywords: \"checkout-service\"}]\n- User asks \"Compare the checkout and payment systems\" → queries: [{semanticQuery: \"How does checkout-service work?\", keywords: \"checkout-service\"}, {semanticQuery: \"How does payment-service work?\", keywords: \"payment-service\"}]\nEach query returns full groups with overview, metrics, dependencies, logs, datasource UIDs, and (when available) code/repo information — enough to start investigating with targeted queries.\n\nRequired: queries (each entry needs semanticQuery and keywords)\nOptional: datasourceUID (pass if a datasource UID is known from the conversation, user query, or previous tool results)\n\nWhen to use:\n- User asks broad questions about their infrastructure or what services are running\n- User asks about specific services or components\n- Need topology, relationships, or configuration\n- Need to discover which datasources (metrics, logs, traces) to query for a service\n- Before querying raw metrics or logs — check here first to find the right datasource UIDs\n- Need to know which repository or source code backs a service (when code evidence is available)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_DESCRIBE_SNOWFLAKE_TABLE",+ "name": "Describe snowflake table",+ "description": "Get column schema for a Snowflake table. Pass the database/schema from list_snowflake_tables results. NEXT: Use query_snowflake with discovered column names."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GENERATE_DEEPLINK",+ "name": "Generate deeplink",+ "description": "Generate deeplink URLs for Grafana resources. Supports dashboards (requires dashboardUid or provisioningPreview), panels (requires dashboardUid or provisioningPreview, plus panelId), and Explore queries (requires datasourceUid and optionally queries). For dashboard and panel links, provisioningPreview points at a dashboard staged on a provisioning repository branch (e.g. a git-sync PR preview). For explore links, the time range and queries are embedded inside the Grafana explore state. Set shorten=true to also attempt a /goto/<uid> short URL; if shortening fails, the full deeplink is returned."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ALERT_GROUP",+ "name": "Get alert group",+ "description": "Get a specific alert group from Grafana OnCall by its ID. Returns the full alert group details, including the most recent alert and its raw payload when the OnCall API provides them. Alert payloads carry integration-specific fingerprints (for example Sentry's payload.data.event.hashes or Alertmanager's payload.alerts[].fingerprint) that identify recurring alerts across different alert groups."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ANNOTATIONS",+ "name": "Get annotations",+ "description": "Fetch Grafana annotations using filters such as dashboard UID, time range and tags."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ANNOTATION_TAGS",+ "name": "Get annotation tags",+ "description": "Returns annotation tags with optional filtering by tag name. Only the provided filters are applied."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ASSERTIONS",+ "name": "Get assertions",+ "description": "Get assertion summary for a given entity with its type, name, env, site, namespace, and a time range"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_CURRENT_ONCALL_USERS",+ "name": "Get current oncall users",+ "description": "Get the list of users currently on-call for a specific Grafana OnCall schedule ID. Returns the schedule ID, name, and a list of detailed user objects for those currently on call."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_DASHBOARD_BY_UID",+ "name": "Get dashboard by uid",+ "description": "Retrieves the complete dashboard, including panels, variables, and settings, for a specific dashboard identified by its UID. The response includes 'apiVersion' and 'isV2': when 'isV2' is true the dashboard uses the v2 schema (panels live under 'elements' keyed by name, arranged by 'layout'; variables under 'variables'), otherwise it is classic v1 ('panels[]' with 'templating.list'). WARNING: Large dashboards can consume significant context window space. Consider using get_dashboard_summary for overview or get_dashboard_property for specific data instead."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_DASHBOARD_PANEL_QUERIES",+ "name": "Get dashboard panel queries",+ "description": "Retrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with `panelId`. Optionally provide `variables` for template variable substitution, which populates `processedQuery` and `requiredVariables` fields. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, and requiredVariables."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_DASHBOARD_PROPERTY",+ "name": "Get dashboard property",+ "description": "Get specific parts of a dashboard using JSONPath expressions to minimize context window usage. JSONPath targets the dashboard's native schema. Classic v1 paths: '$.title' (title)\\, '$.panels[*].title' (all panel titles)\\, '$.panels[0]' (first panel)\\, '$.templating.list' (variables)\\, '$.annotations.list' (saved dashboard annotation queries/definitions)\\, '$.tags' (tags)\\, '$.panels[*].targets[*].expr' (all queries). v2 dashboards (see isV2 from get_dashboard_by_uid) use different paths: '$.title'\\, '$.elements' (panels\\, keyed by name)\\, '$.variables' (variables)\\, '$.annotations'. Use this instead of get_dashboard_by_uid when you only need specific dashboard properties."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_DASHBOARD_SUMMARY",+ "name": "Get dashboard summary",+ "description": "Get a compact summary of a dashboard including title\\, panel count\\, panel types\\, variables\\, and other metadata without the full JSON. Use this for dashboard overview and planning modifications without consuming large context windows."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_DATASOURCE",+ "name": "Get datasource",+ "description": "Retrieves detailed information about a specific datasource by UID or name. Returns the full datasource model, including name, type, URL, access settings, JSON data, and secure JSON field status. Provide either uid or name; uid takes priority if both are given."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_INCIDENT",+ "name": "Get incident",+ "description": "Get a single incident by ID. Returns the full incident details including title, status, severity, labels, timestamps, and other metadata."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_INVESTIGATION",+ "name": "Get investigation",+ "description": "Get one Grafana Assistant investigation (AI-driven root-cause investigation) by ID.\n\nReturns the investigation's identifiers (investigationId and chatId), the authoritative row lifecycle state and metadata (title, description, state, summary, labels, team ownership, timestamps, completion quality, failure details), and the engine work snapshot (sessionStatus, mode, epoch, plan, report content).\n\nThe row's state field is authoritative for investigation lifecycle (pending, in_progress, completed, failed, cancelled, paused). The snapshot's sessionStatus only describes the engine session (idle, active, pause) — do not infer completion or failure from it. Legacy (v1) investigations may have no snapshot; the row metadata is still returned with snapshotError set."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_INVESTIGATION_THREAD",+ "name": "Get investigation thread",+ "description": "Get the working thread of one Grafana Assistant investigation (AI-driven root-cause investigation) by ID: the user-visible conversation between the investigation agent and its tools.\n\nResolves the investigation to its backing chat and returns the non-hidden user-visible messages in order. Each message keeps only prose (the agent's narrative and findings), tool calls (toolName and toolInput), and tool results (raw query output); internal reasoning and bookkeeping blocks are excluded. Tool results are returned verbatim and can be large — use limit and offset to page through long threads (total reports the full user-visible count).\n\nUse this to inspect the raw data behind a report's [cite:pN] citations: list_investigation_evidence maps each panel ID to a toolUseId, and the tool_result block with that toolUseId in this thread holds the captured query output."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ONCALL_SHIFT",+ "name": "Get oncall shift",+ "description": "Get detailed information for a specific Grafana OnCall shift using its ID. A shift represents a designated time period within a schedule when users are actively on-call. Returns the full shift details."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_PANEL_IMAGE",+ "name": "Get panel image",+ "description": "Render a Grafana dashboard panel or full dashboard as a PNG image. Returns the image as base64 encoded data. Requires the Grafana Image Renderer service to be installed. Either dashboardUid (for stored dashboards) or provisioningPreview (for dashboards staged on a provisioning repository branch, e.g. a git-sync PR) must be supplied. Use this for generating visual snapshots of dashboards for reports, alerts, or presentations."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_PLUGIN",+ "name": "Get plugin",+ "description": "Check whether a Grafana plugin is installed and retrieve its details (name, version, type, enabled status). Returns installed=false when the plugin is not found. Use install_plugin when a plugin is not installed to install plugin after confirming this action with the user."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_QUERY_EXAMPLES",+ "name": "Get query examples",+ "description": "Get example queries for a specific datasource type. Provides sample queries with descriptions for Prometheus (PromQL), Loki (LogQL), ClickHouse (SQL with Grafana macros), CloudWatch (metric configurations), and InfluxDB (Flux and InfluxQL). Use this to understand query syntax and common patterns for each datasource. TIP: Use list_datasources to find datasource UIDs, or get_datasource if you know the exact name."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_RESOURCE_DESCRIPTION",+ "name": "Get resource description",+ "description": "List available permissions and assignment capabilities for a Grafana resource type."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_RESOURCE_PERMISSIONS",+ "name": "Get resource permissions",+ "description": "List all permissions set on a specific Grafana resource (e.g., dashboard, datasource, folder) by its type and ID."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ROLE_ASSIGNMENTS",+ "name": "Get role assignments",+ "description": "List all assignments for a specific role, showing which users, teams, and service accounts have been assigned this role."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_ROLE_DETAILS",+ "name": "Get role details",+ "description": "Get detailed information about a specific Grafana role by its UID, including permissions, metadata, and configuration."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GET_SNAPSHOT",+ "name": "Get snapshot",+ "description": "Get a Grafana snapshot by key, including snapshot metadata and dashboard payload."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_GRAFANA_API_REQUEST",+ "name": "Grafana api request",+ "description": "Make an authenticated HTTP request to the Grafana API. Similar to 'gh api' for GitHub. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_INSTALL_PLUGIN",+ "name": "Install plugin",+ "description": "Install a Grafana plugin by its plugin ID. If the version is not already confirmed with the user, omit it — the tool will look up the latest version and return it for confirmation before installing."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ALERT_GROUPS",+ "name": "List alert groups",+ "description": "List alert groups from Grafana OnCall with filtering options. Supports filtering by alert group ID, route ID, integration ID, state (new, acknowledged, resolved, silenced), team ID, time range, labels, and name. For time ranges, use format '{start}_{end}' ISO 8601 timestamp range (e.g., '2025-01-19T00:00:00_2025-01-19T23:59:59' for a specific day). For labels, use format 'key:value' (e.g., ['env:prod', 'severity:high']). Returns a list of alert group objects with their details. Supports pagination."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ALL_ROLES",+ "name": "List all roles",+ "description": "List all roles in Grafana. Optionally filter to show only roles that can be delegated by the current user. Returns role details including UID, name, permissions, and metadata."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ATHENA_CATALOGS",+ "name": "List athena catalogs",+ "description": "START HERE for Athena: List available data catalogs (e.g. AwsDataCatalog, Iceberg connectors). NEXT: Use list_athena_databases with a catalog."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ATHENA_DATABASES",+ "name": "List athena databases",+ "description": "List databases in an Athena catalog. Use after list_athena_catalogs. NEXT: Use list_athena_tables with a database."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ATHENA_TABLES",+ "name": "List athena tables",+ "description": "List tables in an Athena database. Use after list_athena_databases. NEXT: Use describe_athena_table to see column schemas before querying."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_CLICKHOUSE_TABLES",+ "name": "List clickhouse tables",+ "description": "START HERE for ClickHouse: List available tables (name, database, engine, row count, size). NEXT: Use describe_clickhouse_table to see column schemas."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_CLOUDWATCH_DIMENSIONS",+ "name": "List cloudwatch dimensions",+ "description": "List dimension keys for a CloudWatch metric. Requires region. Supports cross-account monitoring via optional accountId parameter. Use after list_cloudwatch_metrics. NEXT: Use query_cloudwatch with discovered dimensions."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_CLOUDWATCH_METRICS",+ "name": "List cloudwatch metrics",+ "description": "List metrics for a CloudWatch namespace. Requires region. Supports cross-account monitoring via optional accountId parameter. Use after list_cloudwatch_namespaces. NEXT: Use list_cloudwatch_dimensions\\, then query_cloudwatch."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_CLOUDWATCH_NAMESPACES",+ "name": "List cloudwatch namespaces",+ "description": "START HERE for CloudWatch: List available namespaces (AWS/EC2, AWS/ECS, AWS/RDS, etc.). Requires region. Supports cross-account monitoring via optional accountId parameter. NEXT: Use list_cloudwatch_metrics with a namespace."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_DATASOURCES",+ "name": "List datasources",+ "description": "List all configured datasources in Grafana. Use this to discover available datasources and their UIDs. Supports filtering by type and/or name (case-insensitive substring match) and pagination."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_GRAPHITE_METRICS",+ "name": "List graphite metrics",+ "description": "Discover available metric paths in a Graphite datasource by browsing the metric tree. Returns nodes matching the query pattern\\, each indicating whether it is a leaf metric (has data) or an expandable branch (has children). Use '*' as a wildcard at any level to enumerate the tree (e.g. '*' → top-level nodes\\, 'servers.*' → all second-level nodes under 'servers'). Drill down progressively to find the full metric path before querying with query_graphite."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_GRAPHITE_TAGS",+ "name": "List graphite tags",+ "description": "List available tag names in a Graphite datasource that uses tag-based metrics. Returns a list of tag name strings (e.g. [\"name\"\\, \"env\"\\, \"region\"]). These tags can be used to build tag-based target expressions for query_graphite (e.g. seriesByTag('name=cpu.load\\,env=prod')). Optionally filter by a prefix. Requires Graphite to be configured with tag support."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_INCIDENTS",+ "name": "List incidents",+ "description": "List Grafana incidents. Allows filtering by status ('active', 'resolved') and optionally including drill incidents. Returns a preview list with basic details."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_INVESTIGATION_EVIDENCE",+ "name": "List investigation evidence",+ "description": "List the evidence citation index for one Grafana Assistant investigation (AI-driven root-cause investigation) by ID.\n\nInvestigation reports cite captured query panels with [cite:pN] markers. Each evidence entry describes one captured panel, keyed by that panel ID: the tool that produced it (prometheus, loki, tempo, pyroscope), a human-readable query summary, the epoch (agent turn) at capture time, the capture timestamp, and the tool call ID that produced it.\n\nThis is an index, not the data: raw query results live in the investigation thread. To see the data behind a citation, call get_investigation_thread and match the entry's toolUseId against the thread's tool results. Legacy (v1) investigations have no engine session and return an empty list."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_INVESTIGATION_PROFILES",+ "name": "List investigation profiles",+ "description": "List the agent profiles available for Grafana Assistant investigations (AI-driven root-cause investigations) on this Grafana Cloud stack.\n\nEach profile describes an investigation agent configuration: its ID, display name, description, whether it is the default, its step budget, the tools it can use, and its content hash. Use a profile's ID as agentProfileId when creating an investigation."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_INVESTIGATIONS",+ "name": "List investigations",+ "description": "List Grafana Assistant investigations (AI-driven root-cause investigations) on this Grafana Cloud stack.\n\nReturns one summary per investigation — ID, chat ID, title, state, timestamps, labels, team ownership, progress, and completion quality — plus the total count of matches for pagination. Results are limited to investigations the authenticated user is allowed to see.\n\nAll filters are optional. Use chatId to find the investigation that owns a known chat (all other filters are then ignored), q for free-text search, state/scope/label/teamName/from/to to narrow results, and limit/offset with the returned total to paginate."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_LOKI_LABEL_NAMES",+ "name": "List loki label names",+ "description": "Lists all available label/field names (keys) found in logs within a specified Loki or VictoriaLogs datasource and time range. Returns a list of unique label strings (e.g., `[\"app\", \"env\", \"pod\"]`). If the time range is not provided, it defaults to the last hour."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_LOKI_LABEL_VALUES",+ "name": "List loki label values",+ "description": "Retrieves all unique values associated with a specific `labelName` within a Loki or VictoriaLogs datasource and time range. Returns a list of string values (e.g., for `labelName=\"env\"`, might return `[\"prod\", \"staging\", \"dev\"]`). Useful for discovering filter options. Defaults to the last hour if the time range is omitted."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ONCALL_SCHEDULES",+ "name": "List oncall schedules",+ "description": "List Grafana OnCall schedules, optionally filtering by team ID. If a specific schedule ID is provided, retrieves details for only that schedule. Returns a list of schedule summaries including ID, name, team ID, timezone, and shift IDs. Supports pagination."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ONCALL_TEAMS",+ "name": "List oncall teams",+ "description": "List teams configured in Grafana OnCall. Returns a list of team objects with their details. Supports pagination."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_ONCALL_USERS",+ "name": "List oncall users",+ "description": "List users from Grafana OnCall. These are OnCall users (separate from Grafana users). Can retrieve all users in the OnCall directory, a specific user by ID, or filter by username. Returns a list of user objects with their details. Supports pagination."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PROMETHEUS_LABEL_NAMES",+ "name": "List prometheus label names",+ "description": "List label names in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Allows filtering by series selectors and time range."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PROMETHEUS_LABEL_VALUES",+ "name": "List prometheus label values",+ "description": "Use after list_prometheus_metric_names to find label values for filtering queries. Gets the values for a specific label name in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Allows filtering by series selectors and time range."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PROMETHEUS_METRIC_METADATA",+ "name": "List prometheus metric metadata",+ "description": "List Prometheus metric metadata. Returns metadata about metrics currently scraped from targets. Note: This endpoint is experimental."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PROMETHEUS_METRIC_NAMES",+ "name": "List prometheus metric names",+ "description": "DISCOVERY: Call this first to find available metrics before querying. Lists metric names in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Retrieves all metric names and filters them using the provided regex. Supports pagination and an optional time range to restrict results to metrics active within that window."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PYROSCOPE_LABEL_NAMES",+ "name": "List pyroscope label names",+ "description": "\nLists all available label names (keys) found in profiles within a specified Pyroscope datasource, time range, and\noptional label matchers. Label matchers are typically used to qualify a service name ({service_name=\"foo\"}). Returns a\nlist of unique label strings (e.g., [\"app\", \"env\", \"pod\"]). Label names with double underscores (e.g. __name__) are\ninternal and rarely useful to users. If the time range is not provided, it defaults to the last hour.\n"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PYROSCOPE_LABEL_VALUES",+ "name": "List pyroscope label values",+ "description": "\nLists all available label values for a particular label name found in profiles within a specified Pyroscope datasource,\ntime range, and optional label matchers. Label matchers are typically used to qualify a service name ({service_name=\"foo\"}).\nReturns a list of unique label strings (e.g. for label name \"env\": [\"dev\", \"staging\", \"prod\"]). If the time range\nis not provided, it defaults to the last hour.\n"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_PYROSCOPE_PROFILE_TYPES",+ "name": "List pyroscope profile types",+ "description": "\nLists all available profile types available in a specified Pyroscope datasource and time range. Returns a list of all\navailable profile types (example profile type: \"process_cpu:cpu:nanoseconds:cpu:nanoseconds\"). A profile type has the\nfollowing structure: <name>:<sample type>:<sample unit>:<period type>:<period unit>. Not all profile types are available\nfor every service. If the time range is not provided, it defaults to the last hour.\n"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_SNAPSHOTS",+ "name": "List snapshots",+ "description": "List Grafana dashboard snapshots with optional query and result limit filters."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_SNOWFLAKE_TABLES",+ "name": "List snowflake tables",+ "description": "START HERE for Snowflake: List available tables (database, schema, name, kind, row count, size) via INFORMATION_SCHEMA. NEXT: Use describe_snowflake_table to see column schemas."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_TEAM_ROLES",+ "name": "List team roles",+ "description": "List all roles assigned to one or more teams. Returns a map of team IDs to their assigned roles."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_TEAMS",+ "name": "List teams",+ "description": "Search for Grafana teams by a query string. Returns a list of matching teams with details like name, ID, and URL."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_USER_ROLES",+ "name": "List user roles",+ "description": "List all roles assigned to one or more users. Returns a map of user IDs to their assigned roles, excluding built-in roles and team-inherited roles."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_LIST_USERS_BY_ORG",+ "name": "List users by org",+ "description": "List users in the Grafana organization. Returns a list of organization users with details like userid, email, role etc."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_ATHENA",+ "name": "Query athena",+ "description": "Query Amazon Athena via Grafana. REQUIRED FIRST: Use list_athena_catalogs -> list_athena_databases -> list_athena_tables -> describe_athena_table to discover schema, then query.\n\nSupports macros: $__timeFilter(column), $__dateFilter(column), $__unixEpochFilter(column), $__timeFrom(), $__timeTo(), $__from, $__to, $__interval, ${varname}\n\nTime formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)\n\nAthena queries are async — Grafana handles polling. Use LIMIT and partition-aware WHERE clauses to avoid timeouts on large tables.\n\nExample: SELECT request_time, status FROM my_table WHERE $__timeFilter(request_time) LIMIT 100"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_CLICKHOUSE",+ "name": "Query clickhouse",+ "description": "Query ClickHouse via Grafana. REQUIRED FIRST: Use list_clickhouse_tables to find tables, then describe_clickhouse_table to see column schemas, then query.\n\nSupports macros: $__timeFilter(column), $__from, $__to, $__interval, ${varname}\n\nTime formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)\n\nExample: SELECT Timestamp, Body FROM otel_logs WHERE $__timeFilter(Timestamp)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_CLOUDWATCH",+ "name": "Query cloudwatch",+ "description": "Query AWS CloudWatch metrics via Grafana. Requires region.\n\nREQUIRED FIRST: Use list_cloudwatch_namespaces -> list_cloudwatch_metrics -> list_cloudwatch_dimensions -> then query.\n\nTime formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)\n\nCommon namespaces: AWS/EC2, AWS/ECS, AWS/RDS, AWS/Lambda, ECS/ContainerInsights\n\nExample dimensions: ECS: {ClusterName, ServiceName}, EC2: {InstanceId}\n\nCross-account monitoring: Use accountId to query metrics from a specific source account (e.g. '123456789012') or 'all' to query all linked accounts. Only applicable when using a CloudWatch monitoring account datasource."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_ELASTICSEARCH",+ "name": "Query elasticsearch",+ "description": "Executes a search query against an Elasticsearch or OpenSearch datasource and retrieves matching documents. Supports Lucene query syntax (e.g., 'status:200 AND host:server1') for both Elasticsearch and OpenSearch. Elasticsearch Query DSL JSON is also supported for Elasticsearch datasources only (not OpenSearch). Returns a list of documents with their index, ID, source fields, and optional score. Use this to search logs, metrics, or any indexed data stored in Elasticsearch or OpenSearch. Defaults to 10 results and sorts by @timestamp in descending order (newest first)."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_GRAPHITE",+ "name": "Query graphite",+ "description": "WORKFLOW: list_graphite_metrics -> query_graphite.\n\nExecutes a Graphite render API query against a Graphite datasource and returns matching metric series with their datapoints. Supports the full Graphite target expression language including wildcard patterns (e.g. 'servers.web*.cpu.load5'), aggregation functions (e.g. 'sumSeries(app.*.requests)'), and tag-based queries (e.g. 'seriesByTag(\\'name=cpu.load\\')'). Datapoints with no recorded value are returned with a null value field. Time range defaults to the last hour if not specified."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_GRAPHITE_DENSITY",+ "name": "Query graphite density",+ "description": "Analyses metric data density for one or more Graphite series over a time window. Returns per-series statistics: fillRatio (fraction of non-null datapoints, 0.0–1.0), totalPoints, nonNullPoints, lastSeen (Unix timestamp of most recent non-null value, or null if none), longestGap (longest consecutive null run in seconds), and estimatedInterval (inferred write interval in seconds). Supports wildcard targets (e.g. 'obox-cl*.sys.sessions') to diagnose stale, sparse, or dead metrics across a cluster. A fillRatio of 0 with lastSeen null means the series reported no data in the requested window."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_INFLUXDB",+ "name": "Query influxdb",+ "description": "Query an InfluxDB datasource via Grafana. Supports both InfluxQL (v1.x) and Flux (v2.x). The 'dialect' parameter selects the query language; if omitted it's inferred from the datasource configuration.\n\nTime formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)\n\nInfluxQL example: SELECT mean(\"value\") FROM \"cpu\" WHERE time > now() - 1h GROUP BY time(1m)\nFlux example: from(bucket: \"metrics\") |> range(start: -1h) |> filter(fn: (r) => r._measurement == \"cpu\")"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_LOKI_LOGS",+ "name": "Query loki logs",+ "description": "Executes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The `logql` parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: `{app=\"foo\"} |= \"error\"`; VictoriaLogs: `{app=\"foo\"} \"error\"`). To count matching log lines precisely, use a `count_over_time()` metric query with queryType='instant'. Prefer using `query_loki_stats` first to cheaply check whether a stream contains data (avoiding expensive queries against empty streams) and `list_loki_label_names` / `list_loki_label_values` to verify labels exist before querying. Note: `query_loki_stats` returns approximate storage-level counts, not exact log line counts. For broad queries that match many lines, set `format` to 'compact' to group results by stream and avoid repeating label metadata on every line. If this server enables the Loki cost guardrail, expensive queries are rejected before execution: query cost is bytes SCANNED, determined only by the stream selector and time range — line filters (|=) and parsers (| json) reduce what is returned, not what is scanned. Use a stream selector with at least one selective positive label matcher (never `{}`, `=~\".*\"`/`=~\".+\"`, or negative-only matchers), keep time ranges narrow, and check size with `query_loki_stats` first; rejected queries return rewrite guidance."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_LOKI_PATTERNS",+ "name": "Query loki patterns",+ "description": "Retrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string and a total count of occurrences. Patterns help identify common log structures and anomalies. The `logql` parameter must be a stream selector (e.g., `{job=\"nginx\"}`) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. **Not supported on VictoriaLogs** datasources - use a `| stats` pipeline instead."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_LOKI_STATS",+ "name": "Query loki stats",+ "description": "Retrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., `{\"streams\": 5, \"chunks\": 50, \"entries\": 10000, \"bytes\": 512000}`). **Important**: the `entries` count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. To count actual matching log lines, use `query_loki_logs` with a `count_over_time()` metric query instead. On VictoriaLogs only `entries` is populated; the other fields remain zero. The `logql` parameter **must** be a simple label selector (e.g., `{app=\"nginx\", env=\"prod\"}`) and does not support line filters, parsers, or aggregations. Defaults to the last hour if the time range is omitted."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_PROMETHEUS",+ "name": "Query prometheus",+ "description": "WORKFLOW: list_prometheus_metric_names -> list_prometheus_label_values -> query_prometheus. Query a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Supports instant queries (single point) and range queries (time range). Time: RFC3339 or relative expressions like 'now'\\, 'now-1h'."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_PROMETHEUS_HISTOGRAM",+ "name": "Query prometheus histogram",+ "description": "Query Prometheus histogram percentiles. DISCOVER FIRST: Use list_prometheus_metric_names with regex='.*_bucket$' to find histograms.\n\nGenerates histogram_quantile PromQL. Example: metric='http_duration', percentile=95, labels='job=\"api\"'\n\nTime formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_PYROSCOPE",+ "name": "Query pyroscope",+ "description": "\nUnified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data\nshows WHEN consumption spiked. Use query_type=\"both\" for complete analysis in one call.\n\nquery_type options (extends Grafana's PyroscopeQueryType):\n- \"profile\": returns profile data (shape controlled by format)\n- \"metrics\": returns time-series data points\n- \"both\" (default): returns both profile and metrics in one response\n\nformat options (shape of the profile data):\n- \"table\" (default): per-function table with flat (self) and cumulative values, ranked by flat\n- \"dot\": call graph in Graphviz DOT format; nodes are per source line, so one function may span several nodes\n"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_QUICKWIT",+ "name": "Query quickwit",+ "description": "Executes a search query against a Quickwit datasource and retrieves matching documents. Supports Lucene query syntax (e.g., 'severity_text:ERROR AND service_name:api') and partial Elasticsearch-compatible Query DSL JSON. The timestamp field is resolved from Quickwit index metadata (not jsonData.timeField). Returns a list of documents with their index, ID, source fields, and optional score. Use this to search logs or other indexed data stored in Quickwit. Defaults to 10 results and sorts by the index timestamp field in descending order (newest first)."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_QUERY_SNOWFLAKE",+ "name": "Query snowflake",+ "description": "Query Snowflake via Grafana. REQUIRED FIRST: Use list_snowflake_tables to find tables (filter by database/schema), then describe_snowflake_table to see column schemas, then query.\n\nSupports macros: $__timeFilter(column), $__timeFrom, $__timeTo, $__from, $__to, $__interval, $__interval_ms, ${varname}\n\nTime formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)\n\nSnowflake event tables (telemetry from logging APIs/auto-instrumentation) live in the database/schema configured by the EVENT TABLE setting; the standard one is SNOWFLAKE.TELEMETRY.EVENTS.\n\nExample: SELECT TIMESTAMP, RECORD['severity_text']::STRING AS LEVEL, VALUE FROM SNOWFLAKE.TELEMETRY.EVENTS WHERE $__timeFilter(TIMESTAMP) AND RECORD_TYPE = 'LOG'"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_RUN_PANEL_QUERY",+ "name": "Run panel query",+ "description": "Executes one or more dashboard panel queries with optional time range and variable overrides. Accepts an array of panel IDs to query in a single call. Fetches the dashboard\\, extracts queries from the specified panels\\, substitutes template variables and Grafana macros ($__range\\, $__rate_interval\\, $__interval)\\, and routes to the appropriate datasource (Prometheus\\, Loki\\, ClickHouse\\, CloudWatch\\, InfluxDB\\, BigQuery\\, MSSQL\\, or PostgreSQL). Returns results keyed by panel ID - partial failures are allowed (some panels can succeed while others fail). Use get_dashboard_summary first to find panel IDs. If a panel uses a template variable datasource you cannot access\\, provide datasourceUid and datasourceType to override."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_SEARCH_DASHBOARDS",+ "name": "Search dashboards",+ "description": "Search for Grafana dashboards by a query string. Returns a list of matching dashboards with details like title, UID, folder, tags, and URL."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_SEARCH_FOLDERS",+ "name": "Search folders",+ "description": "Search for Grafana folders by a query string. Returns matching folders with details like title, UID, and URL."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_SEARCH_PLUGIN_INFORMATION",+ "name": "Search plugin information",+ "description": "Search the Grafana plugin catalog by keyword to discover available plugins before installing or getting plugin details on a specific instance. Returns results sorted by trust: official Grafana Labs plugins first, then commercial partner plugins, then community plugins. Use this tool when a user describes a plugin by purpose or partial name (e.g. 'azure monitoring', 'loki', 'database') — it returns the exact pluginId to pass to get_plugin or install_plugin. Results include warnings for enterprise-only or Angular-based plugins."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_SUGGEST_LOKI_ALLOY_LABEL_CONFIG",+ "name": "Suggest loki alloy label config",+ "description": "Generates an Alloy loki.process snippet enforcing an approved label set via stage.label_keep, with optional log-level normalisation and soft-enforcement placeholders."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_DOCS_CONFIG",+ "name": "Tempo docs-config",+ "description": "Documentation on Tempo configuration. Best for questions about how to configure or operate Tempo. Request the overview to learn which configuration block does what, or the reference for the complete list of options and their defaults."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_DOCS_TRACEQL",+ "name": "Tempo docs-traceql",+ "description": "Documentation on TraceQL search. Best for retrieval of traces. This covers basic attributes all the way through aggregates, pipelining, structural queries, and more. Includes examples."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_GET_ATTRIBUTE_NAMES",+ "name": "Tempo get-attribute-names",+ "description": "Get a list of available attribute names that can be used in TraceQL queries. This is useful for finding the names of attributes that can be used in a query."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_GET_ATTRIBUTE_VALUES",+ "name": "Tempo get-attribute-values",+ "description": "Get a list of values for a fully scoped attribute name. This is useful for finding the values of a specific attribute. i.e. you can find all the services in the data by asking for resource.service.name"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_GET_TRACE",+ "name": "Tempo get-trace",+ "description": "Retrieve a specific trace by ID"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_TRACEQL_METRICS_INSTANT",+ "name": "Tempo traceql-metrics-instant",+ "description": "Retrieve a single metric value given a TraceQL metrics query. The value is at the current instant or end. Most metrics questions can be answered with instant values."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_TRACEQL_METRICS_RANGE",+ "name": "Tempo traceql-metrics-range",+ "description": "Retrieve a metric series given a TraceQL metrics query. The series ranges from start to end."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_TEMPO_TRACEQL_SEARCH",+ "name": "Tempo traceql-search",+ "description": "Search for traces using TraceQL queries"+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_UPDATE_ALERT_GROUP",+ "name": "Update alert group",+ "description": "Update the state of a Grafana OnCall alert group: acknowledge, unacknowledge, resolve, or unresolve it by ID. Returns the alert group's resulting OnCall state (one of new, acknowledged, resolved, silenced), or a stateWarning explaining why that state could not be read back after a successful update."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_UPDATE_ANNOTATION",+ "name": "Update annotation",+ "description": "Updates the provided properties of an annotation by ID. Only fields included in the request are modified; omitted fields are left unchanged."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_UPDATE_DASHBOARD",+ "name": "Update dashboard",+ "description": "Create or update a dashboard. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid'\\, 'message'\\, and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one\\, many\\, or All values from a multi-select variable inside a regex expression or matcher\\, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions must be written into dashboard JSON under 'annotations.list'; the create_annotation tool creates annotation events and does not add a reusable dashboard annotation query/definition to the saved dashboard. For stat panels over the current dashboard range\\, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr'\\, '$.panels[1].title'\\, '$.panels[2].targets[0].datasource'\\, '$.templating.list/-'\\, and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {\"op\": \"remove\"\\, \"path\": \"$.panels[2]\"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. v2 dashboards (check 'isV2' from get_dashboard_by_uid) use a different shape: patch '$.elements.<name>.spec.title' or '$.elements.<name>.spec.data.spec.queries[0].spec' and edit '$.variables'/'$.layout' rather than '$.panels'/'$.templating.list'. Full-JSON saves containing top-level 'elements'/'layout' are written as v2 and require a Kubernetes-capable Grafana. After creating or updating a dashboard\\, verify that panel queries return data by using `run_panel_query` or the appropriate query tool (`query_prometheus`\\, `query_loki_logs`\\, etc.) to validate expressions before considering the task complete."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_UPDATE_DATASOURCE",+ "name": "Update datasource",+ "description": "Update non-secret datasource fields by UID. Omitted fields are preserved. IMPORTANT: always call this tool twice. First call: provide only the uid — the tool returns the datasource's field schema. After receiving the schema, ask the user which fields they want to change and confirm each new value; do not infer or reset fields the user did not mention. Second call: provide the uid, schemaReviewed=true, and the changed values in the fields map. Returns an update message and a health check. For secrets, direct the user to the Grafana UI."+ },+ {+ "slug": "GRAFANA_CLOUD_MCP_UPDATE_INCIDENT",+ "name": "Update incident",+ "description": "Update an existing Grafana incident by ID. Allows changing the status ('active' or 'resolved'), the severity, and the title. Only the provided fields are changed. Use this to resolve an incident or to correct its severity or title as part of an on-call workflow."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "grafana_cloud_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "grafana:read,grafana:query,grafana:write"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "grafbase","name": "Grafbase",@@ -214243,6 +220861,516 @@}]},+ {+ "slug": "higgsfield_mcp",+ "name": "Higgsfield MCP",+ "logo": "https://logos.composio.dev/api/higgsfield_mcp",+ "description": "Higgsfield MCP lets agents generate authorized images, videos, characters, and audio, reuse prior creations, and inspect credit balances through Higgsfield's creative platform.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 89,+ "triggerCount": 0,+ "version": "20260903_00",+ "tools": [+ {+ "slug": "HIGGSFIELD_MCP_ANIMATION_ACTIONS",+ "name": "Animation actions",+ "description": "Read-only catalog of the 3D rig animation library (678 actions: locomotion, gestures, dancing, combat, daily actions). Search by name or browse by group/category to find the animation_action_id for 3D generation with enable_animation=true. Each result has a preview_url GIF — when several candidates fit (e.g. many Idle or Walk variants), show the user the previews as markdown images and let them pick instead of choosing blindly. Does not create jobs."+ },+ {+ "slug": "HIGGSFIELD_MCP_APPS_DESCRIBE",+ "name": "Apps describe",+ "description": "Get an app's action contract: with `action`, the full input/output schema + execution mode for that one action; without it, a summary of every action. Also returns `manifest_revision`, which apps_invoke requires. Read-only."+ },+ {+ "slug": "HIGGSFIELD_MCP_APPS_INVOKE",+ "name": "Apps invoke",+ "description": "Run one described action on a Marketplace app AS the current user. First call apps_describe(app_id, action) to get the exact `arguments` schema and the `manifest_revision`, then pass them here. Long-running actions return { id, status: \"queued\" }. If a widget is visible, it polls the status action automatically — do not re-invoke get_* as a follow-up poll. In text-only clients, poll by invoking the app's status action (e.g. get_render) until status is completed/failed. The action's own annotations (from apps_describe) indicate cost/side-effects; confirm with the user before an expensive or destructive action."+ },+ {+ "slug": "HIGGSFIELD_MCP_APPS_SEARCH",+ "name": "Apps search",+ "description": "Search Higgsfield Marketplace apps callable through MCP. Returns each app's id, name, and the actions it exposes. Flow: apps_search to find an app → apps_describe(app_id, action) to get an action's argument schema + manifest_revision → apps_invoke to run it. Read-only; does not call any app."+ },+ {+ "slug": "HIGGSFIELD_MCP_BALANCE",+ "name": "Balance",+ "description": "Get the user's available credits and current subscription plan. For transaction history, call `transactions` instead."+ },+ {+ "slug": "HIGGSFIELD_MCP_CANCEL_TRIAL_AUTO_RENEWAL",+ "name": "Cancel trial auto renewal",+ "description": "Cancel the auto-renewal of the Higgsfield MCP free trial. Call this when the user asks to cancel the trial, cancel auto-renewal, stop the upcoming charge, or asks how to cancel. IMPORTANT SEMANTICS: cancelling stops the automatic charge at the end of the trial ONLY — the user KEEPS trial access and remaining trial credits until the trial ends; nothing is charged. First call WITHOUT `confirm` (or confirm=false): in UI clients this opens a confirmation card with 'Keep trial with auto-renewal' and 'Cancel auto-renewal' buttons; in text-only clients relay `assistant_response` verbatim and wait for the user's explicit confirmation. Only call again with `confirm=true` after the user explicitly confirmed the cancellation in chat. Never pass confirm=true on the first call."+ },+ {+ "slug": "HIGGSFIELD_MCP_CONFIRM_BILLING_PURCHASE",+ "name": "Confirm billing purchase",+ "description": "INTERNAL — invoked ONLY by the plans widget on an explicit user Confirm click. Do NOT call this tool yourself; it charges the user's real saved payment method off-session. To help a user upgrade, top up, or set auto top-up, call `show_plans_and_credits` instead — it returns checkout links and, in UI clients, opens the widget where the user confirms the charge. Covers auto_topup and topup via the `action` field (upgrade_plan is temporarily disabled — plan upgrades use the hosted checkout link). The backend either charges the saved card (`result: \"charged\"`) or returns a `checkout_url` to redirect (`result: \"redirect\"`). Buying a brand-new subscription is not handled here — that uses the hosted checkout link."+ },+ {+ "slug": "HIGGSFIELD_MCP_CONFIRM_TRIAL_CANCEL",+ "name": "Confirm trial cancel",+ "description": "INTERNAL — invoked ONLY by the cancel-trial confirmation widget on an explicit user click of 'Cancel auto-renewal'. Do NOT call this tool yourself; to cancel the trial's auto-renewal use `cancel_trial_auto_renewal` instead. Stops the trial's auto-renewal (cancel_at_period_end) — trial access and remaining credits stay until the trial ends."+ },+ {+ "slug": "HIGGSFIELD_MCP_CREATE_VOICE",+ "name": "Create voice",+ "description": "Open the Create Voice Apps UI. Call this immediately when the user asks to create a voice, call the Create Voice tool, or needs a local browser record/upload surface and no confirmed audio_media_id is already present. Do not ask the user to upload an audio file or provide the name in chat first; the widget collects the required name plus record/upload audio. If the user already has or attached an audio file in chat, still call this tool with initial_tab='upload' — remote tools cannot read Claude chat attachments, so the user re-selects the file in the widget's Upload tab (it uploads directly to Higgsfield). Do not try to pass a chat attachment or ask for a URL. The widget records/uploads, confirms the audio, and creates the voice itself end-to-end — and if the user is out of credits or on a free plan it shows the plans/credits UI inline. After the widget reports success you do NOT need to call create_voice_from_confirmed_audio again. Only call create_voice_from_confirmed_audio yourself when a confirmed audio_media_id is already present in the prompt and no UI step is needed."+ },+ {+ "slug": "HIGGSFIELD_MCP_CREATE_VOICE_FROM_CONFIRMED_AUDIO",+ "name": "Create voice from confirmed audio",+ "description": "Backend-only creation of a cloned voice from an already confirmed audio upload. Do not call this tool until audio_media_id and name are already known. For direct creation, first upload speech audio with media_upload, PUT the bytes, then call media_confirm with type='audio'. Pass that confirmed media_id here as audio_media_id plus a required name. If the user needs to record or upload local audio in an Apps UI-capable client, call create_voice instead; that widget records/uploads, confirms, and creates the voice itself, so you do not call this tool for the UI flow. The audio should be clear speech, roughly 10 seconds to 3 minutes, and no larger than the upload limit. The backend charges the voice-clone credit cost on successful creation. Cloning is asynchronous: on success the tool returns the new voice_id plus a status, and a fresh clone is usually still 'processing' and not yet usable. Use the returned voice_id with voice_type='element' for generate_audio or voice_change only once it is ready (status='completed' and is_audio_eligible=true). If status is 'processing' or is_audio_eligible is not true, the clone is still training — re-check it with list_voices before generating instead of submitting right away; status 'voice_clone_failed'/'failed' means cloning did not succeed. If recovery_tool is returned, call it immediately; do not explain/ask first."+ },+ {+ "slug": "HIGGSFIELD_MCP_CREATE_WEBSITE",+ "name": "Create website",+ "description": "Start a new full-stack website. Creates the website and a git repo: a React 19 + TanStack Start app, server-rendered, in ONE Cloudflare Worker, with D1 / R2 / KV / Durable Objects / Containers available (all DISABLED by default). Returns a website_id — pass it to every later website tool. The 'type' param is REQUIRED and is the USER'S choice, not yours: unless the user has already made it unambiguous, ASK the user whether they want a plain website (no Higgsfield integration) or a Higgsfield-integrated app (Sign in with Higgsfield + AI image/video generation via the Higgsfield SDK) BEFORE calling this tool. Apps are scaffolded from a v2 starter template and REQUIRE the 'template' param — pick the closest of studio / preset / app-detail per the template param's guide ('custom' is ONLY for when the user explicitly says \"use custom template\" — never pick it yourself). The chosen layout ships as real code already wired as the home page; you ADAPT IT IN PLACE, never rebuild it. Websites take an OPTIONAL template: pass 'scroll-scrub' for an animated website (its scrub engine ships pre-built) and omit it for a non-animated one. App and website templates are not interchangeable — a cross-kind name is rejected. Workflow: (0) call get_workflow_instructions with { workflow: \"website-builder-flow\" } FIRST to load the stack, design contract, and hard rules (REQUIRED before building or editing); (1) create_website; (2) call website_repo_access to get the repo's git URL + scoped token, clone/edit/commit/push with the terminal (for apps, read app/src/layouts/AGENTS.md + app/src/components/AGENTS.md right after cloning); (3) deploy_website to ship it live — and deploy again after ANY later change (publish_website only lists what is already live; it does not deploy)."+ },+ {+ "slug": "HIGGSFIELD_MCP_DEPLOY_WEBSITE",+ "name": "Deploy website",+ "description": "Build and deploy the website via CI, then return its live URL. Every deploy ships the live site at the website's public URL (there is no separate preview stage). IMPORTANT: commit and git push ALL your changes BEFORE calling this — the build runs from the pushed repo. Deploy again after ANY later change: publish_website does NOT deploy (it only lists the already-live build on the community feed), so this tool is the only way changes ship. A failed build returns the log; a still-running build returns status 'pending' — call website_status to check."+ },+ {+ "slug": "HIGGSFIELD_MCP_DUBBING",+ "name": "Dubbing",+ "description": "Dub a video into another language: translate the spoken audio, synthesize it in the target language, and lip-sync the result back onto the video. Use this when the user asks to dub, translate the speech of, or localize a clip into another language. Pass video_id for the source video (a confirmed uploaded media_id or a completed video generation job_id) and target_language as one of the supported language codes. Supported languages (code=language): eng=English, cmn=Chinese, fra=French, hin=Hindi, ita=Italian, jpn=Japanese, kor=Korean, por=Portuguese, rus=Russian, tur=Turkish, spa=Spanish, deu=German, ara=Arabic, pol=Polish, ind=Indonesian, fil=Filipino, swe=Swedish, fin=Finnish. This tool does not use prompt or count; output dimensions are taken from the source video automatically."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_3D",+ "name": "Generate 3d",+ "description": "Generate a 3D GLB mesh. Use `models_explore(type:'3d')` to pick a model and see its `medias[].roles` and `parameters`. Apps UI local file: call `media_upload_widget`; remote tools cannot read Claude chat attachments. Web media URL: call `media_import_url`, pass returned `media_id`; `medias[].value` must be media_id/job_id, not URL. Defaults: `image_to_3d` for general image-to-3D with optional texturing, PBR, and rigging; `multi_image_to_3d` when 2-4 views of the same subject are available (better geometric accuracy); `sam_3_3d` for single-object reconstruction; `3d_rigging` to rig an existing 3D model (takes `model_url`, not images — pass a prior 3D job_id or an https GLB URL). For animated rigs, search clip ids with the `animation_actions` tool and pass `animation_action_id` with `enable_animation:true`. The mesh reproduces only what is in the source image — to add or change props, clothing, or held objects, edit the image first with `generate_image`, then convert the edited result. Pass model-specific params as top-level fields. Apply `adjustments` returned by the server. If `recovery_tool` is returned, call it immediately. `get_cost:true` preflights credits without submitting."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_AUDIO",+ "name": "Generate audio",+ "description": "Generate one speech/voice request (text-to-speech) and render it in the generation widget. This tool accepts one prompt; for 2-12 independent lines or prompts, use the headless generate_audio_batch tool instead. DEFAULT model: seed_audio (Seed Audio 1.0 by ByteDance) — use it unless the user explicitly asks for a different engine. seed_audio takes a preset or reference-element voice (voice_type 'preset'|'element' + voice_id) plus optional tuning params (format, sample_rate, speech_rate, loudness_rate, pitch_rate), and can clone a voice from an audio_references media item or take an image_references cue. To use a specific named engine instead, set model:'text2speech_v2' and pass variant (one of elevenlabs|minimax|seed_speech|vibe_voice|cozy_voice) together with voice_type + voice_id. Get voice ids from list_voices; use models_explore(type:'audio') to inspect each model's params. This tool only generates speech: it cannot generate music or sound effects for general use, and there is no standalone music/SFX model here — decline general music or sound-effect requests rather than substituting a speech model. The models sonilo_music (music), mirelo_text_to_audio (sound effects) and inworld_text_to_speech (voice) exist ONLY for the game-generation pipeline and must not be used for standalone audio. get_cost:true preflights credits without submitting. use_unlim defaults false — pass true only when the user explicitly asks to use their unlimited/free-trial generations, never to save them credits on your own initiative."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_AUDIO_BATCH",+ "name": "Generate audio batch",+ "description": "Submit 1-12 independent audio generations in parallel without opening a widget. Each requests[] item accepts the same params as generate_audio, creates exactly one job, and keeps its caller-provided index in the response. Use for multiple distinct prompts or inputs; use generate_audio for one user-facing generation. Poll returned job IDs with jobs_wait in agent-chosen groups of at most 12. For larger sets, collect indexed jobs across submission batches. After every job in the user's set is terminal, pass the collected jobs to exactly one show_generation_by_ids call for up to 60 jobs; never use show_generations or call job_display once per job."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_IMAGE",+ "name": "Generate image",+ "description": "Generate one image request and render its result(s) in the generation widget. Use count 2-4 only for variants of the same prompt, inputs, and settings; for 2-12 independent image requests with different prompts or inputs, use the headless generate_image_batch tool instead. Apps UI local file media: call `media_upload_widget`; do not ask for Claude chat attachments because remote tools cannot read them. Web media URL: call `media_import_url`, then pass returned `media_id`; `medias[].value` must be media_id/job_id, not URL. Defaults: `marketing_studio_image` for commercial/product/ads; `soul_cast` for text-only character/avatar; `soul_2`+`soul_id` for trained reusable Soul; `soul_2`/`nano_banana_pro` for one-off character refs; `soul_2` for portraits/fashion/UGC/editorial; `nano_banana_pro` for 4K/text/diagrams. Ambiguous create-character/avatar: offer reusable Soul training (5-20 photos, ~10 min) vs one-off; do not train generic silently. Use `show_characters(action='train')` only if explicitly requested or user provides 5-20 photos. Use `models_explore` for aspect_ratios, params, medias roles. Top-level model params; apply `adjustments`. If `recovery_tool` returned, call it immediately; do not explain/ask first. `get_cost:true` preflights credits. `use_unlim` defaults false — pass true only when the user explicitly asks to use their unlimited/free-trial generations, never to save them credits on your own initiative."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_IMAGE_BATCH",+ "name": "Generate image batch",+ "description": "Submit 1-12 independent image generations in parallel without opening a widget. Each requests[] item accepts the same params as generate_image, creates exactly one job, and keeps its caller-provided index in the response. Use for multiple distinct prompts or inputs; use generate_image for one user-facing generation. Poll returned job IDs with jobs_wait in agent-chosen groups of at most 12. For larger sets, collect indexed jobs across submission batches. After every job in the user's set is terminal, pass the collected jobs to exactly one show_generation_by_ids call for up to 60 jobs; never use show_generations or call job_display once per job."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_VIDEO",+ "name": "Generate video",+ "description": "Generate one direct video request and render it in the generation widget. Use count 2-4 only for variants of the same prompt, inputs, and settings; use headless generate_video_batch for 2-12 independent requests. GENJUTSU TRIGGERS: route `Higgsfield Genjutsu` by intent. Copy, repeat, reproduce, mimic, or transfer motion, movement, actions, gestures, dance, or camera motion from one driving video to reference-image subjects -> `hf_mult_motion_control`. Replace, change, or swap an object, product, garment, or character in one source video from reference images -> `hf_mult_replace_object`. These are direct `generate_video` models, not legacy `motion_control` or `ad-multiplier`; reserve ad-multiplier for explicitly requested independent variants. Pass images with role `image` and exactly one source/driving video with role `video`. LOCAL/ATTACHED INPUT GATE: without confirmed media_id values, call `media_upload_widget` first as the only tool in that turn; never inspect /mnt/user-data/uploads, run shell, or ask for a chat attachment. For mixed image+video use type:`auto`, multiple:true. For web media call `media_import_url`; `medias[].value` must be media_id/job_id. Defaults: `marketing_studio_video` for ads/products, `clipify` for YouTube clips, `seedance_2_5` for general video, `kling3_0` for multi-shot, audio, or motion transfer, and `minimax_h3` for 2K keyframes or mixed references. Marketing Studio: fetch URL products with `show_marketing_studio(action='fetch')`; create uploaded-image products with type `product`. List missing hooks/settings before presets. Use declared media roles and model-supported audio only. Use models_explore for durations/params. Apply adjustments and immediately call any recovery_tool. get_cost:true preflights credits. Set use_unlim:true only when explicitly requested."+ },+ {+ "slug": "HIGGSFIELD_MCP_GENERATE_VIDEO_BATCH",+ "name": "Generate video batch",+ "description": "Submit 1-12 independent video generations in parallel without opening a widget. Each requests[] item accepts the same params as generate_video, creates exactly one job, and keeps its caller-provided index in the response. Use for multiple distinct prompts or inputs; use generate_video for one user-facing generation. Poll returned job IDs with jobs_wait in agent-chosen groups of at most 12. For larger sets, collect indexed jobs across submission batches. After every job in the user's set is terminal, pass the collected jobs to exactly one show_generation_by_ids call for up to 60 jobs; never use show_generations or call job_display once per job."+ },+ {+ "slug": "HIGGSFIELD_MCP_GET_EXPLAINER_PRESETS",+ "name": "Get explainer presets",+ "description": "Show the explainer video style presets (CMS-managed catalog). Returns preset ids, names, and preview media. When the user picks one, resolve it with resolve_explainer_preset to get the style reference media_id for generations."+ },+ {+ "slug": "HIGGSFIELD_MCP_GET_WORKFLOW_BUNDLE_FILE",+ "name": "Get workflow bundle file",+ "description": "Read a safe text file or directory from a workflow's resource folder. Use this after get_workflow_instructions when the SKILL.md requires a template, reference, or script file."+ },+ {+ "slug": "HIGGSFIELD_MCP_GET_WORKFLOW_INSTRUCTIONS",+ "name": "Get workflow instructions",+ "description": "Ad Multiplier — load workflow 'ad-multiplier' when the user asks to 'multiply my video', 'multiply my ad', create multiple independently edited versions of one supplied 4-30 second video, or regenerate the same ad with different people or products. Load this workflow before Marketing Studio, model browsing, or direct generation. Brand Asset Creation: for branded-asset work including logo recoloring/export, a branded PowerPoint/presentation deck, or analyzing an official brandbook to produce an asset, even when all inputs are supplied or no generation is needed, load 'brand-asset-creation' before sandbox_exec. Faceless video generation, AI-narrated video, narrated animated explainer video, narrated / personal / philosophical story video, YouTube/Instagram thumbnail or video cover, product photoshoot, packshot, studio or lifestyle product photography, product hero banner, product carousel, static product ad pack, virtual model product try-on, conceptual product still, or product-photo restyle, UGC-style ad for a website / SaaS / store / product page from its URL ('SaaS UGC'), any other UGC / creator-style short video for a product — a talking-head creator review (the default UGC ask), a product-only ad with no creator on camera, an unboxing / first-reaction / haul, a try-on / fit check / OOTD, a step-by-step tutorial with on-screen steps, a character sheet, character reference, model sheet, turnaround, expression sheet, or consistent multi-view character prompt, any branding work — a logo, visual identity, brand kit, brandbook, branded mockups, merchandise, packaging, signage, social graphics, posters, or banners ('brand-asset-creation'), including recoloring or exporting an existing official SVG/PNG logo even when no new design or image generation is requested, or building / editing a website, web app, landing page, or browser game with the website tools ('website-builder-flow'): before building ANY of these, use this tool to discover and load the bundled workflow (each a SKILL.md that orchestrates the generate_* tools). Call with NO argument to list available workflows and their triggers. Call with a workflow name to load that workflow's full SKILL.md plus the list of files readable via get_workflow_bundle_file."+ },+ {+ "slug": "HIGGSFIELD_MCP_JOB_DISPLAY",+ "name": "Job display",+ "description": "Show one specific previous generation in the single-result UI widget by job ID. Use when the user wants to inspect or re-display that individual result, including workflows that require separate approval of named candidates or individual previews before finalization. Do not call job_display once per job merely to reproduce an ordinary completed batch; use one show_generation_by_ids call for ordinary batch results instead."+ },+ {+ "slug": "HIGGSFIELD_MCP_JOB_STATUS",+ "name": "Job status",+ "description": "Check the status and results of an async job. Returns instantly. For non-terminal jobs the response includes poll_after_seconds — wait that many seconds before calling again. Typical total times: image ~10-20s, video ~60-180s."+ },+ {+ "slug": "HIGGSFIELD_MCP_JOBS_WAIT",+ "name": "Jobs wait",+ "description": "Long-poll 1-12 generation jobs together without opening a widget. Waits up to timeout_seconds (default 15, max 15) for every job to reach a terminal state, then returns compact indexed statuses and result URLs. Use job IDs returned by generate_image_batch, generate_video_batch, or generate_audio_batch. For larger sets, choose groups of at most 12 and wait for each group. Permanent lookup failures are returned once without blocking the other jobs; transient lookup failures are retried within the timeout. When all_terminal is false, wait poll_after_seconds before calling again. After every wait group in the user's generation set is terminal, collect their indexed jobs and display them with one show_generation_by_ids call when within that tool's limit. Never use show_generations or call job_display once per batch job."+ },+ {+ "slug": "HIGGSFIELD_MCP_LIST_VOICES",+ "name": "List voices",+ "description": "List available voices for speech and voice tools. Returns built-in preset voices plus the user's own custom voices. Each voice has a voice_id and a voice_type ('preset' or 'element'); pass that exact pair to the audio models (via generate_audio — seed_audio or text2speech_v2) and to the voice_change tool to select the speaking voice. Use the preview_url to hear a sample. Paginate with the returned next_cursor."+ },+ {+ "slug": "HIGGSFIELD_MCP_LIST_WEBSITE_CATEGORIES",+ "name": "List website categories",+ "description": "List the content categories a website can be filed under — each with a slug, label, description, and display position. create_website REQUIRES a `category`; call this first to get the valid slugs, then pass the closest one ('other' when nothing fits)."+ },+ {+ "slug": "HIGGSFIELD_MCP_LIST_WEBSITES",+ "name": "List websites",+ "description": "List the websites you own — each with its id, name, slug, and live URL. Use this to find the id of a website you created earlier so you can edit, deploy, or check its status."+ },+ {+ "slug": "HIGGSFIELD_MCP_LIST_WORKSPACES",+ "name": "List workspaces",+ "description": "List every workspace the user can access (their private workspace plus any shared/team workspaces). The `is_selected` field marks which workspace MCP operations currently target. Use when the user asks which workspaces they have, or wants to switch workspace."+ },+ {+ "slug": "HIGGSFIELD_MCP_MARKETING_STUDIO_V2_AVATARS",+ "name": "Marketing studio v2 avatars",+ "description": "Widget-internal: list the user's Marketing Studio avatars (preset and custom) for the avatar picker."+ },+ {+ "slug": "HIGGSFIELD_MCP_MARKETING_STUDIO_V2_COSTS",+ "name": "Marketing studio v2 costs",+ "description": "Widget-internal: the Marketing Studio v2 pricing document. credits = cost_units / cost_units_per_credit; video flows cost fixed_cost_units + cost_units_per_second × duration."+ },+ {+ "slug": "HIGGSFIELD_MCP_MARKETING_STUDIO_V2_CREATE",+ "name": "Marketing studio v2 create",+ "description": "Widget-internal: recreate a Marketing Studio v2 preset — validates inputs against the preset's recreate contract and submits one generation."+ },+ {+ "slug": "HIGGSFIELD_MCP_MARKETING_STUDIO_V2_PRESETS",+ "name": "Marketing studio v2 presets",+ "description": "Widget-internal: load a page of the Marketing Studio v2 preset feed for a category."+ },+ {+ "slug": "HIGGSFIELD_MCP_MARKETING_STUDIO_V2_STATUS",+ "name": "Marketing studio v2 status",+ "description": "Widget-internal: poll status and results of submitted Marketing Studio v2 jobs."+ },+ {+ "slug": "HIGGSFIELD_MCP_MEDIA_CONFIRM",+ "name": "Media confirm",+ "description": "Confirm file uploads after using media_upload's upload_url method. Call this only after every curl PUT returned HTTP 200. Supports confirming multiple uploads at once via media_ids. "+ },+ {+ "slug": "HIGGSFIELD_MCP_MEDIA_IMPORT_URL",+ "name": "Media import url",+ "description": "Import an HTTPS image, video, or audio URL into Higgsfield storage and return a confirmed media_id. Use this before generate_image/generate_video when the user provides a web media URL; generation medias should receive the returned media_id, not the original URL. Max URL payload: 50 MB."+ },+ {+ "slug": "HIGGSFIELD_MCP_MEDIA_UPLOAD",+ "name": "Media upload",+ "description": "Upload media for use in generation, or general files (documents, archives, code) for sharing. Returns presigned URLs for clients that can upload bytes themselves; run the generated curl commands or PUT the bytes to each upload_url, then call media_confirm. The media type is inferred from the filename extension: image/video/audio extensions become generation inputs; other whitelisted extensions (pdf, zip, tar, docx, csv, code files, …) are uploaded as general files and return a permanent URL, but cannot be used as generation inputs. General files are the agent's own upload path — the widget does not accept them, so upload the bytes to upload_url yourself (e.g. from a code execution environment). Supports batch uploads via files[]. Do not use this for user-provided local image/video/audio in Claude Apps UI-capable clients; call media_upload_widget instead so the user chooses the file in the Higgsfield widget and the browser uploads it directly."+ },+ {+ "slug": "HIGGSFIELD_MCP_MEDIA_UPLOAD_WIDGET",+ "name": "Media upload widget",+ "description": "Required local-media intake for Higgsfield in Apps UI-capable clients. Call this immediately as the only tool in the turn when the user refers to an attached/local photo, image, video, or audio but the prompt has no confirmed media_id yet. Do not inspect /mnt/user-data/uploads, run shell/sandbox commands, or ask the user to attach the file in Claude chat; remote MCP tools cannot read chat attachments. This widget is the upload surface: the user re-selects one or more files in the browser, the browser uploads them directly to Higgsfield storage, the widget confirms them, then sends the confirmed media_id/media_ids back to Claude for the next generation or analysis tool call. Use type auto with multiple enabled when one request needs mixed media, such as reference images plus a driving video; one video and one audio file may be combined with multiple images. The widget accepts media only; for general files (archives, documents, code) use media_upload instead and upload the bytes to the presigned upload_url yourself."+ },+ {+ "slug": "HIGGSFIELD_MCP_MODELS_EXPLORE",+ "name": "Models explore",+ "description": "Find generation models. Use recommend with goal + input context; use get for model constraints. Items carry supports_unlim when the model accepts free-trial unlimited generations; the top-level unlim block says whether the caller can spend them right now, and the trailing 'Unlim configs' text lists the configurations their allowance actually covers."+ },+ {+ "slug": "HIGGSFIELD_MCP_MOTION_CONTROL",+ "name": "Motion control",+ "description": "Animate an existing character image with the motion and camera movement from a reference video using Kling 3.0 Motion Control. Use this when the user asks to recast, puppeteer, transfer motion, or make a character follow a driving clip. Pass image_id for the character still and motion_video_id for the reference motion video; each can be a confirmed uploaded media_id or a completed generation job_id. This tool does not use prompt or count; the scene prompt and background setup are handled automatically. resolution controls output quality, and scene_control chooses whether the background is based on the image or the video."+ },+ {+ "slug": "HIGGSFIELD_MCP_OUTPAINT_IMAGE",+ "name": "Outpaint image",+ "description": "Expand or uncrop an existing image by outpainting beyond the original frame while preserving the source content. Use this when the user asks to extend the background, make an image wider or taller, change the canvas shape, or fill new edges around an image. Pass image_id for the source image and aspect_ratio for the target canvas. Optional width and height can be provided together; otherwise they default from aspect_ratio. This tool does not use prompt or count. Set params.get_cost=true to estimate credits without submitting a job."+ },+ {+ "slug": "HIGGSFIELD_MCP_PARTICIPATE_IN_CONTEST",+ "name": "Participate in contest",+ "description": "Enter the website in the current Higgsfield app contest, together with the social-media links promoting it. A website not yet PUBLISHED to the community feed is published automatically by the entry — no need to call publish_website first. The website DOES need a live production deploy (deploy_website), else the entry is rejected. BEFORE entering, make sure the page metadata in app/src/app-meta.json is filled with real values (og_title etc.) — the auto-publish lists the website on the feed and an empty og_title makes it INVISIBLE there. Pass one or more urls, each a social-media link (YouTube, X/Twitter, Instagram, or TikTok); any other host is rejected. There is a single active contest, so no contest id is needed. Calling again for the same website OVERWRITES its urls (use it to fix or add links), it does not create a second entry."+ },+ {+ "slug": "HIGGSFIELD_MCP_PERSONAL_CLIPPER_CREATE",+ "name": "Personal clipper create",+ "description": "Turn YouTube videos into ready-to-share clips. This is a long-running job and can take up to 30+ minutes. Before starting, ask the user how many clips they want, which clip aspect ratio to use, and which subtitle font they prefer."+ },+ {+ "slug": "HIGGSFIELD_MCP_PERSONAL_CLIPPER_JOBS",+ "name": "Personal clipper jobs",+ "description": "Show recent clipping jobs."+ },+ {+ "slug": "HIGGSFIELD_MCP_PERSONAL_CLIPPER_STATUS",+ "name": "Personal clipper status",+ "description": "Check clip creation progress."+ },+ {+ "slug": "HIGGSFIELD_MCP_PRESETS_SHOW",+ "name": "Presets show",+ "description": "Show available Higgsfield presets for image-to-video generation. Returns preset ids, names, previews, and descriptions."+ },+ {+ "slug": "HIGGSFIELD_MCP_PUBLISH_WEBSITE",+ "name": "Publish website",+ "description": "Publish the website: lists the website's CURRENT LIVE production deploy on the Higgsfield community feed ('show in feed'), where other users can discover it. This does NOT deploy — deploy_website (which every build flow already runs) must have shipped the latest changes first; publishing with undeployed changes lists the OLD live build, and re-publishing does not re-deploy. BEFORE publishing, the page metadata in app/src/app-meta.json MUST be filled with real values — og_title, og_description, favicon_url, og_image_url — the feed card renders from them (read fresh from the pushed repo at publish time) and a website with an empty og_title is INVISIBLE on the feed; the live page's own head tags are baked at build time, so deploy AFTER changing them. Also OFFER the user a cover video for the card (og_video_url) — ask their permission first (video generation costs credits), never generate it unprompted. Commit and git push the metadata (and all other changes), then deploy, BEFORE calling this. Publish when the user asks to publish / share / go live on the feed, OR when they opted in to publishing at the start of the build — in that case publish automatically once the site is deployed with its metadata filled, without waiting to be asked again. For a plain deploy without a feed listing use deploy_website instead. EXCEPTION: a website whose production was never deployed (or was taken down by unpublish) falls back to deploying first — that returns status 'pending' while CI runs and the website is listed automatically once the deploy succeeds (check with website_status)."+ },+ {+ "slug": "HIGGSFIELD_MCP_REFRAME",+ "name": "Reframe",+ "description": "Expand or reframe an existing video to a new aspect ratio while preserving the source content. Use this when the user asks to make a video vertical, horizontal, square, wider, taller, or fill new edges around a video. Pass medias with exactly one source video and aspect_ratio for the target canvas. Optional image references can guide the filled area; optional start_image can pin the first frame when the user provides a first-frame anchor. For source videos over 15 seconds, pass duration_seconds and resolution and use only the source video. This tool does not use prompt or count. Set params.get_cost=true to estimate credits without submitting a job."+ },+ {+ "slug": "HIGGSFIELD_MCP_REMOVE_BACKGROUND",+ "name": "Remove background",+ "description": "Remove or cut out the background from an existing image or video. Use this when the user asks for background removal, a transparent background, an isolated subject, a clean cutout, or a subject-only asset. Pass media_id for the source media and media_type as image or video; the matching background remover is selected automatically. This tool does not use prompt, count, or style parameters."+ },+ {+ "slug": "HIGGSFIELD_MCP_RENAME_WEBSITE",+ "name": "Rename website",+ "description": "Rename the website's SUBDOMAIN (the slug in its public URL). The site is re-deployed under the new subdomain and the OLD subdomain STOPS WORKING — anyone holding the old URL must be given the new one. Storage (database, files, config) and the code repo are KEPT; only the public address changes. Runs a full re-deploy and can take a couple of minutes; returns once the site is live at the new URL. Fails if the new subdomain is already taken or reserved, or if a deploy is already in flight — pick another subdomain and retry."+ },+ {+ "slug": "HIGGSFIELD_MCP_RESOLVE_EXPLAINER_PRESET",+ "name": "Resolve explainer preset",+ "description": "Resolve a explainer video style preset (from get_explainer_presets) into a style reference media_id: the backend imports the preset's style image into the user's media storage. Pass the returned media_id as the style reference image in generation calls for every scene of the explainer."+ },+ {+ "slug": "HIGGSFIELD_MCP_REVEAL_GENERATION",+ "name": "Reveal generation",+ "description": "Confirm the user has rights to the content of an `ip_detected` generation and flip its status to `completed`. Backend accepts only seedance-family jobs (cs_3_0, seedance_2_0, ms_video, etc) and only while the job is still in `ip_detected` state. Returns the updated generation. Used by the job-list widget's Reveal button after the user accepts the rights confirmation modal."+ },+ {+ "slug": "HIGGSFIELD_MCP_SANDBOX_EXEC",+ "name": "Sandbox exec",+ "description": "Execute a shell command in a remote Higgsfield cloud Linux sandbox — NOT your local machine or the client's own shell. Whenever a task needs shell tooling (ffmpeg, image/file conversion, scripting), use this tool, never a built-in or local bash/shell tool: only this sandbox has the media toolchain preinstalled and can reach the user's Higgsfield media. Preinstalled: ffmpeg/ffprobe, ImageMagick, sox, python3 with Pillow and faster-whisper, node/npm/npx, sharp-cli, Playwright with headless Chromium, caption fonts (Metropolis, Montserrat), zip/unzip, git, curl, jq. Use it for media processing (trim, convert, overlay, concat with ffmpeg), image manipulation, file conversion, scripting, and packaging that dedicated tools don't cover. The sandbox is isolated per user and is discarded ~10 seconds after a call finishes, so files in /home/user only survive between back-to-back calls — chain multi-step work into a single command (&&) and export results before finishing, or expect to re-download inputs. It has internet access: bring files in with curl from media URLs (media_import_url or generation results). For an output created here, call media_upload BEFORE starting the producing command, then append `curl -f -X PUT --upload-file <file> '<upload_url>'` to that SAME command so the ephemeral file is uploaded before it exits; call media_confirm only after HTTP 200. Never pass a sandbox path to media_upload_and_confirm: that tool accepts only client attachments. Commands run in /home/user and time out after timeout_seconds (default 60, max 120); for longer work (large renders, installs) set background:true and poll the returned log/status files with later sandbox_exec calls. Background work receives a 15-minute sandbox lease, and shorter poll calls never reduce its remaining lifetime. Set restart:true to discard the sandbox and start clean. Workflow bundle scripts are already installed in every sandbox under $HF_WORKFLOWS (/home/user/.higgsfield/workflows), laid out as $HF_WORKFLOWS/<workflow>/scripts/... — run them straight from there (they survive restart:true), and never paste script contents into the command."+ },+ {+ "slug": "HIGGSFIELD_MCP_SELECT_WORKSPACE",+ "name": "Select workspace",+ "description": "Set or clear the active workspace — the one all subsequent MCP operations bill against and read from (generations, balance, transactions, uploads, custom references). How to work with workspaces: (1) call `list_workspaces` first to see the user's workspaces with their `id`, plan, available credits, and which one is currently active (`is_selected`); (2) call `select_workspace` with the chosen `workspace_id` to switch — e.g. to run and bill work under a shared/team workspace instead of the private default; (3) call again with `clear: true` to return to the default private workspace. The selection persists across sessions and clients until changed or cleared, so it stays in effect for later turns without re-selecting. When the user belongs to more than one workspace, confirm which one to use before billable operations. Returns an error if the workspace doesn't exist or the user isn't a member."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHORTS_STUDIO_CREATE",+ "name": "Shorts studio create",+ "description": "Start a Shorts Studio short: restyle one uploaded source video (4s–120s) into a set of AI-generated short-form clips using a style preset. PAID — reserves credits. Prerequisites, gathered in whatever order fits the conversation: (1) a style preset — pick one via shorts_studio_list_presets or make one with shorts_studio_create_preset; (2) a source video — an uploaded video_input id from media_upload_widget (type=video). If the user hasn't provided a source video yet, ask them to upload one before calling this. Output orientation defaults to 9:16 (vertical); pass aspect_ratio:'16:9' for horizontal. Returns a session with empty job_ids; poll shorts_studio_status until clips appear. Set get_cost=true with duration_seconds to estimate the credit cost without submitting a job — no preset or source video needed for the estimate."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHORTS_STUDIO_CREATE_PRESET",+ "name": "Shorts studio create preset",+ "description": "Create a user-owned Shorts Studio style preset from reference media (videos + images). This just stores a STYLE — no generation, no credits. Reference media must be public https URLs (use an uploaded media's url or media_import_url first). Limits: ≤10 media total, each video's duration ≤30s (send `duration` so the cap applies). Returns the id and preset_source to feed into shorts_studio_create. If the user did not give a name, invent a random friendly two-word name yourself (e.g. 'Amber Drift', 'Neon Tide', 'Velvet Dusk') — never leave it blank or ask."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHORTS_STUDIO_LIST_PRESETS",+ "name": "Shorts studio list presets",+ "description": "Browse Shorts Studio style presets — the visual STYLE a short is restyled toward. Use this when the user wants to make a short and needs to choose a look: they can pick one of these or create their own style with shorts_studio_create_preset. Returns the user's own presets first, then the CMS library; each item carries a `preset_source` to pass straight into shorts_studio_create. Paginated: if next_cursor is not null, pass it as cursor to get the next page."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHORTS_STUDIO_LIST_SESSIONS",+ "name": "Shorts studio list sessions",+ "description": "List the caller's past Shorts Studio sessions (newest first) to find a session_id to poll with shorts_studio_status."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHORTS_STUDIO_STATUS",+ "name": "Shorts studio status",+ "description": "Poll one Shorts Studio session. Returns {id, status, job_ids}. status='completed' means every clip job is terminal (not necessarily successful). Poll each job_id via job_status for its clip video url and per-clip status."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_CHARACTERS",+ "name": "Show characters",+ "description": "Soul Characters widget — reusable trained identity models. Actions: `list` (browse), `train` (needs `name` + 5-20 ref images, ~10 min, non-blocking — widget polls), `status` (inspect by `soul_id`). Presence of `name`/`images`/`medias` ⇒ train mode. Call `train` only on explicit ask for a reusable Soul / digital twin / identity, or when 5+ ref photos are supplied.\nRef images accept: media_id UUIDs from media_confirm, completed image-job IDs, or https URLs. Never local paths — upload via media_upload → PUT bytes → media_confirm first.\n\nCONSTRAINTS:\n- Trained Soul is usable ONLY with `soul_2` (Soul V2) and `soul_cinematic` (Soul Cinema). For any other model, the user needs `show_reference_elements`.\n- ONE soul_id per generation. Multi-character shots ('me + friend', 'two people') must use `show_reference_elements` (supports multiple `<<<UUID>>>` placeholders).\n\nAMBIGUITY GUARD — character/avatar/digital-twin/'use my face' requests without a chosen path: do NOT call this tool yet; ask the user to pick:\n 1. Train Soul (this tool) — identity-faithful, ONE person, 5-20 photos, ~10 min, Soul V2 / Cinema only.\n 2. Save as Element (`show_reference_elements` action=create) — instant, single image, multiple subjects allowed, works with Nano Banana Pro / 2, GPT Image 2, Seedream 4.5 / 5 lite, Cinema Studio Image 2.5, Cinema Studio Video 2 / 3.0, Seedance 2.0, Kling 3.0.\n→ Soul signals: 'train' / 'digital twin' / 'identity' / 5+ photos of same person. → Force Elements: >1 character in shot, non-person subject, single image, mention of a non-Soul model, instant result wanted.\n\nAfter ready: `generate_image` with `model: 'soul_2'` (or `soul_cinematic`) + the returned `soul_id`."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_GENERATION_BY_IDS",+ "name": "Show generation by ids",+ "description": "Render exactly 1-60 requested generation jobs in the full-profile gallery widget, ordered by index and paginated locally in groups of 12. Use once every jobs_wait group is terminal for generate_image_batch, generate_video_batch, or generate_audio_batch. Pass the complete indexed set collected from the batch tools. This tool fetches only those job IDs in bounded groups: it never loads generation history, uses cursors, requests additional pages, or adds other jobs. Do not use show_generations or job_display to present a completed batch."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_GENERATIONS",+ "name": "Show generations",+ "description": "Browse completed non-Marketing Studio generation history and render one paginated page in the gallery widget. Returns generations with {id, type, status, model, params, results}. Use only when the user explicitly asks to browse regular generation history. Do not use this history tool after generate_*_batch or jobs_wait; show an exact completed batch with one show_generation_by_ids call instead. Use show_marketing_studio_generations for Marketing Studio video/image/ad history. Pass a prior generation's id as value in the medias array of a new generation to reuse it. Use job_display only to inspect one specific previous result. Paginated: if next_cursor is not null, pass it as cursor to get the next page."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_MARKETING_STUDIO_GENERATIONS",+ "name": "Show marketing studio generations",+ "description": "Browse past completed Marketing Studio generations only. Returns Marketing Studio video and ad/image generations with {id, type, status, model, params, results}. Use show_generations for non-Marketing Studio image/video history."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_MARKETING_STUDIO_V2",+ "name": "Show marketing studio v2",+ "description": "Open Marketing Studio — a template gallery widget with category tabs (UGC ads, product shots, motion graphics, posters, ads, marketplace) and a preset grid the user browses and recreates from with their own product image. Use this whenever the user asks for Marketing Studio or wants marketing assets from a template/preset catalog. The widget handles preset selection, inputs, generation, and result display itself — no follow-up tool calls needed."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_MEDIAS",+ "name": "Show medias",+ "description": "List your uploaded media files by type. Returns media IDs, URLs, and creation timestamps. Call once with the single type the user asked for (default image); do not enumerate the other types unless the user explicitly asks for them. Pass media IDs as value in the medias array of generation tools. Paginated: if next_cursor is not null, pass it as cursor to get the next page."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_PLANS_AND_CREDITS",+ "name": "Show plans and credits",+ "description": "Open the single combined pricing widget for everything billing-related. The widget has two tabs the user can switch between: **Upgrade Plan** (Plus + Ultra, monthly + annual subscription cards) and **Top-up Credits** (one-time credit packs of 500 / 1,000 / 2,000 / 4,000 credits). Cards include feature lists, 7-Day Unlimited highlights, and 365-Day Unlimited blocks pulled from the live pricing config. Each plan card and credit pack has a CTA that links directly to the relevant Stripe or Higgsfield checkout/setup URL — no separate tool is needed to mint checkouts. For every billing request, the text response and `assistant_response` are intentionally short, user-facing sales copy with checkout URLs wrapped as action-specific Markdown links such as `[Go to Checkout](url)`, `[Higgsfield Upgrade](url)`, `[Higgsfield Credit Top-up](url)`, `[Higgsfield Auto-refill](url)`, `[Higgsfield Team Top-up](url)`, or `[Higgsfield Team Auto-refill](url)`; relay that response verbatim instead of summarizing, saying only that the widget opened, or listing options without links. If the user asks to buy credits or they are out of credits, first push auto-refill when `auto_refill_purchase_link` is present, then show `credit_purchase_links`. If the user asks to upgrade or a minimum plan is required, show `plan_purchase_links`. Pass `intent='auto_refill'` for out-of-credits recovery, `intent='topup'` for one-time credit packs, `intent='upgrade'` for plan upgrades, or `intent='trial'` when the user specifically asks for the free trial so the response is ordered for that purchase path. FREE TRIAL: when `free_trial` is present in the response, the user is eligible for a 3-day $0 Plus trial with MCP-only credits — the widget shows it and the text response leads with it. In text-only clients ALWAYS relay `free_trial.compliance_note` verbatim (MCP-only, card required, automatic charge after the trial unless cancelled, how to cancel by saying 'cancel auto-renewal'). When `free_trial` is absent, NEVER speculate about trial eligibility or mention fraud/abuse checks — present the paid plans neutrally. When `initial_view='trial_upgrade'`, the user's trial credits are exhausted: relay the numbered upgrade options plus the renewal reminder, and mention that saying 'cancel auto-renewal' stops the upcoming charge while keeping trial access. To cancel the trial's auto-renewal, call `cancel_trial_auto_renewal` instead of this tool. Use this tool for ANY of these requests: plans, pricing, subscriptions, upgrade options, comparing tiers, buying credits, topping up credits, refilling credits, credit packs. Do not look for separate `show_plans` or `show_credit_topups` tools — both have been merged into this one. Returns `already_subscribed: true` when the workspace is already on a paid plan; the widget hides the Upgrade tab in that case and shows only credit top-ups. Team-plan workspaces: `workspace_kind` field indicates the context. When `workspace_kind='team_owner'`, the widget renders team-specific Top-up and Auto-refill UIs and emits `team_purchase_links` (two links: `team_top_up` and `team_auto_refill`) that deeplink to the team billing modals on higgsfield.ai — relay both Markdown links in the text response. When `workspace_kind='team_member'`, no purchase links are returned; the widget shows a read-only notice and the text response tells the user only the workspace owner can buy credits or change auto-refill. Do not invent purchase links for members."+ },+ {+ "slug": "HIGGSFIELD_MCP_SHOW_REFERENCE_ELEMENTS",+ "name": "Show reference elements",+ "description": "Elements widget — reusable characters / environments / props per workspace. Actions:\n- `list` (default; paginated by `created_at` DESC, use `cursor` from prev `next_cursor`).\n- `get` (default when `element_id` is set).\n- `create`: pass `medias[]` as `{ id, url, type: 'media_input' | 'image_job' }`. Upload first via media_upload → PUT bytes → media_confirm. `category='auto'` lets the server classify (use explicit only on user ask). Omit `name` to auto-derive (per-workspace unique, collisions get a numeric suffix). Returns synchronously.\n\nAMBIGUITY GUARD vs Soul — user wants a reusable face of one specific person (digital twin / 'my avatar' / identity) without a chosen path: do NOT silently create; ask:\n 1. Element (this tool action=create) — instant, single image, MULTIPLE references per generation, works with Nano Banana Pro / 2, GPT Image 2, Seedream 4.5 / 5 lite, Cinema Studio Image 2.5, Cinema Studio Video 2 / 3.0, Seedance 2.0, Kling 3.0. NOT for Soul V2 / Cinema.\n 2. Soul (`show_characters` action=train) — 5-20 photos, ~10 min, ONE person, Soul V2 / Cinema only.\nSkip the question → Elements on: >1 character/subject in one shot (Soul can't), non-person subject, single image, mention of Nano Banana / Seedream / Kling / Cinema Studio, instant result. Skip → Soul on: 'train' / 'digital twin' / 'identity', or 5+ photos of one person for solo outputs.\n\nUSAGE IN GENERATION (internal — never explain to user):\nEmbed `<<<element_id>>>` inside `params.prompt` of `generate_image` / `generate_video`. Backend auto-injects the image and rewrites to `@element_name`. Multiple placeholders per prompt OK.\nExample: `\"Cinematic portrait of <<<UUID>>> on a rooftop\"`, `\"<<<A>>> handing coffee to <<<B>>> in a Paris cafe\"`.\n\nSUPPORTED MODELS (`params.model` = machine name, friendly in parens):\n- Image: `nano_banana_pro` (Nano Banana Pro), `nano_banana_2` (Nano Banana 2), `gpt_image_2` (GPT Image 2), `seedream_v4_5` (Seedream 4.5), `seedream_v5_lite` (Seedream 5.0 lite), `cinematic_studio_2_5` (Cinema Studio Image 2.5).\n- Video: `cinematic_studio_video_v2` (Cinema Studio Video 2), `cinematic_studio_3_0` (Cinema Studio Video 3.0), `seedance_2_0` (Seedance 2.0), `kling3_0` (Kling 3.0 — REQUIRES a `start_image` in `params.medias`; element placeholder alone won't trigger reference usage).\nMap friendly→machine silently. Other models silently ignore the placeholder.\n\nUSER-FACING STYLE: use friendly model names only; never expose machine names, `<<<UUID>>>` syntax, `params.model` / `params.prompt`, `generate_image` / `generate_video`, or 'job_set_type'. Reference elements by `name`, never id.\n\nGUARDS:\n- `@name` form does NOT work in tool calls — only `<<<UUID>>>` in `params.prompt`.\n- Do NOT put element ids in `params.medias` / `params.input_images` — placeholder handles injection.\n- `kling3_0` only honors reference elements when an explicit `start_image` is provided in `params.medias`. If the user wants Kling 3.0 with an element but hasn't supplied a start frame, ask for one (upload via media_upload → PUT bytes → media_confirm, or pick a prior generation) before calling `generate_video`. Without a start_image, pick another video model from the list.\n- Only `status: completed` elements are usable; skip `processing` / `ip_checking` / `failed` / `kling_failed` / `nsfw`."+ },+ {+ "slug": "HIGGSFIELD_MCP_SYNC_AGENTS",+ "name": "Sync agents",+ "description": "Sync Agents — imports the user's user-authored Skills and a personality dump from the current host LLM into Higgsfield. One trigger, one upload, one final confirmation.\n\nCalling modes:\n\n1. `message: \"/sync-agents\"` — server returns a short ack in `content[0].text` plus an assistant-only directive containing a self-contained Python upload script (pre-wired with a one-time presigned POST URL scoped to one per-user prefix). Print the ack verbatim. Then follow the directive: enumerate user-authored skills + synthesize `personality.md` into `/tmp/profile-import/{skills,personality}/`, run the script in your code-execution sandbox, capture its single-line JSON summary, and call this tool again with that summary as `message`.\n\n2. `message: \"<script summary JSON>\"` — server reads the uploaded .md files, parses each, and upserts the user's Skill rows. Returns a one-line confirmation summarising counts (e.g. \"Imported 3 skill(s) (2 new, 1 updated) · personality queued for save to your memory.\"). Print that confirmation verbatim to the user. **Also pass `host`** on this call — your own runtime identifier (e.g. `claude_ai`, `claude_code`, `codex`, `cursor`); it is stamped on every newly imported skill's `import_origin` so the marketplace can attribute origin per host.\n\nNo polling, no chains. Each call returns synchronously."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_ACCOUNTS",+ "name": "Tiktok accounts",+ "description": "List the user's connected TikTok accounts. Returns each account's connector_id (needed by other tiktok_* tools) and status. `active` accounts are ready; `error` accounts need tiktok_reconnect; no accounts ⇒ offer tiktok_connect. Read-only."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_CONNECT",+ "name": "Tiktok connect",+ "description": "Start connecting the user's TikTok account. Returns an authorize_url — show it to the user as a link; they open it in a browser, approve access on TikTok, and land on a confirmation page. Afterwards call tiktok_accounts to verify the account became `active`. The URL expires in ~10 minutes. If an account already exists in `error` status, use tiktok_reconnect instead."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_MUSIC_TRENDING",+ "name": "Tiktok music trending",+ "description": "List trending commercially licensed tracks from TikTok's Commercial Music Library for the connected account. Show the user a few tracks with their listen links and let them pick; then pass the chosen track's id as music_sound_id to tiktok_publish. Music works for DIRECT_POST only (TikTok drafts don't keep it). There is no keyword search — offer genre/country/date_range filters instead. Read-only."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_MUSIC_TUNE",+ "name": "Tiktok music tune",+ "description": "Open the tuning editor for one Commercial Music Library track the user already picked (via tiktok_music_trending): trim start/end and set track/original volumes. Pass the same genre/country_code/date_range filters that were used when the track was found, or the lookup may miss. The user copies the final configuration from the editor and pastes it into the chat; pass those values to tiktok_publish. Read-only."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_PREPARE_PUBLISH",+ "name": "Tiktok prepare publish",+ "description": "Step 1 of publishing to TikTok. Validates the media and TikTok account, creates a publish session, and returns what the user must review and choose (preview, privacy options, required declarations, confirmations). The media URL must be a Higgsfield-hosted asset (TikTok requires a verified source domain). Then collect the user's choices and call tiktok_publish. mode=DIRECT_POST posts to the profile; mode=UPLOAD_TO_DRAFT saves to the user's TikTok drafts. MEDIA LIMITS — check before calling, and convert or downscale locally if a file does not comply; a rejected file costs a full convert-and-re-upload round trip, and TikTok rejects some files only asynchronously, after the post was submitted. Photos: JPEG or WebP only (PNG is rejected by TikTok, and Higgsfield image generation emits PNG — convert first), each at most 20 MB, resolution must fit within 1920x1080 or 1080x1920, up to 35 images. Videos: MP4, WebM or MOV, at most 1 GB, 3-600 seconds, at least 360 px on both sides, 23-60 FPS."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_PUBLISH",+ "name": "Tiktok publish",+ "description": "Step 2 of publishing. Call only after tiktok_prepare_publish and after collecting the user's explicit choices and confirmations. Pass the publish_session_id from prepare (the media is locked to it — do not resend URLs). Set every flag listed in the prepare response's required_confirmations to true; these represent real user consent (AIGC/branded-content/music/privacy). Optionally attach a commercial track via music_sound_id from tiktok_music_trending (DIRECT_POST only). Returns a publish_id for tiktok_publish_status. PUBLISH QUOTAS per account, enforced before TikTok is called: at most 5 posts per minute and 13 posts per 24 hours, both rolling (TikTok's own ceiling is 6/minute and 15/day). A rejection returns code=cadence_burst or cadence_daily plus retry_after_seconds — wait that long instead of retrying, since retrying sooner only earns another rejection. Failed attempts and drafts do not consume quota; a post TikTok accepted does. Duration, frame size and frame rate are measured from the media file itself by tiktok_prepare_publish, before a publish slot is spent — there is no duration argument, never ask the user for one. music_sound_volume, video_original_sound_volume, music_sound_start and music_sound_end apply only together with music_sound_id and only to videos; without a track, or on a photo post, they are ignored. MEDIA LIMITS — check before calling, and convert or downscale locally if a file does not comply; a rejected file costs a full convert-and-re-upload round trip, and TikTok rejects some files only asynchronously, after the post was submitted. Photos: JPEG or WebP only (PNG is rejected by TikTok, and Higgsfield image generation emits PNG — convert first), each at most 20 MB, resolution must fit within 1920x1080 or 1080x1920, up to 35 images. Videos: MP4, WebM or MOV, at most 1 GB, 3-600 seconds, at least 360 px on both sides, 23-60 FPS."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_PUBLISH_STATUS",+ "name": "Tiktok publish status",+ "description": "Step 3 of publishing. Fetch processing status for a publish_id returned by tiktok_publish. TikTok may take a few minutes to process before the post is live. Read-only."+ },+ {+ "slug": "HIGGSFIELD_MCP_TIKTOK_RECONNECT",+ "name": "Tiktok reconnect",+ "description": "Re-run the TikTok OAuth for an existing connector in `error` status (expired/revoked access). Returns a fresh authorize_url — show it to the user as a link, then verify with tiktok_accounts."+ },+ {+ "slug": "HIGGSFIELD_MCP_TRANSACTIONS",+ "name": "Transactions",+ "description": "List the user's credit transactions (spend/refund/grant/deduct), newest first. Paginated: if next_cursor is not null, pass it as cursor to get the next page."+ },+ {+ "slug": "HIGGSFIELD_MCP_UPSCALE_IMAGE",+ "name": "Upscale image",+ "description": "Upscale and enhance an existing image. Use this when the user asks to upscale, enhance, or increase the resolution of an image to 2K/4K. This tool does not use prompt or count. Provider selects the upscale backend; currently only 'bytedance' is supported (the default). You MUST pass the source image's width and height in pixels (the caller supplies them; the server does not infer them). Set params.get_cost=true to preflight credits (flat cost) without submitting a job."+ },+ {+ "slug": "HIGGSFIELD_MCP_UPSCALE_VIDEO",+ "name": "Upscale video",+ "description": "Upscale and enhance an existing video. Use this when the user asks to upscale, enhance, sharpen, denoise, restore, or convert a video to higher resolution. This tool does not use prompt or count, and does not support cost preflight. Choose a provider: 'bytedance' (preset-based, target 1080p/2K/4K — you MUST pass the source video width/height in pixels and may set fps to 24/30/60) or 'topaz' (Topaz Video, aspect-ratio based, target 1080p/2160p — no source dimensions needed)."+ },+ {+ "slug": "HIGGSFIELD_MCP_VIDEO_ANALYSIS_CREATE",+ "name": "Video analysis create",+ "description": "Start a scene-by-scene analysis of a video. Provide EXACTLY ONE of: (a) video_input_id — UUID of a video the user has uploaded via media_upload/media_confirm, or (b) youtube_url — a YouTube link (youtube.com / youtu.be hosts only). Returns immediately with status='queued'; poll video_analysis_status until status='completed'. Processing typically takes 3-5 minutes on average. IMPORTANT: warn the user up front that the longer the video, the less accurate the scene-by-scene analysis becomes — short clips give the most reliable results."+ },+ {+ "slug": "HIGGSFIELD_MCP_VIDEO_ANALYSIS_JOBS",+ "name": "Video analysis jobs",+ "description": "List the user's video analyses in the current workspace, newest first. Paginate by passing the previous response's cursor."+ },+ {+ "slug": "HIGGSFIELD_MCP_VIDEO_ANALYSIS_STATUS",+ "name": "Video analysis status",+ "description": "Get the status and result of a video analysis. Poll this after video_analysis_create until status='completed' (scenes populated) or 'failed' (fail_reason populated). Analyses typically finish in 3-5 minutes — poll accordingly every 30-60 seconds."+ },+ {+ "slug": "HIGGSFIELD_MCP_VIRALITY_PREDICTOR",+ "name": "Virality predictor",+ "description": "Virality Predictor predicts a video's virality potential, engagement, attention, audience response, retention risk, hook strength, and creative performance with an interactive dashboard. Use when the user asks whether a video can go viral or wants creative-performance analysis. Create starts analysis from a confirmed uploaded video or completed generated video; preview re-opens an existing dashboard."+ },+ {+ "slug": "HIGGSFIELD_MCP_VOICE_CHANGE",+ "name": "Voice change",+ "description": "Replace the spoken voice in a video with a different voice while keeping the original timing and visuals, then re-merge the new audio onto the video. Use this when the user asks to change, swap, or revoice the speaker in a clip. Pass video_id for the source video (a confirmed uploaded media_id or a completed video generation job_id) and voice_id for the target voice. voice_type selects whether voice_id is a built-in preset voice ('preset') or a workspace reference element ('element'). This tool does not use prompt or count; output dimensions are taken from the source video automatically."+ },+ {+ "slug": "HIGGSFIELD_MCP_WEBSITE_DB",+ "name": "Website db",+ "description": "Inspect the website's database (D1 / SQLite), READ-ONLY. The website has ONE database — the live site's real data. Pick an operation: 'tables' (list tables); 'schema' (a table's columns — needs table); 'rows' (a page of rows — needs table; optional filters, order_by + order_dir, limit (default 50) + offset); 'query' (one read-only SELECT/WITH — needs sql). Writes and DDL are rejected."+ },+ {+ "slug": "HIGGSFIELD_MCP_WEBSITE_REPO_ACCESS",+ "name": "Website repo access",+ "description": "Get direct git access to a website's repo to edit it — THE way to get the website's code. Returns the repo URL, branch, slug, and a scoped token; clone it with the terminal tool, edit files, commit + push, then call deploy_website. Clone into a directory named after the slug so multiple websites can share the workspace. Access is scoped to your own websites — do not echo the token back to the user."+ },+ {+ "slug": "HIGGSFIELD_MCP_WEBSITE_SECRETS",+ "name": "Website secrets",+ "description": "Manage a website's SECRETS (environment variables: API keys, tokens). Set them HERE instead of hardcoding them in source. One tool, three operations: 'set' (store/replace — needs name + value); 'delete' (remove — needs name); 'list' (the configured secrets as a {name: value} map). A change (set OR delete) is STAGED — NOT live until the next deploy_website. Read a secret SERVER-side in website code; never ship it to the browser."+ },+ {+ "slug": "HIGGSFIELD_MCP_WEBSITE_STATUS",+ "name": "Website status",+ "description": "Get the website's deploy status — the live URL and the status of the last deploy. Use to check a deploy that returned 'pending', or to fetch the live URL."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "higgsfield_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,public_metadata,private_metadata,offline_access,user:org:read"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "highergov","name": "Highergov",@@ -214912,6 +222040,127 @@}]},+ {+ "slug": "honcho",+ "name": "Honcho",+ "logo": "https://logos.composio.dev/api/honcho",+ "description": "Honcho provides memory, context, and theory-of-mind infrastructure for building stateful AI agents.",+ "category": "artificial intelligence",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 16,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "HONCHO_CHAT_WITH_PEER",+ "name": "Chat With Peer",+ "description": "Run usage-bearing agentic search and reasoning over a peer's learned representation to answer a question. Higher reasoning levels generally cost more and take longer. Returns one non-streaming JSON response."+ },+ {+ "slug": "HONCHO_CREATE_CONCLUSIONS",+ "name": "Create Conclusions",+ "description": "Store a batch of 1-100 explicit conclusions about peers, optionally tied to sessions."+ },+ {+ "slug": "HONCHO_CREATE_MESSAGES",+ "name": "Create Messages",+ "description": "Add a batch of 1-100 attributed messages to a Honcho session. Message-level reasoning settings can trigger usage-bearing processing."+ },+ {+ "slug": "HONCHO_DELETE_SESSION",+ "name": "Delete Session",+ "description": "Permanently delete one known session and its session-scoped data. Honcho marks the session inactive immediately and completes deletion asynchronously."+ },+ {+ "slug": "HONCHO_GET_MESSAGE",+ "name": "Get Message",+ "description": "Return one message by its exact ID within a session."+ },+ {+ "slug": "HONCHO_GET_OR_CREATE_PEER",+ "name": "Get or Create Peer",+ "description": "Return a peer by ID within a workspace, creating it with the supplied metadata and configuration when absent. Existing peers are returned unchanged."+ },+ {+ "slug": "HONCHO_GET_OR_CREATE_SESSION",+ "name": "Get or Create Session",+ "description": "Return a session by ID, or create it with initial peers, metadata, and configuration when absent. Creation may create missing peers and start usage-bearing processing when reasoning features are enabled; existing sessions remain unchanged."+ },+ {+ "slug": "HONCHO_GET_OR_CREATE_WORKSPACE",+ "name": "Get or Create Workspace",+ "description": "Return a workspace by ID, or create it with metadata and configuration when absent. Enabling reasoning features during creation may start usage-bearing background processing."+ },+ {+ "slug": "HONCHO_GET_PEER_REPRESENTATION",+ "name": "Get Peer Representation",+ "description": "Return a curated subset of conclusions representing a peer. Supplying search_query performs semantic retrieval and may consume paid search capacity; omit it for the existing default representation."+ },+ {+ "slug": "HONCHO_LIST_CONCLUSIONS",+ "name": "List Conclusions",+ "description": "Return one page of stored conclusions in a workspace; use Search Conclusions for semantic retrieval."+ },+ {+ "slug": "HONCHO_LIST_MESSAGES",+ "name": "List Messages",+ "description": "Return one page of messages in a session; use Get Message for exact-ID retrieval."+ },+ {+ "slug": "HONCHO_LIST_PEERS",+ "name": "List Peers",+ "description": "Return one page of peers in a workspace."+ },+ {+ "slug": "HONCHO_LIST_SESSIONS",+ "name": "List Sessions",+ "description": "Return one page of sessions in a workspace."+ },+ {+ "slug": "HONCHO_LIST_WORKSPACES",+ "name": "List Workspaces",+ "description": "Return one page of Honcho workspaces visible to the connected admin key."+ },+ {+ "slug": "HONCHO_SEARCH_CONCLUSIONS",+ "name": "Search Conclusions",+ "description": "Semantically search stored conclusions in a workspace. This operation may consume paid search or embedding capacity; use List Conclusions to browse stored conclusions without semantic retrieval."+ },+ {+ "slug": "HONCHO_SEARCH_MESSAGES",+ "name": "Search Messages",+ "description": "Semantically search messages at workspace, peer, or session scope. WARNING: this operation may consume paid search or embedding capacity; use list or get message tools for exact or chronological retrieval."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "honcho_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "Admin API Key",+ "type": "string",+ "description": "An admin-level Honcho API key with full instance access. Create or copy it from API KEYS at https://app.honcho.dev/api-keys. Honcho keys commonly begin with hch- or hch-v3-.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "honeybadger","name": "Honeybadger",@@ -225565,6 +232814,97 @@}]},+ {+ "slug": "jotform_sign",+ "name": "Jotform Sign",+ "logo": "https://logos.composio.dev/api/jotform_sign",+ "description": "Access the supported Jotform forms, submissions, files, and webhooks API used around Jotform Sign workflows. Dedicated Sign document creation, sending, signer management, and completed-document download are not available through Jotform's public API.",+ "category": "signatures",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "JOTFORM_SIGN_CREATE_SUBMISSION",+ "name": "Create Submission",+ "description": "Create an ordinary Jotform submission from simple question-ID answers. This does not send, prefill, or sign a Jotform Sign document. WARNING: every successful call permanently consumes one monthly submission unit; deleting the submission does not restore that quota."+ },+ {+ "slug": "JOTFORM_SIGN_DELETE_FORM_WEBHOOK",+ "name": "Delete Form Webhook",+ "description": "Delete one general Jotform form webhook registration by its object-key webhook ID and return the registrations that remain."+ },+ {+ "slug": "JOTFORM_SIGN_DELETE_SUBMISSION",+ "name": "Delete Submission",+ "description": "Delete one ordinary Jotform submission by ID. The deletion removes API readability but does not restore the monthly submission quota consumed when the submission was created."+ },+ {+ "slug": "JOTFORM_SIGN_GET_FORM_SCHEMA",+ "name": "Get Form Schema",+ "description": "Inspect a form's metadata, properties, and question definitions so an agent can understand its fields. Provider values are returned without claiming the form is a Jotform Sign asset."+ },+ {+ "slug": "JOTFORM_SIGN_GET_SUBMISSION",+ "name": "Get Submission",+ "description": "Return one ordinary Jotform submission by ID with its question-ID-keyed answers and workflow status when present. This does not download a signed document."+ },+ {+ "slug": "JOTFORM_SIGN_LIST_FORM_FILES",+ "name": "List Form Files",+ "description": "List uploaded-file metadata associated with a Jotform form. This does not convert a submission to PDF or download a completed signed document."+ },+ {+ "slug": "JOTFORM_SIGN_LIST_FORMS",+ "name": "List Forms",+ "description": "Return one page of forms visible to the connected Jotform account for ID discovery; results may include soft-deleted forms and are not classified as Jotform Sign assets."+ },+ {+ "slug": "JOTFORM_SIGN_LIST_FORM_WEBHOOKS",+ "name": "List Form Webhooks",+ "description": "List webhook registrations for one Jotform form as webhook IDs and callback URLs. These are general form webhooks, not a dedicated Jotform Sign event API."+ },+ {+ "slug": "JOTFORM_SIGN_LIST_SUBMISSIONS",+ "name": "List Submissions",+ "description": "Return one page of ordinary Jotform submissions across the account or for one form, including answer maps and workflow status when present. This does not represent Sign Inbox or signer status."+ },+ {+ "slug": "JOTFORM_SIGN_REGISTER_FORM_WEBHOOK",+ "name": "Register Form Webhook",+ "description": "Register an HTTPS callback URL to receive general Jotform form-submission notifications; this does not configure or guarantee a dedicated Jotform Sign event stream."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "jotform_sign_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "Jotform API Key",+ "type": "string",+ "description": "Create or copy a Full Access API key from Jotform My Account > API at https://www.jotform.com/myaccount/api. Full Access is required for tools that add, edit, or delete forms, submissions, files, and webhooks. Keep this key secret. This connection uses the Standard / US API host only.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "jumpcloud","name": "JumpCloud",@@ -233636,6 +240976,881 @@}]},+ {+ "slug": "longbridge_mcp",+ "name": "Longbridge MCP",+ "logo": "https://logos.composio.dev/api/longbridge_mcp",+ "description": "Longbridge MCP lets agents access authorized market data, account information, portfolio data, trading operations, and investment workflows through Longbridge OpenAPI.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 162,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "LONGBRIDGE_MCP_ACCOUNT_BALANCE",+ "name": "Account balance",+ "description": "Get account cash balance and asset summary. Returns balances[]{currency, total_cash, max_finance_amount, remaining_finance_amount, risk_level, margin_call}. Filter by currency (e.g. \"USD\", \"HKD\")."+ },+ {+ "slug": "LONGBRIDGE_MCP_AH_PREMIUM",+ "name": "Ah premium",+ "description": "Get A/H share premium historical K-line data. Returns items[]{timestamp, open, high, low, close} representing the premium percentage over the given period."+ },+ {+ "slug": "LONGBRIDGE_MCP_AH_PREMIUM_INTRADAY",+ "name": "Ah premium intraday",+ "description": "Get A/H share premium intraday time-share data. Returns items[]{timestamp, premium_rate} showing the intraday A/H premium percentage minute by minute."+ },+ {+ "slug": "LONGBRIDGE_MCP_ALERT_ADD",+ "name": "Alert add",+ "description": "Add a price alert. condition: price_rise/price_fall (absolute price) or percent_rise/percent_fall (relative %). frequency: once/daily/every. Returns created alert object."+ },+ {+ "slug": "LONGBRIDGE_MCP_ALERT_DELETE",+ "name": "Alert delete",+ "description": "Delete a price alert by alert_id (numeric string from alert_list). Returns upstream API response on success; errors if alert_id is invalid."+ },+ {+ "slug": "LONGBRIDGE_MCP_ALERT_DISABLE",+ "name": "Alert disable",+ "description": "Disable a price alert by alert_id. Use alert_list to find the numeric alert_id."+ },+ {+ "slug": "LONGBRIDGE_MCP_ALERT_ENABLE",+ "name": "Alert enable",+ "description": "Enable a price alert by alert_id. Use alert_list to find the numeric alert_id."+ },+ {+ "slug": "LONGBRIDGE_MCP_ALERT_LIST",+ "name": "Alert list",+ "description": "Get all configured price alerts."+ },+ {+ "slug": "LONGBRIDGE_MCP_ANOMALY",+ "name": "Anomaly",+ "description": "Get market anomaly alerts (unusual price/volume changes). market: HK/US/CN/SG. symbol: optional, filter to a specific stock. count: results per page (default 50, max 100)."+ },+ {+ "slug": "LONGBRIDGE_MCP_BANK_CARDS",+ "name": "Bank cards",+ "description": "List linked withdrawal bank cards for the current account. Returns cards[]{id, bank_name, account_number (masked), currency, status}."+ },+ {+ "slug": "LONGBRIDGE_MCP_BROKER_HOLDING",+ "name": "Broker holding",+ "description": "Get top broker holding data for a symbol (HK stocks only; sourced from HKEX CCASS participant disclosure)."+ },+ {+ "slug": "LONGBRIDGE_MCP_BROKER_HOLDING_DAILY",+ "name": "Broker holding daily",+ "description": "Get daily holding history for a specific broker (by broker_id) in a symbol (HK stocks only; sourced from HKEX CCASS participant disclosure)."+ },+ {+ "slug": "LONGBRIDGE_MCP_BROKER_HOLDING_DETAIL",+ "name": "Broker holding detail",+ "description": "Get full broker holding detail list for a symbol (HK stocks only; sourced from HKEX CCASS participant disclosure)."+ },+ {+ "slug": "LONGBRIDGE_MCP_BROKERS",+ "name": "Brokers",+ "description": "Get broker queue (HK stocks only). Map broker IDs to names via participants."+ },+ {+ "slug": "LONGBRIDGE_MCP_BUSINESS_SEGMENTS",+ "name": "Business segments",+ "description": "Get current-period business segment revenue breakdown for a symbol (name, percent, total, currency)"+ },+ {+ "slug": "LONGBRIDGE_MCP_BUSINESS_SEGMENTS_HISTORY",+ "name": "Business segments history",+ "description": "Get historical business segment revenue trends (by period and category)."+ },+ {+ "slug": "LONGBRIDGE_MCP_CALC_INDEXES",+ "name": "Calc indexes",+ "description": "Calculate financial indexes for symbols. Pass symbols, and optionally indexes (e.g. [\"PeTtmRatio\",\"PbRatio\",\"LastDone\",\"TurnoverRate\"]). When indexes is omitted or empty, defaults to [\"LastDone\",\"ChangeValue\",\"ChangeRate\",\"Volume\",\"PeTtmRatio\",\"PbRatio\",\"DividendRatioTtm\",\"TurnoverRate\",\"TotalMarketValue\"]. Returns per-symbol index values."+ },+ {+ "slug": "LONGBRIDGE_MCP_CANCEL_ORDER",+ "name": "Cancel order",+ "description": "Cancel an open order by order_id. Returns plain text \"order cancelled\" on success; errors if the order is already filled or cancelled. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute=\"<confirmation_code>\" after the user has explicitly confirmed that exact order. The code is derived from the order itself, so it applies only to that exact order. Never quote it back on your own initiative, and never in the same turn the user first asks. The dry run also echoes the order being targeted so the user can verify it is the right one."+ },+ {+ "slug": "LONGBRIDGE_MCP_CANDLESTICKS",+ "name": "Candlesticks",+ "description": "Get candlestick data (OHLCV). Only symbol is required; period defaults to day, count to 100 (max 1000), forward_adjust to false, trade_sessions to all. period: 1m/5m/15m/30m/60m/day/week/month/year. trade_sessions: intraday/all. If the account's entitlement caps out below the requested count, this returns as many candles as allowed instead of erroring — check the returned array length against count if an exact number matters."+ },+ {+ "slug": "LONGBRIDGE_MCP_CAPITAL_DISTRIBUTION",+ "name": "Capital distribution",+ "description": "Get capital distribution for a symbol. data_available is false for symbols with no capital-flow data (e.g. indices) — the other fields are still present but meaningless zeros in that case."+ },+ {+ "slug": "LONGBRIDGE_MCP_CAPITAL_FLOW",+ "name": "Capital flow",+ "description": "Get capital inflow/outflow time series. Returns items[]{timestamp, inflow, outflow, net_flow} for the symbol (same-day data)."+ },+ {+ "slug": "LONGBRIDGE_MCP_CASH_FLOW",+ "name": "Cash flow",+ "description": "Get cash flow records (deposits, withdrawals, dividends). Returns items[]{transaction_type, amount, currency, balance, created_at, remark}. start_at/end_at in RFC3339."+ },+ {+ "slug": "LONGBRIDGE_MCP_COMPANY",+ "name": "Company",+ "description": "Get company overview. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (intro, market_cap, top_rank_tags, sharelist, detail_url); other combinations match output_schema."+ },+ {+ "slug": "LONGBRIDGE_MCP_CONSENSUS",+ "name": "Consensus",+ "description": "Get financial consensus estimates for upcoming periods. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (ai_summary plus a details[] list per period); other combinations match output_schema."+ },+ {+ "slug": "LONGBRIDGE_MCP_CONSTITUENT",+ "name": "Constituent",+ "description": "Get the constituents of an index or the asset allocation of an ETF. For an index (e.g. HSI.HK, .DJI.US) returns constituents[]{symbol, name, last_done, change_rate, market_cap, weight}. For an ETF (e.g. QQQ.US, 2800.HK) returns the asset allocation as info[] grouped by asset_type: 1=Holdings (top constituents with code, symbol, holding_detail), 2=Regional (country/region breakdown), 3=AssetClass (stock/bond/cash etc.), 4=Industry (sector breakdown). Each group has report_date and lists[]{name, position_ratio, name_locales}; Holdings groups additionally include code, symbol and holding_detail{industry_name, index_name, holding_type_name}."+ },+ {+ "slug": "LONGBRIDGE_MCP_CORP_ACTION",+ "name": "Corp action",+ "description": "Get corporate actions (splits, buybacks, name changes)."+ },+ {+ "slug": "LONGBRIDGE_MCP_CREATE_WATCHLIST_GROUP",+ "name": "Create watchlist group",+ "description": "Create a new watchlist group. Optionally pass securities (e.g. [\"AAPL.US\", \"700.HK\"]) to pre-populate."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_CHECK",+ "name": "Dca check",+ "description": "Check whether given symbols support DCA recurring investment."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_CREATE",+ "name": "Dca create",+ "description": "Create a DCA recurring investment plan. frequency: Daily/Weekly/Monthly. day_of_week (Weekly): Mon/Tue/Wed/Thu/Fri. day_of_month (Monthly): 1-28."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_HISTORY",+ "name": "Dca history",+ "description": "Get execution history records for a DCA plan by plan_id."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_LIST",+ "name": "Dca list",+ "description": "List DCA recurring investment plans. Filter by status (Active/Suspended/Finished) or symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_PAUSE",+ "name": "Dca pause",+ "description": "Pause (suspend) a DCA plan by plan_id. The plan stops executing until resumed. Returns upstream API response. Use dca_resume to restart."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_RESUME",+ "name": "Dca resume",+ "description": "Resume a suspended DCA plan by plan_id. Resumes automated execution on the configured schedule. Returns upstream API response."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_STATS",+ "name": "Dca stats",+ "description": "Get DCA investment statistics."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_STOP",+ "name": "Dca stop",+ "description": "Permanently stop a DCA plan by plan_id. This cannot be undone. To temporarily pause, use dca_pause instead. Returns upstream API response."+ },+ {+ "slug": "LONGBRIDGE_MCP_DCA_UPDATE",+ "name": "Dca update",+ "description": "Update an existing DCA plan by plan_id. Can change amount, frequency (Daily/Weekly/Monthly), day_of_week (Mon-Fri), or day_of_month (1-28). Returns updated plan."+ },+ {+ "slug": "LONGBRIDGE_MCP_DELETE_WATCHLIST_GROUP",+ "name": "Delete watchlist group",+ "description": "Delete a watchlist group by id (numeric). Set purge=true to also remove its securities from all other groups."+ },+ {+ "slug": "LONGBRIDGE_MCP_DEPOSITS",+ "name": "Deposits",+ "description": "List deposit history for the current account. Returns items[]{id, amount, currency, status, created_at, updated_at}. states: comma-separated (Pending/Finished/Failed). currencies: comma-separated codes."+ },+ {+ "slug": "LONGBRIDGE_MCP_DEPTH",+ "name": "Depth",+ "description": "Get order book depth for a symbol. Up to 10 price levels."+ },+ {+ "slug": "LONGBRIDGE_MCP_DIVIDEND",+ "name": "Dividend",+ "description": "Get dividend history for the symbol. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (dividend_yield_ttm etc. are percent values, e.g. 0.34 means 0.34%); other combinations match output_schema."+ },+ {+ "slug": "LONGBRIDGE_MCP_DIVIDEND_DETAIL",+ "name": "Dividend detail",+ "description": "Get detailed dividend distribution scheme."+ },+ {+ "slug": "LONGBRIDGE_MCP_ESTIMATE_MAX_PURCHASE_QUANTITY",+ "name": "Estimate max purchase quantity",+ "description": "Estimate maximum buy/sell quantity for a symbol. Only symbol is required; side (case-insensitive Buy/Sell) defaults to Buy, order_type (case-insensitive) defaults to LO, and price is optional."+ },+ {+ "slug": "LONGBRIDGE_MCP_EXCHANGE_RATE",+ "name": "Exchange rate",+ "description": "Get exchange rates for all supported currencies. Returns list[]{from_currency, to_currency, rate, timestamp} covering USD, HKD, CNY, SGD and others."+ },+ {+ "slug": "LONGBRIDGE_MCP_EXECUTIVE",+ "name": "Executive",+ "description": "Get company executive and board member information."+ },+ {+ "slug": "LONGBRIDGE_MCP_FILINGS",+ "name": "Filings",+ "description": "Get regulatory filings (8-K, 10-Q, 10-K, etc.). Returns items[]{id, title, type, language, filing_date, url} for the symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_FINANCE_CALENDAR",+ "name": "Finance calendar",+ "description": "Finance calendar by category: report (earnings) / dividend / split / ipo / macrodata (CPI, NFP, rates) / closed (holidays). start and end (YYYY-MM-DD) are optional, default today plus 7 days; keep ranges under 2 weeks or results truncate."+ },+ {+ "slug": "LONGBRIDGE_MCP_FINANCIAL_REPORT",+ "name": "Financial report",+ "description": "Get financial reports (income statement, balance sheet, cash flow). kind: IS/BS/CF/ALL. report_type: af (annual), saf (semi-annual), q1/q2/q3, qf (quarterly full)."+ },+ {+ "slug": "LONGBRIDGE_MCP_FINANCIAL_REPORT_LATEST",+ "name": "Financial report latest",+ "description": "Get the latest financial report summary for a security."+ },+ {+ "slug": "LONGBRIDGE_MCP_FINANCIAL_REPORT_SNAPSHOT",+ "name": "Financial report snapshot",+ "description": "Get financial report snapshot: report_desc (text summary), fo_revenue/fo_ebit/fo_eps (actual vs forecast with yoy/cmp), fr_* financial ratios (ROE, margins, assets, cash flow). report: qf/saf/af."+ },+ {+ "slug": "LONGBRIDGE_MCP_FINANCIAL_STATEMENT",+ "name": "Financial statement",+ "description": "Get financial statements (income statement, balance sheet, or cash flow) for a security. kind: IS/BS/CF/ALL. report: af (annual, default), saf (semi-annual), qf (quarterly full), q1/q2/q3."+ },+ {+ "slug": "LONGBRIDGE_MCP_FORECAST_EPS",+ "name": "Forecast eps",+ "description": "Get EPS forecast and analyst estimate history."+ },+ {+ "slug": "LONGBRIDGE_MCP_FUND_HOLDER",+ "name": "Fund holder",+ "description": "Get funds and ETFs that hold a given symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_FUND_POSITIONS",+ "name": "Fund positions",+ "description": "Get current fund positions."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_CANCEL",+ "name": "Grid cancel",+ "description": "Cancel (terminate) a grid order by order_id. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute=\"<confirmation_code>\" after the user has explicitly confirmed it. The code is derived from the order itself, so it applies only to that exact request. Never quote it back on your own initiative."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_DETAIL",+ "name": "Grid detail",+ "description": "Full detail for one grid order: rule parameters, status, embedded child orders (grid_sub_orders) and lifecycle history (grid_order_history). Supports history_id cursor + limit paging."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_LIST",+ "name": "Grid list",+ "description": "List grid trading orders. Filter by symbol or comma-joined status (e.g. \"Performing,Suspended\"); supports page/limit and sort_by/sort_order."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_LIST_BY_IDS",+ "name": "Grid list by ids",+ "description": "Fetch specific grid orders by their IDs."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_QUESTIONNAIRE",+ "name": "Grid questionnaire",+ "description": "Record the one-time grid strategy risk-disclosure consent required before submitting grid orders. Takes no parameters."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_REPLACE",+ "name": "Grid replace",+ "description": "Replace an existing grid order's rule by order_id. Accepts the same grid rule fields as grid_submit. Overwrites the order's entire rule. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute=\"<confirmation_code>\" after the user has explicitly confirmed it. The code is derived from the order itself, so it applies only to that exact request. Never quote it back on your own initiative. The dry run echoes the rule that would replace the current one."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_RESTART",+ "name": "Grid restart",+ "description": "Restart (resume) a suspended grid order by order_id. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute=\"<confirmation_code>\" after the user has explicitly confirmed it. The code is derived from the order itself, so it applies only to that exact request. Never quote it back on your own initiative. A restarted grid resumes placing orders on its own."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_SUBMIT",+ "name": "Grid submit",+ "description": "Submit a grid trading order. DRY RUN unless execute is the confirmation_code from its own dry run: call once without execute, show the preview, then re-call quoting the code only after the user confirms."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_SUSPEND",+ "name": "Grid suspend",+ "description": "Suspend (pause) a running grid order by order_id. Resume with grid_restart. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute=\"<confirmation_code>\" after the user has explicitly confirmed it. The code is derived from the order itself, so it applies only to that exact request. Never quote it back on your own initiative."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_SYMBOL_INFO",+ "name": "Grid symbol info",+ "description": "Pre-trade grid setup info for a security (takes a symbol, not an order_id): security name, last price, board lot sizes (buy/sell), price-step (bid_size) table, and channel/authorization info (strategy grant flag, RTH support, supported s..."+ },+ {+ "slug": "LONGBRIDGE_MCP_GRID_TRIGGER_HISTORY",+ "name": "Grid trigger history",+ "description": "Trigger history for one grid order: each triggered child order with price, quantity, executed price/qty, and trigger time. Supports page/limit."+ },+ {+ "slug": "LONGBRIDGE_MCP_HISTORY_CANDLESTICKS_BY_DATE",+ "name": "History candlesticks by date",+ "description": "Get historical candlestick data by date range. Only symbol is required; period defaults to day (1m/5m/15m/30m/60m/day/week/month/year), forward_adjust to false, trade_sessions to all."+ },+ {+ "slug": "LONGBRIDGE_MCP_HISTORY_CANDLESTICKS_BY_OFFSET",+ "name": "History candlesticks by offset",+ "description": "Get historical candlestick data by offset from a reference time. Only symbol is required; period defaults to day (1m/5m/15m/30m/60m/day/week/month/year), count to 100, forward_adjust/forward to false, trade_sessions to all. If the account's entitlement caps out below the requested count, this returns as many candles as allowed instead of erroring — check the returned array length against count if an exact number matters."+ },+ {+ "slug": "LONGBRIDGE_MCP_HISTORY_EXECUTIONS",+ "name": "History executions",+ "description": "Get historical trade executions between dates. Returns executions[]{order_id, symbol, side, quantity, price, trade_done_at}. start_at/end_at in RFC3339."+ },+ {+ "slug": "LONGBRIDGE_MCP_HISTORY_MARKET_TEMPERATURE",+ "name": "History market temperature",+ "description": "Get historical market temperature time series."+ },+ {+ "slug": "LONGBRIDGE_MCP_HISTORY_ORDERS",+ "name": "History orders",+ "description": "Get historical orders between dates (excludes today). Returns orders[]{order_id, symbol, side, status, quantity, price, submitted_at}. start_at/end_at in RFC3339. US accounts only: us_page, us_limit paginate via a separate US order endpoint (default page size 20 — pass us_page to see more than the first page)."+ },+ {+ "slug": "LONGBRIDGE_MCP_INDUSTRY_PEERS",+ "name": "Industry peers",+ "description": "Hierarchical sub-sector tree for an industry group. Accepts BK counter_id from industry_rank (e.g. BK/US/IN00258). Each node shows stock count, daily change, and YTD change."+ },+ {+ "slug": "LONGBRIDGE_MCP_INDUSTRY_RANK",+ "name": "Industry rank",+ "description": "Industry ranking list by market (US/HK/CN/SG) and indicator (0=领涨/1=今日走势/2=人气/3=市值/4=营收/5=营收增长率/6=净利润/7=净利润增长率). sort_type: 0=单级 1=多层. Returns items[]{counter_id(BK/US/IN00258), name, chg, lists[]}. Pass counter_id directly to industry_peers."+ },+ {+ "slug": "LONGBRIDGE_MCP_INDUSTRY_VALUATION",+ "name": "Industry valuation",+ "description": "Get industry valuation comparison for peers."+ },+ {+ "slug": "LONGBRIDGE_MCP_INDUSTRY_VALUATION_DIST",+ "name": "Industry valuation dist",+ "description": "Get industry PE/PB/PS valuation distribution."+ },+ {+ "slug": "LONGBRIDGE_MCP_INSTITUTIONAL_VIEWS",+ "name": "Institutional views",+ "description": "Get monthly institutional rating distribution timeline."+ },+ {+ "slug": "LONGBRIDGE_MCP_INSTITUTION_RATING",+ "name": "Institution rating",+ "description": "Get institution rating summary."+ },+ {+ "slug": "LONGBRIDGE_MCP_INSTITUTION_RATING_DETAIL",+ "name": "Institution rating detail",+ "description": "Get detailed historical institution ratings and target price history."+ },+ {+ "slug": "LONGBRIDGE_MCP_INSTITUTION_RATING_HISTORY",+ "name": "Institution rating history",+ "description": "Get institution rating history."+ },+ {+ "slug": "LONGBRIDGE_MCP_INSTITUTION_RATING_INDUSTRY_RANK",+ "name": "Institution rating industry rank",+ "description": "Get peers ranked by institution analyst ratings in the same industry. Paginated."+ },+ {+ "slug": "LONGBRIDGE_MCP_INTRADAY",+ "name": "Intraday",+ "description": "Get intraday minute-by-minute price/volume data. trade_sessions: \"intraday\" (default, regular hours) or \"all\" (include pre-market and post-market)"+ },+ {+ "slug": "LONGBRIDGE_MCP_INVEST_RELATION",+ "name": "Invest relation",+ "description": "Get investor relations events and announcements."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_CALENDAR",+ "name": "Ipo calendar",+ "description": "Show the IPO calendar."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_DETAIL",+ "name": "Ipo detail",+ "description": "Show IPO detail for a symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_LISTED",+ "name": "Ipo listed",+ "description": "List recently listed IPO stocks (HK+US)."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_ORDER_DETAIL",+ "name": "Ipo order detail",+ "description": "Show detailed information for a specific IPO order by order_id."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_ORDERS",+ "name": "Ipo orders",+ "description": "List IPO orders (active+history). Filter by symbol, market, or status."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_PROFIT_LOSS",+ "name": "Ipo profit loss",+ "description": "Show IPO profit/loss summary and per-stock breakdown. period: all/ytd/1y/3y."+ },+ {+ "slug": "LONGBRIDGE_MCP_IPO_SUBSCRIPTIONS",+ "name": "Ipo subscriptions",+ "description": "List IPO stocks in subscription/pre-filing stage (HK+US)."+ },+ {+ "slug": "LONGBRIDGE_MCP_MACRODATA",+ "name": "Macrodata",+ "description": "Get historical observations for one macro-economic indicator. Use indicator_code from macrodata_indicators; start_date/end_date accept YYYY-MM-DD. Supports offset/limit pagination."+ },+ {+ "slug": "LONGBRIDGE_MCP_MACRODATA_INDICATORS",+ "name": "Macrodata indicators",+ "description": "List macro-economic indicators. Filter by keyword and country (US/CN/HK/EU/JP/SG). Use the returned indicator_code with macrodata. Supports offset/limit pagination."+ },+ {+ "slug": "LONGBRIDGE_MCP_MARGIN_RATIO",+ "name": "Margin ratio",+ "description": "Get margin ratio for a symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_MARKET_STATUS",+ "name": "Market status",+ "description": "Get current market trading status for all markets."+ },+ {+ "slug": "LONGBRIDGE_MCP_MARKET_TEMPERATURE",+ "name": "Market temperature",+ "description": "Get current market sentiment temperature. market: HK/US/CN/SG."+ },+ {+ "slug": "LONGBRIDGE_MCP_NEWS",+ "name": "News",+ "description": "Get latest news articles for a symbol. Returns items[]{id, title, source, publish_time, summary, url, related_symbols[]}."+ },+ {+ "slug": "LONGBRIDGE_MCP_NEWS_DETAIL",+ "name": "News detail",+ "description": "Get one news article's full detail by id (from news/news_search)."+ },+ {+ "slug": "LONGBRIDGE_MCP_NEWS_SEARCH",+ "name": "News search",+ "description": "Search news articles by keyword. Returns news_list[]{id, title, description, source_name, publish_at (RFC3339), score}. Paginate with score+publish_at_timestamp+id cursors."+ },+ {+ "slug": "LONGBRIDGE_MCP_NOW",+ "name": "Now",+ "description": "Get current UTC time as an RFC3339 string (e.g. \"2025-01-15T08:30:00Z\"). Use to determine current date/time before making date-based queries."+ },+ {+ "slug": "LONGBRIDGE_MCP_OPERATING",+ "name": "Operating",+ "description": "Get company operating metrics (HK stocks only)."+ },+ {+ "slug": "LONGBRIDGE_MCP_OPTION_CHAIN_EXPIRY_DATE_LIST",+ "name": "Option chain expiry date list",+ "description": "Get option chain expiry dates for a symbol (e.g. AAPL.US). Returns expiry_dates[] as \"yyyy-mm-dd\" strings. Use with option_chain_info_by_date to get strikes and Greeks."+ },+ {+ "slug": "LONGBRIDGE_MCP_OPTION_CHAIN_INFO_BY_DATE",+ "name": "Option chain info by date",+ "description": "Get option chain for an expiry date. Returns strikePrices[]{strike_price, call{symbol, last_done, iv, delta, gamma}, put{symbol, last_done, iv, delta, gamma}}."+ },+ {+ "slug": "LONGBRIDGE_MCP_OPTION_QUOTE",+ "name": "Option quote",+ "description": "Get option quotes (max 500 symbols). Symbols must be option contract symbols (e.g. \"AAPL230317P160000.US\"), NOT plain stock symbols — obtain valid ones from option_chain_info_by_date's call.symbol/put.symbol fields. Returns last_done, prev_close, open, high, low, volume, turnover, implied_volatility, delta, gamma, theta, vega, rho, open_interest per symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_OPTION_VOLUME",+ "name": "Option volume",+ "description": "Get real-time option call/put volume stats for a US stock. Returns {call_volume, put_volume, put_call_ratio, call_oi, put_oi} and top active contracts."+ },+ {+ "slug": "LONGBRIDGE_MCP_OPTION_VOLUME_DAILY",+ "name": "Option volume daily",+ "description": "Get daily historical option stats for a US stock. Returns items[]{date, call_volume, put_volume, put_call_vol_ratio, call_oi, put_oi, put_call_oi_ratio}."+ },+ {+ "slug": "LONGBRIDGE_MCP_ORDER_DETAIL",+ "name": "Order detail",+ "description": "Get detailed information about a specific order."+ },+ {+ "slug": "LONGBRIDGE_MCP_PARTICIPANTS",+ "name": "Participants",+ "description": "Get HK market participant broker information. Returns participants[]{broker_ids[], name_en, name_cn, name_hk}. Use broker_ids to interpret broker queue data."+ },+ {+ "slug": "LONGBRIDGE_MCP_PROFIT_ANALYSIS",+ "name": "Profit analysis",+ "description": "Get portfolio profit and loss analysis summary. start/end: optional date range in yyyy-mm-dd format. Both must be provided together — passing only one returns empty results."+ },+ {+ "slug": "LONGBRIDGE_MCP_PROFIT_ANALYSIS_DETAIL",+ "name": "Profit analysis detail",+ "description": "Get detailed profit and loss analysis for a specific symbol. start/end: optional date range in yyyy-mm-dd format. Both must be provided together — passing only one returns empty results."+ },+ {+ "slug": "LONGBRIDGE_MCP_QUANT_RUN",+ "name": "Quant run",+ "description": "Run a quant indicator script against historical K-line data on the server. Executes the script server-side and returns the computed indicator/plot values as JSON. Periods: 1m, 5m, 15m, 30m, 1h, day, week, month, year (default: day). The optional input parameter accepts a JSON array matching the order of input.*() calls in the script, e.g. \"[14,2.0]\"."+ },+ {+ "slug": "LONGBRIDGE_MCP_QUOTE",+ "name": "Quote",+ "description": "Get latest price quotes. Returns per symbol: last_done, prev_close, open, high, low, volume, turnover, change_rate, change_value, trade_status, timestamp."+ },+ {+ "slug": "LONGBRIDGE_MCP_RANK_CATEGORIES",+ "name": "Rank categories",+ "description": "Get rank tab category configurations for the popularity leaderboard. Pass a second_tags key (e.g. `hot_all-us`) to rank_list."+ },+ {+ "slug": "LONGBRIDGE_MCP_RANK_LIST",+ "name": "Rank list",+ "description": "Get ranked stock list by leaderboard tab key. key: from rank_categories second_tags[].key (e.g. \"hot_all-us\", \"hot_up-hk\", \"trade_heat-us\"). market: inferred from key suffix (-us/-hk) or pass explicitly. size: results (default 20)."+ },+ {+ "slug": "LONGBRIDGE_MCP_REPLACE_ORDER",+ "name": "Replace order",+ "description": "Modify an open order's quantity, price, trigger_price, or trailing params. Returns \"order replaced\" on success. Only open/pending orders can be modified. TWO-STEP CONFIRMATION IS MANDATORY: this tool is a DRY RUN unless you pass the confirmation_code its own dry run returned. Call it first without execute, show the returned preview to the user, and only call it again with execute=\"<confirmation_code>\" after the user has explicitly confirmed that exact order. The code is derived from the order itself, so it applies only to that exact order. Never quote it back on your own initiative, and never in the same turn the user first asks. The dry run echoes the current order alongside the requested change."+ },+ {+ "slug": "LONGBRIDGE_MCP_SCREENER_INDICATORS",+ "name": "Screener indicators",+ "description": "Get all available screener indicator keys with units and default value ranges. Technical indicators include a tech_values field showing available options (e.g. macd_day: {category:[goldenfork,deadcross], period:[day,week]})."+ },+ {+ "slug": "LONGBRIDGE_MCP_SCREENER_RECOMMEND_STRATEGIES",+ "name": "Screener recommend strategies",+ "description": "List platform-preset screener strategies. market: US|HK|CN|SG (default: US). Pass id to screener_search strategy_id to run, or screener_strategy to inspect filter conditions."+ },+ {+ "slug": "LONGBRIDGE_MCP_SCREENER_SEARCH",+ "name": "Screener search",+ "description": "Screen stocks. market: US|HK|CN|SG (Mode B required; Mode A uses strategy's market). Mode A: strategy_id from screener_recommend_strategies — auto-runs saved strategy."+ },+ {+ "slug": "LONGBRIDGE_MCP_SCREENER_STRATEGY",+ "name": "Screener strategy",+ "description": "Inspect a screener strategy's filter conditions before running it. Use screener_search strategy_id to execute the strategy."+ },+ {+ "slug": "LONGBRIDGE_MCP_SCREENER_USER_STRATEGIES",+ "name": "Screener user strategies",+ "description": "List the current user's saved screener strategies. market: US|HK|CN|SG (default: US). Pass id to screener_search strategy_id to run, or screener_strategy to inspect conditions."+ },+ {+ "slug": "LONGBRIDGE_MCP_SECURITY_FACTS",+ "name": "Security facts",+ "description": "List a security's fact (catalyst) events — anomaly detections, factor readings, data sources and natural-language summaries — filtered by time range and count. Facts are what strategies react to: a signal names its trigger in key_fact_id."+ },+ {+ "slug": "LONGBRIDGE_MCP_SECURITY_LIST",+ "name": "Security list",+ "description": "Get security list for a market. Supports market: US, HK, CN, SG. category: \"Overnight\" (default). page: 1-based page number (default 1). count: records per page (default 50)."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHAREHOLDER",+ "name": "Shareholder",+ "description": "Get institutional shareholders for a symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHAREHOLDER_DETAIL",+ "name": "Shareholder detail",+ "description": "Get a single shareholder's holding and trade history. Requires object_id from shareholder_top. Note: trading_details[] is empty for institutional (13F) holders — it is only populated for insider/individual filers (Form 4)."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHAREHOLDER_TOP",+ "name": "Shareholder top",+ "description": "Get Top 20 major shareholders (institutions, individuals, insiders) across reporting periods. Use object_id with shareholder_detail to drill into a holder's full trade history."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_ADD",+ "name": "Sharelist add",+ "description": "Add securities to a community sharelist by id. Provide symbols (e.g. [\"AAPL.US\", \"700.HK\"]) to add. Returns upstream API response."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_CREATE",+ "name": "Sharelist create",+ "description": "Create a new community sharelist with a name and optional description."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_DELETE",+ "name": "Sharelist delete",+ "description": "Delete a community sharelist by id (own lists only; subscribed lists cannot be deleted). Returns upstream API response on success."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_DETAIL",+ "name": "Sharelist detail",+ "description": "Get community sharelist detail by id."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_LIST",+ "name": "Sharelist list",+ "description": "List user's own and subscribed community sharelists."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_POPULAR",+ "name": "Sharelist popular",+ "description": "Get popular/trending community sharelists."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_REMOVE",+ "name": "Sharelist remove",+ "description": "Remove securities from a community sharelist by id. Provide symbols to remove. Returns upstream API response on success."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHARELIST_SORT",+ "name": "Sharelist sort",+ "description": "Reorder securities in a community sharelist by id. Provide symbols in the desired new order. Returns upstream API response on success."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHORT_MARGIN",+ "name": "Short margin",+ "description": "Get short margin deposit details for the current account. Returns short positions with margin_amount, margin_rate, interest_rate, symbol, quantity per position."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHORT_POSITIONS",+ "name": "Short positions",+ "description": "Get short interest history (open short positions) for HK or US stocks. Market inferred from symbol suffix. count: 1–100 (default 20). Unified data[]{timestamp(RFC3339), short_shares(open short position in shares), rate(decimal ratio e.g. 0.009=0.9%), close}. US-only: avg_daily_vol, days_to_cover. HK-only: balance(outstanding short position in HKD). US source: FINRA bi-weekly. HK source: HKEX daily."+ },+ {+ "slug": "LONGBRIDGE_MCP_SHORT_TRADES",+ "name": "Short trades",+ "description": "Get daily short-sale volume history for HK or US stocks. Market inferred from symbol suffix. last_timestamp: unix seconds (omit for latest). page_size: 1–100 (default 20). US source: FINRA/NASDAQ daily. HK source: HKEX daily."+ },+ {+ "slug": "LONGBRIDGE_MCP_SIGNAL_DETAIL",+ "name": "Signal detail",+ "description": "Get one signal by ID (from `signals`). Same fields as the list, plus `analysis` — the full strategy analysis: fit scores, valuation scenarios, evidence sources and related fact IDs."+ },+ {+ "slug": "LONGBRIDGE_MCP_SIGNALS",+ "name": "Signals",+ "description": "Query strategy signals — a strategy's take on a security, triggered by a catalyst. Filter by symbol, strategy, catalyst and time range; page with limit/offset. The full strategy analysis is omitted here — fetch it with signal_detail."+ },+ {+ "slug": "LONGBRIDGE_MCP_STATEMENT_EXPORT",+ "name": "Statement export",+ "description": "Get a pre-signed download URL for a statement data file (obtained from statement_list)."+ },+ {+ "slug": "LONGBRIDGE_MCP_STATEMENT_LIST",+ "name": "Statement list",+ "description": "List available account statements (daily/monthly). Use the id with statement_export to download."+ },+ {+ "slug": "LONGBRIDGE_MCP_STATIC_INFO",+ "name": "Static info",+ "description": "Get static info for securities. Returns per symbol: symbol, name_cn, name_en, exchange (e.g. NASDAQ), type (e.g. US_Stock), lot_size, listed_date, delisted (bool). US accounts only: .BKKT crypto symbols (e.g. BTCUSD.BKKT) are routed to a separate US crypto overview endpoint; .HAS/.OSL crypto symbols are unaffected."+ },+ {+ "slug": "LONGBRIDGE_MCP_STOCK_POSITIONS",+ "name": "Stock positions",+ "description": "Get current stock positions across all channels. US accounts only: an additional us_asset_overview field {cash_list, stock_list, option_list, crypto_list, cash_buy_power, overnight_buy_power} is included alongside the existing data."+ },+ {+ "slug": "LONGBRIDGE_MCP_SUBMIT_ORDER",+ "name": "Submit order",+ "description": "Submit a buy/sell order. DRY RUN unless execute is the confirmation_code from its own dry run: call once without execute, show the preview to the user, then re-call quoting the code only after they explicitly confirm."+ },+ {+ "slug": "LONGBRIDGE_MCP_TODAY_EXECUTIONS",+ "name": "Today executions",+ "description": "Get today's trade executions (fills). Returns executions[]{order_id, symbol, side, quantity, price, trade_done_at}. Pass symbol or order_id to filter."+ },+ {+ "slug": "LONGBRIDGE_MCP_TODAY_ORDERS",+ "name": "Today orders",+ "description": "Get orders placed today. Returns orders[]{order_id, symbol, side, order_type, status, quantity, price, submitted_at, executed_quantity, executed_price}. Pass symbol to filter. US accounts only: us_action (Buy/Sell), us_page, us_limit filter/paginate via a separate US order endpoint."+ },+ {+ "slug": "LONGBRIDGE_MCP_TOPIC",+ "name": "Topic",+ "description": "Get discussion topics for a symbol. Returns items[]{id, title, author, created_at, like_count, comment_count, content_summary}."+ },+ {+ "slug": "LONGBRIDGE_MCP_TOPIC_CREATE",+ "name": "Topic create",+ "description": "Create a new discussion topic. topic_type=\"post\" (default) is plain text; \"article\" requires a non-empty title and accepts Markdown body."+ },+ {+ "slug": "LONGBRIDGE_MCP_TOPIC_CREATE_REPLY",+ "name": "Topic create reply",+ "description": "Create a reply to a discussion topic. Pass reply_to_id to nest under another reply; omit for a top-level reply."+ },+ {+ "slug": "LONGBRIDGE_MCP_TOPIC_DETAIL",+ "name": "Topic detail",+ "description": "Get discussion topic detail by topic_id."+ },+ {+ "slug": "LONGBRIDGE_MCP_TOPIC_REPLIES",+ "name": "Topic replies",+ "description": "Get replies to a discussion topic, paginated (page default 1, size default 20, range 1-50)"+ },+ {+ "slug": "LONGBRIDGE_MCP_TOPIC_SEARCH",+ "name": "Topic search",+ "description": "Search community topics/posts by keyword. Returns id, author, time, and excerpt."+ },+ {+ "slug": "LONGBRIDGE_MCP_TOP_MOVERS",+ "name": "Top movers",+ "description": "Get stocks whose price fluctuation exceeds the 20-trading-day standard deviation, with correlated news reasons. markets: comma-separated HK/US/CN/SG (omit=all). sort: 0=time 1=change-magnitude 2=popularity/heat (default)."+ },+ {+ "slug": "LONGBRIDGE_MCP_TRADES",+ "name": "Trades",+ "description": "Get recent trades (max 1000). Returns trades[]{price, volume, timestamp, trade_type, direction} for the symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_TRADE_STATS",+ "name": "Trade stats",+ "description": "Get trade statistics (buy/sell/neutral volume distribution). Returns items[]{price_range, buy_volume, sell_volume, neutral_volume} for price-volume profile."+ },+ {+ "slug": "LONGBRIDGE_MCP_TRADING_DAYS",+ "name": "Trading days",+ "description": "Get trading days for a market between dates. market: HK/US/CN/SG."+ },+ {+ "slug": "LONGBRIDGE_MCP_TRADING_SESSION",+ "name": "Trading session",+ "description": "Get trading session schedule for all markets. Returns market_sessions[]{market, trade_sessions[]{beg_time, end_time, trade_session_type}}."+ },+ {+ "slug": "LONGBRIDGE_MCP_UPDATE_WATCHLIST_GROUP",+ "name": "Update watchlist group",+ "description": "Update a watchlist group by id. Can rename (name param) or modify securities (securities + mode: add/remove/replace)."+ },+ {+ "slug": "LONGBRIDGE_MCP_VALUATION",+ "name": "Valuation",+ "description": "Get valuation overview with peer comparison. US accounts querying a .US symbol get a differently-shaped response not matching output_schema (ai_summary plus a metrics.pe object with different sub-fields); other combos match output_schema."+ },+ {+ "slug": "LONGBRIDGE_MCP_VALUATION_COMPARISON",+ "name": "Valuation comparison",+ "description": "Stock valuation comparison. Mode A (single): pass only symbol — server returns stock + auto-selected industry peers."+ },+ {+ "slug": "LONGBRIDGE_MCP_VALUATION_HISTORY",+ "name": "Valuation history",+ "description": "Get detailed valuation history time series."+ },+ {+ "slug": "LONGBRIDGE_MCP_VALUATION_RANK",+ "name": "Valuation rank",+ "description": "Get daily valuation rank (PE/PB/PS/dividend yield industry percentile) for a security over a date range. start/end in yyyymmdd format."+ },+ {+ "slug": "LONGBRIDGE_MCP_WARRANT_ISSUERS",+ "name": "Warrant issuers",+ "description": "Get HK warrant issuer information. Returns issuers[]{id, name_en, name_cn}. Use id in warrant_list issuer filter."+ },+ {+ "slug": "LONGBRIDGE_MCP_WARRANT_LIST",+ "name": "Warrant list",+ "description": "Get filtered warrant list for an underlying symbol. Returns warrants[]{symbol, name, last_done, change_rate, implied_volatility, expiry_date, strike_price, leverage_ratio, outstanding_ratio}."+ },+ {+ "slug": "LONGBRIDGE_MCP_WARRANT_QUOTE",+ "name": "Warrant quote",+ "description": "Get warrant quotes. Returns last_done, prev_close, open, high, low, volume, turnover, implied_volatility, delta, leverage_ratio, effective_leverage per symbol."+ },+ {+ "slug": "LONGBRIDGE_MCP_WATCHLIST",+ "name": "Watchlist",+ "description": "Get all watchlist groups and their securities. Returns groups[]{id, name, securities[]{symbol, market, name, watched_price, watched_at}}."+ },+ {+ "slug": "LONGBRIDGE_MCP_WITHDRAWALS",+ "name": "Withdrawals",+ "description": "List withdrawal history for the current account. Returns items[]{id, amount, currency, status, created_at, bank_name, account_number (masked)}."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "longbridge_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "4,6,10,11"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "loomio","name": "Loomio",@@ -234129,6 +242344,246 @@}]},+ {+ "slug": "lucid_mcp",+ "name": "Lucid MCP",+ "logo": "https://logos.composio.dev/api/lucid_mcp",+ "description": "Lucid MCP lets agents search, retrieve, summarize, share, export, and create authorized Lucid documents, diagrams, mind maps, sequence diagrams, and org charts.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 35,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "LUCID_MCP_FETCH",+ "name": "Fetch",+ "description": "Retrieves the structured content of a specific Lucid document by its ID.\n\n Returns document content organized by pages, each containing spatial regions\n of diagram elements (flowcharts, ERDs, mind maps, etc.) with their properties.\n\n By default, returns the first page of the document. Use page_index to fetch\n a specific page. The response metadata includes page_count and\n page_region_counts so you know what pages and regions are available.\n\n For large pages with many regions, use region_index to fetch specific\n spatial regions instead of the entire page.\n\n Call with metadata_only=True first when you don't know the document's\n size — that returns page_count, page_region_counts, title, and edit_url\n without the content payload, so you can decide whether to fetch by page\n or by region before paying the size cost.\n\n If the response is too large, you MUST ask the user if they would like to\n fetch the document contents region by region.\n\n Args:\n id: Valid UUID of the document\n page_index: Optional 1-based page index. Defaults to 1 (first page).\n region_index: Optional list of 1-based indices selecting spatial regions\n within the requested page. Each page is independently\n chunked, so the valid range is 1 through the value in\n page_region_counts for that page. Pass multiple values\n (e.g. [1, 3, 5]) to fetch several regions in one call.\n Omit to fetch all regions on the page.\n metadata_only: When True, skip fetching content and return only\n document metadata (page_count, page_region_counts,\n title, edit_url). Use this to size up a document\n before deciding how to fetch it.\n "+ },+ {+ "slug": "LUCID_MCP_GET_MCP_RESOURCE",+ "name": "Get mcp resource",+ "description": "Reads a resource from this MCP server by URI.\n\n When a tool description says to read a resource (e.g. \"read lucid://diagram-specification\"),\n use this tool with that URI to retrieve the full content.\n\n Call with no arguments to list all available resources and their URIs.\n\n Args:\n resource_uri: The URI of the resource to read (e.g. \"lucid://diagram-specification\").\n Leave empty to list available resources.\n "+ },+ {+ "slug": "LUCID_MCP_LIST_DOCUMENT_THREAD_COMMENTS",+ "name": "List document thread comments",+ "description": "List comments on a specific collaboration thread of a Lucid document.\n\n Args:\n document_id: The UUID of the document.\n thread_id: The ID of the thread whose comments to fetch.\n\n Returns:\n JSON string of the Lucid API response (array of comment objects).\n "+ },+ {+ "slug": "LUCID_MCP_LIST_DOCUMENT_THREADS",+ "name": "List document threads",+ "description": "List collaboration threads on a Lucid document.\n\n Args:\n document_id: The UUID of the document.\n\n Returns:\n JSON string of the Lucid API response (array of thread objects).\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_ADD_BLOCK",+ "name": "Lucid add block",+ "description": "\n Add a new block (shape) to a Lucid document.\n\n DISCOVERY: Use lucid_shape_library to find valid block_type values for the target\n document, and lucid_shape_details to fetch a shape's default size, colors, and\n text-area names before calling this tool. Hallucinated class names produce 400 errors.\n\n Args:\n document_id: UUID of the document to modify\n block_type: Block class name. Examples: StickiesStickyNoteBlock, TextBlock,\n SparkFrameBlock, LucidCardBlock, RectangleBlock, ShapeDiamondBlock, ShapeCircleBlock\n x: X coordinate position (default 0)\n y: Y coordinate position (default 0)\n text: Text content for the block\n text_areas: Named text-area content updates, as a non-empty list of\n {\"key\": str, \"text\": str}. Use this for shapes with multiple text areas.\n Mutually exclusive with text.\n width: Block width in pixels\n height: Block height in pixels\n fill_color: Fill color in #RRGGBB format\n line_color: Border color in #RRGGBB format\n line_width: Border width\n stroke_style: Border style — one of \"solid\", \"dashed\", \"dotted\", \"dashdot\",\n \"dashdotdot\", \"dashed24\", \"dashed32\", \"dashed44\", \"dashlongdash\",\n \"dotdotdot\", \"longdash\"\n rotation: Rotation in degrees\n text_align: Horizontal text alignment — \"left\", \"center\", or \"right\"\n text_v_align: Vertical text alignment — \"top\", \"middle\", or \"bottom\"\n container_id: Item ID of a container block to place this block inside\n page_id: Page ID to add the block to (defaults to first page if omitted)\n bold: Whether to make the text bold\n italic: Whether to make the text italic\n underline: Whether to underline the text\n font_size: Font size in points (e.g. 14)\n text_color: Text color in #RRGGBB format\n strike: Whether to strikethrough the text\n superscript: Whether to make the text superscript\n subscript: Whether to make the text subscript\n font_family: Font family name (e.g. \"Arial\"); canvas falls back if unknown\n highlight_color: Text highlight color in #RRGGBB format\n link: Hyperlink to attach to the block. Accepts the same inputs the\n canvas \"Link to\" field accepts: an http(s) or ftp URL, a bare\n domain like \"www.example.com\" (auto-prefixed with http://), or\n the API-only forms \"mailto:<email>\" and \"page://<pageId>\". The\n page id form references a page in the same document.\n auto_font_size: Toggles Lucid's auto-fit-to-shape font sizing on the new\n block. True enables it (text resizes to fit the shape); False disables\n it (text keeps an explicit point size); omitted uses the block class's\n default. Providing a concrete font_size automatically disables\n auto-font-size, so callers do not need to also pass auto_font_size=False\n alongside a font_size. Mutually exclusive with a non-null font_size\n when set to True.\n\n Returns:\n JSON with success status and new itemId\n\n Example:\n Add a blue sticky note with bold text at position (200, 150):\n lucid_add_block(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n block_type=\"StickiesStickyNoteBlock\",\n x=200,\n y=150,\n text=\"Hello world\",\n fill_color=\"#FFD700\",\n bold=True,\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_ADD_DYNAMIC_TABLE",+ "name": "Lucid add dynamic table",+ "description": "\n Add a dynamic table to a Lucid document.\n\n Dynamic tables organize items into rows and columns and can be used for\n matrices, grids, kanban-style boards, planning tables, and prioritization\n maps. The table is created empty; add shapes/cards separately after the\n table exists.\n\n Args:\n document_id: UUID of the document to modify\n x: X coordinate position for the table's top-left placement (default 0)\n y: Y coordinate position for the table's top-left placement (default 0)\n rows: Optional row labels. If omitted, the canvas creates default rows.\n columns: Optional column labels. If omitted, the canvas creates default columns.\n page_id: Page ID to add the table to (defaults to first page if omitted)\n\n Returns:\n JSON with success status and generatorId for the new dynamic table\n\n Example:\n Create a simple priority matrix:\n lucid_add_dynamic_table(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n x=100,\n y=100,\n rows=[\"High impact\", \"Low impact\"],\n columns=[\"Low effort\", \"High effort\"],\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_ADD_ITEMS_TO_DYNAMIC_TABLE",+ "name": "Lucid add items to dynamic table",+ "description": "\n Add existing canvas blocks to a dynamic table.\n\n The generator's grouping logic places each block in the correct\n row/column based on its pivot-field value. Blocks whose pivot field\n does not match any row/column label land in the table's default cell.\n\n Args:\n document_id: UUID of the document containing the dynamic table\n generator_id: ID of the dynamic table generator (use the fetch\n tool to get the generator ID from the document)\n block_ids: IDs of existing blocks on the canvas to add to the table\n\n Returns:\n JSON with success status, number of blocks added, and an optional\n error message if some or all blocks could not be added.\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_ADD_LINE",+ "name": "Lucid add line",+ "description": "\n Add a new line to a Lucid document, connecting two points or shapes.\n\n Each endpoint is either:\n - A position endpoint: provide endpoint_x and endpoint_y (absolute canvas coords).\n - A shape endpoint: provide endpoint_shape_id. STRONGLY PREFER setting\n endpoint_auto_link=True for shape endpoints — the canvas will attach the line\n to the best side of the shape based on the line's direction and will re-route\n automatically as the shape is moved or resized. This is almost always the right\n choice when connecting two shapes and removes the need to reason about which\n side the line should enter from.\n\n Only set endpoint_position_x/y (a 0–1 relative coordinate on the shape) when\n you need a specific attachment point on the shape — for example when the user\n explicitly requests \"connect to the top of the box\" or when the line must\n terminate at a fixed anchor. If you do set explicit positions, avoid the\n default center (0.5, 0.5) because the line will overlap text inside the shape;\n pick a side instead (e.g. position_x=0, position_y=0.5 for the left edge).\n\n Use the fetch tool to get shape IDs from the document.\n\n Args:\n document_id: UUID of the document to modify\n endpoint1_x: X coordinate of the line's start point\n endpoint1_y: Y coordinate of the line's start point\n endpoint1_shape_id: Item ID of the shape to connect the start to\n endpoint1_position_x: Relative X position on start shape (0=left, 1=right, default 0.5)\n endpoint1_position_y: Relative Y position on start shape (0=top, 1=bottom, default 0.5)\n endpoint2_x: X coordinate of the line's end point\n endpoint2_y: Y coordinate of the line's end point\n endpoint2_shape_id: Item ID of the shape to connect the end to\n endpoint2_position_x: Relative X position on end shape (default 0.5)\n endpoint2_position_y: Relative Y position on end shape (default 0.5)\n line_color: Line color in #RRGGBB format\n line_width: Line width in pixels\n stroke_style: Line style — one of \"solid\", \"dashed\", \"dotted\", \"dashdot\",\n \"dashdotdot\", \"dashed24\", \"dashed32\", \"dashed44\", \"dashlongdash\",\n \"dotdotdot\", \"longdash\"\n text: Label text on the line\n page_id: Page ID to add the line to (defaults to first page if omitted)\n line_shape: Line routing — exactly one of \"elbow\" (right-angle),\n \"diagonal\" (straight), \"curve\" (smooth Bezier), or \"cyclical\" (loop).\n Omit to let the canvas pick its default routing. Set explicitly to\n \"elbow\" to force right-angle even when the canvas would default elsewhere.\n When the user says \"curved\" or \"smooth\" → \"curve\"; \"straight\" or \"direct\"\n → \"diagonal\"; \"right angle\" or \"orthogonal\" → \"elbow\"; \"loop\" → \"cyclical\".\n endpoint1_style: Arrow/terminator at the start. Case-sensitive. Examples:\n \"None\", \"Arrow\", \"Hollow Arrow\", \"Open Arrow\", \"Diamond\", \"Circle One\".\n Read resource lucid://endpoint-styles for the full list (UML, BPMN, ERD).\n endpoint2_style: Arrow/terminator at the end (same allowed values).\n endpoint1_auto_link: Only applies when endpoint1 connects to a shape.\n STRONGLY PREFERRED when connecting to a shape: set to True and the canvas\n picks the optimal side of the shape for the line to attach to and\n automatically re-routes when the shape moves or resizes. Overrides\n endpoint1_position_x/y when True. Leave False/unset only when you need\n to pin the endpoint to a specific spot on the shape.\n endpoint2_auto_link: Same as endpoint1_auto_link, for the end endpoint.\n Strongly preferred when endpoint2 connects to a shape.\n bold: Whether to make the label text bold\n italic: Whether to italicize the label text\n underline: Whether to underline the label text\n font_size: Label font size in points (e.g. 14)\n text_color: Label text color in #RRGGBB format\n strike: Whether to strikethrough the label text\n superscript: Whether to make the label text superscript\n subscript: Whether to make the label text subscript\n font_family: Label font family name (e.g. \"Arial\"); canvas falls back if unknown\n highlight_color: Label highlight color in #RRGGBB format\n\n Returns:\n JSON with success status and new itemId\n\n Example:\n Connect two shapes with a curved red arrow and a bold label:\n lucid_add_line(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n endpoint1_shape_id=\"kydGSpnbx.C4\",\n endpoint1_auto_link=True,\n endpoint2_shape_id=\"mydGB1ri3RCq\",\n endpoint2_auto_link=True,\n line_shape=\"curve\",\n line_color=\"#FF0000\",\n endpoint2_style=\"Arrow\",\n text=\"connects to\",\n bold=True,\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_DIAGRAM_FROM_SPECIFICATION",+ "name": "Lucid create diagram from specification",+ "description": "Creates a Lucid document using the Standard Import format (.lucid file).\n\n PREFLIGHT HARD GATE:\n - STOP and use lucid_convert_svg_to_diagram instead if an SVG of the diagram exists. Do NOT hand-author Standard Import JSON when SVG is available.\n - If this tool description appears truncated, summarized, quoted, or incomplete, first try to retrieve, expand, or read the full tool definition before deciding whether to call this tool.\n - If the full tool definition cannot be retrieved, use the most complete visible description available, but do not treat missing, hidden, summarized, or truncated text as permission to ignore any visible MUST, REQUIREMENT, HARD GATE, or PREREQUISITE instruction.\n - Read: lucid://diagram-specification\n - Reading lucid://diagram-specification is required before every call to this tool.\n - Do not call this tool until all visible hard prerequisites have been satisfied.\n - Do not call this tool until any available fuller tool-definition text has been read.\n\n AUTHORITY MODEL:\n - The full, untruncated tool description is authoritative for WHEN to call this tool when it is available, including intent classification, collaborative planning behavior, source/input dependency handling, clarification behavior, default generation behavior, and prerequisite handling.\n - If the full tool description cannot be retrieved, the most complete visible description is authoritative, but visible requirements remain binding and missing text must not be interpreted as permission to proceed.\n - The resource at lucid://diagram-specification is authoritative for HOW to construct the standard_import_json argument.\n - Do not duplicate, infer, or guess the Standard Import JSON format from this tool description. Read and follow lucid://diagram-specification for supported shapes, line syntax, container behavior, assisted layout rules, validation constraints, and all other formatting requirements.\n - Reading the referenced resource satisfies formatting/specification prerequisites. It does not replace the tool description's behavioral rules about when to call the tool, when to plan collaboratively, when to check for missing source/input dependencies, or when to ask clarifying questions.\n\n EXECUTION ORDER:\n A. Honor visible hard prerequisites.\n B. If the visible tool description appears truncated or incomplete, try to retrieve, expand, or read the full tool definition.\n C. If the full tool definition cannot be retrieved, continue only with the most complete visible description available and keep all visible MUST/REQUIREMENT/HARD GATE/PREREQUISITE instructions binding.\n D. Read all required referenced resources, including lucid://diagram-specification.\n E. Use the full available tool description, or the most complete visible description if the full definition cannot be retrieved, to decide WHEN to call the tool.\n F. Classify the user's intent.\n G. Apply intent precedence: collaborative planning beats default generation.\n H. Apply the source/input dependency gate. If required referenced source content is missing or inaccessible, ask for it and do not generate.\n I. If generation is appropriate, construct and validate standard_import_json using lucid://diagram-specification.\n J. Call the tool.\n\n SOURCE / INPUT DEPENDENCY GATE:\n Before generating, check whether the requested diagram depends on external, user-provided, uploaded, attached, linked, selected, or previously referenced content.\n\n A request depends on referenced source content when the user asks for a diagram based on content such as:\n - \"my file\"\n - \"the file\"\n - \"the uploaded file\"\n - \"the attached document\"\n - \"this PDF\"\n - \"this spreadsheet\"\n - \"this image\"\n - \"this screenshot\"\n - \"the link\"\n - \"this URL\"\n - \"the document I mentioned\"\n - \"the data\"\n - \"the dataset\"\n - \"the spec\"\n - \"the text above\"\n - \"the previous diagram\"\n - \"the selected content\"\n\n If the referenced source content is not actually available in the conversation, tool context, connected source, or provided arguments, do NOT generate a substitute, generic, or placeholder diagram. Ask exactly one short question requesting the missing source or clarifying what content to use.\n\n If the referenced source content is available, inspect or use that content before generating, unless another higher-priority rule requires collaborative planning or clarification first.\n\n This gate takes precedence over ordinary generation. A missing referenced source means the request is not an ordinary request, even if a plausible diagram type can be inferred.\n\n Do not confuse missing referenced content with ordinary subject matter. For example, \"Create a diagram about a file upload workflow\" is an ordinary generation request because \"file upload workflow\" is the subject, not a missing referenced file.\n\n Examples:\n - User: \"Create a diagram about my file.\" No file is available. Correct: ask the user to upload or link the file.\n - User: \"Make a flowchart from the attached PDF.\" No PDF is available. Correct: ask for the PDF.\n - User: \"Create a diagram from this spreadsheet.\" A spreadsheet is available. Correct: inspect/use the spreadsheet, then generate if appropriate.\n - User: \"Create a diagram about a file upload workflow.\" Correct: generate, because the user named the workflow as the subject.\n\n INTENT PRECEDENCE:\n Before generating, classify the user's request.\n\n Collaborative planning mode has precedence over default generation. Enter collaborative planning mode when the user explicitly asks the assistant to help with the planning, brainstorming, design, thinking, mapping, or iteration process before or while creating the diagram.\n\n Trigger collaborative planning mode for phrases such as:\n - \"help me plan...\"\n - \"help me design...\"\n - \"help me brainstorm...\"\n - \"help me think through...\"\n - \"help me work through...\"\n - \"help me map out...\"\n - \"help me iterate...\"\n - \"let's plan...\"\n - \"let's design...\"\n - \"let's brainstorm...\"\n - \"let's map out...\"\n - \"let's iterate...\"\n - \"work with me to...\"\n - \"before you generate...\"\n - \"before creating...\"\n\n In collaborative planning mode:\n 1. Do NOT create the diagram immediately.\n 2. Ask focused planning questions about the diagram type, subject, key elements, audience, level of detail, and desired output.\n 3. Propose a concise draft diagram spec or outline for confirmation.\n 4. Generate only after the user confirms, provides enough direction, or asks you to proceed.\n\n Do NOT enter collaborative planning mode merely because the diagram topic contains planning-related, brainstorming-related, design-related, or mapping-related words.\n\n Bare content phrases such as \"planning diagram,\" \"project plan,\" \"roadmap,\" \"brainstorming board,\" \"design flow,\" \"map out the process,\" or \"process map\" can be ordinary generation requests if the user is asking for a diagram about that subject rather than asking the assistant to collaborate on the planning process.\n\n ORDINARY REQUESTS:\n An ordinary request is a request where the user primarily asks to create, make, generate, build, or draw a diagram and provides enough information to identify:\n 1. a plausible diagram type,\n 2. a concrete or reasonably inferable subject, and\n 3. any referenced source content needed to create the requested diagram is available.\n\n A request is not ordinary if it depends on missing referenced content such as an unuploaded file, missing attachment, unavailable link, absent data, inaccessible selected content, or unavailable prior context.\n\n For ordinary requests, generate the diagram immediately using sensible defaults. Do NOT ask clarifying questions for ordinary requests, because users expect this tool to produce a diagram, not start a planning conversation.\n\n Examples of ordinary requests:\n - \"Create a flowchart with Start, Decision, and End connected by arrows.\"\n - \"Build a BPMN process with a start event and parallel tasks.\"\n - \"Create a project planning flowchart.\"\n - \"Make a mind map for a marketing launch plan.\"\n - \"Create a diagram that maps out our onboarding process.\"\n - \"Generate a simple architecture diagram for a web app.\"\n - \"Create a roadmap diagram for Q3 planning.\"\n - \"Create a diagram about a file upload workflow.\"\n\n Examples that require collaborative planning first:\n - \"Create a diagram and help me plan.\"\n - \"Help me plan a project flowchart.\"\n - \"Let's map out the onboarding process before creating the diagram.\"\n - \"Work with me to design the architecture diagram.\"\n - \"Before you generate, help me think through the process.\"\n\n Examples that require missing source/input clarification first:\n - \"Create a diagram about my file.\" when no file is available.\n - \"Make a flowchart from the attached PDF.\" when no PDF is attached.\n - \"Create a diagram from this spreadsheet.\" when no spreadsheet is available.\n - \"Generate a process map based on the link.\" when no link is provided or accessible.\n\n CLARIFICATION:\n Ask exactly ONE short clarifying question, then generate, if any of the following are true:\n 1. The request is internally contradictory, such as \"create a sequence diagram of our org structure.\"\n 2. The request is so abstract that no reasonable default exists, such as \"make me a diagram,\" meaning you cannot name both a concrete subject and a plausible diagram type.\n 3. Required referenced source content is missing or inaccessible, such as an unuploaded file, missing attachment, unavailable link, absent data, inaccessible selected content, or unavailable prior context.\n 4. Two defensible interpretations would produce substantively different diagrams and the user signaled they care about correctness with words such as \"important,\" \"for a presentation,\" \"get it right,\" or similar.\n\n Otherwise, generate now and state your assumptions in one line alongside the result so the user can redirect. Example:\n \"Generated as a flowchart with 5 stages; say 'change' to adjust.\"\n\n TOOL OUTPUT:\n This tool creates a .lucid ZIP file containing a document.json built from standard_import_json.\n\n Do not attempt to guess the Standard Import JSON format. The API validates strictly. Invalid or unsupported JSON can cause import failure. Use lucid://diagram-specification as the source of truth for all Standard Import JSON formatting, validation, layout, and supported-shape details.\n\n SHAPE NAMES: The standard import format requires the same canonical class names as\n lucid_add_block, so guessing them will fail validation. Use lucid://diagram-specification\n as the source of truth for supported shapes and their class names. (The\n lucid_shape_library / lucid_shape_details discovery tools require a document_id and\n operate on an existing document, so they cannot be used to pre-validate class names for\n this tool, which creates a new document.)\n\n Args:\n title: The title for the new document.\n standard_import_json: JSON string in Lucid Standard Import format. Construct this according to lucid://diagram-specification.\n product: Target product, either \"lucidchart\" or \"lucidspark\".\n use_assisted_layout: Auto-arranges shapes after import when true by default. See lucid://diagram-specification for when to set this true or false.\n\n Size Limits:\n - Total document.json: 2MB maximum.\n - Use concise JSON.\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_DOCUMENT_SHARE_LINK",+ "name": "Lucid create document share link",+ "description": "Creates a new share link for a document with specified permissions.\n\n Args:\n document_id: Valid UUID of the document to share\n role: Access permission level - one of: \"view\", \"comment\", \"edit\", \"editandshare\"\n restrict_to_account: Limit access to account members only (default: True)\n expires: Optional ISO 8601 timestamp for link expiration (e.g., \"2025-12-31T23:59:59Z\")\n allow_anonymous: Allow anonymous access via the share link (default: False)\n\n Returns:\n The acceptUrl string for the created share link. The link's properties\n (role, restrictToAccount, allowAnonymous, expires, documentId) are also\n attached as structuredContent so the share-link MCP app can display them.\n "+ },+ {+ "slug": "LUCID_MCP__LUCID_CREATE_EMBED",+ "name": " lucid create embed",+ "description": "Internal tool for MCP Apps extension only. Creates an embed for a Lucid document, returning an embed ID."+ },+ {+ "slug": "LUCID_MCP__LUCID_CREATE_EMBED_SESSION_TOKEN",+ "name": " lucid create embed session token",+ "description": "Internal tool for MCP Apps extension only. Creates a session token for an existing embed, returning a token and embed URL."+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_ERD",+ "name": "Lucid create erd",+ "description": "Creates a Lucid document containing a data-backed Entity Relationship Diagram (ERD).\n\n Use this tool when the user wants to create an ERD / database schema diagram\n from a set of entities (tables) and the foreign-key relationships between them.\n If the user provides raw SQL DDL, a CSV schema, or a Salesforce export, convert\n it into the structured `entities` / `relationships` form described below.\n\n The result is a real, editable ERD: each entity becomes an editable entity table\n and each relationship becomes a crow's-foot foreign-key line. The schema is stored\n as ERD data on the document, not as loose shapes.\n\n Each entity must have:\n - id: Unique string identifier (referenced by relationships)\n - name: Entity / table name (must be unique)\n - attributes: List of columns, each with a 'name' and optional 'type' and 'key'\n (e.g. \"PK\" for a primary key)\n\n Each relationship must have:\n - from: id of the entity that holds the foreign key (the \"many\" side)\n - to: id of the referenced entity (the \"one\" side)\n - fromAttribute (optional): the FK column on `from`\n - toAttribute (optional): the referenced PK column on `to`\n - fromCardinality / toCardinality (optional): one of one, many, zeroOrOne,\n zeroOrMore, oneOrMore, exactlyOne\n - label (optional): relationship label\n\n Example entities:\n [\n {\"id\": \"user\", \"name\": \"User\", \"attributes\": [\n {\"name\": \"id\", \"type\": \"uuid\", \"key\": \"PK\"},\n {\"name\": \"email\", \"type\": \"varchar\"}\n ]},\n {\"id\": \"post\", \"name\": \"Post\", \"attributes\": [\n {\"name\": \"id\", \"type\": \"uuid\", \"key\": \"PK\"},\n {\"name\": \"author_id\", \"type\": \"uuid\"}\n ]}\n ]\n Example relationships:\n [\n {\"from\": \"post\", \"to\": \"user\", \"fromAttribute\": \"author_id\", \"toAttribute\": \"id\",\n \"fromCardinality\": \"many\", \"toCardinality\": \"one\", \"label\": \"written by\"}\n ]\n\n Args:\n title: Document title (max 3000 characters)\n entities: List of entity dicts with id, name, and attributes (max 200 entities)\n relationships: List of relationship dicts referencing entity ids\n product: Target product - \"lucidchart\" (default) or \"lucidspark\"\n\n Returns:\n JSON with the created document details including document ID and edit URL\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_FOLDER",+ "name": "Lucid create folder",+ "description": "Create a new folder in the user's Lucid account.\n\n Args:\n name: Folder name (1-300 characters, no leading/trailing whitespace).\n folder_type: Either \"folder\" (default) or \"team\".\n parent: Parent folder for the new folder. Pass an integer\n folder ID to nest it under that folder. Omit (or pass the\n literal string \"root\") to create it at the root\n\n Returns:\n JSON string with the created folder resource (including its `id`).\n\n Example:\n lucid_create_folder(name=\"Project plans\", parent=12345)\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_MIND_MAP",+ "name": "Lucid create mind map",+ "description": "Creates a Lucid document containing a mind map from structured node data.\n\n Use this tool when the user wants to create a mind map or hierarchical\n topic diagram. Provide the topics as a flat list of nodes with parent-child\n relationships.\n\n Each node must have:\n - id: Unique string identifier\n - text: Display text for the node\n - parentId: ID of the parent node (null or omitted for the root node)\n\n There must be exactly one root node (with null/missing parentId).\n\n Example nodes:\n [\n {\"id\": \"1\", \"text\": \"Main Topic\", \"parentId\": null},\n {\"id\": \"2\", \"text\": \"Subtopic A\", \"parentId\": \"1\"},\n {\"id\": \"3\", \"text\": \"Subtopic B\", \"parentId\": \"1\"},\n {\"id\": \"4\", \"text\": \"Detail A1\", \"parentId\": \"2\"}\n ]\n\n Args:\n title: Document title (max 3000 characters)\n nodes: List of node dicts with id, text, and optional parentId fields (max 1000 nodes)\n product: Target product - \"lucidchart\" (default) or \"lucidspark\"\n\n Returns:\n JSON with the created document details including document ID and edit URL\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_ORG_CHART",+ "name": "Lucid create org chart",+ "description": "Creates a Lucidchart document containing an org chart from structured node data.\n\n Use this tool when the user wants to create an organizational chart,\n team structure, or reporting hierarchy diagram. Provide the people/roles\n as a flat list of nodes with manager-report relationships.\n\n Each node must have:\n - id: Unique string identifier\n - name: Person or role name\n - managerId: ID of the manager node (null or omitted for the top-level person)\n\n Optional fields per node:\n - role: Job title or role description\n - imageUrl: URL to a profile image\n\n There must be exactly one root node (with null/missing managerId).\n\n Example nodes:\n [\n {\"id\": \"1\", \"name\": \"Alice Smith\", \"managerId\": null, \"role\": \"CEO\"},\n {\"id\": \"2\", \"name\": \"Bob Jones\", \"managerId\": \"1\", \"role\": \"VP Engineering\"},\n {\"id\": \"3\", \"name\": \"Carol White\", \"managerId\": \"1\", \"role\": \"VP Marketing\"},\n {\"id\": \"4\", \"name\": \"Dave Brown\", \"managerId\": \"2\", \"role\": \"Senior Engineer\"}\n ]\n\n Args:\n title: Document title (max 3000 characters)\n nodes: List of node dicts with id, name, and optional managerId/role/imageUrl fields (max 1000 nodes)\n\n Returns:\n JSON with the created document details including document ID and edit URL\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_CREATE_SEQUENCE_DIAGRAM",+ "name": "Lucid create sequence diagram",+ "description": "Creates a Lucid document containing a UML sequence diagram from PlantUML markup.\n\n REQUIREMENT: Before attempting to use this tool, you MUST read the resource at lucid://sequence-diagram-specification\n for details on participant types, arrows, syntax, and examples.\n\n Use this tool when the user wants to create a UML sequence diagram showing\n interactions between participants over time. Provide the diagram definition\n using PlantUML sequence diagram syntax.\n\n Styling:\n Diagrams are automatically styled with Lucid blue theme colors (blue\n participants, blue arrows, light blue fills). You do not need to add\n color directives for a good-looking diagram. However, you can optionally\n override colors on individual elements.\n\n Args:\n title: Document title (max 3000 characters)\n markup: PlantUML sequence diagram markup (max 50KB)\n product: Target product - \"lucidchart\" (default) or \"lucidspark\"\n\n Returns:\n JSON with the created document details including document ID and edit URL\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_DELETE_ITEMS",+ "name": "Lucid delete items",+ "description": "\n Delete one or more blocks or lines from a Lucid document.\n\n This action is destructive and cannot be undone via the API.\n Use the fetch tool first to get item IDs from the document.\n\n Args:\n document_id: UUID of the document to modify\n item_ids: List of item IDs to delete\n\n Returns:\n JSON with success status, deletedCount, and any errors\n\n Example:\n lucid_delete_items(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n item_ids=[\"FxdGNC-3_L46\", \"LYdG8~L0mHE-\"],\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_EDIT_DYNAMIC_TABLE_METADATA",+ "name": "Lucid edit dynamic table metadata",+ "description": "Edit the metadata/settings of an existing dynamic table.\n\n Updates the reactive settings of a dynamic-table generator: the agile capacity-planning\n and load-tracking-graphic toggles, and the row/column group-by fields. Only the parameters\n you provide are changed; omitted parameters are left as-is.\n\n Group-by fields accept a field name (e.g. \"status\", \"sprint\", \"assignee\", \"priority\") or\n \"none\" to remove that grouping. An invalid field name returns an error listing the valid\n options for that table.\n\n Standard data fields (status, assignee, priority, parent, estimate, project, reporter,\n sprint, team, work item type) pivot on the live data-source value. Add the cards (e.g. via\n lucid_add_items_to_dynamic_table or lucid_import_integration_cards) BEFORE setting the pivot\n or you will get a validation error. The table will not automatically add cards if you hit\n that error; add the cards and call this tool again.\n\n Args:\n document_id: UUID of the document containing the dynamic table.\n generator_id: ID of the dynamic table generator (from the fetch/canvas-query tools).\n enable_agile_capacity_planning: Toggle agile capacity planning on or off.\n show_load_tracking_graphic: Toggle the load-tracking graphic on or off.\n column_group_by_field: Field to group columns by, or \"none\" to remove column grouping.\n row_group_by_field: Field to group rows by, or \"none\" to remove row grouping.\n\n Returns:\n JSON string from the underlying tool (success/error envelope).\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_EDIT_ITEM",+ "name": "Lucid edit item",+ "description": "\n Edit an existing block or line in a Lucid document.\n\n Use the fetch tool first to get item IDs from the document.\n\n For blocks: use x, y, width, height to move/resize.\n For lines: use endpoint params to reposition endpoints (same as lucid_add_line).\n Do not mix block position params with line endpoint params.\n\n Args:\n document_id: UUID of the document to modify\n item_id: ID of the item to edit\n text: New text content\n text_areas: Named text-area content updates, as a non-empty list of\n {\"key\": str, \"text\": str}. Use this for shapes with multiple text areas.\n Mutually exclusive with text.\n fill_color: Fill color in #RRGGBB format\n line_color: Border/line color in #RRGGBB format\n line_width: Border/line width in pixels\n stroke_style: Border/line style — one of \"solid\", \"dashed\", \"dotted\",\n \"dashdot\", \"dashdotdot\", \"dashed24\", \"dashed32\", \"dashed44\",\n \"dashlongdash\", \"dotdotdot\", \"longdash\"\n rotation: Rotation in degrees\n text_align: Horizontal text alignment — \"left\", \"center\", or \"right\"\n text_v_align: Vertical text alignment — \"top\", \"middle\", or \"bottom\"\n x: Absolute X position (blocks only)\n y: Absolute Y position (blocks only)\n width: Width in pixels (blocks only)\n height: Height in pixels (blocks only)\n endpoint1_x: X coordinate of the line's start point\n endpoint1_y: Y coordinate of the line's start point\n endpoint1_shape_id: Item ID of the shape to connect the start to\n endpoint1_position_x: Relative X position on start shape (0=left, 1=right)\n endpoint1_position_y: Relative Y position on start shape (0=top, 1=bottom)\n endpoint2_x: X coordinate of the line's end point\n endpoint2_y: Y coordinate of the line's end point\n endpoint2_shape_id: Item ID of the shape to connect the end to\n endpoint2_position_x: Relative X position on end shape\n endpoint2_position_y: Relative Y position on end shape\n bold: Whether to make the text bold\n italic: Whether to make the text italic\n underline: Whether to underline the text\n font_size: Font size in points (e.g. 14)\n text_color: Text color in #RRGGBB format\n strike: Whether to strikethrough the text\n superscript: Whether to make the text superscript\n subscript: Whether to make the text subscript\n font_family: Font family name (e.g. \"Arial\"); canvas falls back if unknown\n highlight_color: Text highlight color in #RRGGBB format\n locked: Lock or unlock the item (any item type). True restricts editing/moving;\n False unlocks; omit to leave the lock state unchanged.\n line_shape: Lines only — routing for the line: \"elbow\" (right angles), \"diagonal\"\n (straight any-angle), \"curve\" (smooth Bezier), or \"cyclical\" (loop).\n endpoint1_style: Lines only — arrow/terminator style at the start endpoint.\n Values are case-sensitive (e.g. \"Hollow Arrow\", not \"hollow_arrow\"). Common\n values: \"None\", \"Arrow\", \"Hollow Arrow\", \"Open Arrow\", \"Diamond\", \"Aggregation\",\n \"Composition\", \"Generalization\". UML, BPMN, and ERD (Crow's Foot) styles also\n supported — read resource lucid://endpoint-styles for the full list.\n endpoint2_style: Lines only — arrow/terminator style at the end endpoint\n (same values as endpoint1_style).\n link: Block-only. Hyperlink to attach to the block. Accepts the same\n inputs the canvas \"Link to\" field accepts: an http(s) or ftp URL,\n a bare domain like \"www.example.com\" (auto-prefixed with http://),\n or the API-only forms \"mailto:<email>\" and \"page://<pageId>\".\n Ignored for lines. To remove an existing link, pass clear_link=True\n instead of setting this.\n clear_link: Block-only. When True, removes any hyperlink currently attached\n to the block. Ignored for lines. Mutually exclusive with link.\n auto_font_size: Block-only. Toggles Lucid's auto-fit-to-shape font sizing on\n a block. True enables it (text resizes to fit the shape); False disables it\n (text keeps an explicit point size); omitted leaves the current state\n unchanged. Silently ignored on lines. Note: providing a concrete font_size\n automatically disables auto-font-size, so callers do not need to also pass\n auto_font_size=False alongside a font_size. Mutually exclusive with a\n non-null font_size when set to True.\n\n Returns:\n JSON with success status and itemId\n\n Example:\n Edit a block's text and color:\n lucid_edit_item(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n item_id=\"dydGcNA5W-MZ\",\n text=\"Updated Step A\",\n fill_color=\"#FFD700\",\n )\n\n Move a line's start endpoint to a new shape:\n lucid_edit_item(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n item_id=\"i1dG5VAgqniu\",\n endpoint1_shape_id=\"kydGSpnbx.C4\",\n endpoint1_position_x=1.0,\n endpoint1_position_y=0.5,\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_EXPORT_DOCUMENT_AS_PNG",+ "name": "Lucid export document as png",+ "description": "Exports a Lucid document page as a PNG image. To crop the image, pass a bounding_box whose x, y, w, and h fields correspond directly to BoundingBox values returned by lucid_fetch. The box can describe one shape or a larger region containing multiple shapes."+ },+ {+ "slug": "LUCID_MCP_LUCID_FETCH_ITEM_IMAGE",+ "name": "Lucid fetch item image",+ "description": "Fetches the source image attached to a specific item in a Lucid document."+ },+ {+ "slug": "LUCID_MCP_LUCID_GET_DOCUMENT_METADATA",+ "name": "Lucid get document metadata",+ "description": "Get metadata for a Lucid document.\n\n The requesting user must have at least read-only access to the document.\n Owner information is returned for unpublished documents when the\n requesting user has view access. For published documents, viewers\n receive account-level owner information; the individual user owner's ID\n is returned only when the requesting user is at least a collaborator.\n\n Args:\n document_id: UUID of the document to retrieve.\n\n Returns:\n JSON string containing the document's metadata, access details,\n location, classification, and owner information when authorized.\n\n Example:\n lucid_get_document_metadata(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_IMPORT_INTEGRATION_CARDS",+ "name": "Lucid import integration cards",+ "description": "Import records from a third-party integration as linked cards.\n\n You MUST call `lucid_list_integrations` first to obtain `instance_id`\n — it is the exact `instanceId` field returned for the desired\n integration instance, not a free-form string, and cannot be guessed\n from context.\n\n Args:\n document_id: UUID of the Lucid document to add cards to.\n integration_id: Which integration the records live in. Today only\n \"jira\" is supported.\n instance_id: The `instanceId` field from a `lucid_list_integrations`\n entry, identifying which connected instance of `integration_id`\n to pull records from. Must come from `lucid_list_integrations`;\n do not construct it.\n record_keys: Integration-specific identifiers for the records to\n import (e.g. Jira issue keys like [\"MCP-1\", \"MCP-2\"]).\n page_id: Page to drop the cards on (defaults to the first page).\n x: Top-left x coordinate of the first card. Defaults to 0.\n y: Top-left y coordinate of the first card. Defaults to 0.\n layout: One of \"grid\", \"row\", \"column\". Defaults to \"grid\".\n\n If the user is not connected to the requested integration instance,\n returns `{status: \"not_connected\", connect_url, ...}` — send the user\n to `connect_url` (their Lucid Apps & Integrations page) to connect.\n Do NOT attempt to authenticate on their behalf.\n\n Returns:\n JSON with `{success, blockIds, dataSourceId, errors}` on success,\n or a structured `{status: \"not_connected\" | \"unsupported_integration\", ...}`\n response when the precondition isn't met. `errors` is a list of\n `{recordKey, error}` entries for keys that could not be imported\n or whose AddBlock op failed; this tool returns partial success\n when only some keys fail.\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_LIST_FOLDER_CONTENTS",+ "name": "Lucid list folder contents",+ "description": "List the documents and subfolders inside a Lucid folder.\n\n Pass `folder_id=None` (the default) to list the user's root folder.\n When more pages are available, the response includes a\n `nextPageToken`; pass it back as `page_token` to fetch the next page.\n\n Args:\n folder_id: Numeric folder ID, or omit/None for the root folder.\n page_size: Page size (1-200, default 50).\n page_token: Opaque cursor from a previous response's\n `nextPageToken` field.\n\n Returns:\n JSON string of the form\n `{\"items\": [...], \"nextPageToken\": \"...\"?}`. The underlying API\n returns items as a bare list and carries pagination in a `Link`\n header; this tool reshapes that into a single object.\n\n Example:\n lucid_list_folder_contents(folder_id=12345, page_size=100)\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_LIST_INTEGRATIONS",+ "name": "Lucid list integrations",+ "description": "List the user's available card integrations and their connection status.\n\n Use this to find out which third-party integrations (e.g. Jira) the user is\n connected to before attempting any integration-backed action.\n\n Returns:\n A JSON array. Each entry describes one integration:\n {\n \"integration\": str, # e.g. \"jira\"\n \"instances\": [\n {\"instanceId\": str, \"name\": str, \"adapterType\": str, \"isConnected\": bool}\n ]\n }\n\n Connection is tracked per instance: an instance with isConnected=false is\n authenticated but not fully connected (its live-sync isn't healthy). An\n integration with no instances, or no instance with isConnected=true, is not\n usable yet. In that case tell the user to connect it from the Lucid editor:\n open a document and use the integration/import panel. Do NOT attempt to\n authenticate on their behalf, and do NOT fabricate a connect link.\n\n # Jira specifics\n `adapterType` is one of \"JiraCloud\", \"JiraDataCenter\", or \"JiraGovCloud\".\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_SEARCH_DOCUMENT",+ "name": "Lucid search document",+ "description": "Locates regions of a Lucid document that contain specific text.\n\n Use this BEFORE `fetch` when you're looking for content you can describe\n with specific words or phrases — it tells you which (pageIndex, regionIndex)\n pairs contain matches so you can then `fetch` only those regions instead of\n paging through the whole document.\n\n Matching is case-insensitive substring over each region's TextAreas\n content (shape labels, sticky-note text, etc.). It does NOT match against\n notes, tags, links, colors, or other metadata.\n\n Returns a JSON object of the form:\n {\n \"matches\": {\n \"<query>\": [\n {\"pageIndex\": 1, \"regionIndex\": 3, \"context\": [\"Q3 KPI Tracking\"]},\n ...\n ],\n \"<otherQuery>\": []\n },\n \"title\": \"...\"\n }\n\n Every query you pass appears as a key in `matches`, even when it has no\n hits — so you can rely on `matches[query]` without first checking presence.\n `pageIndex` and `regionIndex` are 1-based and can be passed directly to\n `fetch` as `page_index` and `region_index`.\n\n Args:\n id: Valid UUID of the document.\n queries: Non-empty list of literal search terms (1-20 items, each at\n most 200 characters). Each query is matched independently as a\n case-insensitive substring; the response groups hits by query.\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_SHAPE_DETAILS",+ "name": "Lucid shape details",+ "description": "Get default size, colors, and advanced/text-area properties for one or more shape\n classes.\n\n Use this tool after lucid_shape_library has narrowed to candidate class names. The\n returned details (default fill/line colors, default size, advanced property descriptors,\n and text-area names) tell you which optional fields lucid_add_block and lucid_edit_item\n can sensibly omit (defaults applied) versus which named text areas the shape supports.\n\n Unknown class names produce a per-shape error in the response rather than failing the\n whole call.\n\n Args:\n document_id: UUID of the document context (so libraries scoped to that product and\n the user's custom libraries are available for lookup).\n class_names: List of shape class names to inspect (e.g. \"StickiesStickyNoteBlock\").\n\n Returns:\n JSON string from the underlying tool (success/result envelope).\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_SHAPE_LIBRARY",+ "name": "Lucid shape library",+ "description": "Discover shapes/blocks available to INSERT into a Lucid document.\n\n This does NOT find documents or text inside a document. To find a\n document by name use `search`; to find text within one open document\n use `lucid_search_document`. Only use this tool when the user wants a\n shape to add to a diagram.\n\n Use this tool to find valid block class names before calling lucid_add_block or\n lucid_edit_item on an existing document; hallucinating class names will produce 400\n errors and this tool returns the canonical list. Note: this requires a document_id and\n operates on an existing document, so it cannot pre-validate class names for\n lucid_create_diagram_from_specification (which creates a new document) — for that flow,\n use the lucid://diagram-specification resource as the canonical shape reference.\n\n Modes (all driven by the same call):\n - No params: lists every visible shape library by id and name.\n - libraryId only: lists groups (folders) within that library, with shapes inlined when\n the library has a single group.\n - libraryId + groupIds: returns the shapes within the specified groups.\n - searchTerm: searches across libraries (or within libraryId if also provided) and\n returns matching shapes. Cannot be combined with groupIds.\n\n The no-param library listing is paginated: when the response includes a NextPageToken,\n pass it back as page_token to fetch the next page of libraries.\n\n After narrowing to a candidate shape, call lucid_shape_details with its className to get\n default size/colors and any custom properties before passing it to add/create tools.\n\n Args:\n document_id: UUID of the document context (libraries available depend on product\n and the user's allow-listed libraries).\n search_term: Optional free-text query against shape names and keywords.\n library_id: Optional library identifier from a previous response.\n group_ids: Optional list of group identifiers within library_id; only valid when\n library_id is also provided (groups belong to a specific library).\n page_token: Optional pagination cursor; pass the NextPageToken from a previous\n no-param listing response to fetch the next page of libraries.\n\n Returns:\n JSON string from the underlying tool (success/result envelope).\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_SUBMIT_FEEDBACK",+ "name": "Lucid submit feedback",+ "description": "Submits user feedback about the Lucid MCP server to the product team.\n\n Use this tool when the user wants to share feedback, report a bug, request\n a feature, or otherwise comment on their experience with the Lucid MCP\n server's tools. The feedback is routed to Lucid's product team.\n\n Args:\n title: A short title summarizing the feedback. Required.\n feedback: The feedback from the user. Required.\n\n Returns:\n A message indicating whether the feedback was successfully submitted.\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_UPDATE_DOCUMENT",+ "name": "Lucid update document",+ "description": "Update a Lucid document's title, parent folder, or custom tags.\n\n Use this tool to rename a document or move it between folders.\n At least one of `title`, `parent`, or `custom_tags` must be provided.\n\n Args:\n document_id: UUID of the document to update\n title: New title for the document. Omit to leave unchanged.\n parent: Move the document to a new parent. Pass an integer\n folder ID to move it under that folder, or the literal\n string \"root\" to move it to the root folder. Omit to leave\n the document where it is.\n custom_tags: Replacement list of custom tag strings. Omit to\n leave existing tags unchanged. Pass an empty list to clear.\n\n Returns:\n JSON string with the updated document resource.\n\n Example:\n lucid_update_document(\n document_id=\"8fb1756d-d7f1-4f8c-933a-40e30fa5d102\",\n title=\"Q3 Roadmap\",\n parent=12345,\n )\n "+ },+ {+ "slug": "LUCID_MCP_LUCID_UPDATE_FOLDER",+ "name": "Lucid update folder",+ "description": "Rename a Lucid folder or move it to a different parent.\n\n At least one of `name` or `parent` must be provided.\n\n Args:\n folder_id: Numeric ID of the folder to update.\n name: New folder name. Omit to leave unchanged.\n parent: Move the folder to a new parent. Pass an integer folder\n ID to move it under that folder, or the literal string\n \"root\" to move it to the root. Omit to leave the folder\n where it is.\n\n Returns:\n JSON string with the updated folder resource.\n\n Example:\n lucid_update_folder(folder_id=12345, name=\"Archived plans\")\n "+ },+ {+ "slug": "LUCID_MCP_POST_DOCUMENT_THREAD_COMMENT",+ "name": "Post document thread comment",+ "description": "Post a new comment to an existing thread on a Lucid document.\n\n Args:\n document_id: The UUID of the document.\n thread_id: The thread to comment on.\n content: The text body of the comment.\n\n Returns:\n JSON string of the created comment.\n "+ },+ {+ "slug": "LUCID_MCP_SEARCH",+ "name": "Search",+ "description": "Search the user's Lucid account for documents by title/keyword.\n\n This is the default tool for a generic \"search for X\" request. Use it\n unless the user explicitly wants shapes to insert (`lucid_shape_library`)\n or text inside a document (`lucid_search_document`). If\n it is ambiguous which of the three the user means, ask before searching.\n\n Args:\n query: String containing space-separated keywords to be searched for (max 400 characters)\n product: Optional list of product types to filter by. Valid values: \"lucidchart\", \"lucidspark\", \"lucidscale\"\n created_start_time: Optional ISO 8601 timestamp to filter documents created after this time (e.g., \"2024-01-01T00:00:00Z\")\n created_end_time: Optional ISO 8601 timestamp to filter documents created before this time (e.g., \"2024-12-31T23:59:59Z\")\n last_modified_after: Optional ISO 8601 timestamp to filter documents modified after this time (e.g., \"2024-01-01T00:00:00Z\")\n owned_by_me: Optional. When true, only return documents you own. Note: ownership can change when a document is moved out of a team folder or transferred to another user, so this reflects current ownership rather than original authorship.\n\n Returns:\n Search results with document titles, IDs, URLs, and parent folder IDs, sorted by relevance.\n Returns up to 200 results (API maximum).\n "+ },+ {+ "slug": "LUCID_MCP_SHARE_DOCUMENT_WITH_COLLABORATORS",+ "name": "Share document with collaborators",+ "description": "Share a Lucid document with collaborators by granting them access.\n\n This tool searches for users by their email addresses, then grants them\n the specified collaborator role on the document.\n\n Args:\n document_id: The UUID of the document to share\n emails: List of email addresses to share the document with (max 100)\n role: The collaborator role to grant. Options:\n - \"view\": View-only access\n - \"edit\": Edit access\n - \"editandshare\": Edit and share access (default)\n - \"comment\": Comment-only access\n\n Returns:\n JSON string with results for each email address, indicating success or failure\n "+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "lucid_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "offline_access"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "luma_labs","name": "Luma Labs",@@ -234543,6 +242998,186 @@}]},+ {+ "slug": "magic_patterns_mcp",+ "name": "Magic Patterns MCP",+ "logo": "https://logos.composio.dev/api/magic_patterns_mcp",+ "description": "Magic Patterns MCP lets agents create and iterate on interface designs, inspect design status and history, read or modify artifact files, and publish authorized design artifacts.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 23,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "MAGIC_PATTERNS_MCP_CREATE_DESIGN",+ "name": "Create design",+ "description": "Creates a new Magic Patterns design. This is the starting point for both prompt-based and code-first workflows.\n\nBEHAVIOR:\n- With prompt: Creates a design and kicks off AI generation (long-running, especially when design-system setup is involved). Do not wait synchronously; poll get_design_status to track progress.\n- Without prompt: Creates a blank design with scaffold files (App.tsx, index.tsx, index.css, tailwind.config.js) — returns immediately.\n- With templateId: Forks an existing design first, then optionally applies the prompt to the fork. The templateId is an editor ID — you can get it from a design URL (the ID in magicpatterns.com/c/<id>) or via get_editor_id_from_url.\n\nYou can optionally specify a design system. If the user mentions one, call list_design_systems first.\n\nNEXT STEPS:\n- With prompt: Call get_design_status(editorId) to poll until generation completes. This often takes a while, so the caller should keep polling instead of assuming the design is ready immediately.\n- Without prompt: Call get_design_status(editorId) to get the active artifact, then create_new_artifact to start editing."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_CREATE_DESIGN_SYSTEM",+ "name": "Create design system",+ "description": "Creates a new, blank design system owned by you and returns its ID + editor URL. Seeds an empty initial version so you can immediately write files into it.\n\nNEXT STEPS:\n- write_design_system_files(designSystemId, files) to add components, styling, and rules\n- publish_design_system(designSystemId) to publish a version\n\nNote: this creates a BLANK design system. Forking from an existing design system is not supported here."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_CREATE_INSPIRATION_DOCUMENT",+ "name": "Create inspiration document",+ "description": "Creates a Magic Patterns inspiration document and returns a shareable magicpatterns.com/inspiration/<id> link that renders the concepts side by side.\n\nPreferred flow: create a PLACEHOLDER here by declaring each concept's { name, description } WITHOUT html, then fill each one in with a separate inspiration_add_variant call (passing the html directly). This lets you publish the link immediately and stream each concept in without ever holding all the HTML at once. The page shows a loading tile per declared concept until its html arrives.\n\nYou may also pass html inline for any/all concepts to publish them fully in one call (the document is only marked ready once every concept has html).\n\nINPUT:\n- title: short label for what the concepts explore (e.g. \"Projects list empty state\").\n- files: 1-8 concepts, each { name, description, html? }. Omit html to declare a placeholder concept to fill later via inspiration_add_variant.\n- repositoryUrl: optional GitHub repo the concepts came from (kept for context).\n- baseline: optional { html, focus, sharedCopy, baselineStyle } — the baseline the variants diverge from (html is the faithful recreation of the current UI).\n\nRESPONSE: { id, url, variants: [{ id, name }] }. Pass each variant id (with the inspiration id) to inspiration_add_variant to fill it in. Return the url to the user; it may require login."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_CREATE_NEW_ARTIFACT",+ "name": "Create new artifact",+ "description": "Creates a new artifact by cloning an existing artifact. The new artifact becomes the active artifact for the design. This gives you a safe \"branch\" to write code to before publishing.\n\nBEFORE CALLING: Always call get_design_status or get_artifact first to get the CURRENT active artifact ID. The user may have changed the active artifact in the UI since you last checked.\n\nWHEN TO USE: Call this BEFORE making file changes (write_artifact_files) so the user can revert to the previous artifact if needed.\n\nThe new artifact is set as active and a version entry is added to the design timeline with the provided name.\n\nNEXT STEPS:\n- Call read_artifact_files(artifactId, fileNames) to understand existing code.\n- Call write_artifact_files(artifactId, files) to make changes.\n- Call publish_artifact(artifactId, editorId) when done."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_CREATE_SLIDE_DECK",+ "name": "Create slide deck",+ "description": "Creates a new Magic Patterns slide deck and kicks off AI generation. A slide deck is a 16:9, full-bleed, one-slide-at-a-time React presentation where each slide maps to a screen in the canvas.\n\nBEHAVIOR:\n- A prompt is REQUIRED — the deck is generated from it (unlike create_design, there is no blank-deck path).\n- Generation is long-running (especially with design-system setup). Do not wait synchronously; poll get_design_status to track progress.\n\nYou can optionally specify a design system. If the user mentions one, call list_design_systems first.\n\nNEXT STEPS:\n- Call get_design_status(editorId) to poll until generation completes. This often takes a while, so keep polling instead of assuming the deck is ready immediately."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_GET_ARTIFACT",+ "name": "Get artifact",+ "description": "Gets the active artifact for a design, including its ID and list of files.\n\nUse this to discover the current artifact before reading files or creating a new artifact branch. Because the editor is collaborative, always call this (or get_design_status) to get the LATEST active artifact — do not rely on a previously cached artifact ID.\n\nNEXT STEPS:\n- Call read_artifact_files(artifactId, fileNames) to read code.\n- Call create_new_artifact(artifactId, name) to create a working copy before making changes."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_GET_DESIGN_STATUS",+ "name": "Get design status",+ "description": "Gets the current status of a design: whether AI generation is active, the active artifact ID, and available files.\n\nALWAYS call this before starting new work on an existing design. The user or other agents may have changed the active artifact, sent prompts, or made edits in the UI since you last checked. This is your source of truth for the current state.\n\nAlso use this to poll for completion after create_design (with prompt) or send_prompt.\n\nRESPONSE:\n- isGenerating: true if AI is still working\n- activeArtifactId: the current active artifact ID (use for create_new_artifact, read_artifact_files, etc.)\n- availableFiles: list of file names in the active artifact\n\nNEXT STEPS:\n- If isGenerating=true: Wait at least 60 seconds before polling again. Generation can take up to 10 minutes.\n- If isGenerating=false: Use activeArtifactId with create_new_artifact (for code-first edits) or read_artifact_files (to inspect generated code)."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_GET_DESIGN_SYSTEM",+ "name": "Get design system",+ "description": "Resolves a design system's active artifact and lists its files. ALWAYS call this first — design systems are collaborative, so the active artifact id can change between calls; never reuse a cached artifactId.\n\nReturns:\n- artifactId: the current active artifact (pass as baseArtifactId to write_design_system_files to detect drift)\n- files: the persisted files (e.g. components/<Name>/*, index.css, tailwind.config.js, rules/*)\n- hasUnpublishedChanges: whether the active artifact differs from the latest published version\n- guide: pointer to the design_system_authoring_guide prompt — load it before writing files\n\nNEXT STEPS:\n- read_design_system_files(designSystemId, fileNames) to read file contents\n- write_design_system_files(designSystemId, files) to create or update files\n- publish_design_system(designSystemId) to publish a new version"+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_GET_EDITOR_ID_FROM_URL",+ "name": "Get editor id from url",+ "description": "Resolves a Magic Patterns URL to an editor ID. Use this when the user shares a Magic Patterns link and you need the editorId for subsequent operations like send_prompt or get_design_status.\n\nNEXT STEPS: Use the returned editorId with send_prompt, get_design_status, get_artifact, or other editor-scoped tools."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_GET_INSPIRATION_DOCUMENT",+ "name": "Get inspiration document",+ "description": "Loads a Magic Patterns inspiration document by its id. An inspiration document is a set of design \"concepts\" (variants) — each a self-contained HTML sketch of a UI direction.\n\nUse this when the user asks to implement/build a specific concept from a Magic Patterns inspiration (e.g. \"Implement Concept B from Magic Patterns inspiration <id>\"). Pass the inspiration id as `inspirationId`.\n\nRESPONSE:\n- title, userPrompt: the original request the concepts explore\n- viewport: the canvas the concepts were authored against (absent = 1280x800 desktop). Any concept you regenerate must be authored at these exact dimensions.\n- status: 'generating' while concepts are still being produced, else 'ready'/'error'.\n- variants: the concepts, in order. Concept A = variants[0], Concept B = variants[1], etc. Each has { id, name, description, implementationPrompt, html, status }. A variant is only usable once its `status` is 'ready'; a non-ready one has empty/partial `html` and must NOT be recreated (retry after generation finishes).\n\nNEXT STEPS: Pick the referenced concept (by letter/name), confirm its `status` is 'ready', then recreate its `html` as a React + TypeScript component in the user's project, keeping the styling 1:1 (same layout, colors, spacing, typography; copy SVGs verbatim)."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_INSPIRATION_ADD_VARIANT",+ "name": "Inspiration add variant",+ "description": "Fills in one concept of an existing Magic Patterns inspiration document with its self-contained HTML.\n\nUse this after create_inspiration_document to stream concepts in one at a time: pass the html directly here instead of holding it all for a single create call. The concept renders live on the shared page as soon as its html arrives, and the document flips to \"ready\" once every concept is filled.\n\nINPUT:\n- inspirationId: the inspiration document id returned by create_inspiration_document.\n- variantId: the concept id returned by create_inspiration_document (targets that specific placeholder). If omitted, the first still-empty concept is filled.\n- name / description: optional; updates the concept's label/direction.\n- html: the full, self-contained HTML document (non-empty).\n\nRESPONSE: { ok, variantId, url }."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_INSPIRATION_CLEAR_VARIANTS",+ "name": "Inspiration clear variants",+ "description": "Resets every concept of an existing Magic Patterns inspiration document back to an empty placeholder — dropping each concept's html and its pre-created \"Iterate\" room.\n\nUse this to REPLACE all concepts: clear the document, then invent a fresh set of directions and stream each one's html back in with inspiration_add_variant (targeting the returned concept ids). The document shows loading tiles again until the new concepts arrive.\n\nINPUT:\n- inspirationId: the inspiration document id returned by create_inspiration_document.\n\nRESPONSE: { ok, url, variants: [{ id, name }] }. Each concept keeps its id and name; pass them to inspiration_add_variant (with a new name/description/html) to fill the fresh concepts in."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_INSPIRATION_UPDATE_VARIANT",+ "name": "Inspiration update variant",+ "description": "Revises a single already-filled concept of a Magic Patterns inspiration document in place, replacing its html (and optionally its name/description).\n\nUse this to UPDATE a subset of concepts (e.g. \"focus more on the messaging\", \"update Concept C\") without touching the others: read the current concepts with get_inspiration_document, regenerate the targeted concept FROM ITS PREVIOUS html, then push the revised html here. The concept's \"Iterate in Magic Patterns\" room is refreshed so it builds from the new html.\n\nINPUT:\n- inspirationId: the inspiration document id.\n- variantId: the concept id to revise (from get_inspiration_document). Required — this targets an existing filled concept, unlike inspiration_add_variant which fills empty placeholders.\n- name / description: optional; updates the concept's label/direction.\n- html: the full, self-contained HTML document (non-empty).\n\nRESPONSE: { ok, variantId, url }."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_LIST_DESIGN_SYSTEMS",+ "name": "List design systems",+ "description": "Lists the design systems available to the authenticated user. Returns both built-in (reserved) design systems and any custom design systems the user has created or has access to.\n\nUse this when the user mentions a specific design system (e.g. \"use Shadcn\", \"with my company design system\") so you can resolve the correct ID to pass to create_design.\n\nEach result includes:\n- id: The unique design system ID to pass to create_design\n- name: The human-readable name\n- isReserved: Whether it is a built-in preset (e.g. Base, Shadcn, MUI)\n- isActive: Whether this is the user's currently active design system"+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_LIST_VERSION_HISTORY",+ "name": "List version history",+ "description": "Lists the artifact version history for a design. Returns the most recent 20 versions with their artifact IDs, version labels, and titles. Use the skip parameter to paginate backwards.\n\nBecause the editor is collaborative, new versions may have been created by the user or AI since you last checked. Use this alongside get_design_status to understand the full picture.\n\nEach version corresponds to a snapshot of the design's code at a point in time. Use the artifactId from a version entry to read_artifact_files for that version, or create_new_artifact to branch from it."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_PUBLISH_ARTIFACT",+ "name": "Publish artifact",+ "description": "Compiles an artifact's source files and sets it as the active artifact for the design. This is the final step in the code-first workflow (Workflow B).\n\nThis tool:\n1. Compiles all source files in an existing artifact version (bundling for preview).\n2. Sets that artifact as the design's active artifact (so it appears in the editor and preview).\n3. Does NOT create a version entry. Call create_new_artifact first and publish the artifactId it returns.\n4. Records your `description` on the version, above the file changes already logged from write_artifact_files.\n\nALWAYS pass a description. The people who open this design did not watch you work, and the version is otherwise an unexplained code change.\n\nNEXT STEPS: The design preview will update. Share the editor URL with the user."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_PUBLISH_DESIGN_SYSTEM",+ "name": "Publish design system",+ "description": "Publishes the design system's active artifact as a new immutable version. STRICT: refuses if the active artifact has validation errors — run write_design_system_files and clear all validationErrors first.\n\nReturns the new version (major.minor) and whether it is backwards-compatible with the previously published version (a breaking change — e.g. a removed component or prop — bumps the major version)."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_READ_ARTIFACT_FILES",+ "name": "Read artifact files",+ "description": "Reads the contents of one or more files from an artifact.\n\nIMPORTANT: Always read files BEFORE making changes with write_artifact_files so you understand the current state.\n\nThis code is meant as a starting point or inspiration. It is NOT production-ready.\nYou should adapt this code to match the user's project style, frameworks, libraries, and conventions."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_READ_DESIGN_SYSTEM_FILES",+ "name": "Read design system files",+ "description": "Reads the contents of one or more files from a design system's active artifact.\n\nDesign system file structure:\n- components/<Name>/index.tsx — component source (named exports only)\n- components/<Name>/<Name>.previews.tsx — preview definitions; default-export a ComponentPreviewModule with componentName, importPath, and previews\n- components/<Name>/Context.md — AI/usage documentation\n- index.css — design system styles / Tailwind imports\n- tailwind.config.js — Tailwind configuration\n- rules/<slug>.md — design rules\n\nCall get_design_system first to discover available file names. Always read before editing."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_READ_RECENT_MESSAGE_HISTORY",+ "name": "Read recent message history",+ "description": "Reads the recent chat item history for a design. Returns the last 10 chat items (user prompts, AI responses, artifact versions, edits). Use the skip parameter to paginate backwards through older items.\n\nBecause the editor is collaborative, the user may have sent prompts or made changes in the UI between your tool calls. Use this to catch up on what happened and understand the current context before acting.\n\nNote: Code contents are omitted from the response to keep it concise. Use read_artifact_files to read full file contents."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_SEND_PROMPT",+ "name": "Send prompt",+ "description": "Sends a natural language prompt to the Magic Patterns AI for an existing design. The AI will interpret the prompt and generate/update code. Returns immediately with a requestId.\n\nBEFORE CALLING: Call get_design_status(editorId) to make sure the design is not already generating (isGenerating=false) and to understand the current state. The user may have sent prompts or made changes in the UI.\n\nUse this for prompt-based updates to existing designs (Workflow A with existing design).\n\n⚠️ IMPORTANT: This kicks off a LONG-RUNNING generation that typically takes 2–10 minutes. Do NOT poll more often than every 60 seconds. Call get_design_status(editorId) once every 60 seconds until isGenerating=false. Do NOT treat slow generation as an error — it is expected."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_WRITE_ARTIFACT_FILES",+ "name": "Write artifact files",+ "description": "Creates or overwrites one or more files in an artifact. If a file exists, it will be replaced. If it doesn't exist, it will be created.\n\nIMPORTANT: This only saves source files — it does NOT compile or publish. Call publish_artifact after you have finished all file changes.\n\nEach file you write is logged onto the version in the design's chat, with a diff the user can open — so the design records what you changed, not just the end result.\n\nNEXT STEPS:\n- Call write_artifact_files again for additional files.\n- When done with all changes, call publish_artifact(artifactId, editorId) to compile and activate."+ },+ {+ "slug": "MAGIC_PATTERNS_MCP_WRITE_DESIGN_SYSTEM_FILES",+ "name": "Write design system files",+ "description": "Creates or overwrites files in a design system. Incoming files are validated, merged onto the existing artifact (existing files are preserved), compiled, and activated immediately.\n\nCOMPONENT FORMAT (required):\n- Use a PascalCase folder and write the complete trio for every code component:\n components/<Name>/index.tsx\n components/<Name>/<Name>.previews.tsx\n components/<Name>/Context.md\n- Export the component from index.tsx as a named export. Default exports reject the entire write; fix the file and retry.\n- Default-export the previews object from <Name>.previews.tsx. It must include componentName, importPath, and previews; every preview needs a render function returning JSX.\n- Do not write flat component files such as components/Button.tsx or components/Button/Button.tsx.\n\nIMPORTANT:\n- Call get_design_system first and pass its artifactId as baseArtifactId. A 409 means someone else changed the design system — re-read and retry.\n- Magic Patterns does not post-process MCP writes. Non-canonical paths, syntax errors, source-format violations, and shell/auto-generated files reject the entire write so you can fix them and retry.\n- validationErrors for incomplete component trios remain non-blocking — fix them before publish_design_system, which is strict.\n\nLoad the design_system_authoring_guide prompt for the full file contract."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "magic_patterns_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "email,offline_access,openid,profile"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "magicslides","name": "MagicSlides",@@ -237205,6 +245840,96 @@}]},+ {+ "slug": "marcopolo_mcp",+ "name": "MarcoPolo MCP",+ "logo": "https://logos.composio.dev/api/marcopolo_mcp",+ "description": "MarcoPolo MCP lets agents securely query, correlate, analyze, and act on authorized data across databases, warehouses, cloud storage, and SaaS applications.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 5,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "MARCOPOLO_MCP_CONNECTION_SETUP",+ "name": "Connection setup",+ "description": "Create a browser setup URL for a credentialed connection.\n\nUse a canonical `type` when known; otherwise pass `intent_text`.\nFor hosted demo data with no credentials, use `install_demo_connection`."+ },+ {+ "slug": "MARCOPOLO_MCP_CONNECTIONS_LIST",+ "name": "Connections list",+ "description": "List visible Marcopolo connections ready in the execution workspace.\n\nReturned names are valid `connection_name` values for `data_query`.\nCapabilities and workspace paths describe supported workspace commands."+ },+ {+ "slug": "MARCOPOLO_MCP_DATA_QUERY",+ "name": "Data query",+ "description": "Run a bounded governed query against a visible connection.\n\nUse this tool in generated code that re-queries live data at view or\nload time: Remote Artifacts, external web apps, scheduled scripts, and\nany other programmatic interface that fetches fresh data on each run.\nDo NOT use it for agent-side analytics or one-off snapshot\nvisualizations — use the `workspace_shell` tool with the connection\nquery CLI instead.\n\nPass the full workspace-relative `query_file` path including the\nconnection prefix, e.g. `connections/<name>/queries/<file>`. Paths\nresolve from `/workspace`, not from any current directory. Author new\nquery files through `workspace_shell` before calling this tool so query\ntext is durable and reusable.\n\nReturns `rows` as a parsed list of record dicts and `row_count` as the\ntotal — no JSON parsing needed. Results are capped by `max_rows`\n(1–5000)."+ },+ {+ "slug": "MARCOPOLO_MCP_INSTALL_DEMO_CONNECTION",+ "name": "Install demo connection",+ "description": "Install hosted demo data with no user credentials.\n\nPass a demo id or natural-language request. Use `connection_setup` for\nreal user-owned connections."+ },+ {+ "slug": "MARCOPOLO_MCP_WORKSPACE_SHELL",+ "name": "Workspace shell",+ "description": "Run a shell command in the persistent /workspace runtime.\n\nUse for all agent-side work: query authoring, analytics, DuckDB joins,\nworkspace files, scripts, git, diagnostics, and cron. The `connection`\nand `cron` CLIs exist only inside this runtime and must be invoked\nthrough this tool."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "marcopolo_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "email,offline_access,openid,profile"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "marketstack","name": "Marketstack",@@ -239235,12 +247960,12 @@],"toolCount": 1,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{"slug": "MERMAID_CHART_MCP_VALIDATE_AND_RENDER_MERMAID_DIAGRAM","name": "Validate and render mermaid diagram",- "description": "\nUse this tool to output a Mermaid diagram:\n- The tool will validate the diagram syntax and render it to a UI widget.\n- The widget will contain the diagram code, a \"Copy Code\" button, and a rendered diagram.\n- If the diagram is invalid, the widget will give user a link to repair the diagram in Mermaid Live.\n"+ "description": "\nUse this tool to output a Mermaid diagram:\n- The tool will validate the diagram syntax and render it to a UI widget.\n- The widget will contain the diagram code, a \"Copy Code\" button, and a rendered diagram.\n- If the diagram is invalid, the widget will give user a link to repair the diagram in Mermaid.\n"}],"triggers": [],@@ -241867,6 +250592,106 @@}]},+ {+ "slug": "midpage_mcp",+ "name": "Midpage MCP",+ "logo": "https://logos.composio.dev/api/midpage_mcp",+ "description": "Midpage MCP gives agents authorized legal-research tools for searching, retrieving, analyzing, and citing cases, statutes, regulations, and related legal materials.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 7,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "MIDPAGE_MCP_ANALYZE_DOCKET_FILING",+ "name": "Analyzedocketfiling",+ "description": "Analyze one docket filing selected from analyzeDocketReport and answer a focused question using passages from that filing.\n\nUse this when the user needs to understand what a specific filing says. This tool answers from the filing text, not from the docket entry description.\n\nINPUT:\n- caseId: The caseId returned by analyzeDocketReport case.caseId.\n- entryNumber: The docket entry number returned by analyzeDocketReport relevantEntries[].entryNumber.\n- attachmentNumber: Optional attachment number returned by analyzeDocketReport relevantEntries[].attachmentNumber. Omit for the main filing on the docket entry.\n- question: The question to answer about this specific filing.\n\nRETURNS:\n- status: \"ok\" or a specific resolution/analysis error.\n- filing: Resolved filing metadata, including entryNumber, optional attachmentNumber, dateFiled, suggestedFileName, and a downloadable Midpage file URL for the filing.\n- answer: Direct answer based only on the filing text.\n- supportingPassages: Passages from the filing that support the answer, with passage and relevance.\n- doesNotAddress: Specific parts of the question that the filing text does not answer. Check this before relying on the answer.\n\nCITATION RULES:\n- When using filing content in an answer, cite the filing with the format below.\n- Every citation must be a markdown hyperlink to filing.url.\n- The ECF No. suffix is important and should be included in filing citations.\n- Use a descriptive filing name, then any real page/pin/paragraph if available, followed by this suffix: ECF No. {filing.entryNumber} ({filing.dateFiled formatted as \"Mar. 3, 2020\"}).\n- Example: [Pl.'s Mot. for Summ. J. 5, ECF No. 30 (Mar. 3, 2020)]({filing.url})\n- If filing.dateFiled is unavailable, omit the parenthetical date rather than inventing one.\n- Never use short cites such as \"id.\" or \"supra\"; repeat the full linked filing citation.\n\nDOWNLOAD GUIDELINES:\n- If the user asks to download or save the filing, use filing.suggestedFileName as the filename."+ },+ {+ "slug": "MIDPAGE_MCP_ANALYZE_DOCKET_REPORT",+ "name": "Analyzedocketreport",+ "description": "Analyze a federal docket report and answer a docket-level question.\n\nUse this for case snapshots, recent activity, procedural posture, service, complaint history, motion history, deadlines, and identifying relevant filings. This tool answers from the docket sheet only; use analyzeDocketFiling when the text of a specific filing is needed.\n\nINPUT:\n- court: Federal court. Prefer Bluebook-style abbreviations such as \"N.D. Cal.\", \"S.D.N.Y.\", \"D. Del.\", \"Bankr. D. Del.\", \"9th Cir.\", or \"Fed. Cir.\"; full federal court names are also accepted.\n- docketNumber: Federal case docket number. Prefer full district/bankruptcy numbers with office or division prefix when known, such as \"4:24-cv-04722\"; appellate numbers look like \"24-1234\".\n- caseName: Optional case caption/name, such as \"Musk v. Altman\". Include it when available, especially if the docket number is incomplete.\n- forceFetch: Optional. Set true only when the user explicitly needs the latest official PACER docket instead of available cached or RECAP data.\n- question: The docket-level question to answer.\n\nRETURNS:\n- status: \"ok\" or a specific resolution/analysis error.\n- case: Resolved case metadata, including caseId for analyzeDocketFiling.\n- docketReport: Docket report metadata, including suggested filename and a downloadable Midpage file URL when one is available.\n- answer: Direct answer based only on the docket sheet.\n- relevantEntries: Docket entries or attachments supporting or relevant to the answer. Use case.caseId plus relevantEntries[].entryNumber and optional relevantEntries[].attachmentNumber with analyzeDocketFiling when the filing text is needed.\n- doesNotAddress: Specific parts of the question that the docket entries do not answer. Check this before relying on the answer.\n- warnings: Important source or parsing limitations, when present.\n\nDOWNLOAD GUIDELINES:\n- If the user asks to download or save the docket report, use docketReport.suggestedFileName as the filename."+ },+ {+ "slug": "MIDPAGE_MCP_ANALYZE_LAW",+ "name": "Analyzelaw",+ "description": "Analyzes a statute, regulation, constitutional provision, or agency guidance document against a specific legal question and returns verified passages. REQUIRED before citing or quoting any statute or regulation.\n\nAUTO-USE: Call this whenever an answer depends on the wording, requirements, exceptions, scope, procedures, or current status of a primary-law provision. Do not wait for the user to say \"research\", \"case\", or \"Midpage\", and do not answer from memory or web snippets when this tool can retrieve the provision.\n\nFINAL-ANSWER LINK RULE: Every statute/regulation citation or specific subsection relied on must be a Markdown link. Link a passage-specific proposition or quote to its deeplinkUrl; use url only for a general reference. If the answer discusses several subsections, link each cited subsection. Never invent subsection path segments.\n\nLOOKUP (provide exactly ONE of these):\n- citation: canonical citation, e.g. \"42 U.S.C. § 1983\", \"Cal. Code Regs. tit. 22, § 51451\"\n- path: full ltree path from a previous result, e.g. \"cfr.t21.cI.scH.p820\"\n- registerCitation: Federal Register or state register citation, e.g. \"89 FR 12345\"\n- id: document UUID from a previous search/lookup\n\nLOOKUP ROUTING:\n- citation identifies a corpus document, not an arbitrary pinpoint within it. If the user's reference appends a subsection to a section-level citation (for example, \"18 U.S.C. § 924(c)(1)(C)\"), call searchLaws with the user's full reference, select the containing provision, then call analyzeLaw with its id. Keep the pinpoint in question so the analysis focuses on it. Do not silently truncate the citation.\n- Popular names and source-law aliases (for example, \"First Step Act of 2018\" or \"ERISA § 514\") are search terms, not citation lookup keys. Call searchLaws with the user's wording, select the intended provision, then call analyzeLaw with its id. Never guess the codified citation from memory.\n\nRequired:\n- question: the legal question to answer. The document text (up to 400k characters) is analyzed internally; raw text is never returned to the calling model\n\nOptional:\n- collection: disambiguates path/citation/registerCitation lookups — a collection id (e.g. \"cfr\", \"uscode\") or human-readable name (e.g. \"Code of Federal Regulations\"); unresolvable values error with did-you-mean suggestions\n- includeHistorical: true to allow superseded or not-yet-effective versions in citation/path/registerCitation lookups (default: current law only); id always returns that exact version\n\nRETURNS:\n- citation, title, number: identification of the provision\n- analysis: summary, passages [{point, quote, deeplinkUrl}] with verified verbatim quotes, and doesNotAddress — aspects of the question the document does not cover. CHECK doesNotAddress BEFORE CITING. deeplinkUrl opens the provision at the quoted passage (and falls back to the bare page URL only when no highlightable span matched)\n- children: for container nodes (title/chapter/part), up to 250 child provisions with id, number, citation, title, sortOrder; childrenTotal is the true count. Children carry no text — fetch a child by its id. For containers with many children, prefer searching directly for the target section\n- parentId: id of the parent node — look it up to zoom out to surrounding context\n- versions: when the provision has version history, every version with effectiveDate, publicationDate, sourceAsOf, isHistorical/isCurrent flags, and isRequested marking the returned one — look up another version by its id (with includeHistorical: true) to compare text over time\n- isCurrent: whether this text is the law in force today; isHistorical: true = superseded (isCurrent false with isHistorical false = not yet effective); effectiveDate/publicationDate when stated by the source; sourceAsOf is the date of the source edition or snapshot and is not necessarily the provision's effective date\n- state (\"Federal\" or a state name), collectionType (statute/regulation/constitution/guidance/executive_order/notice)\n- url: Midpage link for this exact version; sourceUrl: the official source\n- ambiguousMatches: when the reference matched multiple documents, the candidates with id, title, citation, path, collection and state — pick one and retry by id\n- error: the provision could not be safely analyzed (including source-file-only text) or the reference could not be resolved. A source-file-only leaf returns metadata, url, and an explicit error; open the page to review it, but do not quote or characterize it from this tool result\n\nHOW TO USE:\n1. Analyze the provision before citing it; quote only from returned analysis passages.\n2. If you get a container (nodeType PARENT), navigate: children lists the subdivisions; drill into the relevant child by id.\n3. Check isCurrent before asserting something is the law today. Historical text has isCurrent: false.\n4. Cite with the exact citation string returned. Use a passage's deeplinkUrl for every passage-specific proposition or quote; use the bare url only for a general reference.\n5. For side-by-side state comparisons (\"50-state survey\" questions), analyze each jurisdiction's governing provision with the same comparison question, then compare the verified propositions, qualifiers, and doesNotAddress fields."+ },+ {+ "slug": "MIDPAGE_MCP_ANALYZE_OPINION",+ "name": "Analyzeopinion",+ "description": "Reviews and annotates a legal opinion, returns key takeaways, holdings, details, excerpts, and tells you how you can use this case in your response. REQUIRED before citing a case.\n\nThis tool returns what the case ACTUALLY supports (not necessarily what you asked about). Use this to:\n1. Find out what propositions this case actually supports\n2. Extract verified quotes\n3. Understand the scope/limitations of each proposition\n4. Know what the case does NOT address (to avoid misattribution)\n\n\nDOCUMENT IDENTIFICATION (provide exactly ONE — omit the others):\n- opinionId: Midpage document ID from search results (e.g., \"7228818\", \"c4efd75e-22e7-471f-8bda-95e10a13e588\"). OMIT this field if you don't have a Midpage ID.\n- reporterCitation: Bluebook citation (e.g., \"556 U.S. 662\", \"123 F.3d 456\") — NOT WL/LEXIS\n- docket: For cases without reporter citations:\n - courtAbbreviation: e.g., \"S.D.N.Y.\", \"9th Cir.\"\n - docketNumber: e.g., \"12-cv-20100\" (omit \"No.\" prefix)\n\nHOW TO CHOOSE:\n1. If you have an opinionId from search results, use ONLY opinionId (fastest)\n2. If you have a reporter citation like \"556 U.S. 662\", use ONLY reporterCitation (omit opinionId)\n3. If you only have a docket number (e.g., \"No. 20-16900 (9th Cir.)\"), use ONLY docket tuple\n4. NEVER use WL or LEXIS citations — use docket tuple instead\n5. NEVER pass \"0\" or placeholder values — omit fields you don't have\n\nINPUT:\n- question: The legal question you want answered. Be specific about the legal element.\n\nRETURNS:\n- citation: Exact bluebook citation string for the case\n- url: General Midpage link for the case as a whole\n- supportedPropositions: Array of propositions this case supports, each with:\n - proposition: Cite-ready statement of what the case holds (USE THIS TEXT when citing)\n - quote: Verbatim quote supporting the proposition\n - scope: Limitations, conditions, what it does NOT apply to\n - centrality: \"core_holding\" (strongest), \"supporting_analysis\" (strong), \"secondary_matter\" (medium), or \"background\" (weakest)\n - opinionSection (optional): the non-majority opinion that this proposition comes from (e.g., \"Jackson, Concurring\", \"Smith, Dissenting\").\n - deeplinkURL: Shareable Midpage deep link that auto-scrolls to that sentence range\n- doesNotAddress: Topics from your question the case does NOT address. CHECK THIS BEFORE CITING.\n- summary: Brief summary of what the case is actually about\n- disposition: Short procedural outcome phrase describing what this court did in this opinion, when available\n- jurisdiction: Court and jurisdiction\n- treatment: Citator status and citation count\n\nHOW TO USE THE OUTPUT:\n1. Check doesNotAddress first - if your intended use is listed, DO NOT cite this case for that purpose\n2. Find a supported proposition that matches your intended use\n3. Use the proposition text (or close paraphrase) when citing - it's verified to match the quote\n4. Include scope limitations when relevant (especially qualifiers)\n5. Prefer \"core_holding\" and \"supporting_analysis\" over \"secondary_matter\" or \"background\" for stronger authority\n6. Never characterize non-majority propositions as the court's controlling holding; clearly signal when they come from concurrence/dissent text\n7. If a proposition is from any non-majority opinion, it must include opinionSection (e.g., \"Jackson, Concurring\")\n8. When citing a specific supported proposition or quote, prefer that proposition's deeplinkURL over the top-level url\n9. Use the top-level url only when referring to the case generally rather than a specific proposition or quote\n\nEXAMPLE:\nIf you ask \"Is expert testimony required to prove truth as a defense to a defamation claim?\" and the case mentions that an expert testified in such a case in passing:\n- supportedPropositions will contain \"An expert testified in order to prove truth of the matter asserted\" as background\n- doesNotAddress will contain \"Whether expert testimony is REQUIRED\" (what you asked about)\n- You should NOT cite this case to say that such testimony is REQUIRED just because the testimony was provided in this one case.\n\nWRITING RULES:\n1. FAVOR paragraph-driven writing: Write like an attorney with clear topic sentences, crisp rule statements with hyperlinked citations, and thoughtful analysis.\n2. FAVOR direct, concise answers: Keep answers short. Answer the question asked, not an expanded version.\n3. FAVOR embedded-quotes in prose: Weave quotes into paragraphs (modify with brackets [] or ellipsis ... while keeping verbatim).\n4. LIMIT lists and bullet points: Use sparingly or unless asked.\n5. AVOID block quotes: Don't dump quotes in block format.\n6. AVOID repetition/summaries.\n7. AVOID emojis.\n\nCITATION RULES:\n- ALWAYS include a citation after each quoted passage\n- ALWAYS mention relevant scope limitations when citing if relevant\n- OFTEN add parentheticals after citations beginning with \"ing\" words or quotes.\n\nCITATION FORMAT:\nEvery citation must be a markdown hyperlink using the returned fields.\nWhen citing a specific supported proposition or quote, use:\n[{citation}]({deeplinkURL})\n\nWhen referring to the case generally, use:\n[{citation}]({url})\n\nExample proposition citation: [International Shoe Co. v. Washington, 326 U.S. 310 (1945)](https://app.midpage.ai/document/1234567?lines=10-12)\n\nExample general case citation: [International Shoe Co. v. Washington, 326 U.S. 310 (1945)](https://app.midpage.ai/document/1234567)\n\n- Use the exact citation string returned by the tool—never abbreviate or modify\n- NEVER use short cites (id., supra)—always full citation with link\n- Prefer deeplinkURL whenever the citation is tied to a specific supported proposition or quote\n- NEVER invent reporter pin cites. If you want a Midpage line-specific link, use the returned deeplinkURL\n- NEVER cite to LEXIS or WL citations; always cite to the exact bluebook citation provided (which may be a docket-number citation in lieu of a reporter for unpublished cases)\n- Include a citation after every legal proposition or quote"+ },+ {+ "slug": "MIDPAGE_MCP_FIND_IN_OPINION",+ "name": "Findinopinion",+ "description": "Find quotable passages within a single opinion using keyword search. Fast, free, no AI.\n\nWHEN AND HOW TO USE THIS TOOL: \n- This tool is optional but recommended.\n- Use this tool after a search, or directly if the user gives you a citation.\n- Check if a search result is actually relevant (sort of like double clicking into a result)\n- To decide which cases are worth the AI cost of analyzeOpinion (only the most relevant!)\n\nHOW NOT TO USE THIS TOOL: \n- Do not use this tool alone. If you intend to cite a case, you must use analyzeOpinion.\n- Do not use this tool unless the user has specifically provided a citation to a case. Default to the search tool. \n\n\nDOCUMENT IDENTIFICATION (provide exactly ONE — omit the others):\n- opinionId: Midpage document ID from search results (e.g., \"7228818\", \"c4efd75e-22e7-471f-8bda-95e10a13e588\"). OMIT this field if you don't have a Midpage ID.\n- reporterCitation: Bluebook citation (e.g., \"556 U.S. 662\", \"123 F.3d 456\") — NOT WL/LEXIS\n- docket: For cases without reporter citations:\n - courtAbbreviation: e.g., \"S.D.N.Y.\", \"9th Cir.\"\n - docketNumber: e.g., \"12-cv-20100\" (omit \"No.\" prefix)\n\nHOW TO CHOOSE:\n1. If you have an opinionId from search results, use ONLY opinionId (fastest)\n2. If you have a reporter citation like \"556 U.S. 662\", use ONLY reporterCitation (omit opinionId)\n3. If you only have a docket number (e.g., \"No. 20-16900 (9th Cir.)\"), use ONLY docket tuple\n4. NEVER use WL or LEXIS citations — use docket tuple instead\n5. NEVER pass \"0\" or placeholder values — omit fields you don't have\n\nQUERY INPUT:\n- query: Key terms to match, NOT a full question\n - GOOD: \"personal jurisdiction minimum contacts purposeful availment\"\n - BAD: \"Does this case establish personal jurisdiction?\" (questions don't work well)\n\nRETURNS:\n- snippets: Verbatim passages from the opinion (can be quoted directly)\n\nLIMITATIONS:\n- Keyword-based only—may miss relevant passages with different wording\n- Easy to take things out of context because you only see a snippet\n- Does NOT tell you if the case supports or contradicts your proposition\n- Does NOT identify qualifiers/exceptions\n\nNEXT STEP: Use analyzeOpinion() on promising cases to get analysis, qualifiers, and verified quotes before citing."+ },+ {+ "slug": "MIDPAGE_MCP_SEARCH",+ "name": "Search",+ "description": "Search US case law across federal and state courts. Returns metadata, highlights, and citator treatment data.\n\nWHEN AND HOW TO USE THIS TOOL: \n- Use this tool to identify US legal opinions that are potentially relevant to the user's question. This is your default legal research tool.\n- Use this tool if your response requires or is likely to require any legal analysis. Alternatively, if the user references a specific citation, you can analyze it directly using analyzeOpinion. \n- Do not presume to know the answer to any legal question - do your research using the tools provided to you. \n- Always use this tool in conjunction with the findInOpinion and/or analyzeOpinion tools. \n\nHOW NOT TO USE THIS TOOL:\n- Do not use this tool alone. This tool is a first step. Follow up with findInOpinion and analyzeOpinion tools to review cases more granularly. \n- You can NEVER cite a case in your response until you have used the analyzeOpinion tool, at minimum, on that case.\n\nWHAT YOU GET:\n- documentId: Use this ID with findInOpinion() and analyzeOpinion()\n- metadata: Bluebook citation (which contains party names, court, date, docket and/or reporter citation)\n- highlights: Brief snippets showing why this case matched (NOT for quoting—use findInOpinion for quotes)\n- treatment: Citator status (positive/negative/caution/neutral), citation counts\n\nQUERY TIPS:\n- This tool combines meaning-based and keyword matching. It works for legal concepts, natural-language issues, exact terms, citations, docket numbers, patent numbers, and other identifiers.\n- Use key terms and concepts, e.g.:\n - personal jurisdiction minimum contacts purposeful availment\n - noncompete duration length duration unconscionable\n- Questions and statements also work well, e.g.:\n - Irreparable harm is the most important factor when analyzing a request for a preliminary injunction.\n - Do Nevada courts consider Delaware law to be persuasive authority on issues of corporate governance?\n- For a known identifier, include it exactly as written, e.g.:\n - patent no 7,479,949\n - 556 U.S. 662\n- If you need exact wording or quotable passages, use findInOpinion on promising results.\n- Run multiple queries in parallel for different legal issues\n- Use filters to narrow by jurisdiction and date\n- Do NOT use the publishStatus filter unless the user explicitly asks to restrict results by publication status, and never when searching for a specific case. Every value excludes all cases that don't match it exactly — \"unknown\" is not a safe default for cases whose status you haven't verified.\n - Each query may return up to 10 results\n - You can run up to 4 queries per call\n\nFILTERS (all optional):\n- jurisdictionType: \"federal\" | \"state\" | \"state_and_federal\"\n- circuits: [\"9\", \"2\", \"supreme_court\", \"dc\"] for federal courts\n- courts: [\"S.D.N.Y.\", \"9th Cir.\"] using Bluebook-style court abbreviations\n- states: [\"California\", \"New York\"] for state courts\n- publishStatus: \"published\" | \"unpublished\" | \"unknown\" | \"in_chambers\" | \"separate\" | \"errata\" | \"relating_to\". Omit unless the user explicitly asks to restrict by publication status. \"unknown\" matches only opinions whose recorded status is missing or uncertain — it does not mean \"status not verified by you\". When filtering (e.g., published-only California research), run a parallel query with \"unknown\", since some jurisdictions leave this field missing.\n- startDate/endDate: \"YYYY-MM-DD\" format\n\nPOSSIBLE NEXT STEPS:\n1. Review highlights and treatment to identify promising cases\n2. Use findInOpinion() on 3-5 candidates to extract quotable passages (optional)\n3. Use analyzeOpinion() on cases you intend to rely on in your final response (REQUIRED before citing)"+ },+ {+ "slug": "MIDPAGE_MCP_SEARCH_LAWS",+ "name": "Searchlaws",+ "description": "Searches Midpage's US primary-law corpus: statutes, regulations, constitutions, and agency guidance — federal plus all 50 states and DC.\n\nAUTO-USE: Call this whenever a user asks what a statute, code section, regulation, administrative rule, or constitutional provision says, requires, permits, prohibits, or whether it applies. Do not wait for the user to say \"research\", \"case\", or \"Midpage\", and do not default to web search for primary-law text available here.\n\nUse this to FIND the governing provision; then call analyzeLaw with the result's id to get its verbatim text before citing.\n\nRESOLUTION: Use searchLaws before analyzeLaw when the user gives (a) a subsection pinpoint that may not be a standalone corpus document, such as \"18 U.S.C. § 924(c)(1)(C)\", or (b) a popular name/source-law alias, such as \"First Step Act of 2018\" or \"ERISA § 514\". Search the user's full wording, choose the intended provision, and pass its id to analyzeLaw. Do not guess a codified citation from memory or silently truncate a pinpoint.\n\nResults are the law in force TODAY by default (currentOnly). Currency is derived: not superseded, not future-effective, no in-force successor.\n\nINPUT:\n- query: legal concepts / key terms (BM25 keyword search — not semantic)\n- states: state names or USPS abbreviations (\"California\", \"TX\"); \"Federal\" for federal law. Validated server-side — unrecognized values error with did-you-mean suggestions instead of silently matching nothing\n- collectionTypes: statute | regulation | constitution | guidance | executive_order | notice\n- collections: specific codes, by id (e.g. \"cfr\", \"wa-rcw\") or human-readable name (e.g. \"Code of Federal Regulations\", \"Texas Administrative Code\") — resolved server-side; unresolvable values error with did-you-mean suggestions\n- pathPrefix: subtree filter within one code — a dot-separated ltree path from a previous result (e.g. \"cfr.t21\" for all of 21 CFR, including descendants), pair with collections. Malformed prefixes error rather than matching nothing.\n- currentOnly: false to include historical versions\n- page / pageSize: pagination over stable search-rank windows (max 50 per page). A page can contain fewer than pageSize results when PostgreSQL rejects index-stale rows; continue to the next page normally.\n\nRETURNS:\n- results: matching provisions with id, citation, title, number, state, collectionId/collectionType, path, nodeType, effectiveDate, snippets (matched fragments; <em> marks the matched terms), isCurrent + isHistorical (isCurrent false with isHistorical false = not yet effective), and url (the Midpage page for that exact version) — pass a result's id to analyzeLaw before citing\n- total: Elasticsearch estimate for the whole query; it can include index-stale rows removed from results by the authoritative PostgreSQL currency check\n- stateCounts: estimated per-state hit counts for the WHOLE query, not just this page. Use them to scope state-survey work, then verify each relevant state with a filtered search; do not treat a zero/nonzero estimate as proof of exhaustive legal coverage.\n- error: set instead of results when a filter could not be resolved or the window was exceeded — the message says how to fix the call\n\nHOW TO USE:\n1. Search broad, then narrow with states/collectionTypes/collections filters.\n2. NEVER cite from snippets — they are relevance context. Call analyzeLaw with the result id and quote from its verbatim text.\n3. For 50-state or N-state surveys: one query without states filter → stateCounts estimates likely coverage → per-state filtered queries → analyzeLaw the top provisions."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "midpage_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,public_metadata,private_metadata,offline_access,user:org:read"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "mighty_networks","name": "Mighty Networks",@@ -245483,7 +254308,7 @@],"toolCount": 21,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260903_00","tools": [{"slug": "MONEYBIRD_ADD_NOTE_TO_CONTACT",@@ -245947,7 +254772,7 @@],"toolCount": 4,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{"slug": "MOSPI_MCP_GET_DATA",@@ -251389,6 +260214,9 @@"authSchemes": ["OAUTH2"],+ "composioManagedAuthSchemes": [+ "OAUTH2"+ ],"toolCount": 11,"triggerCount": 0,"version": "20260807_00",@@ -253378,6 +262206,91 @@}]},+ {+ "slug": "octagon_mcp",+ "name": "Octagon MCP",+ "logo": "https://logos.composio.dev/api/octagon_mcp",+ "description": "Octagon MCP lets agents access authorized public- and private-market intelligence, SEC filings, earnings transcripts, financial metrics, stock data, deep research, and prediction-market analysis.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 4,+ "triggerCount": 0,+ "version": "20260904_00",+ "tools": [+ {+ "slug": "OCTAGON_MCP_OCTAGON_AGENT",+ "name": "Octagon-agent",+ "description": "Orchestrates all agents for comprehensive market intelligence analysis. Capabilities: Combines insights from SEC filings, earnings calls, financial metrics, stock data, institutional holdings, private company research, funding analysis, M&A transactions, investor intelligence, debt analysis, and news and press releases to provide holistic market intelligence. Best for: Complex research requiring multiple data sources and comprehensive analysis across public and private markets. Example queries: 'Retrieve year-over-year growth in key income-statement items for AAPL, limited to 5 records and filtered by period FY', 'Analyze the latest 10-K filing for AAPL and extract key financial metrics and risk factors', 'Retrieve the daily closing prices for AAPL over the last 30 days', 'Analyze AAPL's latest earnings call transcript and extract key insights about future guidance', 'Provide a comprehensive overview of Stripe, including its business model and key metrics', 'Retrieve the funding history for Stripe, including all rounds and investors'"+ },+ {+ "slug": "OCTAGON_MCP_OCTAGON_DEEP_RESEARCH_AGENT",+ "name": "Octagon-deep-research-agent",+ "description": "A comprehensive agent that can utilize multiple sources for deep research analysis. Capabilities: Aggregate research across multiple data sources, synthesize information, and provide comprehensive investment research. Best for: Investment research questions requiring up-to-date aggregated information from the web. Example queries: 'Research the financial impact of Apple's privacy changes on digital advertising companies' revenue and margins', 'Analyze the competitive landscape in the cloud computing sector, focusing on AWS, Azure, and Google Cloud margin and growth trends', 'Investigate the factors driving electric vehicle adoption and their impact on battery supplier financials'"+ },+ {+ "slug": "OCTAGON_MCP_OCTAGON_PREDICTION_MARKETS_AGENT",+ "name": "Octagon-prediction-markets-agent",+ "description": "A specialized agent for creating research reports on Kalshi events (Polymarket coming soon). See what's driving prices, compare market vs model probabilities, and find potential mispricings.\n\n Note: It's recommended to attempt to retrieve a cached report first as new reports may take several minutes to generate.\n Example queries: 'https://kalshi.com/markets/kxbtcy/btc-price-range-eoy/kxbtcy-27jan0100', 'https://kalshi.com/markets/kxnbawest/nba-western-conference-championship/kxnbawest-26', 'https://kalshi.com/markets/kxtrdban/congress-banned-from-trading-stocks/kxtrdban-25dec31'"+ },+ {+ "slug": "OCTAGON_MCP_PREDICTION_MARKETS_HISTORY",+ "name": "Prediction markets history",+ "description": "Fetch historical data for a prediction market event by ticker.\nSupports pagination (limit, cursor) and time window (captured_from, captured_to) and optionally include analysis columns.\n\nNote: For a typical Kalshi Market URL, the event ticker is the final segment in the URL.\nFor example, for the URL https://kalshi.com/markets/kxbtcy/btc-price-range-eoy/kxbtcy-27jan0100, the event ticker is kxbtcy-27jan0100."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "octagon_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "email,offline_access,openid,profile"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "odoo","name": "Odoo",@@ -253813,7 +262726,7 @@],"toolCount": 43,"triggerCount": 0,- "version": "20260731_00",+ "version": "20260903_00","tools": [{"slug": "OMNISEND_ADD_CART_PRODUCT",@@ -255977,6 +264890,97 @@}]},+ {+ "slug": "openfunnel_agent_primitives",+ "name": "OpenFunnel Agent Primitives",+ "logo": "https://logos.composio.dev/api/openfunnel_agent_primitives",+ "description": "OpenFunnel Agent Primitives provides composable company search, research, lookup, and enrichment APIs for AI sales agents.",+ "category": "ai sales tools",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_CANCEL_BULK_LOOKALIKE_SEARCH",+ "name": "Cancel Bulk Lookalike Search",+ "description": "Irreversibly request cancellation of a pending or running bulk lookalike job. The response only acknowledges the asynchronous request; use GET_BULK_LOOKALIKE_RESULTS afterward to observe terminal cancelled status and retrieve partial results. Companies delivered before cancellation remain available and billable."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_GET_BULK_LOOKALIKE_RESULTS",+ "name": "Get Bulk Lookalike Results",+ "description": "Check an asynchronous bulk lookalike job and return one result page. Use status to determine completion: pending, running, and cancelling jobs remain pollable even when next_cursor is null."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_GET_CREDIT_BALANCE",+ "name": "Get Credit Balance",+ "description": "Return total, used, and remaining credits for the connected OpenFunnel account before or after paid searches."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_LIST_COUNTRY_CODES",+ "name": "List Country Codes",+ "description": "List all ISO 3166-1 alpha-3 country codes accepted by tech-search country filters, ordered by company volume."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_LIST_FIRMOGRAPHIC_OPTIONS",+ "name": "List Firmographic Options",+ "description": "List the live funding stages, location codes, and employee bounds accepted by lookalike search filters."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_LOOKUP_COMPANIES",+ "name": "Lookup Companies",+ "description": "Resolve a batch of 1-100 company names, domains, or LinkedIn URLs to ordered candidate records. Exact identifiers can still return multiple matches, so every candidate is preserved."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_RESEARCH_COMPANY",+ "name": "Research Company",+ "description": "Qualify one known company from recent hiring activity, current team composition, or both, with cited evidence. Each successful call is charged at the workspace-configured per-call credit price; an unresolved-domain 404 is free."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_SEARCH_COMPANIES_BY_TECH_STACK",+ "name": "Search Companies by Tech Stack",+ "description": "Return one fixed page of 50 companies whose recent job postings mention a technology. A live non-enriched full page consumed 25 credits; enrichment or firmographic filters may cost more. Follow next_cursor only when needed."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_SEARCH_LOOKALIKE_COMPANIES",+ "name": "Search Lookalike Companies",+ "description": "Find up to 100 companies similar to a natural-language trait or seed domains. Each returned company consumes 1 credit, and even an unexpected semantic match is billable, so choose limit deliberately."+ },+ {+ "slug": "OPENFUNNEL_AGENT_PRIMITIVES_START_BULK_LOOKALIKE_SEARCH",+ "name": "Start Bulk Lookalike Search",+ "description": "Start an asynchronous lookalike job for up to 10,000 companies. Delivered results are billed when the job completes, so choose limit deliberately and use GET_BULK_LOOKALIKE_RESULTS to monitor the returned job_id."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "openfunnel_agent_primitives_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Your OpenFunnel Agent Primitives API key beginning with \"of_\". To obtain or recover it, follow the email verification flow at https://docs.openfunnel.dev/agent-primitives/authentication: request a six-digit code with your email, then verify the code to receive the key. Keep it secret.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "opengraph_io","name": "OpenGraph.io",@@ -257192,6 +266196,86 @@}]},+ {+ "slug": "otter_ai_mcp",+ "name": "Otter.ai MCP",+ "logo": "https://logos.composio.dev/api/otter_ai_mcp",+ "description": "Otter.ai MCP lets agents retrieve the authenticated user's profile, search authorized meetings and conversations, and fetch complete transcripts for analysis and summarization.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 3,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "OTTER_AI_MCP_OTTER_FETCH",+ "name": "Otter fetch",+ "description": "Fetch one meeting's complete verbatim transcript by ID - full speaker-attributed, timestamped content, plus its AI summary, action items, outline, and attendees. READ-ONLY.\n\n Returns the speaker-turn structure, not just a summary. Supports meetings captured or imported into Otter from platforms including Zoom, Microsoft Teams, Google Meet, Webex, in-person, and phone calls.\n\n When to use:\n - User wants to read, get, quote, or analyze what was said in a specific meeting\n - User asks \"what did [person] say about [topic]?\" and you have a meeting ID\n - User wants the full transcript, not just a summary\n - User wants to cite specific moments with speaker attribution\n - Follow-up after `otter_search` when the user wants deeper content than the summary\n\n When NOT to use:\n - User has not yet identified the meeting - use `otter_search` first\n - User only needs the summary or action items - those are in `otter_search` results\n\n Tool selection: once you have an Otter meeting ID, use this tool for verbatim\n quotes and speaker-attributed transcript analysis rather than a platform-native\n recording tool.\n\n Input: accepts ONLY a meeting ID, not a URL. If the user provides an Otter URL of\n the form https://otter.ai/u/{ID}, extract the ID before calling.\n "+ },+ {+ "slug": "OTTER_AI_MCP_OTTER_GET_USER_INFO",+ "name": "Otter get user info",+ "description": "Get current Otter.ai user's name, email, and current date/time (PST) - READ-ONLY.\n\n Call before `otter_search` to anchor temporal expressions (\"this week\", \"yesterday\")\n to the user's actual date, and to pass the username for participation-status filtering.\n\n When to use:\n - Before any `otter_search` involving temporal expressions\n - When a query depends on who the user is (e.g. meetings they attended vs. shared with them)\n - Once per session is enough; cache the result\n\n "+ },+ {+ "slug": "OTTER_AI_MCP_OTTER_SEARCH",+ "name": "Otter search",+ "description": "Search meetings across platforms by date, attendee, topic, keyword, or title. READ-ONLY.\n\n Primary tool for finding meetings captured or imported into Otter from Zoom, Microsoft Teams, Google Meet, Webex, in-person meetings, and phone calls. Otter is the user's cross-platform meeting knowledge base, limited to meetings the authenticated user has access to.\n\n Returns meeting metadata, AI summaries, outlines, and action items ranked by relevance. Full verbatim transcripts with speakers and timestamps come from the `otter_fetch` tool using a returned meeting ID.\n\n When to use:\n - User asks about meetings, calls, recordings, or conversations without an ID\n - User wants to find, summarize, get, pull, or recall a past meeting by topic,\n attendee, date, or content (\"What did [person] say about X?\", \"summarize\n yesterday's standup\", \"find the meeting where we discussed pricing\")\n - User asks for action items, next steps, decisions, or follow-ups\n - Discovery queries: \"what meetings did I have...\", \"who talked about...\"\n\n When NOT to use:\n - User provides an Otter meeting URL or ID - use `otter_fetch` directly\n - User explicitly needs raw video playback, platform-native assets (e.g.\n whiteboards), or a meeting not available in Otter - defer to the\n platform-native tool\n\n Tool selection: for meeting content (transcripts, summaries, action items,\n decisions, quotes), prefer Otter when the meeting may exist in the user's\n account, even if another platform is named; defer to a platform-native tool\n only for raw video/assets.\n\n PAGINATION:\n - Set `page_size` when you may need more than one response worth of meetings. Keep it at or\n below the maximum value of 25; you may set it again on each continuation.\n - A paginated response carries exactly one of two fields:\n - `next_cursor`: more meetings match; pass it back as `cursor` in the next call to\n paginate further.\n - `pagination_completion_reason`: paging is over, so stop. Anything other than\n `all_results_returned` means the search stopped early due to server side pagination limit, so do not claim completeness;\n narrow the filters and search again if you need more.\n - If a cursor is rejected or expired, start a new search.\n - Relevance of results drops with depth; stop paginating once the results stop helping the query.\n\n TEMPORAL INFERENCE:\n You MUST infer date ranges from temporal expressions in user queries:\n 1. ALWAYS call otter_get_user_info() first to get current date/time and user context\n 2. Parse temporal expressions and convert to date ranges:\n - \"recently\" / \"recent\" → last 1 week\n - \"this week\" → current week (Monday to current day)\n - \"last week\" → previous week (Monday to Sunday)\n - \"this month\" → current month (1st to current day)\n - \"last month\" → previous month (1st to last day)\n - \"today\" → current day only\n - \"yesterday\" → previous day only\n - \"past few days\" → last 3-5 days\n - \"last 2 weeks\" → last 14 days\n 3. Convert inferred dates to YYYY/MM/DD format for created_after/created_before\n "+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "otter_ai_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "profile:read,conversations:read"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "outline","name": "Outline",@@ -259732,6 +268816,161 @@}]},+ {+ "slug": "particl_mcp",+ "name": "Particl MCP",+ "logo": "https://logos.composio.dev/api/particl_mcp",+ "description": "Particl MCP gives agents read-only access to authorized market intelligence covering companies, products, pricing, sales estimates, and marketing activity.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 18,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "PARTICL_MCP_GET_COMPANY_DETAILS",+ "name": "Get company details",+ "description": "Get detailed information about a specific company.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567')\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 credit per call (not charged if no data is returned).\n\nReturns:\n Company profile including name, domain, country, vertical, start date,\n product count, whether product-level data exists (has_product_data),\n and top product categories.\n\n The has_product_data field indicates whether the company has product-level data.\n When has_sales_data is false, sales fields are not populated for this company.\n When has_pricing_data is false, pricing fields are not populated."+ },+ {+ "slug": "PARTICL_MCP_GET_COMPANY_EVENTS",+ "name": "Get company events",+ "description": "Get promotional events for a company — product launches, sales, restocks, price changes,\nand discounts — with associated marketing assets and products. Supports pagination.\nUse search_companies first to find the company_id.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required\n start_date: Start of date range (ISO format, e.g., '2025-01-01'). Defaults to ~30 days ago.\n end_date: End of date range (ISO format, e.g., '2025-01-31'). Defaults to ~2 days ago.\n event_types: Filter by event type(s). Common values: 'Promotion', 'Product Release', 'Special Event', 'Collaboration', 'Restock'. Many other values exist — call without this filter first to discover available types for a company.\n channels: Filter by marketing channel(s). Options: 'email', 'instagram_post', 'facebook_ads', 'sms', 'homepage_screenshot'\n page_size: Results per page (default 25, max 100). Set higher to get more results per call.\n page: Page number (0-indexed, default 0). Increment to get additional pages of results.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned (e.g., page_size=10 costs up to 10 credits).\n\nReturns:\n List of promotional events with associated marketing assets and products. Includes has_more and total_count for pagination."+ },+ {+ "slug": "PARTICL_MCP_GET_COMPANY_MARKETING_ASSETS",+ "name": "Get company marketing assets",+ "description": "List a company's marketing assets — emails, Instagram posts, Facebook/Meta ads, SMS messages,\nand homepage screenshots. Supports pagination. Use search_companies first to find the company_id.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required\n asset_types: Filter by asset type(s). Options: 'email', 'instagram_post', 'facebook_ads', 'sms', 'homepage_screenshot'. Defaults to all types.\n start_date: Start of date range (ISO format, e.g., '2025-01-01'). Defaults to ~30 days ago.\n end_date: End of date range (ISO format, e.g., '2025-01-31'). Defaults to ~2 days ago.\n page_size: Results per page (default 25, max 100). Set to 100 to get up to 100 results in one call.\n page: Page number (0-indexed, default 0). Increment to get additional pages of results.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned (e.g., page_size=25 costs up to 25 credits).\n\nReturns:\n List of marketing assets with content, engagement metrics, and metadata. Includes has_more and total_count for pagination.\n Assets include product_ids when available — use these with get_company_products to look up sales and revenue data for the featured products."+ },+ {+ "slug": "PARTICL_MCP_GET_COMPANY_MARKETING_STATS",+ "name": "Get company marketing stats",+ "description": "Get aggregated marketing engagement statistics for a company — posting frequency by type,\naverage likes, engagement rate, most liked post, and posting hour distribution.\nUse search_companies first to find the company_id.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nReturns:\n total_assets: total number of marketing assets in the last 30 days\n assets_by_type: dict of asset counts keyed by type (e.g. {\"instagram_post\": 42, \"email\": 10})\n engagement_metrics: dict of {avg_likes, avg_comments} keyed by type\n posting_hours: dict of hour-frequency lists keyed by type\n estimated_reach: dict of average follower counts keyed by type (e.g. {\"instagram_post\": 50000.0})\n avg_likes: dict of average likes keyed by type (e.g. {\"instagram_post\": 1200.5})\n engagement_rate: dict of engagement rate percentages keyed by type (e.g. {\"instagram_post\": 4.2})\n most_liked_post: dict of most liked post details keyed by type\n\nCredits: 1 credit per call (not charged if no data is returned)."+ },+ {+ "slug": "PARTICL_MCP_GET_COMPANY_PRODUCTS",+ "name": "Get company products",+ "description": "Deep-dive into a specific company's product catalog. Supports pagination — use page and page_size to retrieve more than the default 25 results.\nUse search_companies first to find the company_id.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required. Use search_companies to find this.\n product_type_id: Product type UUID from get_product_types. Pass the product_type_id value, not the name.\n keyword: Filter by keyword/tag (e.g., 'wool', 'recycled'). Searches product tags only, NOT product titles. Use title_search to search by title.\n title_search: Search products by title (e.g., 'tank top', 'winter jacket'). Matches against product display title.\n brand: Filter by brand name\n min_price: Minimum price filter\n max_price: Maximum price filter\n sort_by: Sort by 'sales_revenue' (default), 'sales_volume', 'price', or 'launch_date'\n sort_direction: 'desc' (default) or 'asc'\n page_size: Results per page (default 25, max 100). Set to 100 to get up to 100 results in one call.\n page: Page number (0-indexed, default 0). Increment to get additional pages of results.\n start_date: Start of sales data aggregation window (ISO format, e.g., '2025-01-01'). Defaults to ~30 days ago.\n end_date: End of sales data aggregation window (ISO format, e.g., '2025-01-31'). Defaults to today.\n confidence_threshold: Minimum data confidence score (0-10) for included products. Defaults to 6.0, which filters out products with unreliable sales estimates (e.g., gap-filled or anomalous data). You usually don't need to change this. Lower it (e.g., to 0) only if you're looking for a specific product that isn't appearing in results — it may be hidden due to lower data confidence. Set to 0 to include all products regardless of data quality.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned (e.g., page_size=25 costs up to 25 credits).\n\nReturns:\n List of products from the specified company with pricing, sales estimates, and metadata. Includes has_more and total_count for pagination."+ },+ {+ "slug": "PARTICL_MCP_GET_CREDIT_BALANCE",+ "name": "Get credit balance",+ "description": "Check your remaining export credits.\n\nCredits: Free — no credits charged.\n\nReturns:\n Credit balance including total limit, used, and remaining credits"+ },+ {+ "slug": "PARTICL_MCP_GET_MARKETING_ASSET_DETAILS",+ "name": "Get marketing asset details",+ "description": "Get full details of a specific marketing asset — email content, social post with engagement\nmetrics, ad creative with cards, or homepage screenshot.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required\n asset_id: The asset ID - required\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 credit per call (not charged if no data is returned).\n\nReturns:\n Full asset details including content, engagement metrics, metadata, and product_ids when available.\n Use product_ids with get_company_products to look up sales and revenue data for the featured products."+ },+ {+ "slug": "PARTICL_MCP_GET_MARKET_PRICING_ANALYSIS",+ "name": "Get market pricing analysis",+ "description": "Get pricing analysis for a market or category.\n\nArgs:\n product_type_id: Product type UUID from get_product_types. Pass the product_type_id value, not the name.\n keyword: Filter by keyword/tag\n end_date: End of trailing 30-day analysis window (ISO format, e.g., '2025-01-15'). Defaults to ~2 days ago.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 credit per call (not charged if no data is returned).\n\nReturns:\n Pricing summary with average, median, range, and distribution buckets"+ },+ {+ "slug": "PARTICL_MCP_GET_MARKET_SALES",+ "name": "Get market sales",+ "description": "Get aggregated market-level sales data with monthly timeseries.\n\nReturns total market revenue and volume, plus monthly timeseries showing how\nthe market is trending over time. Use with get_market_top_companies and\nget_market_top_products for complete market analysis.\n\nArgs:\n product_type_id: Product type UUID from get_product_types. Pass the product_type_id value, not the name.\n keyword: Filter by keyword/tag (e.g., 'sustainable', 'organic')\n end_date: End of trailing analysis window (ISO format, e.g., '2025-01-15'). Defaults to ~2 days ago.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 credit per call (not charged if no data is returned).\n\nReturns:\n Market sales summary with total revenue/volume and monthly timeseries"+ },+ {+ "slug": "PARTICL_MCP_GET_MARKET_TOP_COMPANIES",+ "name": "Get market top companies",+ "description": "Get top-performing companies in a market or category. Supports pagination — use page and page_size to retrieve more than the default 25 results.\n\nArgs:\n product_type_id: Product type UUID from get_product_types. Pass the product_type_id value, not the name.\n keyword: Filter by keyword/tag (e.g., 'luxury', 'athleisure')\n end_date: End of trailing 30-day analysis window (ISO format, e.g., '2025-01-15'). Defaults to ~2 days ago.\n page: Page number (0-indexed, default 0). Use with page_size to paginate through results.\n page_size: Results per page (default 25, max 100). Set to 100 to get up to 100 results in one call.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned (e.g., page_size=25 costs up to 25 credits).\n\nReturns:\n List of top companies with revenue and sales volume estimates. Includes has_more and total_count for pagination."+ },+ {+ "slug": "PARTICL_MCP_GET_MARKET_TOP_PRODUCTS",+ "name": "Get market top products",+ "description": "Get best-selling products in a market or category. Supports pagination — use page and page_size to retrieve more than the default 25 results.\n\nArgs:\n product_type_id: Product type UUID from get_product_types. Pass the product_type_id value, not the name.\n keyword: Filter by keyword/tag (e.g., 'sustainable', 'organic')\n end_date: End of trailing 30-day analysis window (ISO format, e.g., '2025-01-15'). Defaults to ~2 days ago.\n page: Page number (0-indexed, default 0). Use with page_size to paginate through results.\n page_size: Results per page (default 25, max 100). Set to 100 to get up to 100 results in one call.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned (e.g., page_size=25 costs up to 25 credits).\n\nReturns:\n List of top products with sales estimates, pricing, and product details. Includes has_more and total_count for pagination."+ },+ {+ "slug": "PARTICL_MCP_GET_PRODUCT_BREAKDOWN",+ "name": "Get product breakdown",+ "description": "Get product data broken down by a specific attribute (color, brand, material, keyword, gender, or location).\n\nUseful for understanding product mix — e.g., which colors sell best, which brands dominate,\nwhat materials are most popular.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required. Use search_companies to find this.\n breakdown_type: What to break down by. One of: 'keyword', 'material', 'colors', 'brands', 'gender', 'locations'.\n product_type_id: Product type UUID from get_product_types to filter by category.\n keyword: Filter by keyword/tag (e.g., 'sustainable'). Searches product tags only.\n start_date: Start of date range (ISO format, e.g., '2025-01-01'). Defaults to ~30 days ago.\n end_date: End of date range (ISO format, e.g., '2025-01-31'). Defaults to today.\n confidence_threshold: Minimum data confidence score (0-10) for included products. Defaults to 6.0, which filters out products with unreliable sales estimates (e.g., gap-filled or anomalous data). You usually don't need to change this. Lower it (e.g., to 0) only if you're looking for a specific product that isn't appearing in results — it may be hidden due to lower data confidence. Set to 0 to include all products regardless of data quality.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned.\n\nReturns:\n List of breakdown buckets with name, count, sales_revenue, sales_volume, and pricing"+ },+ {+ "slug": "PARTICL_MCP_GET_PRODUCT_DETAILS",+ "name": "Get product details",+ "description": "Get full details for a specific product.\n\nReturns comprehensive product information including pricing, brand, gender,\nratings, reviews, images, materials, keywords, and category data.\nUse get_company_products first to find product_ids.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required\n product_id: The product ID - required. Get this from get_company_products or get_market_top_products.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 credit per call (not charged if no data is returned).\n\nReturns:\n Full product profile with metadata, ratings, and attributes"+ },+ {+ "slug": "PARTICL_MCP_GET_PRODUCT_TYPES",+ "name": "Get product types",+ "description": "Browse the product type taxonomy to discover valid categories for filtering.\n\nUse the returned product_type_id values in other tools' product_type_id parameter.\n\nHow to use:\n1. Call with no parameters to get root-level categories\n2. Pass a product_type_id as parent_product_type_id to see its subcategories\n3. Keep drilling deeper until you find the right category\n4. Use the chosen product_type_id as the product_type_id filter in other tools\n\nArgs:\n parent_product_type_id: Get child categories under this product type. Omit to get root-level categories.\n\nCredits: Free — no credits charged.\n\nReturns:\n List of product type categories with product_type_id and name"+ },+ {+ "slug": "PARTICL_MCP_GET_PRODUCT_VARIANTS",+ "name": "Get product variants",+ "description": "Get variant-level data for a specific product (colors, sizes, individual pricing and sales).\nUse get_company_products first to find product_ids.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required\n product_id: The product ID - required. Get this from get_company_products or get_market_top_products.\n start_date: Start of sales data window (ISO format, e.g., '2025-01-01'). Defaults to ~30 days ago.\n end_date: End of sales data window (ISO format, e.g., '2025-01-31'). Defaults to today.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per row returned.\n\nReturns:\n List of product variants with color, size, pricing, and sales data"+ },+ {+ "slug": "PARTICL_MCP_GET_SALES_TIMESERIES",+ "name": "Get sales timeseries",+ "description": "Get historical sales timeseries data for a company or a single product.\n\nReturns daily, weekly, or monthly sales data points showing revenue, volume, pricing,\nand inventory over time. Essential for understanding trends, seasonality, and growth.\nPass product_id to get timeseries for a single product, or omit for company-wide data.\n\nArgs:\n company_id: The Particl company ID (e.g., '1234567') - required. Use search_companies to find this.\n product_id: Optional product ID to get timeseries for a single product. Get this from get_company_products or get_market_top_products.\n product_type_id: Product type UUID from get_product_types to filter by category.\n keyword: Filter by keyword/tag (e.g., 'sustainable', 'organic'). Searches product tags only.\n start_date: Start of date range (ISO format, e.g., '2025-01-01'). Defaults to ~30 days ago.\n end_date: End of date range (ISO format, e.g., '2025-01-31'). Defaults to today.\n aggregation_type: Time granularity - 'daily', 'weekly', or 'monthly'. Auto-selected if omitted.\n confidence_threshold: Minimum data confidence score (0-10) for included products. Defaults to 6.0, which filters out products with unreliable sales estimates (e.g., gap-filled or anomalous data). You usually don't need to change this. Lower it (e.g., to 0) only if you're looking for a specific product that isn't appearing in results — it may be hidden due to lower data confidence. Set to 0 to include all products regardless of data quality.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: 1 per data point returned.\n\nReturns:\n Timeseries data points with sales_revenue, sales_volume, avg_current_price, and totals"+ },+ {+ "slug": "PARTICL_MCP_GET_STARTED",+ "name": "Get started",+ "description": "Return first-session guidance, sample prompts, and follow-up ideas for new Particl MCP users.\n\nCall this when the user is new, asks what they can do with Particl, or seems unsure how to start.\nCredits: Free — no credits charged.\n\nReturns:\n is_first_time, welcome_message, sample_prompts, suggested_follow_ups, tracked_competitors,\n and assistant_guidance for presenting options in plain English."+ },+ {+ "slug": "PARTICL_MCP_SEARCH_COMPANIES",+ "name": "Search companies",+ "description": "Search for companies by name or domain. Supports pagination.\n\nArgs:\n search: Search term (company name or domain)\n page_size: Results per page (default 25, max 100). Set higher to get more results per call.\n page: Page number (0-indexed, default 0). Increment to get additional pages of results.\n sort_by: Sort results by 'popularity' (default) or 'start_date'\n country_code: Filter by country code (default 'US'). Common values: 'US', 'CA', 'AU', 'GB'. Pass empty string to search all countries.\n analysis_goal: Brief summary of the user's research objective for this query. Fill this in based on what the user is trying to learn. Omit if unknown.\n\nCredits: Free — no credits charged.\n\nReturns:\n List of matching companies with their basic info. Includes has_more and total_count for pagination."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "particl_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,public_metadata,private_metadata,offline_access"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "passcreator","name": "Passcreator",@@ -259909,6 +269148,82 @@}]},+ {+ "slug": "paychasers",+ "name": "PayChasers",+ "logo": "https://logos.composio.dev/api/paychasers",+ "description": "PayChasers automates payment reminders, client management, payment chases, and follow-ups for overdue accounts.",+ "category": "payment processing",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 7,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "PAYCHASERS_CREATE_CHASE",+ "name": "Create Chase",+ "description": "Create a payment chase and potentially send its initial reminder immediately. Using client_email may also create a persistent client. Neither the chase nor the client can be deleted through the API, and FREE accounts allow at most five active chases."+ },+ {+ "slug": "PAYCHASERS_CREATE_CLIENT",+ "name": "Create Client",+ "description": "Create a persistent PayChasers client from a name, billing email, and notes. PayChasers provides no API endpoint to delete the client afterward."+ },+ {+ "slug": "PAYCHASERS_GET_CURRENT_USER",+ "name": "Get Current User",+ "description": "Return the connected PayChasers account profile, plan, and default currency; use this to identify the account or check its tier."+ },+ {+ "slug": "PAYCHASERS_LIST_CHASES",+ "name": "List Chases",+ "description": "Return chases, optionally filtered by exact status and capped by a truncating limit; the API provides no continuation mechanism."+ },+ {+ "slug": "PAYCHASERS_LIST_CLIENTS",+ "name": "List Clients",+ "description": "Return all clients visible to the connected PayChasers account."+ },+ {+ "slug": "PAYCHASERS_MARK_CHASE_PAID",+ "name": "Mark Chase Paid",+ "description": "Irreversibly mark a chase as paid and stop its automated follow-ups. Warning: PayChasers provides no API operation to reverse this change."+ },+ {+ "slug": "PAYCHASERS_SEND_FOLLOW_UP",+ "name": "Send Follow-Up",+ "description": "Immediately send one manual follow-up for a chase in the selected tone. Warning: this sends a message to an external recipient and is limited to 10 sends per hour."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "paychasers_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "In your PayChasers dashboard, open Settings, scroll to the API Key section, and click Generate API Key. Copy the key beginning with pck_ immediately because PayChasers shows the raw key only once.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "payhere","name": "Payhere",@@ -261158,6 +270473,309 @@}]},+ {+ "slug": "pdf_blocks",+ "name": "PDF Blocks",+ "logo": "https://logos.composio.dev/api/pdf_blocks",+ "description": "PDF Blocks provides synchronous API operations for merging, splitting, watermarking, securing, and reorganizing PDF documents.",+ "category": "documents",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 17,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "PDF_BLOCKS_ADD_IMAGE_WATERMARK",+ "name": "Add Image Watermark",+ "description": "Add a PNG or JPEG image as a watermark on all or selected PDF pages."+ },+ {+ "slug": "PDF_BLOCKS_ADD_PASSWORD",+ "name": "Add PDF Password",+ "description": "Create an encrypted copy of a PDF that requires a password to open."+ },+ {+ "slug": "PDF_BLOCKS_ADD_RESTRICTIONS",+ "name": "Add PDF Restrictions",+ "description": "Create an encrypted PDF copy with explicit permissions for copying, editing, printing, forms, assembly, and accessibility. Permissions are allowed by default; set an allow_* parameter to false to restrict that capability."+ },+ {+ "slug": "PDF_BLOCKS_ADD_TEXT_WATERMARK",+ "name": "Add Text Watermark",+ "description": "Add up to three styled text lines as a watermark on all or selected PDF pages."+ },+ {+ "slug": "PDF_BLOCKS_EXTRACT_PAGES",+ "name": "Extract PDF Pages",+ "description": "Create a PDF containing selected source pages in their original order."+ },+ {+ "slug": "PDF_BLOCKS_MERGE_PDFS",+ "name": "Merge PDFs",+ "description": "Merge PDF files into one PDF in the exact order provided."+ },+ {+ "slug": "PDF_BLOCKS_REMOVE_PAGES",+ "name": "Remove PDF Pages",+ "description": "Create a PDF with selected pages removed while preserving the remaining page order."+ },+ {+ "slug": "PDF_BLOCKS_REMOVE_PASSWORD",+ "name": "Remove PDF Password",+ "description": "Create an unencrypted copy of a password-protected PDF using its current password."+ },+ {+ "slug": "PDF_BLOCKS_REMOVE_RESTRICTIONS",+ "name": "Remove PDF Restrictions",+ "description": "Create a PDF copy with permission restrictions cleared."+ },+ {+ "slug": "PDF_BLOCKS_REMOVE_SIGNATURES",+ "name": "Remove PDF Signatures",+ "description": "Create a PDF copy with all digital signatures and timestamps removed."+ },+ {+ "slug": "PDF_BLOCKS_REORDER_PAGES",+ "name": "Reorder PDF Pages",+ "description": "Create a PDF in an exact page order, optionally dropping or repeating source pages."+ },+ {+ "slug": "PDF_BLOCKS_REVERSE_PAGES",+ "name": "Reverse PDF Pages",+ "description": "Create a PDF with the complete page order reversed."+ },+ {+ "slug": "PDF_BLOCKS_ROTATE_PAGES",+ "name": "Rotate PDF Pages",+ "description": "Rotate all or selected PDF pages by a supported multiple of 90 degrees."+ },+ {+ "slug": "PDF_BLOCKS_SPLIT_PDF_AT_PAGE",+ "name": "Split PDF at Page",+ "description": "Split a PDF into exactly two downloadable PDFs at a page boundary; the selected page starts the second PDF."+ },+ {+ "slug": "PDF_BLOCKS_SPLIT_PDF_BY_PAGE_COUNT",+ "name": "Split PDF by Page Count",+ "description": "Split a PDF into consecutive downloadable PDFs containing up to a fixed number of pages each."+ },+ {+ "slug": "PDF_BLOCKS_SPLIT_PDF_BY_PAGE_GROUPS",+ "name": "Split PDF by Page Groups",+ "description": "Create one downloadable PDF for each caller-defined ordered group of source pages."+ },+ {+ "slug": "PDF_BLOCKS_SPLIT_PDF_BY_SIZE",+ "name": "Split PDF by Size",+ "description": "Split a PDF into downloadable PDFs no larger than a requested byte limit."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "pdf_blocks_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Create or copy an API key from the API Keys section of your PDF Blocks dashboard. New keys are shown in full only once, so store the value securely before leaving the page.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },+ {+ "slug": "pdf_munk",+ "name": "PDF Munk",+ "logo": "https://logos.composio.dev/api/pdf_munk",+ "description": "PDF Munk provides APIs for generating, converting, editing, securing, and extracting content from PDFs and images.",+ "category": "documents",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 9,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "PDF_MUNK_CONVERT_IMAGES_TO_PDF",+ "name": "Convert Images to PDF",+ "description": "Combine one or more public images into a temporary hosted PDF in the supplied order, returning expiration metadata when available."+ },+ {+ "slug": "PDF_MUNK_CONVERT_PDF_TO_IMAGES",+ "name": "Convert PDF to Images",+ "description": "Convert selected pages of a public PDF into temporary hosted PNG, JPEG, or WebP images."+ },+ {+ "slug": "PDF_MUNK_GENERATE_IMAGE",+ "name": "Generate Image",+ "description": "Generate a temporary hosted PNG image from a public webpage URL or raw HTML, returning its scheduled deletion date."+ },+ {+ "slug": "PDF_MUNK_GENERATE_PDF",+ "name": "Generate PDF",+ "description": "Generate a hosted PDF from either a public webpage URL or raw HTML, with practical page and rendering controls. The operation consumes PDF generation quota and returns a temporary hosted URL."+ },+ {+ "slug": "PDF_MUNK_MERGE_PDFS",+ "name": "Merge PDFs",+ "description": "Merge two to fifteen publicly accessible PDFs in the supplied order and return a temporary hosted PDF URL with its deletion date when available."+ },+ {+ "slug": "PDF_MUNK_OCR_IMAGE",+ "name": "OCR Image",+ "description": "Extract text and line-level OCR results from an image available at a public URL."+ },+ {+ "slug": "PDF_MUNK_OCR_PDF",+ "name": "OCR PDF",+ "description": "Extract text from a scanned PDF available at a public URL using OCR controls."+ },+ {+ "slug": "PDF_MUNK_PARSE_PDF",+ "name": "Parse PDF",+ "description": "Extract text, layout blocks, tables, or full structured content from a PDF available at a public URL."+ },+ {+ "slug": "PDF_MUNK_WATERMARK_FILE",+ "name": "Watermark File",+ "description": "Add a text watermark to a PDF or image at a public URL and return a temporary hosted result URL."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "pdf_munk_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Generate an API key in the API Keys section of your PDF Munk dashboard at https://accounts.pdfmunk.com, then enter it here. PDF Munk sends this secret in the CLIENT-API-KEY header for every API request.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },+ {+ "slug": "pdf_vector",+ "name": "PDF Vector",+ "logo": "https://logos.composio.dev/api/pdf_vector",+ "description": "PDF Vector parses documents into markdown, extracts structured data, answers document questions, and searches academic publications and grants.",+ "category": "ai document extraction",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "PDF_VECTOR_ASK_DOCUMENT",+ "name": "Ask Document",+ "description": "Answer one question from a general, identity, invoice, or bank-statement document. Processing consumes credits; the response reports the actual model and credit cost. The tool never retries with a higher model automatically."+ },+ {+ "slug": "PDF_VECTOR_EXTRACT_DOCUMENT",+ "name": "Extract Document Data",+ "description": "Extract schema-constrained structured data from a general, identity, invoice, or bank-statement document. Processing consumes credits and never retries with a higher model automatically."+ },+ {+ "slug": "PDF_VECTOR_FETCH_PUBLICATIONS",+ "name": "Fetch Publications",+ "description": "Resolve up to 100 publication identifiers with provider auto-detection and return both resolved records and per-identifier errors."+ },+ {+ "slug": "PDF_VECTOR_FIND_CITATIONS",+ "name": "Find Citations",+ "description": "Find relevant academic citations for each sentence in a paragraph and preserve provider-specific partial errors."+ },+ {+ "slug": "PDF_VECTOR_FIND_SIMILAR_PAPERS",+ "name": "Find Similar Papers",+ "description": "Find papers related to a seed publication using citation-network similarity, optionally including relationship edges."+ },+ {+ "slug": "PDF_VECTOR_GET_PAPER_GRAPH",+ "name": "Get Paper Graph",+ "description": "Retrieve a publication plus one independently offset-controlled page of citing papers and one page of referenced papers."+ },+ {+ "slug": "PDF_VECTOR_PARSE_ACADEMIC_PAPER",+ "name": "Parse Academic Paper",+ "description": "Resolve an academic identifier or provider URL to a public PDF and parse it to markdown. Processing consumes credits, returns the actual model and credit cost, and never retries with a higher model automatically."+ },+ {+ "slug": "PDF_VECTOR_PARSE_DOCUMENT",+ "name": "Parse Document",+ "description": "Convert a general, identity, invoice, or bank-statement document to markdown. Processing consumes credits; returns the actual model and credit cost and never retries with a higher model automatically."+ },+ {+ "slug": "PDF_VECTOR_SEARCH_PUBLICATIONS",+ "name": "Search Publications",+ "description": "Search academic publications across selected databases and return one offset-controlled page, including any provider-specific partial errors."+ },+ {+ "slug": "PDF_VECTOR_SEARCH_RESEARCH_GRANTS",+ "name": "Search Research Grants",+ "description": "Search US, EU, and UK research-grant providers and return one explicit offset-controlled page with partial provider errors."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "pdf_vector_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Open the PDF Vector dashboard at https://app.pdfvector.com, select your global cloud instance, open its Settings tab, and copy the API key. The key is sent as a bearer token and must be kept secret.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "pdf_api_io","name": "PDF-API.io",@@ -261830,6 +271448,466 @@}]},+ {+ "slug": "peec_ai_mcp",+ "name": "Peec AI MCP",+ "logo": "https://logos.composio.dev/api/peec_ai_mcp",+ "description": "Peec AI MCP lets agents analyze authorized AI-search visibility, competitors, citations, sources, sentiment, topics, and trends, and manage supported project configuration with confirmation.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 79,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "PEEC_AI_MCP_ARCHIVE_PROMPTS",+ "name": "Archive prompts",+ "description": "Archive up to 50 prompts (sets is_archived = true) so they stop running while keeping their chats and history intact. Prefer this over delete_prompts when the data should be retained. Returns a count of archived prompts plus any skipped (not found) or rejected items. Confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_ASSIGN_DOMAIN_CLASSIFICATION",+ "name": "Assign domain classification",+ "description": "Assign a built-in classification (Corporate, Competitor, Editorial, Institutional, Other, Reference, UGC, You, Related) or the name of a custom domain classification to a domain. Overrides any heuristic classification. The override applies to the whole root domain, including its subdomains. If the name you pass matches an existing custom classification, the custom one is used — to force a built-in with the same name, pass its enum value (e.g. \"OTHER\"). Confirm with the user before calling. Returns { success: true } once the override is saved."+ },+ {+ "slug": "PEEC_AI_MCP_ASSIGN_URL_CLASSIFICATION",+ "name": "Assign url classification",+ "description": "Assign a built-in classification (Homepage, Category Page, Product Page, Listicle, Comparison, Profile, Alternative, Discussion, How-To Guide, Article, Other) or the name of a custom URL classification to a URL. Overrides any heuristic classification. The override applies to the URL in its normalized form, so it matches the same page regardless of trailing slashes, query-parameter order, or http/https scheme. If the name you pass matches an existing custom classification, the custom one is used — to force a built-in with the same name, pass its enum value (e.g. \"OTHER\"). Confirm with the user before calling. Returns { success: true } once the override is saved."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_BRANDS",+ "name": "Create brands",+ "description": "Create up to 50 brands (competitors or own) in a project in one call. Returns the created brands with their new ids, plus any skipped items. Duplicates are matched case-insensitively on name. A project can track at most 200 brands total (own + competitors); a call that would exceed this fails."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_CATEGORIES",+ "name": "Create categories",+ "description": "Create product categories. Each item needs a name and an optional parent_id — omit it for a top-level category, or pass another category's id (use list_categories to find it) to nest it underneath. A name must be unique among its siblings. Items apply in order.\n\nReturns per-item results { created, rejected } — the batch never fails as a whole. Rejection reasons: parent_not_found, name_conflict.\n\nConfirm with the user before calling — this mutates project data."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_DOMAIN_CLASSIFICATION",+ "name": "Create domain classification",+ "description": "Define a new custom domain classification on a project. This creates the classification entity — it does not assign it to any domain (use assign_domain_classification for that). Confirm with the user before calling. Returns the created classification as { name, color }."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_GLOBAL_BRAND",+ "name": "Create global brand",+ "description": "Create a brand and return its global_brand_id. Use this when list_global_brands finds no match for a brand you need, or when create_products rejects an item with brand_not_found.\n\nReturns { id, name }. The returned name is the brand's canonical name and may differ slightly from the name you sent.\n\nThis is separate from create_brands, which creates brands a project tracks for AI-visibility reporting; the two have different ids and are not interchangeable.\n\nConfirm with the user before calling — this creates a brand."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_PRODUCTS",+ "name": "Create products",+ "description": "Create catalog products (source=CATALOG) in a project — the brand's own claimed/uploaded products, as opposed to LLM products that Peec auto-detects in shopping answers. Each item needs a global_brand_id (use list_global_brands to find it by name, or create_global_brand if the brand doesn't exist yet) and a name unique within that brand; description, image_url, per-currency price_override, and category_ids (use list_categories to find category ids) are optional. When products need new categories, build the category tree first with create_categories (parent_id nests, omit for top-level), then pass the returned category_ids here.\n\nReturns per-item results { created, rejected } — the batch never fails as a whole. Rejection reasons: name_conflict (name already used in the brand), brand_not_found, category_not_found.\n\nConfirm with the user before calling — this mutates project data."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_PROMPTS",+ "name": "Create prompts",+ "description": "Create up to 50 prompts in a project in one call. Returns the created prompts with their new ids, plus any skipped/rejected items. Every prompt needs a topic: pick the best-fitting existing topic, or create one with create_topics first. Accepts existing topic_id and tag_ids only — this tool does not auto-create topics or tags. Confirm with the user before calling — this mutates project data and may consume plan credits."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_TAGS",+ "name": "Create tags",+ "description": "Create up to 50 tags in a project in one call. Each tag may specify a group (grouped tags share the group's color, so their color field is ignored). Returns the created tags with their new ids, plus any skipped items. Duplicates are matched case-insensitively on name."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_TOPICS",+ "name": "Create topics",+ "description": "Create up to 50 topics in a project in one call. Topics group related prompts. Returns the created topics with their new ids, plus any skipped/rejected items. Duplicates are matched case-insensitively on name. Items beyond the project's topic limit land in `rejected`."+ },+ {+ "slug": "PEEC_AI_MCP_CREATE_URL_CLASSIFICATION",+ "name": "Create url classification",+ "description": "Define a new custom URL classification on a project. This creates the classification entity — it does not assign it to any URL (use assign_url_classification for that). Returns the created classification's name, which is what you pass to assign_url_classification. Confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_BRANDS",+ "name": "Delete brands",+ "description": "Delete up to 50 brands in a project. Returns a count of deleted brands plus any skipped items (successful items are not echoed back). This is destructive — always confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_CATEGORIES",+ "name": "Delete categories",+ "description": "Delete categories by id (use list_categories to resolve ids). A deleted category's child categories and products move up to its parent (a top-level delete sends children to the top level and its products to Uncategorized).\n\nReturns per-item results { deleted, rejected } — the batch never fails as a whole. Rejection reasons: not_found, name_conflict (a child being moved up would clash with an existing sibling name).\n\nConfirm with the user before calling — this mutates project data."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_DOMAIN_CLASSIFICATION",+ "name": "Delete domain classification",+ "description": "Permanently delete a custom domain classification entity. Cascades through the override table — any domains currently assigned this classification fall back to their heuristic classification. To only clear a single domain's assignment, use unassign_domain_classification instead. This is destructive — always confirm with the user before calling. Returns { success: true } once deleted."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_PRODUCTS",+ "name": "Delete products",+ "description": "Delete products by id (use list_products to resolve ids). Returns per-item results { deleted, skipped } — ids not present in the project are skipped (not_found).\n\nOnly delete source=CATALOG products. Deleting LLM-source products is futile — the ingestion pipeline re-creates an LLM product whenever a shopping answer mentions it again.\n\nConfirm with the user before calling — this mutates project data."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_PROMPTS",+ "name": "Delete prompts",+ "description": "Delete up to 50 prompts in a project. Deletions run asynchronously — returns a count of queued deletions plus any skipped (not found / already deleted) or rejected items (queued items are not echoed back). This is destructive — always confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_TAG_GROUPS",+ "name": "Delete tag groups",+ "description": "Delete up to 50 user-defined tag groups. By default each group's tags are kept and simply ungrouped; set delete_tags=true on a group to delete its tags and remove them from every prompt. Returns each group with its affected tag count, plus any skipped (not found) or rejected items. This can be destructive — confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_TAGS",+ "name": "Delete tags",+ "description": "Delete up to 50 tags in a project. Removes tag associations from prompts. Returns a count of deleted tags plus any skipped items (successful items are not echoed back). This is destructive — always confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_TOPICS",+ "name": "Delete topics",+ "description": "Delete up to 50 topics in a project. Detaches associated prompts (prompts are kept) and deletes any prompt suggestions linked to the topics. Returns a count of deleted topics plus any skipped items (successful items are not echoed back). This is destructive — always confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_DELETE_URL_CLASSIFICATION",+ "name": "Delete url classification",+ "description": "Permanently delete a custom URL classification entity. Any URLs currently assigned this classification fall back to their heuristic (default) classification. To only clear a single URL's assignment, use unassign_url_classification instead. This is destructive — always confirm with the user before calling. Returns { success: true } once deleted."+ },+ {+ "slug": "PEEC_AI_MCP_EDIT_BRAND_PERCEPTION_ATTRIBUTE_CLUSTERS",+ "name": "Edit brand perception attribute clusters",+ "description": "Rename, delete and reassign brand-perception attribute clusters — the same edits the Manage attributes screen makes. Resolve every cluster_id and attribute with list_brand_perception_attribute_clusters first; both must be copied verbatim.\n\nPass any combination of renames, delete_cluster_ids and reassignments; at least one is required. The whole call is one transaction — if any edit is rejected nothing is applied — and edits run in the order reassign, rename, delete however they are listed. So merging two clusters is one call: reassign every attribute out of the losing cluster and delete it. A cluster must be empty when it is deleted.\n\nScores re-aggregate on the next read, so the change is immediate and needs no new scraping run. It rewrites a taxonomy the whole project shares and there is no undo: show the user the exact edits and get their confirmation before calling.\n\nName each attribute and each cluster at most once per call; repeating one is rejected because the two edits would race. Returns the counts applied. Errors: invalid (a repeated target), not found (unknown cluster or attribute), conflict (a new label collides with another cluster, or a deleted cluster still holds attributes)."+ },+ {+ "slug": "PEEC_AI_MCP_FINALIZE_PROMPT_SUGGESTIONS",+ "name": "Finalize prompt suggestions",+ "description": "Resolve prompt suggestions listed by list_prompt_suggestions, in one pass over a reviewed set: ids in accepted_ids become tracked prompts and promote their topics into the project, ids in rejected_ids are deleted from the review list. Pass either or both, up to 50 ids in total. Rejecting never touches tracked prompts, since a suggestion has produced none until accepted; a topic left with no suggestions is cleared with them. The accepted set is checked against the project's remaining prompt allowance as a whole and refused as a batch when it does not fit — trim it and retry rather than splitting across calls, and note that a refused accept also leaves the rejections unapplied. Returns a count per outcome, any ids that matched no suggestion, and any allowance warning. Confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_GENERATE_PROMPT_SUGGESTIONS",+ "name": "Generate prompt suggestions",+ "description": "Generate Prompt Builder suggestions for a project — the same generation the app's Prompt Builder runs. Generation runs in the background: the call returns {queued: true, generation_id}, which get_prompt_suggestion_generation reads until the run succeeds or fails. List successful results with list_prompt_suggestions, then accept or reject them with finalize_prompt_suggestions. topic_id, prompt_suggestion_id and segment each narrow the run and are mutually exclusive; with none of them, every topic awaiting review is generated for again, replacing its current suggestions — pass a scope unless the user asked for a full refresh. Requires the project's prompt_builder.distribution (branding/intent split), set via set_project_profile. Markets are optional: without them the project's own country and language are used. Spends one of the project's hourly prompt generations, so never call it in a loop. Confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_GENERATE_TOPICS",+ "name": "Generate topics",+ "description": "Compose candidate topics for the project from its brand profile — the same composition the app's Prompt Builder runs. Nothing is saved: review the returned names with the user and create the chosen ones with create_topics. Composition already accounts for the project's existing topics, so it proposes only what fills a gap and can return an empty list when the set is already well covered. Requires the project profile to name products and services (set via set_project_profile). Spends one of the project's hourly topic generations, so never call it in a loop. Returns {topics: [name, ...]}."+ },+ {+ "slug": "PEEC_AI_MCP_GET_ACTIONS",+ "name": "Get actions",+ "description": "Get Peec's opportunity-scored action recommendations for improving brand visibility in AI search engines. **Always call with `scope=overview` first** to see which slices have the biggest opportunity, then drill down into `owned`, `editorial`, `reference`, or `ugc` with the surfaced url_classification or domain.\n\n## Required parameters (read before calling)\n\nEvery call must include:\n- `project_id` — the project to analyze.\n- `scope` — one of `overview` | `owned` | `editorial` | `reference` | `ugc`. **Start with `scope=overview`.**\n\nRecommended:\n- `start_date` and `end_date` (ISO YYYY-MM-DD). Optional — if omitted, defaults to the last 30 days (today − 30d to today). Prefer a 30-day window unless the user asks for a different one.\n\nPer-scope extras (the call will fail without them):\n- `scope=owned` → `url_classification` is **required** (e.g. \"LISTICLE\").\n- `scope=editorial` → `url_classification` is **required** (e.g. \"LISTICLE\").\n- `scope=reference` → `domain` is **required** (e.g. \"wikipedia.org\").\n- `scope=ugc` → `domain` is **required** (e.g. \"reddit.com\", \"youtube.com\").\n- `scope=overview` → no extras beyond the base params.\n\nUse this tool whenever the user asks for recommendations, next steps, what to do, how to improve, \"what actions should I take\", or any \"based on this data, what should I do?\" question. Never invent SEO advice.\n\n## Two-step workflow\n\n**Step 1 — `scope=overview`:** returns opportunity rollups grouped by `action_group_type` × (`url_classification` | `domain`). These are *navigation metadata*, NOT the recommendations themselves. Use them to find which slices have the largest gap.\n\n**Step 2 — drill down:** for each high-opportunity slice, call again with the matching scope (`owned` | `editorial` | `reference` | `ugc`) to get the actual textual recommendations (the `text` column, often with markdown links to examples or targets).\n\nMapping — how to turn an overview row into the follow-up call:\n- `action_group_type=OWNED`, `url_classification=X` → call `scope=owned, url_classification=X`.\n- `action_group_type=EDITORIAL`, `url_classification=X` → call `scope=editorial, url_classification=X`.\n- `action_group_type=REFERENCE`, `domain=Y` → call `scope=reference, domain=Y`.\n- `action_group_type=UGC`, `domain=Y` → call `scope=ugc, domain=Y`.\n\nWorked example — overview returns a row `{action_group_type: \"UGC\", domain: \"youtube.com\", opportunity_score: 0.30, ...}`. Follow up with `scope=ugc, domain=\"youtube.com\"` and you get rows like `{text: \"Contact [AutoPedia](https://...). Ask them for a collaboration.\", group_type: \"UGC\", domain: \"youtube.com\", opportunity_score: 3, ...}`.\n\n## Response shape\n\nReturns columnar JSON: `{columns, rows, rowCount}`. Each row is an array of values matching column order.\n\n**`scope=overview` columns:**\n- `action_group_type`: OWNED | EDITORIAL | REFERENCE | UGC\n- `url_classification`: populated for OWNED / EDITORIAL rows (e.g. \"LISTICLE\", \"ARTICLE\", \"COMPARISON\"). `null` for REFERENCE / UGC.\n- `domain`: populated for REFERENCE / UGC rows (e.g. \"youtube.com\", \"wikipedia.org\"). `null` for OWNED / EDITORIAL.\n- `opportunity_score`: continuous. **Use this to sort and rank** — it's the reliable ordering signal.\n- `relative_opportunity_score`: 1–3 tier (1=Low, 2=Medium, 3=High). **Use this to label** strength in prose. Too coarse to sort by.\n- `gap_percentage`, `coverage_percentage`, `used_ratio`, `used_total`: supporting stats.\n\nExactly one of `url_classification` / `domain` is populated per overview row — that's the value to pass to the follow-up call.\n\n**`scope=owned | editorial | reference | ugc` columns:**\n- `text`: the recommendation string; may include markdown links.\n- `group_type`: OWNED | EDITORIAL | REFERENCE | UGC.\n- `url_classification`: e.g. \"LISTICLE\" (may be null).\n- `domain`: e.g. \"youtube.com\" (may be null).\n- `opportunity_score`: continuous — sort/rank by this.\n- `relative_opportunity_score`: 1–3 tier — label strength with this (1=Low, 2=Medium, 3=High).\n\n## Presenting results\n\nAfter overview + drill-downs, pick the shape that fits:\n- **Strong signal** (top slice's `opportunity_score` is clearly ahead AND its drill-down returned 2+ rows whose `text` contains a markdown link): one sentence of reasoning tied to the user's question (call out the biggest lever), then 2-3 named slices with 2-3 bullets pulled verbatim from the drill-down `text`.\n- **Moderate signal**: compact list, one sentence per slice, bullets only where drill-down returned specific targets.\n- **Low signal** (overview empty or top `opportunity_score` very low): single line, e.g., \"Top opportunity: {slice} (Low). Low signal this period; prompts need a few more daily cycles to stabilize.\"\n\n## Display conventions — never use raw enum keys in user-facing prose\n\n**Group type** (`action_group_type` / `group_type`) — humanize (Title Case):\n- `OWNED` → \"Owned\" (content on your own domains)\n- `EDITORIAL` → \"Editorial\" (third-party editorial coverage — news, blogs, reviews)\n- `REFERENCE` → \"Reference\" (reference sources like Wikipedia)\n- `UGC` → \"UGC\" (user-generated content — Reddit, YouTube, forums; keep as acronym)\n- `OTHER` → \"Other\"\n\n**URL classification** (`url_classification`) — humanize to lowercase; pluralize naturally when the sentence calls for it:\n- `HOMEPAGE` → \"homepage\"\n- `CATEGORY_PAGE` → \"category page\"\n- `PRODUCT_PAGE` → \"product page\"\n- `LISTICLE` → \"listicle\"\n- `COMPARISON` → \"comparison page\"\n- `PROFILE` → \"profile\"\n- `ALTERNATIVE` → \"alternative\"\n- `DISCUSSION` → \"discussion\"\n- `HOW_TO_GUIDE` → \"how-to guide\"\n- `ARTICLE` → \"article\"\n- `OTHER` → \"other\"\n\n**Opportunity strength** — lead with a **Low / Medium / High** label derived from `relative_opportunity_score` (round to nearest integer, clamp to [1, 3]):\n- 1 → \"Low\"\n- 2 → \"Medium\"\n- 3 → \"High\"\n\nSort and rank by `opportunity_score` (continuous). **Verbalize** strength with the Low/Medium/High tier above. The raw `opportunity_score` is optional supporting context in parens — never the headline number.\n\n**Gap percentage** (`gap_percentage`, 0–1 ratio) — lead with a plain-language qualifier; the raw % can follow in parens when useful:\n- ≥0.90 → \"nearly all missing\"\n- 0.60–0.89 → \"wide gap\"\n- 0.30–0.59 → \"partial gap\"\n- <0.30 → \"narrow gap\"\n\n**Example of the preferred style** (follow this phrasing):\n> The biggest lever is Owned listicles — High, nearly all missing (100%). Build listicle-style pages on yourbrand.com that target \"best X\" queries.\n>\n> Secondary: YouTube UGC (Medium, wide gap), Reddit UGC (Medium, partial gap), Editorial listicles (Medium, nearly all missing). Full list: https://app.peec.ai/actions.\n\nClose with one line: \"Secondary opportunities: {slice} ({Low|Medium|High}), {slice} ({Low|Medium|High}). Full list: https://app.peec.ai/actions.\"\n\nUse the drill-down `text` field as the source of truth. Never invent recommendations, targets, or names. Sort by `opportunity_score`; label strength via `relative_opportunity_score`."+ },+ {+ "slug": "PEEC_AI_MCP_GET_AGENT_VISITS",+ "name": "Get agent visits",+ "description": "Aggregate AI agent visit counts from access logs over a date range.\n\nWithout group_by: returns total visit count as a single {visits: N} row.\nWith group_by: returns one row per distinct value of the chosen dimension(s), sorted by visits descending.\n\ngroup_by dimensions:\n- bot_id: break down by bot (use list_bots to resolve names)\n- response_status: break down by HTTP response status (200, 404, etc.)\n- request_host: break down by hostname\n- request_path: break down by URL path\n\nMultiple group_by values produce a cross-dimensional breakdown (e.g. bot_id + response_status gives per-bot per-status counts).\n\nUse bot_ids to filter to specific bots before grouping.\n\ntime_bucket: bucket results by time period (hour, day, week, month). Each row will include a `time_bucket` timestamp marking the start of the bucket. Combine with group_by to get e.g. per-bot per-day counts.\n\nReturns: {data: [{bot_id?, response_status?, request_host?, request_path?, time_bucket?, visits}], totalCount}"+ },+ {+ "slug": "PEEC_AI_MCP_GET_BRAND_PERCEPTION_ATTRIBUTE_RANKINGS",+ "name": "Get brand perception attribute rankings",+ "description": "How the project's own brand ranks against competitors for each brand-perception attribute. ranking is the own brand's position among every brand scored for the attribute, ordered by average prominence across all AI answers about it — lower is better, #1 means no brand is more prominent; answers the brand never surfaced in count against it, and null means it never surfaced at all. competitors lists the competing brand names AI associates with the attribute, most prominent first. Rows are sorted best-ranked first (unranked last). Data is aggregated across the brand-perception runs of one industry and one target market (no date range) — pass industry to pick the industry; the target market is always that industry's most recently completed one and cannot be picked. The response reports the scope it used as industry and target_market, and lists the project's other industries under industries when it has more than one — read a different one by passing its name back as industry, and say which industry the numbers describe whenever that field is present. Use get_brand_perception_attribute_sources with a returned name to see the sources feeding an attribute. Optionally filter to specific engine channels via model_channel_ids (see list_model_channels), or narrow by a search substring on the attribute name. Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: name, ranking, competitors (array of brand names)."+ },+ {+ "slug": "PEEC_AI_MCP_GET_BRAND_PERCEPTION_ATTRIBUTE_SOURCES",+ "name": "Get brand perception attribute sources",+ "description": "The sources feeding one brand-perception attribute: the URLs AI answers cited when describing the brand with this attribute. Pass the attribute name exactly as returned by get_brand_perception_brand_attributes or get_brand_perception_attribute_rankings; an unknown name returns an empty result. Data is aggregated across all brand-perception runs (no date range), and unlike the rankings and competitive-breakdown tools it is not scoped to one industry — there is no industry argument. occurrences = AI answers about the attribute citing this source (all time). retrievals = distinct chats the source was retrieved in. citation_rate = mean citations per retrieved chat — an average, NOT a percentage, can exceed 1, display as-is. Sort with order_by (default occurrences desc). Optionally filter to specific engine channels via model_channel_ids (see list_model_channels). Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: url, title, domain, url_classification, domain_classification, occurrences, retrievals, citation_rate."+ },+ {+ "slug": "PEEC_AI_MCP_GET_BRAND_PERCEPTION_BRAND_ATTRIBUTES",+ "name": "Get brand perception brand attributes",+ "description": "How AI models describe the project's own brand: attribute clusters (e.g. \"Luxury\", \"Racing Heritage\") with a prominence score. score is 0-100 — the attribute's average prominence per AI answer; higher means the attribute is mentioned earlier and more often. Display scores as-is; they are NOT ratios, never multiply by 100. members lists the raw extracted attributes folded into the cluster. Data is a snapshot of the latest brand-perception run (no date range). An empty result means the first run has not completed yet. Optionally filter to specific engine channels via model_channel_ids (see list_model_channels). Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: name, score, members."+ },+ {+ "slug": "PEEC_AI_MCP_GET_BRAND_PERCEPTION_COMPETITIVE_BREAKDOWN",+ "name": "Get brand perception competitive breakdown",+ "description": "The full competitive breakdown matrix: for every brand-perception attribute, the average prominence of each brand (the project's own brand and its competitors) across AI answers. score is 0-100 — higher means the brand tends to be mentioned earlier when AI talks about that attribute; display as-is, never multiply by 100. is_own marks the project's own brand. One row per attribute x brand cell; attributes are sorted by the own brand's score (strongest first) and brands by score within each attribute. limit/offset paginate ATTRIBUTES, not rows — each attribute contributes one row per brand, and totalCount is the total attribute count. Data is aggregated across the brand-perception runs of one industry and one target market (no date range) — pass industry to pick the industry; the target market is always that industry's most recently completed one and cannot be picked. The response reports the scope it used as industry and target_market, and lists the project's other industries under industries when it has more than one — read a different one by passing its name back as industry, and say which industry the numbers describe whenever that field is present. Optionally filter to specific engine channels via model_channel_ids (see list_model_channels). Returns columnar JSON: {columns, rows, rowCount, totalCount}. Columns: attribute, brand, score, is_own."+ },+ {+ "slug": "PEEC_AI_MCP_GET_BRAND_REPORT",+ "name": "Get brand report",+ "description": "Get a report on brand visibility, sentiment, and position across AI search engines.\n\nResults are aggregated for the entire date range by default. Use the \"date\", \"week\", or \"month\" dimension for time-bucketed breakdowns (daily, ISO week, or calendar month). When the range spans many days, prefer \"week\" or \"month\" over \"date\": coarser buckets return far fewer rows (180 days ≈ 26 weeks or 6 months vs. 180 daily rows), which avoids the row limit truncating the series and keeps the trend readable. Reach for \"date\" only when day-level granularity is essential and the range is short. Edge buckets may be partial: a range starting or ending mid-week/mid-month produces a first/last bucket that only aggregates the in-range days, so its values can look low — don't read that as a real dip.\n\nDimensions multiply the row count: rows = entities × dimension value combinations (e.g. 2 brands broken down by \"date\" over 180 days = 360 rows). The default limit of 100 will silently truncate such queries — raise \"limit\" to the row count you actually need. If rowCount equals limit, results were truncated; narrow the request (fewer entities, a shorter date range, fewer dimensions) or page through with \"offset\".\n\nReturns columnar JSON: {columns, rows, rowCount, total}. Each row is an array of values matching column order. Columns:\n- brand_id — the brand ID\n- brand_name — the brand name\n- visibility: 0–1 ratio — fraction of AI responses that mention this brand. 0.45 means 45% of conversations.\n- mention_count: number of times the brand was mentioned\n- share_of_voice: 0–1 ratio — brand's fraction of total mentions across all tracked brands\n- sentiment: 0–100 scale — how positively AI platforms describe the brand (most brands score 65–85)\n- position: average ranking when the brand appears (lower is better, 1 = mentioned first)\n- Raw aggregation fields (for custom calculations): visibility_count, visibility_total, sentiment_sum, sentiment_count, position_sum, position_count\n\nWhen dimensions are selected, rows also include the relevant dimension columns: prompt_id, model_id, model_channel_id, tag_id, topic_id, chat_id, date, week, month, country_code. model_channel_id, tag_id and topic_id are each followed by a model_channel_name / tag_name / topic_name column with the human-readable name.\n\nDimensions explained:\n- prompt_id: individual search queries/prompts\n- model_id: AI search engine (e.g. chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2) — deprecated, prefer model_channel_id\n- model_channel_id: stable engine channel (e.g. openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1) — survives model upgrades\n- tag_id: custom user-defined tags\n- topic_id: topic groupings\n- date: daily bucket (YYYY-MM-DD)\n- week: ISO week bucket, value is the Monday start (YYYY-MM-DD)\n- month: calendar month bucket, value is the first of the month (YYYY-MM-DD)\n- country_code: country (ISO 3166-1 alpha-2, e.g. \"US\", \"DE\")\n- chat_id: individual AI chat/conversation ID\n\nTwo filter inputs at different SQL stages — pick by intent:\n- filters (WHERE, pre-aggregation): shrinks BOTH numerator and denominator of ratio metrics. Putting brand_id here narrows everything to that brand — including share_of_voice's denominator — so SoV collapses to 1.0.\n- having (HAVING, post-aggregation): selects which aggregated rows are returned WITHOUT shrinking ratio-metric denominators. Use brand_id here for a single-brand report where SoV stays a real [0,1] fraction (X's share against competitors per dimension).\n\nMetric semantics:\n- visibility = visibility_count / visibility_total within each (brand × dimension) group. Per-row by construction; both filters and having behave intuitively.\n- share_of_voice = brand's mention_count / sum of mentions across all brands in the same (dimension) cell. Pre-aggregation filters narrow num+denom together; post-aggregation having does not.\n- When dimensions are requested, share_of_voice's denominator is per-dimension. Example: dimension prompt_id ⇒ share_of_voice for (brand X, prompt P) = X's mentions in P / all brands' mentions in P.\n\nSort results with order_by: array of {field, direction} entries. Direction defaults to desc. Sortable fields: visibility, visibility_count, mention_count, sentiment, position, share_of_voice, date, week, month. Multiple entries create a multi-key sort. Sorting by a time field (date, week or month) requires the matching dimension to be selected."+ },+ {+ "slug": "PEEC_AI_MCP_GET_CHAT",+ "name": "Get chat",+ "description": "Get the full content of a single chat (one AI engine's response to one prompt on one date). Returns:\n- messages: the user prompt and assistant response(s)\n- brands_mentioned: brands detected in the response with their position\n- sources: URLs the model retrieved, with citation counts and position\n- queries: search queries the model issued\n- products: product gallery entries extracted from the response\n- features: signal flags for special elements detected in the assistant response (SHOPPING, PRODUCT_COMPARISON, AD, MAP, WEB_SEARCH). Use list_chats with the `features` filter to query chats by these.\n- maps: local-business map cards (one per business pinned in a map widget) with { name, url } where `url` is the Google Maps directions deeplink for that business.\n- ads: paid ad placements rendered by the model. Each ad has { brand_name, url, id, ad_unit_type, ads_request_id, cards } where cards carry { title, body, image_url, target_url } and target_url is the clickout URL (with attribution UTM params).\n- prompt: { id }\n- model: { id } — deprecated, prefer model_channel\n- model_channel: { id } — stable engine channel id (e.g. \"openai-0\")\n\nUse list_chats to discover chat IDs for a project."+ },+ {+ "slug": "PEEC_AI_MCP_GET_CHATS_REPORT",+ "name": "Get chats report",+ "description": "Aggregate counts and rich-answer-feature shares over a project's chats for a date range. Answers questions like \"how many chats\", \"what share rendered a map / shopping / web-search / ad / comparison result\", and \"how many distinct prompts / engines / countries does tag X span\" — use it instead of paging through list_chats.\n\nGroup by one or more dimensions, or omit dimensions for a single total row over all matching chats.\n\nMetric columns:\n- chat_count — chats in the group (denominator of the feature percentages)\n- prompt_count / model_channel_count / country_count — distinct prompts / engine channels / countries the group spans (country_count excludes chats with no country)\n- shopping_count / shopping_percentage — answers with a shopping / product gallery\n- product_comparison_count / product_comparison_percentage — answers with a product comparison\n- ad_count / ad_percentage — answers with an ad\n- map_count / map_percentage — answers with a map / local-business result\n- web_search_count / web_search_percentage — answers with web-search sources\n\nPercentages are 0–1 ratios of chat_count (0.75 = 75%). Coverage counts collapse to 1 for the dimension you group by, so read them against dimensions you did NOT split on. Raise \"limit\" for time or high-cardinality breakdowns, to the row count you need rather than to the maximum.\n\nDimensions: prompt_id, model_id (chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2 — deprecated, prefer model_channel_id), model_channel_id (openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1), tag_id, topic_id, date / week / month, country_code, chat_id. tag_id / topic_id / model_channel_id rows also carry a matching *_name column.\n\nReturns {columns, rows, rowCount}; each row is an array of values aligned to columns."+ },+ {+ "slug": "PEEC_AI_MCP_GET_DOMAIN_REPORT",+ "name": "Get domain report",+ "description": "Get a report on source domain visibility and citations across AI search engines.\n\nResults are aggregated for the entire date range by default. Use the \"date\", \"week\", or \"month\" dimension for time-bucketed breakdowns (daily, ISO week, or calendar month). When the range spans many days, prefer \"week\" or \"month\" over \"date\": coarser buckets return far fewer rows (180 days ≈ 26 weeks or 6 months vs. 180 daily rows), which avoids the row limit truncating the series and keeps the trend readable. Reach for \"date\" only when day-level granularity is essential and the range is short. Edge buckets may be partial: a range starting or ending mid-week/mid-month produces a first/last bucket that only aggregates the in-range days, so its values can look low — don't read that as a real dip.\n\nDimensions multiply the row count: rows = domains × dimension value combinations (e.g. 5 domains broken down by \"date\" over 180 days = 900 rows). The default limit of 100 will silently truncate such queries — raise \"limit\" to the row count you actually need. If rowCount equals limit, results were truncated; narrow the request (fewer entities, a shorter date range, fewer dimensions) or page through with \"offset\".\n\nReturns columnar JSON: {columns, rows, rowCount}. Each row is an array of values matching column order. Columns:\n- domain: the source domain (e.g. \"example.com\")\n- classification: domain type — Corporate (official company sites), Editorial (news, blogs, magazines), Institutional (government, education, nonprofit), UGC (social media, forums, communities), Reference (encyclopedias, documentation), Competitor (direct competitors), You (the user's own domains), Other, or null\n- retrieved_percentage: 0–1 ratio — fraction of chats that included at least one URL from this domain. 0.30 means 30% of chats.\n- retrieval_rate: average number of URLs from this domain pulled per chat. Can exceed 1.0 — values above 1.0 mean multiple pages from the same domain are retrieved per conversation.\n- citation_rate: average number of inline citations when this domain is retrieved. Can exceed 1.0 — higher values indicate stronger content authority.\n- retrieved_chat_count: the canonical \"retrievals\" metric — number of distinct chats in which at least one URL from this domain was retrieved. When a user asks about \"retrievals\" for a domain, report THIS number; it matches the Domains table in the UI.\n- retrieval_count: URL-level count — total number of distinct URL retrievals from this domain across all chats (raw numerator of retrieval_rate). A single chat can retrieve several URLs, so this is always at least as large as retrieved_chat_count and is NOT the canonical \"retrievals\" number.\n- citation_count: total number of citations from this domain (raw count).\n- mentioned_brand_ids: array of brand IDs mentioned alongside URLs from this domain (may be empty)\n\nWhen dimensions are selected, rows also include the relevant dimension columns: prompt_id, model_id, model_channel_id, tag_id, topic_id, chat_id, date, week, month, country_code. model_channel_id, tag_id and topic_id are each followed by a model_channel_name / tag_name / topic_name column with the human-readable name.\n\nDimensions explained:\n- prompt_id: individual search queries/prompts\n- model_id: AI search engine (e.g. chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2) — deprecated, prefer model_channel_id\n- model_channel_id: stable engine channel (e.g. openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1) — survives model upgrades\n- tag_id: custom user-defined tags\n- topic_id: topic groupings\n- date: daily bucket (YYYY-MM-DD)\n- week: ISO week bucket, value is the Monday start (YYYY-MM-DD)\n- month: calendar month bucket, value is the first of the month (YYYY-MM-DD)\n- country_code: country (ISO 3166-1 alpha-2, e.g. \"US\", \"DE\")\n- chat_id: individual AI chat/conversation ID\n\nTwo filter inputs at different SQL stages — pick by intent:\n- filters (WHERE, pre-aggregation): population fields (model/country/prompt/tag/topic/chat) shrink both numerator and denominator (total_chat_count). Source-side fields (domain/url/classification) and per-row mentioned-brand predicates (mentioned_brand_id, mentioned_brand_count, gap) shrink only the source-row scope; total_chat_count is computed from a chat-level table that doesn't carry these columns.\n- having (HAVING, post-aggregation): selects which aggregated rows are returned WITHOUT shrinking ratio-metric denominators.\n\nMentioned-brand predicates and source-side fields exist in both — the WHERE form tests each source row pre-aggregation (shrinks numerators); the HAVING form tests the aggregated mentioned_brands union per domain (purely selective).\n\nNumeric predicates:\n- mentioned_brand_count: {field: \"mentioned_brand_count\", operator: \"gt\"|\"gte\"|\"lt\"|\"lte\", value: <number>} — filter by number of unique brands mentioned alongside the domain.\n- gap: {field: \"gap\", operator: \"gt\"|\"gte\"|\"lt\"|\"lte\", value: <number>} — gap analysis filter. Excludes domains where the project's own brand is mentioned, and filters by the number of competitor brands present. Example: {field: \"gap\", operator: \"gte\", value: 2} returns domains where the own brand is absent but at least 2 competitors are mentioned.\n\nMetric semantics:\n- retrieved_percentage and retrieval_rate use total_chat_count as the denominator. Filtering to a single domain via having still yields a meaningful retrieved_percentage < 1.0 — do not interpret it as 100%.\n- When dimensions are requested, total_chat_count is per-dimension. Example: dimension prompt_id ⇒ each row's total_chat_count is the chat count for that prompt, so retrieved_percentage is the per-prompt retrieval rate.\n- citation_rate = citation_count / retrieved_chat_count per row; it's independent of total_chat_count and naturally per-(domain × dimension).\n\nSort results with order_by: array of {field, direction} entries. Direction defaults to desc. Sortable fields: citation_rate, retrieval_count, citation_count, date, week, month. Sorting by a time field (date, week or month) requires the matching dimension to be selected. (retrieved_percentage and retrieval_rate are not sortable because they depend on totalChatCount fetched in a separate query.)"+ },+ {+ "slug": "PEEC_AI_MCP_GET_PRODUCT",+ "name": "Get product",+ "description": "Get one product's detailed metrics over a date range — the drill-down companion to list_products, which returns a thin row per product.\n\nReturns {data, primary_currency}, where data is null if the product is not in the project. data always includes:\n- id, name, brand, source (CATALOG or LLM), first_seen_at\n- visibility (0–1), win_rate (0–1), avg_position (rank, lower is better), avg_rating (mean 0–5 star rating across the product's AI mentions; null when none carried a rating), mention_count\n- *_delta for each metric above (visibility_delta, win_rate_delta, avg_position_delta, avg_rating_delta, mention_count_delta) — change vs the immediately preceding equal-length period; null when the previous period had nothing to compare against\n\nEverything else is opt-in via the 'fields' argument (default: none) to keep the response lean — list any of these to include them:\n- description, image_url\n- price_range / price_override — per-currency effective catalog range (min/max) and the raw overrides behind it\n- ai_price_map / ai_price_delta_map — per-currency median price across the product's AI mentions, and its change\n- variants — the product's live catalog variants (SKU-level), each with id, name, and a per-currency price_map (ISO-4217 → price; a variant carries a single entry). Capped at 50 with no pagination: a product with more than 50 variants returns only the first 50 by name.\n- four QFO (query fan-out) breakdowns of what surfaced this product, each up to 25 rows with distinct_chat_count (+ its previous-period value and delta): shopping_queries / shopping_query_terms (Google-Shopping fan-out queries and their n-grams) and fanout_queries / fanout_query_terms (web-search fan-out queries and their n-grams). Unrequested QFO breakdowns are skipped, not just omitted — no ClickHouse pass runs for them.\n\nVisibility divides by the product's relevant-prompt chats (prompts it is mentioned in or SODA-linked to), not all shopping chats. Metrics cover [start_date, end_date]; deltas compare against the equal-length period ending the day before start_date.\n\nWith merchant_ids, the headline metrics, price maps, and QFO breakdowns count only chats where the product is sold through one of those merchants (the visibility denominator stays unscoped) — pass one merchant id for that seller's rating, price, mentions, and the queries that surface its offers."+ },+ {+ "slug": "PEEC_AI_MCP_GET_PROJECT_PROFILE",+ "name": "Get project profile",+ "description": "Read a project's brand profile — the description, industry, brand-identity adjectives, target markets, audience distribution, and product/service list that Peec uses to generate prompt suggestions. Returns { profile } where profile may be null if the project hasn't been profiled yet. Call this before set_project_profile so you can show the user the current values."+ },+ {+ "slug": "PEEC_AI_MCP_GET_PROMPT_SUGGESTION_GENERATION",+ "name": "Get prompt suggestion generation",+ "description": "Read the authoritative status of a run returned by generate_prompt_suggestions. QUEUED and RUNNING are non-terminal; SUCCEEDED and FAILED are terminal. A successful run can produce zero suggestions. After success, call list_prompt_suggestions to review the current suggestions."+ },+ {+ "slug": "PEEC_AI_MCP_GET_SHOPPING_ATTRIBUTES",+ "name": "Get shopping attributes",+ "description": "Compare the qualitative characteristics and features that AI engines associate with a product (or the whole catalog) against competitors. These attributes are extracted from shopping answers and are qualitative — for the numeric shopping metrics (visibility, win rate, position) use get_shopping_summary or get_shopping_trend instead.\n\nscope=product compares one product (needs product_id); scope=overview compares the whole catalog. compare_by picks the grid columns: brand (default) or product (scope=product only). tab picks the value type.\n\nReturns a nested grid (not columnar): { tab, competitors[], groups[], total_groups }. Each competitor is a brand ({global_brand_id, name, domain, mentions}) or product ({product_id, name, brand_name, image_url, mentions}); every group's per-competitor arrays align to the competitors order. Group shape by tab:\n- characteristics: { dimension_id, name, total_mentions(+_delta), value_count, values: [{value, mentions(+_delta), competitor_mentions[]}] }\n- facts: { ..., value_type: BOOLEAN, unit, own: {true_count, false_count, unrecognized_count}, competitor_values[] }\n- dimensions: { ..., own: {min, max, average, median} | null, competitor_values: (stats | null)[] }\nDeltas are vs an explicit comparison window (previous_start_date/previous_end_date) or the equal-length window immediately before."+ },+ {+ "slug": "PEEC_AI_MCP_GET_SHOPPING_SUMMARY",+ "name": "Get shopping summary",+ "description": "Return catalog-wide shopping metrics over a date range — avg_visibility, avg_win_rate, and avg_position, each with a period-over-period delta — as a single aggregated row across the filtered scope. Deltas compare against previous_start_date/previous_end_date when given, else the auto-derived previous period. For a per-entity or per-time breakdown, use get_shopping_trend or list_shopping_performance."+ },+ {+ "slug": "PEEC_AI_MCP_GET_SHOPPING_TREND",+ "name": "Get shopping trend",+ "description": "Return a per-bucket shopping time series (visibility, win_rate, avg_position, sov) for specific products or global brands over a date range. Requires bucket (day/week/month) and exactly one of product_ids or brand_ids. Returns { entity_type, series[] }, one series per entity with a points array; has_data flags buckets with no underlying chats. For a single catalog-wide aggregate use get_shopping_summary; for a ranked table use list_shopping_performance."+ },+ {+ "slug": "PEEC_AI_MCP_GET_URL_CONTENT",+ "name": "Get url content",+ "description": "Fetches and returns the content of a URL for downstream analysis — the markdown Peec extracted from the page.\n\nReturns the exact content Peec's pipeline indexed, with no extra fetch. Works for any URL Peec has scraped for the project; you do not need to call get_url_report first.\n\nIf Peec has no record of the URL it returns 404.\n\nInput notes:\n- url is the full URL, copied verbatim. Trailing slashes and scheme variations change the resolved source ID.\n- max_length caps the returned content (default 100000 characters). If the stored content is longer, truncated=true — re-request with a higher max_length.\n\nReturned fields:\n- url, title, domain, channel_title: page metadata\n- classification: domain-level classification\n- url_classification: page-level classification (HOMEPAGE, LISTICLE, COMPARISON, ...)\n- content: the page's markdown content. null when the URL is tracked but scraping hasn't completed yet (can take up to 24h).\n- content_length: original character length before truncation (0 when content is null)\n- truncated: true if content was truncated to max_length\n- content_updated_at: ISO timestamp of last scrape, or null if not yet scraped"+ },+ {+ "slug": "PEEC_AI_MCP_GET_URL_REPORT",+ "name": "Get url report",+ "description": "Get a report on source URL visibility and citations across AI search engines.\n\nResults are aggregated for the entire date range by default. Use the \"date\", \"week\", or \"month\" dimension for time-bucketed breakdowns (daily, ISO week, or calendar month). When the range spans many days, prefer \"week\" or \"month\" over \"date\": coarser buckets return far fewer rows (180 days ≈ 26 weeks or 6 months vs. 180 daily rows), which avoids the row limit truncating the series and keeps the trend readable. Reach for \"date\" only when day-level granularity is essential and the range is short. Edge buckets may be partial: a range starting or ending mid-week/mid-month produces a first/last bucket that only aggregates the in-range days, so its values can look low — don't read that as a real dip.\n\nDimensions multiply the row count: rows = URLs × dimension value combinations (e.g. 5 URLs broken down by \"date\" over 180 days = 900 rows). The default limit of 100 will silently truncate such queries — raise \"limit\" to the row count you actually need. If rowCount equals limit, results were truncated; narrow the request (fewer entities, a shorter date range, fewer dimensions) or page through with \"offset\".\n\nReturns columnar JSON: {columns, rows, rowCount}. Each row is an array of values matching column order. Columns:\n- url: the full source URL (e.g. \"https://example.com/page\")\n- classification: page type — Homepage, Category Page, Product Page, Listicle (list-structured articles), Comparison (product/service comparisons), Profile (directory entries like G2 or Yelp), Alternative (alternatives-to articles), Discussion (forums, comment threads), How-To Guide, Article (general editorial content), Other, or null\n- title: page title or null\n- channel_title: channel or author name (e.g. YouTube channel, subreddit) or null\n- citation_count: total number of explicit citations across all chats\n- retrieval_count: total number of distinct chats that retrieved this URL, regardless of whether it was cited\n- citation_rate: average number of inline citations per chat when this URL is retrieved. Can exceed 1.0 — higher values indicate more authoritative content.\n- mentioned_brand_ids: array of brand IDs mentioned alongside this URL (may be empty)\n\nWhen dimensions are selected, rows also include the relevant dimension columns: prompt_id, model_id, model_channel_id, tag_id, topic_id, chat_id, date, week, month, country_code. model_channel_id, tag_id and topic_id are each followed by a model_channel_name / tag_name / topic_name column with the human-readable name.\n\nDimensions explained:\n- prompt_id: individual search queries/prompts\n- model_id: AI search engine (e.g. chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2) — deprecated, prefer model_channel_id\n- model_channel_id: stable engine channel (e.g. openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1) — survives model upgrades\n- tag_id: custom user-defined tags\n- topic_id: topic groupings\n- date: daily bucket (YYYY-MM-DD)\n- week: ISO week bucket, value is the Monday start (YYYY-MM-DD)\n- month: calendar month bucket, value is the first of the month (YYYY-MM-DD)\n- country_code: country (ISO 3166-1 alpha-2, e.g. \"US\", \"DE\")\n- chat_id: individual AI chat/conversation ID\n\nTwo filter inputs at different SQL stages — pick by intent:\n- filters (WHERE, pre-aggregation): population fields shrink the chat scope; source-side and per-row mentioned-brand predicates (mentioned_brand_id, mentioned_brand_count, gap) shrink the source-row scope.\n- having (HAVING, post-aggregation): selects which aggregated URL rows are returned.\n\nShared fields exist on both — the WHERE form tests each source row pre-aggregation (shrinks numerators); the HAVING form tests the aggregated mentioned_brands union per URL (purely selective). Use filters to prune source rows early; use having to combine with mentioned_brand_*/gap expressions on the grouped union.\n\nNumeric predicates:\n- mentioned_brand_count: {field: \"mentioned_brand_count\", operator: \"gt\"|\"gte\"|\"lt\"|\"lte\", value: <number>} — filter by number of unique brands mentioned alongside the URL.\n- gap: {field: \"gap\", operator: \"gt\"|\"gte\"|\"lt\"|\"lte\", value: <number>} — gap analysis filter. Excludes URLs where the project's own brand is mentioned, and filters by the number of competitor brands present. Example: {field: \"gap\", operator: \"gte\", value: 2} returns URLs where the own brand is absent but at least 2 competitors are mentioned.\n\nMetric semantics:\n- citation_rate = citation_count / retrieval_count, both aggregated per (url × dimension) row from the same filtered group. There's no cross-row denominator, so neither filters nor having can collapse the metric — it stays meaningful even when narrowing to a single url or domain.\n- retrieval_count is the count of distinct chats containing this URL within the filtered + dimension-grouped scope. Compare across rows to gauge a URL's relative retrieval strength. Do not divide retrieval_count by an external chat-count to compute a \"retrieval percentage\" — use the domain report for that aggregate.\n\nSort results with order_by: array of {field, direction} entries. Direction defaults to desc. Sortable fields: retrieval_count, retrievals, citation_count, citation_rate, date, week, month. Multiple entries create a multi-key sort. Sorting by a time field (date, week or month) requires the matching dimension to be selected."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_BOTS",+ "name": "List bots",+ "description": "List all known AI crawler/agent bots that visit the site (e.g. GPTBot, ClaudeBot, PerplexityBot). Each bot has an ID, provider, and type.\n\nBot types:\n- training: crawlers that collect data for model training (e.g. GPTBot, ClaudeBot)\n- search: bots that retrieve content for AI-powered search (e.g. PerplexityBot)\n- userQuery: bots triggered by real-time user queries\n- other: miscellaneous bots\n\nUse the returned bot IDs with get_agent_visits to filter visit counts by specific bots.\n\nReturns: {data: [{id, provider, type}]}"+ },+ {+ "slug": "PEEC_AI_MCP_LIST_BRAND_PERCEPTION_ATTRIBUTE_CLUSTERS",+ "name": "List brand perception attribute clusters",+ "description": "The editable attribute taxonomy behind brand perception: every cluster with its id, label and the raw extracted attributes grouped under it. Use this to resolve the cluster_id values edit_brand_perception_attribute_clusters needs, and to see attributes that are grouped wrongly. Prefer get_brand_perception_brand_attributes when the question is about scores — this tool carries no scores, but it does list clusters that have no score yet. unassigned holds extracted attributes that belong to no cluster (not paginated). is_custom marks a cluster a person added by hand. Returns columnar JSON: {columns, rows, rowCount, totalCount, unassigned}. Columns: cluster_id, name, is_custom, members."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_BRANDS",+ "name": "List brands",+ "description": "List brands tracked in a project — includes the user's own brand and competitors. Use this tool to resolve brand names to IDs before filtering reports (brand_id filter), and to label brand IDs from report output with their human-readable names before presenting results. Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: id, name, domains, aliases, is_own. aliases are alternate names the brand is matched under. is_own indicates which brand belongs to the user. These are the brands a project tracks for visibility reporting — separate from list_global_brands, which searches the global product catalog used when creating products."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_CATEGORIES",+ "name": "List categories",+ "description": "List a project's product categories. Categories are an org-wide tree (e.g. Footwear > Shoes > Running Shoes); each row carries its full `path` and its `parent_id`, so the flat list rebuilds the tree. Use a row's `id` in the `category_ids` of create_products or update_products to categorize products. Returns columnar JSON: {columns, rows, rowCount, totalCount}. Columns: id, name, path, parent_id."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_CHATS",+ "name": "List chats",+ "description": "List chats (individual AI responses) for a project over a date range. Each chat is produced by running one prompt against one AI engine on a given date.\n\nFilters:\n- brand_id: only chats that mentioned the given brand\n- prompt_id: only chats produced by the given prompt\n- model_id: only chats from the given AI engine (chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2) — deprecated, prefer model_channel_id\n- model_channel_id: only chats from the given engine channel (openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1)\n- features: only chats that contain all of the given features (SHOPPING, PRODUCT_COMPARISON, AD, MAP, WEB_SEARCH)\n\nIf both model_id and model_channel_id are provided, model_channel_id takes precedence and model_id is ignored.\n\nExcludes chats whose prompt has been deleted or archived. Set include_archived_prompts=true to include chats for archived prompts (e.g. historical lookback for a prompt that is no longer tracked). Chats for deleted prompts are always excluded.\n\nUse the returned chat IDs with get_chat to retrieve full message content, sources, and brand mentions.\n\nReturns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: id, prompt_id, model_id, model_channel_id, date, features."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_DOMAIN_CLASSIFICATIONS",+ "name": "List domain classifications",+ "description": "List the custom domain classifications defined for a project. These complement the built-in classifications (Corporate, Competitor, Editorial, Institutional, Other, Reference, UGC, You, Related) and can be assigned to domains via assign_domain_classification. Returns columnar JSON: {columns, rows, rowCount, totalCount}. Columns: name, color."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_GLOBAL_BRANDS",+ "name": "List global brands",+ "description": "Search Peec's global brand catalog — the shared registry of real-world brands (e.g. Nike, Apple) that products attach to. Use it to find the global_brand_id for a brand before creating products with create_products. This is NOT the same as list_brands: list_brands returns the brands you track inside a project (your own brand plus the competitors you monitor for AI visibility), whereas list_global_brands searches every brand in Peec's catalog. The two have different ids and are not interchangeable. Primarily used with `search` to look up a brand by name (matches names and aliases). Pass ownership ('own', 'competitor', or 'all') instead to list the project's shopping brands by global_brand_id — the ids shopping product filters take — ranked by mentions, with their mention_count and is_own. Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matches ignoring limit/offset. Columns: id, name, domain, description, mention_count, is_own."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_MERCHANTS",+ "name": "List merchants",+ "description": "List the merchants (sellers, e.g. Amazon / eBay) whose product offers surfaced in AI answers, ranked over a date range. Each row carries mention_count, share_of_voice (0–1: this merchant's mentions over all merchants' mentions in the filtered population), win_rate (0–1 buy-box rate: position-1 mentions over all mentions), avg_position (rank, lower is better), avg_rating (mean 0–5 star rating; null when unrated), and a *_delta for each vs the previous window.\n\nScope the population with category_ids or product_ids for per-category or per-product seller breakdowns — with product_ids, share_of_voice is the share among that product's sellers. merchant_ids instead keeps only those merchants' rows without shrinking the share_of_voice denominator (e.g. to compare two known sellers). Pass a merchant_id from here to get_product's merchant_ids for that seller's per-product rating and price.\n\nMerchants with no current-window mentions are omitted."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_MODEL_CHANNELS",+ "name": "List model channels",+ "description": "List the AI engine channels tracked by Peec. A model channel is a stable identifier for an AI engine (e.g. \"openai-0\" = ChatGPT UI) that persists even as the underlying model is upgraded — use it to filter or break down reports by engine without worrying about model version changes. Use this tool to resolve channel descriptions (e.g. \"ChatGPT UI\", \"Perplexity\") to channel IDs before filtering reports (model_channel_id filter), and to label channel IDs from report output before presenting results. The current_model_id column gives the model ID currently active in the channel — pass this as model_id where reports require it. is_active indicates whether the channel is enabled for this project — inactive channels return empty data. unsupported_country_codes lists country codes that cannot be used with this channel (chats requested for those countries are not created). Returns columnar JSON: {columns, rows, rowCount}. Columns: id, description, current_model_id, is_active, unsupported_country_codes."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_MODELS",+ "name": "List models",+ "description": "Deprecated — prefer list_model_channels, which returns stable channel IDs that survive model upgrades. List AI engines (models) tracked by Peec. Use this tool to resolve model names (e.g., \"ChatGPT\", \"Perplexity\", \"Gemini\") to IDs before filtering reports (model_id filter/dimension), and to label model IDs from report output with their human-readable names before presenting results. Match user-supplied names against the name column; the id column is the canonical string to pass back as model_id. is_active indicates whether the model is enabled for this project — inactive models will return empty data in reports. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, name, is_active."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_PRODUCTS",+ "name": "List products",+ "description": "List a project's products with headline metrics over a date range, filtered by the shopping filter pack.\n\nReturns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: id, name, brand, source (CATALOG = claimed/uploaded, LLM = AI-detected), image_url, price_range (per-currency effective range), categories (category ids), mention_count, win_count, avg_position, avg_rating (mean 0–5 star rating across the product's AI mentions; null when none carried a rating), visibility, share_of_voice. Metrics cover [start_date, end_date].\n\nFor catalog cleanup, dedup, or category/name fixes, filter to source=CATALOG — LLM products aren't part of the user's catalog."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_PROJECTS",+ "name": "List projects",+ "description": "List active projects the authenticated user has access to. By default, only projects with an active status (CUSTOMER, PITCH, TRIAL, ONBOARDING, API_PARTNER) are returned — this is what you want in almost every case. Only set include_inactive to true if the user asked for a specific project that wasn't in the active list; do not set it preemptively. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, name, status, language_code (ISO 639-1, the language the project's prompts run in). The id is used as project_id in other tools. Call this first to discover available projects."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_PROMPTS",+ "name": "List prompts",+ "description": "List prompts (conversational questions tracked daily across AI engines) in a project. Supports filtering by topic_id, tag_id, and is_archived. Returns only active prompts by default — pass is_archived=true to list archived prompts instead (e.g. when a prompt_id from older report output isn't found among the active ones). Use the `search` parameter to resolve prompt text to IDs (fuzzy, ranked by relevance) before filtering reports (prompt_id filter/dimension), and use this tool to label prompt IDs from report output with their actual text before presenting results. Search scans at most the 20000 most recent prompts and sets `search_truncated: true` in the result when the project exceeds that. Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: id, text, tag_ids (array of tag ID strings), tags (array of tag names, aligned with tag_ids), topic_id (string or null), topic (topic name, string or null), volume (relative search volume bucket: \"very low\" | \"low\" | \"medium\" | \"high\" | \"very high\", or null when unavailable — describe volume to users using the bucket label), is_archived (boolean — true when the prompt is no longer tracked daily), created_at (ISO 8601 date string, e.g. \"2025-09-22\", when the prompt was created — use to identify prompts older than a given age). When presenting prompts to users, use the name columns (text, topic, tags) — the id columns exist only for filtering. Pass `fields` to return only the columns you need."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_PROMPT_SUGGESTIONS",+ "name": "List prompt suggestions",+ "description": "List a project's prompt suggestions — prompts generated by the Prompt Builder and awaiting review, which are not tracked and produce no data until accepted. Accept or reject them with finalize_prompt_suggestions. Their ids are prefixed `pr_`, and a suggestion keeps that id when accepted, so the accepted prompt is findable under the same id with list_prompts. Filter by topic_id to review one topic at a time. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, text, topic_id, tag_ids (array of tag ID strings — resolve names with list_tags), country (the market the suggestion was generated for), volume (relative search volume, or null when unavailable). Pass `fields` to return only the columns you need."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_SEARCH_QUERIES",+ "name": "List search queries",+ "description": "List the general web-search queries an AI engine fanned out to while answering prompts in a project over a date range — the text sub-queries it sent to a search index, NOT product/shopping lookups (use list_shopping_queries for those). Each row represents one web-search sub-query the engine issued for a given chat.\n\nFilters:\n- prompt_id: only queries from chats produced by this prompt\n- chat_id: only queries from this chat\n- model_id: only queries from this AI engine (chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2)\n- model_channel_id: only queries from this channel (openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1)\n- topic_id: only queries from chats whose prompt belongs to this topic\n- tag_id: only queries from chats whose prompt carries this tag\n\nUse get_chat with a returned chat_id to inspect the full AI response that produced these sub-queries.\n\nReturns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: prompt_id, chat_id, model_id, model_channel_id, date, query_index, query_text."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_SHOPPING_DEMAND",+ "name": "List shopping demand",+ "description": "Rank the query terms that drive shopping demand by how many distinct chats they appear in, with a trend vs a comparison window. Returns an aggregated ranking, not per-chat rows — for the individual queries in each chat use list_shopping_queries or list_search_queries instead.\n\nkind selects what is ranked:\n- shopping_query: product fan-out queries\n- fanout_query: web-search fan-out queries\n- query_term: n-grams across shopping queries (n sets the width, default 2 = bigrams)\n\nmode selects how the ranking is ordered:\n- top: highest distinct-chat count now\n- trending: biggest gainers vs the comparison window\n- losing: biggest decliners vs the comparison window\n- new: appeared in this window only\n\nColumns: kind, text, distinct_chat_count, distinct_chat_count_previous (count in the comparison window), delta (change vs the comparison window)."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_SHOPPING_PERFORMANCE",+ "name": "List shopping performance",+ "description": "List products or categories (via entity_type) ranked by shopping performance over a date range. Performance columns are visibility, win_rate, avg_position, and appearances, each with a period-over-period delta. order_by picks the ranking metric (visibility, win_rate, or appearances); mode selects which entities to surface: top = highest now, trending = biggest gainers vs the previous period, losing = biggest decliners."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_SHOPPING_QUERIES",+ "name": "List shopping queries",+ "description": "List the product/shopping queries an AI engine fanned out to while answering prompts in a project over a date range. Each row represents one shopping sub-query and the distinct products returned for it in a given chat.\n\nFilters:\n- prompt_id: only queries from chats produced by this prompt\n- chat_id: only queries from this chat\n- model_id: only queries from this AI engine (chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-3.1-flash-lite-search, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, deepseek-v4-pro, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4, grok-4.3, grok-4.6, qwen-3-6-plus, qwen-3-7-plus, amazon-rufus-scraper, mistral-small-4, mistral-medium-3-5, muse-spark-1.2)\n- model_channel_id: only queries from this channel (openai-0, openai-1, qwen-0, openai-2, perplexity-0, perplexity-1, google-0, google-1, google-2, google-3, google-4, anthropic-0, anthropic-1, deepseek-0, meta-0, meta-1, xai-0, xai-1, microsoft-0, amazon-0, mistral-0, mistral-1)\n- topic_id: only queries from chats whose prompt belongs to this topic\n- tag_id: only queries from chats whose prompt carries this tag\n\nUse get_chat with a returned chat_id to inspect the full AI response that produced these sub-queries.\n\nReturns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: prompt_id, chat_id, model_id, model_channel_id, date, query_text, products (array of product names)."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_TAG_GROUPS",+ "name": "List tag groups",+ "description": "List the user-defined tag groups in a project, each with its shared color and tag count. Use this to discover group names before filtering list_tags by group or before renaming/deleting a group. System groups (branding/intentType) are not included — they appear on tags via list_tags."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_TAGS",+ "name": "List tags",+ "description": "List tags in a project. Tags are cross-cutting labels that can be assigned to any prompt. Use this tool to resolve tag names to IDs before filtering (tag_id filter/dimension, list_prompts), and to label tag IDs from report output with their human-readable names before presenting results. Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: id, name, is_system, group. The `group` column holds a system group for system tags or the user-defined group name for user tags (null if ungrouped). Pass `group` to filter to a single user-defined group; use list_tag_groups to discover group names. System tags (is_system=true) are maintained by Peec and auto-assigned to every prompt by its branding/intent classification — they cannot be created, edited, or deleted, but they can be assigned to prompts. A system tag's group is \"branding\" (branded / non-branded) or \"intentType\" (informational / commercial / transactional); these are mutually exclusive: a prompt carries exactly one tag per group, so assigning a system tag (via update_prompts) overwrites whichever tag that prompt already had in that group rather than adding a second. Filter on the existing system tags — never create your own branded/intent tags."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_TOPICS",+ "name": "List topics",+ "description": "List topics in a project. Topics are folder-like groupings — each prompt belongs to exactly one topic. Use this tool to resolve topic names to IDs before filtering (topic_id filter/dimension, list_prompts), and to label topic IDs from report output with their human-readable names before presenting results. Returns the project's confirmed topics; pass include_suggested=true to also return topics still awaiting confirmation, which carry no prompts yet. Returns columnar JSON: {columns, rows, rowCount, totalCount}. rowCount is the rows in this page; totalCount is the total matching records ignoring limit/offset. Columns: id, name, is_suggested (boolean — always false unless include_suggested is set)."+ },+ {+ "slug": "PEEC_AI_MCP_LIST_URL_CLASSIFICATIONS",+ "name": "List url classifications",+ "description": "List the custom URL classifications defined for a project. These complement the built-in classifications (Homepage, Category Page, Product Page, Listicle, Comparison, Profile, Alternative, Discussion, How-To Guide, Article, Other) and can be assigned to URLs via assign_url_classification. Returns columnar JSON: {columns, rows, rowCount, totalCount}. Columns: name, color."+ },+ {+ "slug": "PEEC_AI_MCP_READ_DOC",+ "name": "Read doc",+ "description": "Read the full markdown content of a single Peec documentation page. Pass the path returned by search_docs (e.g. 'metrics/brand-metrics/visibility'). Answer strictly from the returned content — never invent product behaviour, metric definitions, limits, or feature claims. Returns {title, path, url, content, videos}, where videos lists the page's YouTube explainer videos as {videoId, title} (pages may also carry [Watch \"…\"](https://youtu.be/…) links in the content). When a returned video is relevant to what the user asked — a walkthrough or explainer of the feature, metric, or workflow in question — PREFER embedding it over linking to it or describing it in text: put [youtube:<videoId>] on its own line at the point in your reply where the video belongs, and it renders inline. Copy the videoId exactly from this tool's result — never guess or invent one, and never embed a video that did not come from this tool. Don't embed the same video twice, don't pad the answer with tangential videos, and skip embedding only when no returned video is relevant. No project context or auth required."+ },+ {+ "slug": "PEEC_AI_MCP_SEARCH_DOCS",+ "name": "Search docs",+ "description": "Search the Peec product documentation (https://docs.peec.ai) and return the most relevant pages. Use this for any question about how Peec works — what a metric means, how a feature behaves, setup steps, plan/credit rules, or 'how do I…' — then call read_doc on the best result to read it in full before answering. Returns columnar JSON {columns, rows, rowCount}. Columns: title, path, url, snippet. Pass the returned path to read_doc. No project context or auth required."+ },+ {+ "slug": "PEEC_AI_MCP_SET_PROJECT_PROFILE",+ "name": "Set project profile",+ "description": "Set the project's own brand-identity profile — its industry, target audience, tone, and similar descriptive fields. This is the project's own identity, not the competitor/monitored brand entities managed by update_brand/update_brands. All fields are required — the whole profile is overwritten, so first call get_project_profile, merge your changes into the existing values, then send the complete profile here. Saving triggers a background refresh of prompt suggestions. Confirm changes with the user before calling. Audience distribution percentages must sum to 100. The project's display name is not part of the profile and cannot be changed via this tool. Returns { success: true } once the profile is saved."+ },+ {+ "slug": "PEEC_AI_MCP_UNARCHIVE_PROMPTS",+ "name": "Unarchive prompts",+ "description": "Unarchive up to 50 prompts (sets is_archived = false), reactivating them so they resume running. Subject to the project's active-prompt plan limit — prompts that would exceed it are rejected. Returns a count of reactivated prompts plus any skipped (not found) or rejected (plan_limit) items. Confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_UNASSIGN_DOMAIN_CLASSIFICATION",+ "name": "Unassign domain classification",+ "description": "Clear the classification override on a whole domain (operates on a domain, e.g. \"example.com\" — for a single URL use unassign_url_classification), restoring the heuristic classification. Does NOT delete the custom classification entity itself (use delete_domain_classification for that). Confirm with the user before calling. Returns { success: true } once the override is cleared."+ },+ {+ "slug": "PEEC_AI_MCP_UNASSIGN_URL_CLASSIFICATION",+ "name": "Unassign url classification",+ "description": "Clear the classification override on a single URL (operates on one full URL — for a whole domain use unassign_domain_classification), restoring the heuristic classification. Does NOT delete the custom classification entity itself (use delete_url_classification for that). Confirm with the user before calling. Returns { success: true } once the override is cleared."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_BRANDS",+ "name": "Update brands",+ "description": "Update up to 50 brands in one call (name, regex, aliases, domains, color per item). Changes to name/regex/aliases trigger background metric recalculation per brand; updates during an ongoing recalculation are rejected. Returns a count of updated brands plus any skipped/rejected items (successful items are not echoed back)."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_CATEGORIES",+ "name": "Update categories",+ "description": "Rename and/or move categories by id (use list_categories to resolve ids). Each item sets name (rename it), parent_id (move it under that category, or null to promote it to the top level), or both.\n\nReturns per-item results { updated, rejected } — the batch never fails as a whole. Rejection reasons: not_found, name_conflict (a sibling already has that name), invalid_move (would nest a category inside itself).\n\nConfirm with the user before calling — this mutates project data."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_PRODUCTS",+ "name": "Update products",+ "description": "Update up to 1000 products by id in one call (use list_products to resolve ids). Per item, set any of: name (unique within the brand), description, image_url, price_override (per-currency; replaces all overrides, {} clears them), category_ids (replaces the product's categories, [] uncategorizes it; use list_categories to find category ids). Omitted fields are left unchanged.\n\nReturns per-item results { updated, skipped, rejected } — the batch never fails as a whole. An item with nothing to apply is skipped (not_found / no_changes / duplicate_id); an unsatisfiable change (name conflict, unknown category) is rejected.\n\nConfirm with the user before calling — this mutates project data."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_PROMPTS",+ "name": "Update prompts",+ "description": "Update the topic and/or tags of up to 50 prompts in one call. Per item, pass tag_ids to fully replace the prompt's tag set, or topic_id = null to detach its topic. Topic and tag ids must already exist. Returns a count of updated prompts plus any skipped/rejected items (successful items are not echoed back)."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_PROMPT_SUGGESTIONS",+ "name": "Update prompt suggestions",+ "description": "Edit up to 50 pending prompt suggestions from list_prompt_suggestions before finalizing: rewrite the text and/or replace the tag set per item. Prefer this over rejecting and regenerating when a suggestion is close but not quite right. Editing keeps a suggestion pending — accept it with finalize_prompt_suggestions to create the tracked prompt. tag_ids fully replaces the item's tags and must be existing tag ids from list_tags; system tags keep at most one per group, the last one passed wins. Returns a count of updated suggestions plus any skipped/rejected items (successful items are not echoed back)."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_TAG_GROUPS",+ "name": "Update tag groups",+ "description": "Rename and/or recolor up to 50 user-defined tag groups in one call. The change applies to every tag in each group. Per group, provide a new name, a new color, or both (a group with neither is rejected). Returns each updated group with its affected tag count, plus any skipped (not found) or rejected items. Confirm with the user before calling."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_TAGS",+ "name": "Update tags",+ "description": "Update up to 50 tags in one call (name, color, and/or group per item). Set a tag's group to move it into a group (inherits the group's color), `null` to ungroup, or omit to leave unchanged. Returns a count of updated tags plus any skipped/rejected items (successful items are not echoed back); system tags are skipped."+ },+ {+ "slug": "PEEC_AI_MCP_UPDATE_TOPICS",+ "name": "Update topics",+ "description": "Rename up to 50 topics in one call. Returns a count of updated topics plus any skipped/rejected items (successful items are not echoed back)."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "peec_ai_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "default"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "peerdom","name": "Peerdom",@@ -265085,6 +275163,96 @@}]},+ {+ "slug": "plaid_mcp",+ "name": "Plaid MCP",+ "logo": "https://logos.composio.dev/api/plaid_mcp",+ "description": "Plaid MCP gives authorized teams read-only Production diagnostics and analytics for Items, Link conversion, usage metrics, API volumes, and team discovery.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 5,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "PLAID_MCP_PLAID_DEBUG_ITEM",+ "name": "Plaid debug item",+ "description": "Diagnose a Plaid item by retrieving its state information.\nThis tool provides comprehensive information about why an item may not be working properly.\n\n<when_to_use>\nUse this tool when you need to diagnose why an item is not functioning as expected\n</when_to_use>\n\n<description>\nIn the response, you will see the following information:\n1. Item State:\n- \"Never extracted\": no extraction has been attempted for this item yet\n- \"Successful\": The most recent extraction was successful\n- \"Retrying\": The most recent extraction encountered a temporary issue and is being retried\n- \"Needs user attention\": The item requires user input and client access is not permitted\n- \"Needs user attention (with access)\": The item requires user input but client access is permitted\n\n2. Item Consent State:\n- Boolean indicating whether the item has active user consent\n- If an item is not consented, it cannot perform extractions or updates\n\n3. Item Deleted At:\n- If set to a non-zero value, indicates when the item was deleted\n- Deleted items cannot retrieve data, and cannot be patched as it is requested by the end users\n- If the item is not deleted yet, the response will be \"not available\"\n\n4. Known Issues:\n- Includes description and status of any known issues affecting the item\n- May provide insights into ongoing problems with the connection\n\nWhen diagnosing an item, follow this sequence:\n- First, check if the item is deleted. If yes, the item cannot work properly.\n- Second, if the item is not deleted but lacks active consent, it cannot function properly.\n- Third, if the item is not deleted:\n\t* Check item state. If it indicates the item needs user attention, the item requires manual intervention.\n\t* Note any known issues as supplementary information, though these are usually not the primary cause of problems.\n\t- If all diagnostics look normal but the user still reports issues, advise them to contact Plaid support.\n</description>\n\n<important> \n- If an item is deleted, it is not working properly. It is not patchable, you should suggest the user to create a new item. \n- If an item is missing active consent, it is not working properly. You should suggest the user to use Update Mode to reauthorize the item.\n- If an item state indicates it needs user attention, the user should use Update Mode to reauthorize the item.\n- If running into error \"the item does not belong to the team\", it means the item is not associated with the team. You must inform the user that the \n item does not belong to their selected team. You may ask if they would like to try other teams associated with their account, but do not automatically attempt other teams.\n- If an item cannot be found, it's possible the item is not in the Production environment. When explaining the error, inform the user that this is a possible reason for the error.\n</important>\n"+ },+ {+ "slug": "PLAID_MCP_PLAID_GET_LINK_ANALYTICS",+ "name": "Plaid get link analytics",+ "description": "Retrieves Plaid Link analytics data for analyzing user conversion and error rates.\n\n<when_to_use>\nUse this tool when you need to:\n- Analyze Link conversion funnel metrics\n- Track user progression through the Link flow\n- Monitor error rates over time\n- Evaluate Link performance and user experience\n\nSome common use cases:\n- Monitoring Link conversion rates and identifying drop-offs\n- Analyzing conversion trends over specific time periods\n- Tracking error patterns and frequency (both by type and total via CountEntities)\n- Generating comprehensive Link performance reports\n- Comparing performance across different stages of the Link flow\n</when_to_use>\n\n<description>\nThe response includes three main components:\n1. Funnel Data (funnel):\n Tracks user progression through key Link stages with counts:\n - countAtLinkOpen: Number of users who opened Link\n - countAtSelectInstitution: Number who selected an institution\n - countAtHandoff: Number who completed the handoff process\n2. Conversion Over Time (conversionOverTime):\n Time series data showing conversion trends with:\n - start: Timestamp marking the start of the series\n - series: Array of named data series, where each contains:\n\t * name: Identifier for the conversion metric\n\t * data: Array of counts, can contain null values\n3. Errors Over Time (errorsOverTime):\n Time series tracking error occurrences with:\n - start: Timestamp marking the start of the series\n - series: Array of named data series, where each contains:\n\t * name: Error type identifier (includes \"CountEntities\" series for total errors across all types)\n\t * data: Array of error counts\n</description>\n\n<important>\n- If user does not provide a date range, please ask them to provide one. You could ask if they want \n to see the data for the last 30 days and you could use the current date as the end date. Note that\n the earliest date available for Link analytics data is September 1, 2023 (9/1/2023).\n</important>\n"+ },+ {+ "slug": "PLAID_MCP_PLAID_GET_TOOLS_INTRODUCTION",+ "name": "Plaid get tools introduction",+ "description": "Returns a list of all available tools with a brief introduction for each.\nUse this tool when users ask questions like \"What is this Plaid MCP Server?\" or \"What tools are available?\". \n\nYour response should follow this format:\n<quote>\nThis is an official Plaid MCP Server made by Plaid. It provides the following functionalities:\t\t\n * <tool_name> - <tool_description>\n * <tool_name> - <tool_description>\n ...\n</quote>"+ },+ {+ "slug": "PLAID_MCP_PLAID_GET_USAGES",+ "name": "Plaid get usages",+ "description": "Retrieves usage metrics for Plaid products and services.\n \n<when_to_use>\nUse this tool when you need to:\n- Get usage data for specific metrics over a time period\n- Track product usage and consumption\n- Monitor API request volumes\n- Generate usage reports for billing purposes\n</when_to_use>\n\n<details>\nThe data shows how many times each Plaid product was used within the specified\ndate range for certain metrics, with results aggregated by day. Common metrics\ninclude number of API calls, authentication requests, and other product-specific\nusage counts.\n</details>\n\n<product_mapping>\nThe key is the product name, and the value is the list of metric types corresponding to that product.\n\n- Auth: [\"auth-request\", \"auth-unverified-request\"]\n- Balance: \"balance-request\"\n- Identity: [\"identity-request\", \"identity-match-request\"]\n- Transactions: [\"transactions\", \"transactions-add\", \"transactions-remove\", \"transactions-active\", \"transactions-refresh\"]\n- Investments: [\"investments-h-add\", \"investments-h\", \"investments-h-remove\", \"investments-h-active\", \"investments-t-add\", \"investments-t\", \"investments-t-remove\", \"investments-t-active\"]\n- Investments Move: \"investments-auth-request\"\n- Liabilities: [\"liabilities-add\", \"liabilities-remove\", \"liabilities-active\", \"liabilities\"]\n- Assets: [\"assets-add\", \"assets-pdf-request\", \"assets-refresh\", \"assets-refresh-monthly\", \"assets-audit-request\", \"assets-history-request\"]\n- Payments: \"payment_initiation-initd\"\n- Enrich: \"enriched-transaction\"\n- Signal: \"momo-frs-eval-request\"\n- Income: [\"income-bank-request\", \"income-bank-refresh\", \"income-payroll-request\", \"income-payroll-refresh\", \"income-document-request\", \"income-document-parsing\", \"income-doc-bank-statemnt\", \"income-document-fraud\"]\n- Statements: \"statements-single-doc\"\n- Identity Verification: [\"idv-base\", \"idv-lightning-group-1\", \"idv-lightning-group-2\", \"idv-lightning-group-3\", \"idv-document\", \"idv-selfie-check\"]\n- Consumer Report: [\"cra-bank-income-request\", \"cra-base-report-create\", \"cra-base-report-refresh\", \"cra-network-insights-req\", \"income-insights-refresh\", \"partner-prism-attrib\", \"partner-prism-scores\"]\n- Monitor: [\"monitor-wl-rescan-add\", \"monitor-wl-rescan-remove\", \"monitor-wl-base\"]\n- Hosted Link Delivery: [\"hosted-link-delivery-eml\", \"hosted-link-delivery-sms\"]\n- Transfer: [\"momo-transfer-ach\", \"momo-transfer-ach-sd\", \"momo-wire-request\", \"momo-rtp-request\", \"momo-transfer-g-ach\", \"momo-transfer-g-ach-sd\", \"momo-transfer-authorized\", \"momo-transfer-manual-req\", \"momo-transfer-return-unauthorized\", \"momo-transfer-return-noc\", \"momo-transfer-return-other\"]\n\n<note>\n- If a user asks for a product similar to one on this list and you're 99% confident it's the same product, query for the product on this list and inform them which product you're querying for. Otherwise, do not query an unrelated product.\n- \"momo-frs-eval-request\" is the metric type used in the API for Signal. When communicating with users, refer to it as \"signal-request\" instead.\n</note>\n</product_mapping>\n\n<example_1>\nUser: \"I want to see the usage data for Transactions\"\nReasoning: The metric types for Transactions are [\"transactions\", \"transactions-add\", \"transactions-remove\", \"transactions-active\", \"transactions-refresh\"].\n\nInput parameters:\n{\n \"metric_types\": [\"transactions\", \"transactions-add\", \"transactions-remove\", \"transactions-active\", \"transactions-refresh\"],\n // other fields ...\n}\n</example_1>\n\n<example_2>\nUser: \"What metrics are available for Identity Verification?\"\nResponse: We support the following metrics for Identity Verification: idv-base, idv-lightning-group-1, idv-lightning-group-2, idv-lightning-group-3, idv-document, idv-selfie-check.\n</example_2>\n\n<important>\n- If metric_types aren't provided, use \"auth-request\" as the default\n- If no date range is provided, ask the user for one (suggest last 30 days with current date as end date)\n- The maximum look-back period is limited to 1 year from the current date\n</important>"+ },+ {+ "slug": "PLAID_MCP_PLAID_LIST_TEAMS",+ "name": "Plaid list teams",+ "description": "\nRetrieve teams associated with the user and present them as a selectable list. \nAfter the user selects a team, capture the team_id of the selected team for use \nin subsequent tool requests.\n\n<important>\n1. You MUST return a numbered list of teams with their names clearly displayed in a human readable format in the conversation dialog\n\t- Format each team as: \"{number}. {company name} (ID: {team_id})\"\n\t- Example: \"1. XXX Corporation (ID: fakeid00000000000000000)\"\n2. Ask the user explicitly to select a team by providing either:\n\t- The number from the list (e.g., \"Please select team 3\")\n\t- The exact team name (e.g., \"I want to use XXX Corporation\")\n\t- The team ID directly (e.g., \"Use team fakeid00000000000000000\")\n3. After user selection, confirm their choice with a clear acknowledgment:\n\t- \"You've selected: {company name} (ID: {team_id})\"\n4. Store and use this team_id for ALL subsequent tool requests that require a team_id parameter\n5. Handle edge cases appropriately:\n\t- If only one team exists, auto-select it and confirm the selection\n\t- If no teams exist, clearly communicate this limitation to the user\n\t- If the response is empty, the user is not a member of any teams. Inform the user that they should \n\t\tvisit dashboard.plaid.com to join or create a team.\n</important>"+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "plaid_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "mcp:dashboard"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "plain","name": "Plain",@@ -267746,7 +277914,7 @@],"toolCount": 7,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{"slug": "POPHIVE_MCP_COMPARE",@@ -267766,7 +277934,7 @@{"slug": "POPHIVE_MCP_GET_DATA","name": "Get data",- "description": "Data catalog and raw-data gateway. The six specialized tools answer\nsingle-slice questions — current status, trend, map/ranking, A-vs-B\ncompare, coverage — with server-verified evidence; try them first,\nescalating here costs one call. Use get_data when evidence can't carry\nthe answer: multi-stratum gaps, history beyond the served window,\ncomplete lists, cross-dataset joins, custom math. Flow: (1) catalog,\n(2) disease='about' for the guide, (3) view schema + data_url,\n(4) download and compute — results are yours but carry the caveats and\naren't server-verified. include_query=true returns a runnable pandas\nsnippet.\n\nTopics: adhd, annual_wellness_visit, anxiety, breast_cancer_screening, cardiovascular_screening, cervical_cancer_screening, chlamydia_screening, colorectal_cancer_screening, combined7, covid19, depression, depression_screening, diabetes, diabetes_screening, dtap, firearm_injury, flu_vaccine_adult, heat_illness, hepa, hepb, hib, influenza, injury_deaths, measles, mmr, obesity, opioid_overdose, opioid_use_disorder, pcv, pelvic_exam, pneumococcal_vaccine_adult, polio, prostate_cancer_screening, rotavirus, rsv, vaccine_exemptions, varicella.\n\nExamples: \"What does PopHIVE track?\", \"Do you have Lyme disease data?\",\n\"Vaccination gaps across insurance types\", \"Raw RSV data for\nConnecticut.\"\n\nNot for: 'is flu rising in Texas?' → get_current_status; 'rank states\nby COVID wastewater' → get_map; 'is RSV worse in CT than NY?' → compare.\n\nCall example: get_data(disease='rsv', view='overall_trend')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."+ "description": "Data catalog and raw-data gateway. The six specialized tools answer\nsingle-slice questions — current status, trend, map/ranking, A-vs-B\ncompare, coverage — with server-verified evidence; try them first,\nescalating here costs one call. Use get_data when evidence can't carry\nthe answer: multi-stratum gaps, history beyond the served window,\ncomplete lists, cross-dataset joins, custom math. Flow: (1) catalog,\n(2) disease='about' for the guide, (3) view schema + data_url,\n(4) download and compute — results are yours but carry the caveats and\naren't server-verified. include_query=true returns a runnable pandas\nsnippet.\n\nTopics: annual_wellness_visit, antimicrobial_resistance, breast_cancer_screening, campylobacter, cardiovascular_screening, cervical_cancer_screening, chlamydia_screening, colorectal_cancer_screening, combined7, community_health, copd, covid19, depression_screening, diabetes, diabetes_screening, diarrhea, dtap, enteric_disease, firearm_injury, flu_vaccine_adult, haemophilus_influenzae, healthcare_access, heat_illness, hepa, hepb, hib, infant_mortality, influenza, injury_deaths, low_birth_weight, maternal_health, maternal_mortality, measles, mmr, obesity, opioid_overdose, opioid_use_disorder, pcv, pelvic_exam, pertussis, pneumococcal_vaccine_adult, polio, prostate_cancer_screening, rotavirus, rsv, salmonella, shigella, stec, strep, teen_births, vaccine_exemptions, varicella, youth_wellbeing.\n\nExamples: \"What does PopHIVE track?\", \"Do you have Lyme disease data?\",\n\"Vaccination gaps across insurance types\", \"Raw RSV data for\nConnecticut.\"\n\nNot for: 'is flu rising in Texas?' → get_current_status; 'rank states\nby COVID wastewater' → get_map; 'is RSV worse in CT than NY?' → compare.\n\nCall example: get_data(disease='rsv', view='overall_trend')\n\n Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers."},{"slug": "POPHIVE_MCP_GET_MAP",@@ -270252,7 +280420,7 @@],"toolCount": 22,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260908_00","tools": [{"slug": "PRISMA_CREATE_CONNECTION",@@ -270405,7 +280573,7 @@"type": "string","description": "Scopes to request from the user, comma separated","required": false,- "default": "workspace:admin"+ "default": "workspace:admin,offline_access"}]},@@ -275443,7 +285611,7 @@],"toolCount": 11,"triggerCount": 0,- "version": "00000000_00",+ "version": "20260908_00","tools": [{"slug": "RAINDROP_CREATE_BOOKMARK",@@ -276947,6 +287115,91 @@}]},+ {+ "slug": "read_ai_mcp",+ "name": "Read AI MCP",+ "logo": "https://logos.composio.dev/api/read_ai_mcp",+ "description": "Read AI MCP lets agents retrieve meeting transcripts, summaries, action items, topics, metrics, and recordings, deploy meeting agents, and share authorized meeting reports.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 4,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "READ_AI_MCP_CREATE_MEETING_AGENT",+ "name": "Create meeting agent",+ "description": "\nSend a Read AI meeting agent (bot) to a video conferencing meeting on \nbehalf of the authenticated user. This creates a new Read AI meeting ID \nand the agent will attempt to join the meeting to record & transcribe it \nfor the user.\n\nWhen to call this tool\n----------------------\nCall this tool when:\n- The user explicitly asks for an agent to \"join\", \"record\", \"capture,\" \"send a bot to\", or\n \"take notes on\" a specific meeting they identify on their calendar, by providing\n a meeting link, or specifying a video conferencing platform with a meeting ID and \n optional password.\n- The meeting is on a supported platform (Zoom, Google Meet, Microsoft Teams)\n\nDo NOT call this tool:\n- For meetings the user has not explicitly authorized an agent to join.\n- To join arbitrary or guessed meeting IDs.\n- If a user wants to record using a desktop or mobile client. Those are available from\n Read AI's website (https://read.ai) and can be used separately. \n\nParameters\n----------\n\nmeeting_url : str\n Meeting URL that can be used to join the meeting. If provided, the meeting_platform \n and meeting_id will be extracted from the URL and those additional parameters are\n not required.\n\nmeeting_platform : str\n The video conferencing platform for the meeting. Must be one of:\n - \"zoom\" (Zoom)\n - \"meet\" (Google Meet)\n - \"teams\" (Microsoft Teams)\n\n If a meeting_url is provided, this parameter is not required.\n\nmeeting_id : str\n The platform-specific meeting identifier (e.g. a Zoom meeting number,\n a Google Meet meeting code like \"abc-defg-hij\", a Teams meeting ID, etc.).\n Provide the raw ID as it would appear in the meeting URL.\n\n If a meeting_url is provided, this parameter is not required.\n\nmeeting_password : Optional[str]\n Optional passcode/password for the meeting, if one is required. Omit if\n the meeting does not require a password or if a meeting_url is provided.\n\nstart_time : Optional[datetime]\n Optional start time to stamp on the created meeting, in ISO 8601 format\n (e.g. \"2026-05-21T15:00:00\" or \"2026-05-21T15:00:00Z\"). If omitted, the\n meeting is stamped with the current time at creation and an agent is \n dispatched immediately to join the meeting. If a time in the future is\n specified, the agent will join the meeting at the specified time.\n\ntitle : Optional[str]\n Optional human-readable title to stamp on the created meeting (e.g.\n \"Q3 Planning Sync\"). If omitted, the meeting is given a generic\n platform-derived default such as \"Zoom Meeting\" or \"Meet Meeting\".\n Only set this when the user has provided or clearly implied a title;\n do not invent one.\n\nReturns\n-------\nstr\n The ULID for the newly created (or matched existing) Read AI meeting that the\n the meeting recording agent has been dispatched for. This meeting ID can be passed to\n other tools such as `get_meeting_by_id` once the meeting has progressed\n far enough to have data available.\n\nBehavior and edge cases\n-----------------------\n- Authentication:\n - Access token is handled internally; do not supply user IDs or tokens.\n - If missing or invalid, the tool fails with errors such as:\n - \"Unauthorized: No access token provided\"\n - \"Invalid token: No subject in access token claims\".\n- Validation:\n - `meeting_id` is required and must be non-empty if a meeting_url is not provided.\n - If the platform / meeting combination is unsupported or the agent cannot\n be deployed (e.g. mobile/desktop platforms, or missing required platform\n integrations), the tool will fail with an error.\n- Idempotency:\n - This tool is idempotent. If an entry for the same meeting already exists in an active\n state, the system may return the existing meeting ID instead of creating\n a new one.\n- Side effects:\n - An agent may join the live meeting and a new meeting ID is created in Read AI.\n\nUsage examples for agents\n-------------------------\n1) User: \"Have Read AI record my Zoom meeting 1234567890.\"\n -> Call:\n {\n \"meeting_platform\": \"zoom\",\n \"meeting_id\": \"1234567890\"\n }\n\n2) User: \"Send the Read AI bot to my Google Meet abc-defg-hij.\"\n -> Call:\n {\n \"meeting_platform\": \"meet\",\n \"meeting_id\": \"abc-defg-hij\"\n }\n\n3) User: \"Join my Zoom 9876543210 with passcode hunter2.\"\n -> Call:\n {\n \"meeting_platform\": \"zoom\",\n \"meeting_id\": \"9876543210\",\n \"meeting_password\": \"hunter2\"\n }\n\n4) User: \"Join my meeting now: https://meet.google.com/abc-defg-hij\"\n -> Call:\n {\n \"meeting_url\": \"https://meet.google.com/abc-defg-hij\"\n }\n\n5) User: \"Join my meeting at 2026-05-21T15:00:00Z: https://meet.google.com/abc-defg-hij\"\n -> Call:\n {\n \"meeting_url\": \"https://meet.google.com/abc-defg-hij\",\n \"start_time\": \"2026-05-21T15:00:00Z\"\n }\n\n6) User: \"Join my Zoom 1234567890 and call it 'Q3 Planning Sync'.\"\n -> Call:\n {\n \"meeting_platform\": \"zoom\",\n \"meeting_id\": \"1234567890\",\n \"title\": \"Q3 Planning Sync\"\n }\n"+ },+ {+ "slug": "READ_AI_MCP_GET_MEETING_BY_ID",+ "name": "Get meeting by",+ "description": "\nRetrieve a single Read AI meeting (owned by or shared with the authenticated user)\nby its ULID identifier, with optional expansion of rich meeting content.\n\nWhen to call this tool\n----------------------\nCall this tool only when:\n- You already have a specific meeting ID (a ULID), and\n- The user wants information about that *one* meeting, such as:\n - Metadata (title, times, participants, platform, report URL)\n - Summary / chapter summaries\n - Action items / key questions\n - Topics discussed\n - Full transcript\n - Metrics/analytics\n - A link to download the recording\n\nDo NOT call this tool:\n- To search or browse meetings by title, date, participant, or keywords\n (use a dedicated list/search tool instead).\n- When working with multiple meetings at once.\n- With guessed or fabricated IDs. Only use IDs explicitly provided by the user\n or returned from another tool.\n\n\nParameters\n----------\nid : str\n The Read AI meeting identifier in ULID format.\n - 26-character, case-insensitive, base32 ULID string\n (e.g. \"01KA3883FYZSFZXE391Q0FMV39\").\n - Must come from:\n - A previous tool (e.g., a meeting list/search tool), or\n - Explicit user input.\n - Do not invent, modify, or \"fix\" IDs.\n\n\nexpand : Optional[List[ExpandableEnum]]\n Optional list specifying which additional sections of the meeting record\n should be fully populated.\n\n Only sections listed here are fetched; all others remain `None`. Request the\n smallest set that satisfies the user’s need. Each additional expand value\n can increase latency and resource usage, especially \"transcript\".\n\n Allowed values (strings):\n - \"summary\": concise natural-language overview of the meeting.\n - \"chapter_summaries\": breakdown into labeled sections/chapters.\n - \"action_items\": follow-up tasks and next steps.\n - \"key_questions\": important or open questions discussed.\n - \"topics\": main themes/subjects covered.\n - \"transcript\": detailed spoken content of the meeting, including who spoke and what they said, suitable for verbatim quotes and fine‑grained analysis.\n - \"metrics\": high-level analytics (e.g., read_score, sentiment, engagement).\n - \"recording_download\": url to download the meeting recording.\n\n\nOutput\n------\nMeetingEvent\n A single meeting object with:\n - Base metadata (id, title, start/end times, scheduled times, platform,\n platform_id, report_url, folders).\n - `access_level`: the authenticated caller's access level on this meeting,\n one of \"owner\", \"editor\", \"viewer_full\", or \"viewer_recap_only\" (or null\n if it could not be resolved). \"editor\" or \"owner\" is required to share the\n report via the `share_meeting_report` tool.\n - Owner and participants (with name/email and attendance status).\n - Expandable fields populated only if requested in `expand`:\n - `summary`: Optional[str]\n - `chapter_summaries`: Optional[List[Chapter]]\n - `action_items`: Optional[List[str]]\n - `key_questions`: Optional[List[str]]\n - `topics`: Optional[List[str]]\n - `transcript`: Optional[Transcript]\n - `metrics`: Optional[Metrics]\n - `recording_download`: Optional[RecordingDownload]\n\n\nBehavior and edge cases\n-----------------------\n- Authentication:\n - Access token is handled internally; do not supply it as a parameter.\n - If missing or invalid, the tool fails with errors such as:\n - \"Unauthorized: No access token provided\"\n - \"Invalid token: No subject in access token claims\".\n- Not found / access issues:\n - If the ID is invalid or the meeting is not accessible to the user,\n the tool fails with \"Not Found\".\n - If the user's Read AI account does not have sufficient quota to view the meeting, the tool fails with \n an \"Out of quota\" error. This is a billing issue and the user can resolve it by upgrading \n their plan. They can resolve this by visiting \"https://app.read.ai/analytics/meetings/{meeting_id}\"\n in their browser, where {meeting_id} is the provided meeting ID.\n\n- Idempotency:\n - Read-only and idempotent. Calling with the same arguments returns the same\n logical result.\n\nUsage examples for agents\n-------------------------\n1) User: \"Give me the summary and action items from meeting 01H9T5X9G5K3M7Y8R0D8AYZ5WQ.\"\n -> Call:\n {\n \"id\": \"01H9T5X9G5K3M7Y8R0D8AYZ5WQ\",\n \"expand\": [\"summary\", \"action_items\"]\n }\n\n2) User: \"Who said 'We should move this to next quarter' in meeting <meeting_ulid>?\"\n -> You need detailed speech text:\n {\n \"id\": \"<meeting_ulid>\",\n \"expand\": [\"transcript\"]\n }\n"+ },+ {+ "slug": "READ_AI_MCP_LIST_MEETINGS",+ "name": "List meetings",+ "description": "\nList Read AI meetings for the authenticated user with optional start-time filters\nand cursor-based pagination.\n\nWhen to call this tool\n----------------------\nCall this tool when:\n- You need to browse or filter a user's meetings by time range.\n- You need meeting IDs (ULIDs) that can later be used with a \"get_meeting_by_id\"\n tool for detailed inspection.\n- You want a page of recent meetings (optionally with summaries or metrics).\n\nDo NOT call this tool:\n- When you already know the specific meeting ID and only need that single\n meeting (use the \"get_meeting_by_id\" tool instead).\n- To search by title, participant, or arbitrary keywords (use a search tool\n if available).\n- To guess or fabricate meeting IDs.\n\nParameters\n----------\nlimit : int, default 10 (max 10)\n Maximum number of meetings to return in this page.\n - Must be ≤ 10.\n - If omitted, defaults to 10.\n\nstart_datetime_gt : Optional[datetime]\n Only include meetings whose start time is strictly greater than this value\n (exclusive lower bound). ISO 8601 string, e.g. \"2025-11-01T00:00:00Z\".\n\nstart_datetime_gte : Optional[datetime]\n Only include meetings whose start time is greater than or equal to this\n value (inclusive lower bound). ISO 8601 string.\n - Typically use either `start_datetime_gt` or `start_datetime_gte`, not both.\n\nstart_datetime_lt : Optional[datetime]\n Only include meetings whose start time is strictly less than this value\n (exclusive upper bound). ISO 8601 string.\n\nstart_datetime_lte : Optional[datetime]\n Only include meetings whose start time is less than or equal to this\n value (inclusive upper bound). ISO 8601 string.\n - Typically use either `start_datetime_lt` or `start_datetime_lte`, not both.\n - For a closed interval [A, B], use:\n - `start_datetime_gte = A`\n - `start_datetime_lte = B`\n\ncursor : Optional[str]\n Cursor for pagination.\n - First page: omit or pass `null`.\n - Next page: pass the ID of the last meeting returned in the previous page\n (`previous_response.data[-1].id`), which acts as a \"start after this\"\n pointer.\n\nexpand : Optional[List[ExpandableEnum]]\n Optional list specifying which extra sections of *each* meeting should be\n fully populated.\n\n Only sections listed here are fetched; all others remain `None`. Because\n this is a list endpoint, expansions apply to every meeting in the page and\n can be expensive. Request only what the user needs.\n\n Allowed values (strings), with the same meanings as in `get_meeting_by_id`:\n - \"summary\": concise overview of each meeting.\n - \"chapter_summaries\": section/chapter breakdown.\n - \"action_items\": follow-up tasks per meeting.\n - \"key_questions\": important or open questions per meeting.\n - \"topics\": main themes/subjects per meeting.\n - \"transcript\": full spoken content per meeting.\n - \"metrics\": analytics such as read_score, sentiment, engagement.\n - \"recording_download\": url to download the meeting recording.\n\nReturns\n-------\nListMeetingResponse\n A paginated list of meetings with:\n - `object`: str – always \"list\".\n - `url`: str – API-style URL for this collection.\n - `has_more`: bool – True if there are more meetings beyond this page.\n - `data`: List[MeetingEvent] – meetings matching the filters, each with:\n - Core metadata (id, title, start/end times, platform, etc.).\n - `access_level`: the caller's access level on the meeting (\"owner\",\n \"editor\", \"viewer_full\", \"viewer_recap_only\", or null). \"editor\"/\"owner\"\n is required to share the report via `share_meeting_report`.\n - Owner and participants.\n - Any expandable fields populated according to `expand`.\n\n\nBehavior and edge cases\n-----------------------\n- Authentication:\n - Access token is handled internally; do not pass it as a parameter.\n - If missing or invalid, the tool raises errors such as:\n - \"Unauthorized: No access token provided\"\n - \"Invalid token: No subject in access token claims\".\n\n- Filtering:\n - All provided filters are combined with logical AND.\n - Conflicting ranges (e.g., lower bound after upper bound) will typically\n return an empty result.\n - Prefer at most one lower-bound parameter (`gt` or `gte`) and one upper-\n bound parameter (`lt` or `lte`).\n\n- Pagination:\n - `limit` controls the number of meetings per page (max 10).\n - Use `has_more` plus `cursor` (last meeting's id from `data`) to fetch\n subsequent pages.\n\n- Idempotency:\n - Read-only and idempotent. Repeating the same call yields the same logical\n results, except for new meetings created in the underlying system.\n\n\nUsage examples for agents\n-------------------------\n1) Get the 10 most recent meetings (no filters, first page):\n -> Call:\n {\n \"limit\": 10\n }\n\n2) Get meetings in November 2025, including brief summaries:\n -> Call:\n {\n \"limit\": 10,\n \"start_datetime_gte\": \"2025-11-01T00:00:00\",\n \"start_datetime_lte\": \"2025-11-30T23:59:59\",\n \"expand\": [\"summary\"]\n }\n\n3) Page through all recent meetings since 2025-11-01:\n First page:\n -> Call:\n {\n \"limit\": 10,\n \"start_datetime_gte\": \"2025-11-01T00:00:00\"\n }\n Next page (if has_more is true):\n -> Call:\n {\n \"limit\": 10,\n \"start_datetime_gte\": \"2025-11-01T00:00:00\",\n \"cursor\": \"<id_of_last_meeting_from_previous_page>\"\n }\n\n4) Find candidate meetings to inspect in detail later:\n - First, list meetings with summaries and metrics:\n {\n \"limit\": 5,\n \"expand\": [\"summary\", \"metrics\"]\n }\n - Then, pick a specific meeting ID and call `readai_get_meeting_by_id`\n with `expand=[\"transcript\"]` if you need the full conversation.\n"+ },+ {+ "slug": "READ_AI_MCP_SHARE_MEETING_REPORT",+ "name": "Share meeting report",+ "description": "\nShare a Read AI meeting report with an email address on behalf of the\nauthenticated user. Grants the recipient access to the meeting at a specified\naccess level and (optionally) emails them an invite.\n\nWhen to call this tool\n----------------------\nCall this tool when:\n- The user explicitly asks to \"share\", \"send\", \"give access to\", or \"invite\n someone to\" a specific meeting report, identified by its ULID.\n- You have already confirmed (via `get_meeting_by_id` or `list_meetings`) that\n the user has \"editor\" or \"owner\" access to that meeting — only editors and\n owners are allowed to share.\n\nDo NOT call this tool:\n- To share meetings the user does not have edit access to. If `access_level`\n from `get_meeting_by_id`/`list_meetings` is \"viewer_full\" or\n \"viewer_recap_only\", the user cannot share and the call will fail.\n- With guessed or fabricated meeting IDs or email addresses. Only use values\n explicitly provided by the user or returned from another tool.\n- To transfer ownership. Ownership cannot be granted through this tool.\n\nParameters\n----------\nid : str\n The Read AI meeting identifier in ULID format (26-character, case-insensitive\n base32). Must come from a previous tool or explicit user input.\n\nemail : str\n The email address to share the report with. Must be a valid email address.\n If the email belongs to an existing Read AI user, access is granted to that\n user directly; otherwise an email-based access invite is created.\n\naccess_level : str\n The access level to grant. One of:\n - \"viewer_recap_only\": can view only the recap/summary of the meeting.\n - \"viewer_full\": full read access to the meeting report.\n - \"editor\": read access plus the ability to edit (and re-share) the report.\n Defaults to \"viewer_full\". \"owner\" is not allowed.\n\nmessage : Optional[str]\n Optional personal message to include in the invite email. Only relevant when\n `notify` is true.\n\nnotify : bool, default true\n Whether to send the recipient an invite email. Set to false to grant access\n silently without notifying them.\n\nReturns\n-------\nShareMeetingResponse\n An object describing the grant:\n - `id`: the meeting ULID that was shared.\n - `shared_with_email`: the email the report was shared with.\n - `access_level`: the access level that was granted.\n - `notified`: whether an invite email was sent.\n - `report_url`: a link to the meeting report.\n\nBehavior and edge cases\n-----------------------\n- Authentication:\n - Access token is handled internally; do not supply user IDs or tokens.\n- Permissions:\n - The caller must have \"editor\" or \"owner\" access to the meeting. If not, the\n tool fails with a \"Forbidden\" error. Confirm the caller's `access_level`\n using `get_meeting_by_id` before calling this tool.\n- Validation:\n - An invalid email address will cause the tool to fail.\n - Granting \"owner\" (or any non-shareable level) will fail.\n- Idempotency:\n - Re-sharing with the same email and access level is safe; the existing grant\n is updated rather than duplicated, and the invite email is not re-sent. The\n `notified` field in the response reflects whether an email was actually\n sent on this call.\n- Side effects:\n - The recipient gains access to the meeting, and (unless `notify` is false,\n or an equivalent grant already existed) an invite email is sent to them.\n\nUsage examples for agents\n-------------------------\n1) User: \"Share meeting 01H9T5X9G5K3M7Y8R0D8AYZ5WQ with [email protected].\"\n -> First confirm the caller can share (get_meeting_by_id -> access_level is\n \"editor\" or \"owner\"), then call:\n {\n \"id\": \"01H9T5X9G5K3M7Y8R0D8AYZ5WQ\",\n \"email\": \"[email protected]\"\n }\n\n2) User: \"Give [email protected] edit access to that meeting and add a note.\"\n -> Call:\n {\n \"id\": \"<meeting_ulid>\",\n \"email\": \"[email protected]\",\n \"access_level\": \"editor\",\n \"message\": \"Please review and update the action items.\"\n }\n\n3) User: \"Quietly share the recap of <meeting_ulid> with [email protected] without emailing them.\"\n -> Call:\n {\n \"id\": \"<meeting_ulid>\",\n \"email\": \"[email protected]\",\n \"access_level\": \"viewer_recap_only\",\n \"notify\": false\n }\n"+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "read_ai_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "offline_access,offline,openid,profile,email,mcp:execute,meeting:read"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "readwise_reader","name": "Readwise Reader",@@ -281564,9 +291817,9 @@"authSchemes": ["API_KEY"],- "toolCount": 62,+ "toolCount": 66,"triggerCount": 0,- "version": "20260826_00",+ "version": "20260903_00","tools": [{"slug": "RESEND_ADD_CONTACT_TO_SEGMENT",@@ -281608,6 +291861,16 @@"name": "Create Domain","description": "Create a domain through the Resend Email API. The domain is created in a pending/unverified state and cannot be used for sending emails until DNS verification is completed."},+ {+ "slug": "RESEND_CREATE_DRAFT_BROADCAST",+ "name": "Create Draft Broadcast",+ "description": "Create a broadcast and leave it as an unsent draft. Use when you want to stage a campaign for review; this action never sends or schedules the broadcast, so a separate send step is always required."+ },+ {+ "slug": "RESEND_CREATE_SEGMENT",+ "name": "Create Segment",+ "description": "Create a new segment for contacts to be added to. Use when you need a fresh list of contacts to target; segments are the modern replacement for audiences."+ },{"slug": "RESEND_CREATE_TEMPLATE","name": "Create Template",@@ -281678,6 +291941,11 @@"name": "Duplicate Template","description": "Duplicate an existing template through the Resend Email API. Use when you need to create a copy of an existing template."},+ {+ "slug": "RESEND_GET_BROADCAST",+ "name": "Get Broadcast",+ "description": "Retrieve a single broadcast by its ID. Use when you need to read back a broadcast's content, recipient segment, schedule and status before sending it."+ },{"slug": "RESEND_GET_CONTACT","name": "Get Contact",@@ -281716,7 +291984,7 @@{"slug": "RESEND_LIST_ALL_CONTACTS","name": "List All Contacts",- "description": "Tool to retrieve a list of all contacts from Resend. Use when you need to fetch contacts across all audiences with optional pagination."+ "description": "Tool to retrieve a list of all contacts from Resend. Use when you need to fetch contacts across all audiences with optional pagination, or only the contacts of a single segment by passing segment_id."},{"slug": "RESEND_LIST_API_KEYS",@@ -281853,6 +292121,11 @@"name": "Update Domain","description": "Update an existing domain."},+ {+ "slug": "RESEND_UPDATE_DRAFT_BROADCAST",+ "name": "Update Draft Broadcast",+ "description": "Update a broadcast that is still an unsent draft. Use when you need to revise a staged campaign; the broadcast is read back first and the update is refused unless its status is 'draft' and it has no scheduled send time."+ },{"slug": "RESEND_UPDATE_EMAIL","name": "Update Email",@@ -282643,6 +292916,102 @@}]},+ {+ "slug": "retable",+ "name": "Retable",+ "logo": "https://logos.composio.dev/api/retable",+ "description": "Retable is a collaborative spreadsheet and database platform for organizing workspaces, projects, tables, columns, rows, and files.",+ "category": "spreadsheets",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 11,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "RETABLE_ADD_COLUMNS",+ "name": "Add Columns",+ "description": "Append one or more typed columns to a table and return the complete resulting column list."+ },+ {+ "slug": "RETABLE_DELETE_COLUMNS",+ "name": "Delete Columns",+ "description": "Permanently delete one or more columns and their cell data, then return the complete remaining column list."+ },+ {+ "slug": "RETABLE_DELETE_ROWS",+ "name": "Delete Rows",+ "description": "Permanently delete one or more rows from a table; missing row IDs are ignored and count as zero deletions."+ },+ {+ "slug": "RETABLE_GET_ROWS",+ "name": "Get Rows",+ "description": "Return all rows or up to 50 selected rows using stable column IDs or title-keyed fields."+ },+ {+ "slug": "RETABLE_GET_TABLE",+ "name": "Get Table",+ "description": "Get one table's metadata, column IDs and types, and views before reading or changing its data."+ },+ {+ "slug": "RETABLE_INSERT_ROWS",+ "name": "Insert Rows",+ "description": "Insert one or more rows into a table in one request and return the created rows with their IDs."+ },+ {+ "slug": "RETABLE_LIST_PROJECT_TABLES",+ "name": "List Project Tables",+ "description": "List tables in one Retable project with their IDs, columns, and parent workspace and project IDs."+ },+ {+ "slug": "RETABLE_LIST_WORKSPACE_PROJECTS",+ "name": "List Workspace Projects",+ "description": "List projects accessible in one workspace, including project IDs needed to discover tables."+ },+ {+ "slug": "RETABLE_LIST_WORKSPACES",+ "name": "List Workspaces",+ "description": "List workspaces visible to the connected Retable account, including each workspace ID needed to discover projects."+ },+ {+ "slug": "RETABLE_SEARCH_ROWS",+ "name": "Search Rows",+ "description": "Search a table for a value in a primary column and return matching rows from an optional starting offset. For text columns, Retable matches the full cell value rather than partial text."+ },+ {+ "slug": "RETABLE_UPDATE_ROWS",+ "name": "Update Rows",+ "description": "Update cells in one or more existing rows in one request and return the updated row IDs."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "retable_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "Log in to Retable at https://app.retable.io, open your profile menu, select API, then generate or enable an API key and copy it. Treat the complete key as secret and paste it without modification.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "retailed","name": "Retailed",@@ -282941,102 +293310,6 @@}]},- {- "slug": "rev_ai",- "name": "Rev AI",- "logo": "https://logos.composio.dev/api/rev_ai",- "description": "Rev AI provides advanced machine learning and speech recognition services for converting audio and video to text.",- "category": "artificial intelligence",- "authSchemes": [- "API_KEY"- ],- "toolCount": 11,- "triggerCount": 0,- "version": "20260826_00",- "tools": [- {- "slug": "REV_AI_DELETE_CUSTOM_VOCABULARY",- "name": "Delete Custom Vocabulary",- "description": "Tool to delete a completed custom vocabulary and its data. Use when you need to remove an unused vocabulary after confirming it's no longer needed."- },- {- "slug": "REV_AI_DELETE_JOB_BY_ID",- "name": "Delete Job By ID",- "description": "Tool to delete a completed transcription job and its data. Use when you need to permanently remove a finished job after confirming it's no longer needed."- },- {- "slug": "REV_AI_GET_ACCOUNT",- "name": "Get Account",- "description": "Tool to retrieve developer account details. Use after authenticating with Rev AI."- },- {- "slug": "REV_AI_GET_CAPTIONS",- "name": "Get Captions",- "description": "Tool to retrieve captions (SRT or VTT) for a completed Rev.ai transcription job. Use after confirming the job status is 'completed'."- },- {- "slug": "REV_AI_GET_CUSTOM_VOCABULARY_DETAILS",- "name": "Get Custom Vocabulary Details",- "description": "Tool to retrieve custom vocabulary processing details. Use when needing to fetch the status and submitted phrases for a specific custom vocabulary after creation."- },- {- "slug": "REV_AI_GET_JOB_BY_ID",- "name": "Get Job by ID",- "description": "Tool to fetch details of a transcription job by its ID. Use when confirming job status and metadata are accurate."- },- {- "slug": "REV_AI_GET_LIST_OF_JOBS",- "name": "Get List of Jobs",- "description": "Tool to get list of transcription jobs from the past 30 days. Use when you need to retrieve and paginate through recent transcription tasks."- },- {- "slug": "REV_AI_GET_TRANSCRIPT_BY_ID",- "name": "Get Transcript by ID",- "description": "Tool to retrieve the transcript of a completed Rev.ai job. Use after confirming job is complete. Supports JSON format (with timestamps and speaker info) or plain text format."- },- {- "slug": "REV_AI_START_STREAM_TRANSCRIPTION",- "name": "Start Stream Transcription",- "description": "Tool to start a WebSocket transcription stream. Use when you need real-time speech-to-text streaming via Rev.ai."- },- {- "slug": "REV_AI_SUBMIT_CUSTOM_VOCABULARY",- "name": "Submit Custom Vocabulary",- "description": "Tool to submit a custom vocabulary for improved speech recognition. Use when you want to process domain-specific terms asynchronously."- },- {- "slug": "REV_AI_SUBMIT_TRANSCRIPTION_JOB",- "name": "Submit Transcription Job",- "description": "Tool to submit a new transcription job. Use when you have a media URL or file bytes ready for async processing."- }- ],- "triggers": [],- "authConfigDetails": [- {- "mode": "API_KEY",- "name": "rev_ai_api_key",- "fields": {- "auth_config_creation": {- "required": [],- "optional": []- },- "connected_account_initiation": {- "required": [- {- "name": "bearer_token",- "displayName": "Rev AI Access Token",- "type": "string",- "description": "The access token generated from the Rev AI account, used for authenticating API requests.",- "required": true,- "default": null- }- ],- "optional": []- }- }- }- ]- },{"slug": "rev","name": "Rev AI",@@ -283266,6 +293539,102 @@}]},+ {+ "slug": "rev_ai",+ "name": "Rev AI",+ "logo": "https://logos.composio.dev/api/rev_ai",+ "description": "Rev AI provides advanced machine learning and speech recognition services for converting audio and video to text.",+ "category": "artificial intelligence",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 11,+ "triggerCount": 0,+ "version": "20260826_00",+ "tools": [+ {+ "slug": "REV_AI_DELETE_CUSTOM_VOCABULARY",+ "name": "Delete Custom Vocabulary",+ "description": "Tool to delete a completed custom vocabulary and its data. Use when you need to remove an unused vocabulary after confirming it's no longer needed."+ },+ {+ "slug": "REV_AI_DELETE_JOB_BY_ID",+ "name": "Delete Job By ID",+ "description": "Tool to delete a completed transcription job and its data. Use when you need to permanently remove a finished job after confirming it's no longer needed."+ },+ {+ "slug": "REV_AI_GET_ACCOUNT",+ "name": "Get Account",+ "description": "Tool to retrieve developer account details. Use after authenticating with Rev AI."+ },+ {+ "slug": "REV_AI_GET_CAPTIONS",+ "name": "Get Captions",+ "description": "Tool to retrieve captions (SRT or VTT) for a completed Rev.ai transcription job. Use after confirming the job status is 'completed'."+ },+ {+ "slug": "REV_AI_GET_CUSTOM_VOCABULARY_DETAILS",+ "name": "Get Custom Vocabulary Details",+ "description": "Tool to retrieve custom vocabulary processing details. Use when needing to fetch the status and submitted phrases for a specific custom vocabulary after creation."+ },+ {+ "slug": "REV_AI_GET_JOB_BY_ID",+ "name": "Get Job by ID",+ "description": "Tool to fetch details of a transcription job by its ID. Use when confirming job status and metadata are accurate."+ },+ {+ "slug": "REV_AI_GET_LIST_OF_JOBS",+ "name": "Get List of Jobs",+ "description": "Tool to get list of transcription jobs from the past 30 days. Use when you need to retrieve and paginate through recent transcription tasks."+ },+ {+ "slug": "REV_AI_GET_TRANSCRIPT_BY_ID",+ "name": "Get Transcript by ID",+ "description": "Tool to retrieve the transcript of a completed Rev.ai job. Use after confirming job is complete. Supports JSON format (with timestamps and speaker info) or plain text format."+ },+ {+ "slug": "REV_AI_START_STREAM_TRANSCRIPTION",+ "name": "Start Stream Transcription",+ "description": "Tool to start a WebSocket transcription stream. Use when you need real-time speech-to-text streaming via Rev.ai."+ },+ {+ "slug": "REV_AI_SUBMIT_CUSTOM_VOCABULARY",+ "name": "Submit Custom Vocabulary",+ "description": "Tool to submit a custom vocabulary for improved speech recognition. Use when you want to process domain-specific terms asynchronously."+ },+ {+ "slug": "REV_AI_SUBMIT_TRANSCRIPTION_JOB",+ "name": "Submit Transcription Job",+ "description": "Tool to submit a new transcription job. Use when you have a media URL or file bytes ready for async processing."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "rev_ai_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "bearer_token",+ "displayName": "Rev AI Access Token",+ "type": "string",+ "description": "The access token generated from the Rev AI account, used for authenticating API requests.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "revolt","name": "Revolt",@@ -287116,7 +297485,7 @@],"toolCount": 24,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260903_00","tools": [{"slug": "SALESFORCE_SERVICE_CLOUD_AGENT_SENSITIVE_DATA_RULE_TRIGGERED",@@ -288860,6 +299229,81 @@}]},+ {+ "slug": "scorecard_mcp",+ "name": "Scorecard MCP",+ "logo": "https://logos.composio.dev/api/scorecard_mcp",+ "description": "Scorecard MCP lets agents manage evaluation projects, testsets, testcases, systems, metrics, runs, records, scores, annotations, and documentation searches.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 2,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "SCORECARD_MCP_EXECUTE",+ "name": "Execute",+ "description": "Runs JavaScript code to interact with the Scorecard API.\n\nYou are a skilled TypeScript programmer writing code to interface with the service.\nDefine an async function named \"run\" that takes a single parameter of an initialized SDK client and it will be run.\nFor example:\n\n```\nasync function run(client) {\n const run = await client.runs.create('314', { metricIds: ['789', '101'], testsetId: '246' });\n\n console.log(run.id);\n}\n```\n\nYou will be returned anything that your function returns, plus the results of any console.log statements.\nDo not add try-catch blocks for single API calls. The tool will handle errors for you.\nDo not add comments unless necessary for generating better code.\nCode will run in a container, and cannot interact with the network outside of the given SDK client.\nVariables will not persist between calls, so make sure to return or log any data you might need later.\nRemember that you are writing TypeScript code, so you need to be careful with your types.\nAlways type dynamic key-value stores explicitly as Record<string, YourValueType> instead of {}."+ },+ {+ "slug": "SCORECARD_MCP_SEARCH_DOCS",+ "name": "Search docs",+ "description": "Search SDK documentation to find methods, parameters, and usage examples for interacting with the API. Use this before writing code when you need to discover the right approach."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "scorecard_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,public_metadata,private_metadata,offline_access,user:org:read"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "scrape_do","name": "Scrape Do",@@ -300694,7 +311138,7 @@],"toolCount": 27,"triggerCount": 0,- "version": "20260721_00",+ "version": "20260903_00","tools": [{"slug": "SPLITWISE_ADD_FRIEND",@@ -304112,255 +314556,6 @@}]},- {- "slug": "strava",- "name": "Strava",- "logo": "https://logos.composio.dev/api/strava",- "description": "Strava is a social fitness network and app designed for cyclists and runners.",- "category": "fitness",- "authSchemes": [- "OAUTH2"- ],- "composioManagedAuthSchemes": [- "OAUTH2"- ],- "toolCount": 36,- "triggerCount": 0,- "version": "20260721_00",- "tools": [- {- "slug": "STRAVA_ADD_ACTIVITY_LAPS",- "name": "Get Activity Laps",- "description": "Retrieves lap data for a specific Strava activity by its identifier. Laps represent segments of an activity, typically auto-generated during activities like running or cycling based on distance intervals, manual lap button presses, or course segments. Use this action when you need detailed performance metrics for each lap within an activity, including timing, distance, speed, cadence, and elevation data."- },- {- "slug": "STRAVA_CREATE_AN_ACTIVITY",- "name": "Create an Activity",- "description": "Creates a manual activity for an athlete. Requires activity:write scope. This endpoint is for manually entered activities only. To upload activity files (FIT, TCX, GPX), use the Upload Activity endpoint instead. Required parameters: name, sport_type, start_date_local, elapsed_time. Optional parameters: type (deprecated), description, distance, trainer, commute."- },- {- "slug": "STRAVA_EXPLORE_SEGMENTS",- "name": "Explore segments",- "description": "Explore segments within a geographic bounding box. Returns the top 10 segments matching the specified geographic boundary and optional filters. Segments are sections of roads or trails where Strava athletes can compete for times. The response includes segment details like: - id: Unique segment identifier - name: Segment name - climb_category: Climbing difficulty (0=NC/flat to 5=HC/hardest) - avg_grade: Average gradient percentage - distance: Segment length in meters - elev_difference: Elevation gain in meters - start_latlng/end_latlng: Start and end coordinates - elevation_profile: URL to elevation profile image"- },- {- "slug": "STRAVA_EXPORT_ROUTE_GPX",- "name": "Export Route as GPX",- "description": "Exports a Strava route as a GPX (GPS Exchange Format) file. GPX files can be used to import routes into GPS devices, other fitness apps, or mapping software. Requires read_all scope for private routes."- },- {- "slug": "STRAVA_EXPORT_ROUTE_TCX",- "name": "Export Route as TCX",- "description": "Exports a Strava route as a TCX (Training Center XML) file. TCX format is widely supported by GPS devices, fitness watches, and training software like Garmin Connect and TrainingPeaks. The exported file contains the route's waypoints, distance, and elevation profile. Requires read_all scope for private routes."- },- {- "slug": "STRAVA_GET_ACTIVITY",- "name": "Get Activity",- "description": "Retrieves detailed information about a specific activity by its ID. Returns a DetailedActivity object containing comprehensive data including distance, time, elevation, speed, heart rate, power data (if available), segment efforts, laps, splits, and more. Permissions required: - activity:read scope for activities with visibility set to 'everyone' or 'followers_only' - activity:read_all scope for activities with visibility set to 'only_me' The activity must be owned by the authenticated athlete."- },- {- "slug": "STRAVA_GET_ACTIVITY_STREAMS",- "name": "Get activity streams",- "description": "Retrieves time-series stream data for a specific activity. Streams are the raw spatial and sensor data recorded during an activity, including GPS coordinates, speed, heart rate, power, etc. Each stream type returns an array of values that correspond to specific time points during the activity. All requested streams have the same number of data points, aligned by index. Common use cases: - GPS track visualization: request 'latlng', 'altitude', 'time' - Performance analysis: request 'heartrate', 'cadence', 'watts', 'time' - Pace/speed analysis: request 'velocity_smooth', 'distance', 'time' Requires activity:read scope. Requires activity:read_all scope for Only Me (private) activities."- },- {- "slug": "STRAVA_GET_ACTIVITY_ZONES",- "name": "Get Activity Zones",- "description": "Returns the heart rate and power zones of a given activity. This is a Summit/Premium feature that provides zone distribution data showing time spent in each training zone. The response includes an array of ActivityZone objects, typically containing: - Heart rate zones: Time distribution across heart rate training zones - Power zones: Time distribution across power training zones (for cycling with power meter) Requirements: - Strava Summit/Premium subscription for the athlete who owns the activity - activity:read scope for Everyone and Followers visibility activities - activity:read_all scope for Only Me (private) activities Common errors: - 404: Activity not found or not accessible - 403: Insufficient permissions to view activity - 402: Summit subscription required"- },- {- "slug": "STRAVA_GET_ATHLETE_STATS",- "name": "Get athlete stats",- "description": "Returns the activity stats of an athlete, including ride, run, and swim totals for recent (last 4 weeks), year-to-date, and all-time periods. Only includes data from activities set to 'Everyone' visibility. Use get_authenticated_athlete to obtain the required athlete ID."- },- {- "slug": "STRAVA_GET_ATHLETE_ZONES",- "name": "Get athlete zones",- "description": "Retrieves the authenticated athlete's heart rate and power training zones. Use this action when you need to access an athlete's configured training zones for heart rate and power, including zone thresholds and time spent in each zone. This is useful for analyzing training intensity distribution and planning workouts based on the athlete's current zone settings. Requires the 'profile:read_all' OAuth scope for access."- },- {- "slug": "STRAVA_GET_AUTHENTICATED_ATHLETE",- "name": "Get authenticated athlete",- "description": "Retrieves the profile of the currently authenticated Strava athlete. Returns athlete information including name, location, account status, profile photos, and social connections. The level of detail depends on the OAuth scope: - With 'profile:read_all' scope: Returns detailed representation (resource_state=3) including follower counts, measurement preferences, FTP, weight, and equipment. - Without 'profile:read_all' scope: Returns summary representation (resource_state=2) with basic profile information only. This is a read-only endpoint that requires no input parameters."- },- {- "slug": "STRAVA_GET_CLUB",- "name": "Get Club",- "description": "Retrieves detailed information about a specific Strava club by its ID. Returns comprehensive club details including name, description, location (city/state/country), member count, sport type, activity types, club type (casual, racing team, company, etc.), privacy settings, and the authenticated athlete's membership status. Use STRAVA_LIST_ATHLETE_CLUBS to get club IDs for clubs the authenticated athlete belongs to, or use a known club ID from a Strava club URL. Returns a 404 error if the club does not exist."- },- {- "slug": "STRAVA_GET_EQUIPMENT",- "name": "Get equipment",- "description": "Retrieves detailed information about a specific piece of gear/equipment. Returns comprehensive details about bikes or shoes including name, brand, model, total distance, and status (primary/retired). The requesting athlete must own the gear - you cannot view other athletes' equipment. Use Cases: - Get detailed specs and usage statistics for a specific bike or shoe - Check if gear is retired or still in active use - View total distance traveled with specific equipment - Retrieve brand and model information for gear inventory Prerequisites: - Gear ID can be obtained from: 1. Get Authenticated Athlete (bikes/shoes arrays in detailed response) 2. Get Activity (gear_id field shows equipment used for that activity) Note: Gear IDs use prefixes: 'b' for bikes (e.g., 'b12345678'), 'g' for shoes (e.g., 'g12345678')."- },- {- "slug": "STRAVA_GET_ROUTE",- "name": "Get route",- "description": "Retrieve detailed information about a specific Strava route. A route is a planned path that athletes can follow, created via the Strava Route Builder. This endpoint returns comprehensive route data including: - Basic info: name, description, activity type (Ride/Run), sub_type - Geographic data: distance (meters), elevation_gain (meters), start/end coordinates - Map data: polyline for rendering the route path, map_urls - Metadata: created_at, updated_at, estimated_moving_time, private status - Segments: list of segments included in the route - Waypoints: custom waypoints added to the route Note: Requires read_all scope to retrieve private routes."- },- {- "slug": "STRAVA_GET_ROUTE_STREAMS",- "name": "Get route streams",- "description": "Get detailed stream data for a route. Returns raw GPS coordinates, elevation, and distance data points along a route's path. This data can be used for mapping, elevation profiles, and route analysis. Available stream types for routes: - latlng: Latitude/longitude coordinate pairs for mapping the route - distance: Cumulative distance along the route in meters - altitude: Elevation values in meters for elevation profiles Note: Requires read_all scope for private routes. Use list_athlete_routes to find route IDs for the authenticated athlete."- },- {- "slug": "STRAVA_GET_SEGMENT",- "name": "Get segment",- "description": "Retrieve detailed information about a specific Strava segment. A segment is a portion of a road or trail where athletes can compete for times. This endpoint returns comprehensive segment data including: - Basic info: name, activity_type (Ride/Run), city, state, country - Geographic data: distance, average_grade, maximum_grade, elevation_high/low, start/end coordinates - Map data: polyline for rendering the segment path - Statistics: effort_count, athlete_count, star_count - Records: xoms (KOM/QOM times), local_legend info - Athlete-specific stats: personal records (requires read_all scope) Note: read_all scope is required to retrieve athlete-specific segment information or to access private segments."- },- {- "slug": "STRAVA_GET_SEGMENT_EFFORT",- "name": "Get segment effort",- "description": "Retrieves detailed information about a specific segment effort by its unique ID. A segment effort represents an athlete's attempt at a particular segment during an activity. This endpoint returns performance metrics including elapsed time, distance, speed, heart rate, power, and cadence data. The segment effort ID can be obtained from: - Activity details (when using include_all_efforts=True with get_activity) - The list_segment_efforts endpoint for a specific segment Note: Requires an active Strava subscription for the authenticated athlete."- },- {- "slug": "STRAVA_GET_SEGMENT_EFFORT_STREAMS",- "name": "Get segment effort streams",- "description": "Returns stream data for a segment effort completed by the authenticated athlete. Streams provide the raw time-series data associated with a segment effort, such as GPS coordinates, altitude, speed, heart rate, power, etc. All streams for a given segment effort have the same length, with values at each index corresponding to the same point in time. Requires read_all scope. The segment effort must be from an activity owned by the authenticated athlete. Use get_activity with include_all_efforts=true or list_segment_efforts to find segment effort IDs."- },- {- "slug": "STRAVA_GET_SEGMENT_STREAMS",- "name": "Get segment streams",- "description": "Get detailed stream data for a segment. Returns raw GPS, elevation, and distance data points along a segment's route. This data can be used for mapping, elevation profiles, and route analysis. Available stream types: - distance: Distance along the segment in meters - latlng: Latitude/longitude coordinate pairs for mapping - altitude: Elevation values in meters for elevation profiles Note: Only distance, altitude, and latlng stream types are available for segments. Other stream types (like heartrate, watts) are only available for activities. Requires read_all scope for private segments."- },- {- "slug": "STRAVA_GET_UPLOAD",- "name": "Get Upload Status",- "description": "Retrieves the status of an upload by its ID. Use this endpoint to poll the processing status of an uploaded activity file. Uploads are processed asynchronously, so you should poll this endpoint (recommended: no more than once per second) until the activity_id is populated or an error is returned. Requires activity:write scope."- },- {- "slug": "STRAVA_GET_ZONES",- "name": "Get zones",- "description": "Retrieves the authenticated athlete's heart rate and power zones. This endpoint returns the athlete's configured training zones for both heart rate and power, including zone thresholds and time spent in each zone. Note: Requires the 'profile:read_all' OAuth scope. If you receive a 401 Unauthorized error, ensure your connection has this scope."- },- {- "slug": "STRAVA_LIST_ACTIVITY_COMMENTS",- "name": "List activity comments",- "description": "Retrieves comments on a specific Strava activity, sorted oldest first. Returns comment details including the comment text, author information, and timestamps. Supports cursor-based pagination for activities with many comments. Requires OAuth scope: activity:read for Everyone/Followers activities, activity:read_all for Only Me (private) activities. Note: Returns an empty list if the activity has no comments or if you don't have permission to view the activity."- },- {- "slug": "STRAVA_LIST_ACTIVITY_KUDOERS",- "name": "List activity kudoers",- "description": "Returns the athletes who kudoed an activity identified by an identifier. Requires activity:read for Everyone and Followers activities. Requires activity:read_all for Only Me activities."- },- {- "slug": "STRAVA_LIST_ACTIVITY_LAPS",- "name": "List activity laps",- "description": "Retrieves lap data for a specific Strava activity. Laps represent segments of an activity, typically auto-generated during activities like running or cycling based on distance intervals, manual lap button presses, or course segments. Each lap contains detailed metrics including timing, distance, speed, cadence, and power data. Note: Pace zones in lap data are only populated for running activities and are based on the athlete's configured race times. Authorization: - Requires 'activity:read' scope for public (Everyone) and Followers-only activities. - Requires 'activity:read_all' scope for private (Only Me) activities."- },- {- "slug": "STRAVA_LIST_ATHLETE_ACTIVITIES",- "name": "List athlete activities",- "description": "Retrieves a paginated list of activities for the authenticated athlete. Returns activity summaries including name, type, distance, duration, elevation gain, speed, heart rate data, and timestamps. Use 'before' and 'after' parameters to filter activities by date range, and 'page'/'per_page' for pagination. Requires OAuth scope: activity:read for public/followers activities, activity:read_all for private activities. Note: Returns an empty list if no activities match the criteria."- },- {- "slug": "STRAVA_LIST_ATHLETE_CLUBS",- "name": "List athlete clubs",- "description": "Retrieves a paginated list of Strava clubs the authenticated athlete is a member of. Returns club details including id, name, location, member count, sport type, and profile images. Use the club id from the response to fetch detailed club information with other club endpoints. Note: Returns an empty list if the athlete is not a member of any clubs."- },- {- "slug": "STRAVA_LIST_ATHLETE_ROUTES",- "name": "List athlete routes",- "description": "Lists routes created by a specific athlete. Returns an array of Route summaries including id, name, distance, elevation gain, and type. Private routes are filtered out unless the token has read_all scope. Only the authenticated athlete's routes can be accessed; attempting to list another athlete's routes returns 403 Forbidden."- },- {- "slug": "STRAVA_LIST_CLUB_ACTIVITIES",- "name": "List club activities",- "description": "Retrieve recent activities from members of a specific club. IMPORTANT: The authenticated athlete must be a member of the requested club to access this endpoint. Use 'List Athlete Clubs' first to get club IDs the athlete belongs to. Pagination is supported (max 200 activities total). Enhanced Privacy Mode is respected for all activities. Note: Club activities have limited data for privacy - they do not include activity IDs, dates, or full athlete names."- },- {- "slug": "STRAVA_LIST_CLUB_ADMINISTRATORS",- "name": "List club administrators",- "description": "Returns a list of the administrators of a given Strava club. The response includes each administrator's first name, last name (possibly abbreviated), and resource state. For public clubs, this endpoint is accessible without membership. For private clubs, the authenticated user may need to be a member to view administrators. Returns an empty list if the club has no visible administrators or access is restricted."- },- {- "slug": "STRAVA_LIST_CLUB_MEMBERS",- "name": "List club members",- "description": "Returns a list of the athletes who are members of a given club. The authenticated athlete must belong to the requested club to access this endpoint. Results are paginated and can be controlled using page and per_page parameters. Note: Due to privacy settings, some member information may be limited."- },- {- "slug": "STRAVA_LIST_SEGMENT_EFFORTS",- "name": "List segment efforts",- "description": "List the authenticated athlete's efforts on a given segment. Returns all segment efforts for the authenticated athlete on the specified segment, optionally filtered by date range. Segment efforts represent each time an athlete has ridden/run a particular segment. The response includes details like: - id: Unique effort identifier - elapsed_time: Time to complete the segment in seconds - moving_time: Moving time on the segment in seconds - start_date: When the effort started - distance: Distance covered in meters - average_watts: Average power output (if power data available) - average_heartrate: Average heart rate (if HR data available) - pr_rank: Personal record ranking (1=PR, 2=2nd best, 3=3rd best, null otherwise) - kom_rank: King/Queen of Mountain ranking position (if in top 10) Note: This endpoint only returns efforts for segments the authenticated athlete has actually completed. If the athlete hasn't ridden/run a segment, an empty list will be returned."- },- {- "slug": "STRAVA_LIST_STARRED_SEGMENTS",- "name": "List starred segments",- "description": "Returns a list of the authenticated athlete's starred segments with summary details including segment name, distance, elevation, grade, and location. Private segments are filtered out unless requested by a token with read_all scope. Use pagination parameters (page, per_page) to navigate through large result sets."- },- {- "slug": "STRAVA_STAR_SEGMENT",- "name": "Star segment",- "description": "Stars/Unstars the given segment for the authenticated athlete. Requires profile:write scope."- },- {- "slug": "STRAVA_UPDATE_ATHLETE",- "name": "Update Athlete",- "description": "Update the currently authenticated athlete's profile. Currently only supports updating the athlete's weight. Requires profile:write scope."- },- {- "slug": "STRAVA_UPLOAD_ACTIVITY",- "name": "Upload Activity",- "description": "Uploads a new activity file (FIT, TCX, or GPX) to create an activity on Strava. The upload is processed asynchronously. This endpoint returns an upload ID immediately, which can be used with the Get Upload endpoint to check processing status and retrieve the created activity ID once processing completes. Typical processing time is under 2 seconds. Files must be 25MB or smaller and contain actual workout data with timestamps for each trackpoint. Requires the activity:write OAuth scope."- },- {- "slug": "STRAVA_VALIDATE_CREDENTIAL",- "name": "Validate credential",- "description": "Validates Strava API credentials by fetching the authenticated athlete's profile. Returns basic athlete information to confirm the access token is valid and active. Use this action when you need to verify that Strava API credentials are properly configured and have not been revoked or expired. This is a read-only operation that requires no input parameters."- }- ],- "triggers": [],- "authConfigDetails": [- {- "mode": "OAUTH2",- "name": "strava_oauth2",- "fields": {- "auth_config_creation": {- "required": [- {- "name": "client_id",- "displayName": "Client id",- "type": "string",- "description": "Client id of the app",- "required": true,- "default": null- },- {- "name": "client_secret",- "displayName": "Client secret",- "type": "string",- "description": "Client secret of the app",- "required": true,- "default": null- }- ],- "optional": [- {- "name": "oauth_redirect_uri",- "displayName": "Redirect URI",- "type": "string",- "description": "Add this Redirect URL to your app's OAuth allow list.",- "required": false,- "default": "https://backend.composio.dev/api/v1/auth-apps/add"- },- {- "name": "scopes",- "displayName": "Scopes",- "type": "string",- "description": "Scopes to request from the user, comma separated",- "required": false,- "default": "read,activity:read,profile:read_all"- }- ]- },- "connected_account_initiation": {- "required": [],- "optional": []- }- }- }- ]- },{"slug": "streamtime","name": "Streamtime",@@ -304873,6 +315068,176 @@}]},+ {+ "slug": "stytch_mcp",+ "name": "Stytch MCP",+ "logo": "https://logos.composio.dev/api/stytch_mcp",+ "description": "Stytch MCP lets authorized agents configure Stytch projects, redirect URLs, SDK settings, email templates, API keys, and other workspace-management resources.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 21,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "STYTCH_MCP_CREATE_EMAIL_TEMPLATE",+ "name": "Createemailtemplate",+ "description": "Creates an custom email template for the project. Either prebuiltCustomization or customHtmlCustomization is required. If Custom HTML is used, it must contain a {{magic_link_url}} placeholder for the magic link."+ },+ {+ "slug": "STYTCH_MCP_CREATE_PROJECT",+ "name": "Createproject",+ "description": "Create new Stytch Project"+ },+ {+ "slug": "STYTCH_MCP_CREATE_PUBLIC_TOKEN",+ "name": "Createpublictoken",+ "description": "Creates a public token for a project"+ },+ {+ "slug": "STYTCH_MCP_CREATE_REDIRECT_URL",+ "name": "Createredirecturl",+ "description": "Create a redirect URL for your project"+ },+ {+ "slug": "STYTCH_MCP_CREATE_SECRET",+ "name": "Createsecret",+ "description": "Create a new secret for a project"+ },+ {+ "slug": "STYTCH_MCP_DELETE_EMAIL_TEMPLATE",+ "name": "Deleteemailtemplate",+ "description": "Delete a specific email template for a project"+ },+ {+ "slug": "STYTCH_MCP_DELETE_PUBLIC_TOKEN",+ "name": "Deletepublictoken",+ "description": "Delete a specific public token for a project"+ },+ {+ "slug": "STYTCH_MCP_DELETE_REDIRECT_URL",+ "name": "Deleteredirecturl",+ "description": "Delete a redirect URL for a project"+ },+ {+ "slug": "STYTCH_MCP_DELETE_SECRET",+ "name": "Deletesecret",+ "description": "Delete a specific secret for a project"+ },+ {+ "slug": "STYTCH_MCP_GET_ALL_EMAIL_TEMPLATES",+ "name": "Getallemailtemplates",+ "description": "Retrieve all email templates for a project"+ },+ {+ "slug": "STYTCH_MCP_GET_ALL_PUBLIC_TOKENS",+ "name": "Getallpublictokens",+ "description": "Retrieve all active public tokens for a project"+ },+ {+ "slug": "STYTCH_MCP_GET_ALL_REDIRECT_UR_LS",+ "name": "Getallredirecturls",+ "description": "Retrieve all redirect URLs for a project"+ },+ {+ "slug": "STYTCH_MCP_GET_B2_BSDK_CONFIG",+ "name": "Getb2bsdkconfig",+ "description": "Retrieves the SDK Configuration for a B2B project"+ },+ {+ "slug": "STYTCH_MCP_GET_CONSUMER_SDK_CONFIG",+ "name": "Getconsumersdkconfig",+ "description": "Retrieves the SDK Configuration for a Consumer project"+ },+ {+ "slug": "STYTCH_MCP_GET_PASSWORD_STRENGTH_CONFIG",+ "name": "Getpasswordstrengthconfig",+ "description": "Retrieve the password strength configuration for a project"+ },+ {+ "slug": "STYTCH_MCP_LIST_PROJECTS",+ "name": "Listprojects",+ "description": "List all Stytch Projects"+ },+ {+ "slug": "STYTCH_MCP_SET_PASSWORD_STRENGTH_CONFIG",+ "name": "Setpasswordstrengthconfig",+ "description": "Set the password strength configuration for a project"+ },+ {+ "slug": "STYTCH_MCP_UPDATE_B2_BSDK_CONFIG",+ "name": "Updateb2bsdkconfig",+ "description": "Updates the SDK Configuration for a B2B project. This is a DANGEROUS method - when calling this method always call getB2BSDKConfig first to get the current config and then pass the entire config object to this method to avoid overwriting changes unintentionally."+ },+ {+ "slug": "STYTCH_MCP_UPDATE_CONSUMER_SDK_CONFIG",+ "name": "Updateconsumersdkconfig",+ "description": "Updates the SDK Configuration for a Consumer project. This is a DANGEROUS method - when calling this method always call getConsumerSDKConfig first to get the current config and then pass the entire config object to this method to avoid overwriting changes unintentionally."+ },+ {+ "slug": "STYTCH_MCP_UPDATE_EMAIL_TEMPLATE",+ "name": "Updateemailtemplate",+ "description": "Update an email template for a project. Either prebuiltCustomization or customHtmlCustomization is required. If Custom HTML is used, it must contain a {{magic_link_url}} placeholder for the magic link."+ },+ {+ "slug": "STYTCH_MCP_UPDATE_REDIRECT_URL",+ "name": "Updateredirecturl",+ "description": "Update valid types for a redirect URL for a project"+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "stytch_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "openid,profile,email,phone,offline_access,read:project_settings,admin:projects,manage:api_keys,manage:api_keys:test,manage:project_settings,manage:project_data"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "suitedash","name": "Suitedash",@@ -307857,6 +318222,130 @@}]},+ {+ "slug": "tableau",+ "name": "Tableau",+ "logo": "https://logos.composio.dev/api/tableau",+ "description": "Tableau is a visual analytics platform transforming the way we use data to solve problems",+ "category": "analytics",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "TABLEAU_GET_CURRENT_SESSION",+ "name": "Get Current Session",+ "description": "Return the Tableau site and user identity established by the connected PAT, including their LUIDs and the user's current site role."+ },+ {+ "slug": "TABLEAU_GET_SERVER_INFO",+ "name": "Get Server Info",+ "description": "Return the connected Tableau deployment's product, build, and supported REST API versions. This public endpoint checks deployment compatibility but does not validate the PAT."+ },+ {+ "slug": "TABLEAU_GET_WORKBOOK",+ "name": "Get Workbook",+ "description": "Return one Tableau workbook by LUID, including its project, owner, tags, views, and freshness settings when available."+ },+ {+ "slug": "TABLEAU_LIST_DATA_SOURCES",+ "name": "List Data Sources",+ "description": "List published data sources visible to the connected PAT on its signed-in Tableau site, with optional filtering and sorting, one page at a time."+ },+ {+ "slug": "TABLEAU_LIST_GROUPS",+ "name": "List Groups",+ "description": "List groups the connected PAT is permitted to see on its signed-in Tableau site, with optional filtering and sorting, one page at a time."+ },+ {+ "slug": "TABLEAU_LIST_JOBS",+ "name": "List Jobs",+ "description": "List active asynchronous jobs the connected PAT is permitted to see on its signed-in Tableau site, optionally narrowed with a Tableau filter expression, one page at a time."+ },+ {+ "slug": "TABLEAU_LIST_PROJECTS",+ "name": "List Projects",+ "description": "List projects visible to the connected PAT on its signed-in Tableau site, with optional filtering and sorting, one page at a time."+ },+ {+ "slug": "TABLEAU_LIST_USERS",+ "name": "List Users",+ "description": "List users the connected PAT is permitted to see on its signed-in Tableau site, with optional filtering and sorting, one page at a time."+ },+ {+ "slug": "TABLEAU_LIST_VIEWS",+ "name": "List Views",+ "description": "List views visible to the connected PAT on its signed-in Tableau site, with optional filtering, sorting, and usage statistics, one page at a time."+ },+ {+ "slug": "TABLEAU_LIST_WORKBOOKS",+ "name": "List Workbooks",+ "description": "List workbooks visible to the connected PAT on its signed-in Tableau site, with optional filtering and sorting, one page at a time."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "tableau_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "full",+ "displayName": "Tableau Server URL",+ "type": "string",+ "description": "The externally reachable HTTPS origin for the deployment. For Tableau Cloud, use the assigned pod URL, such as https://10ay.online.tableau.com, never generic https://online.tableau.com.",+ "required": true,+ "default": null+ },+ {+ "name": "generic_api_key",+ "displayName": "Personal Access Token Name",+ "type": "string",+ "description": "The PAT name from Tableau My Account Settings > Personal Access Tokens. Create a dedicated PAT for this connection.",+ "required": true,+ "default": null+ },+ {+ "name": "generic_token",+ "displayName": "Personal Access Token Secret",+ "type": "string",+ "description": "The PAT secret displayed once when you create the token. Store it as securely as a password.",+ "required": true,+ "default": null+ }+ ],+ "optional": [+ {+ "name": "version",+ "displayName": "REST API Version",+ "type": "string",+ "description": "The classic Tableau REST API version supported by this deployment, without a leading v.",+ "required": false,+ "default": "3.28"+ },+ {+ "name": "generic_id",+ "displayName": "Site Content URL",+ "type": "string",+ "description": "The permanent browser URL subpath after /site/. Leave empty only for the default site on Tableau Server.",+ "required": false,+ "default": ""+ }+ ]+ }+ }+ }+ ]+ },{"slug": "taggun","name": "Taggun",@@ -307968,6 +318457,97 @@}]},+ {+ "slug": "tailscale",+ "name": "Tailscale",+ "logo": "https://logos.composio.dev/api/tailscale",+ "description": "Tailscale is a secure networking platform for managing tailnets, devices, users, DNS, access policies, services, and other network administration resources.",+ "category": "it operations",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "TAILSCALE_GET_DEVICE",+ "name": "Get Device",+ "description": "Get the full current record for one manageable Tailscale device by ID."+ },+ {+ "slug": "TAILSCALE_GET_DNS_CONFIGURATION",+ "name": "Get DNS Configuration",+ "description": "Return the selected tailnet's combined MagicDNS, nameserver, search-path, and split-DNS configuration."+ },+ {+ "slug": "TAILSCALE_GET_TAILNET_SETTINGS",+ "name": "Get Tailnet Settings",+ "description": "Return current tailnet-wide approval, update, key-duration, HTTPS, routing, logging, and posture settings."+ },+ {+ "slug": "TAILSCALE_LIST_CONFIGURATION_AUDIT_LOGS",+ "name": "List Configuration Audit Logs",+ "description": "Return configuration audit events for an explicit RFC3339 time window in the selected tailnet, optionally filtered by actor, target, or event name."+ },+ {+ "slug": "TAILSCALE_LIST_DEVICE_ROUTES",+ "name": "List Device Routes",+ "description": "Return the subnet routes advertised and currently enabled for a Tailscale device."+ },+ {+ "slug": "TAILSCALE_LIST_TAILNET_DEVICES",+ "name": "List Tailnet Devices",+ "description": "Return all devices in the selected tailnet, including identifiers, names, addresses, tags, authorization state, and connectivity metadata. Supports exact server-side filtering by hostname, tags, and ephemeral state."+ },+ {+ "slug": "TAILSCALE_LIST_USERS",+ "name": "List Users",+ "description": "Return users in the selected tailnet, optionally filtered by membership type or role."+ },+ {+ "slug": "TAILSCALE_SET_DEVICE_AUTHORIZATION",+ "name": "Set Device Authorization",+ "description": "Approve or revoke approval for one device when device approval is enabled on the tailnet."+ },+ {+ "slug": "TAILSCALE_SET_DEVICE_ROUTES",+ "name": "Set Device Routes",+ "description": "Replace the enabled subnet routes for one device with an explicit list of routes. Routes may be enabled before the device advertises them."+ },+ {+ "slug": "TAILSCALE_SET_DEVICE_TAGS",+ "name": "Set Device Tags",+ "description": "Replace all ACL tags assigned to one Tailscale device."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "tailscale_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Access Token",+ "type": "string",+ "description": "Generate a case-sensitive API access token (beginning with tskey-api-) from the Tailscale admin console at Settings > Keys (https://login.tailscale.com/admin/settings/keys). API access tokens expire after 1 to 90 days and inherit the permissions of the user who created them.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "talenthr","name": "Talenthr",@@ -310774,6 +321354,97 @@}]},+ {+ "slug": "thecompaniesapi",+ "name": "The Companies API",+ "logo": "https://logos.composio.dev/api/thecompaniesapi",+ "description": "Search, enrich, and analyze company data, technologies, locations, lists, and related business intelligence.",+ "category": "business intelligence",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 10,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "THECOMPANIESAPI_CREATE_LIST",+ "name": "Create List",+ "description": "Create an empty static company list with email notifications disabled."+ },+ {+ "slug": "THECOMPANIESAPI_DELETE_LIST",+ "name": "Delete List",+ "description": "Permanently delete a company list by ID and return the deleted list record."+ },+ {+ "slug": "THECOMPANIESAPI_ENRICH_JOB_TITLE",+ "name": "Enrich Job Title",+ "description": "Normalize a job title and infer its department and seniority classification."+ },+ {+ "slug": "THECOMPANIESAPI_GET_ACCOUNT_CONTEXT",+ "name": "Get Account Context",+ "description": "Return the connected user, current team, subscription state, and remaining credit balance."+ },+ {+ "slug": "THECOMPANIESAPI_GET_COMPANY",+ "name": "Get Company",+ "description": "Return the cached company profile for an exact domain, optionally in a compact form; this tool does not force a paid refresh."+ },+ {+ "slug": "THECOMPANIESAPI_LIST_COMPANIES_IN_LIST",+ "name": "List Companies In List",+ "description": "Return one page of companies currently contained in a specified company list."+ },+ {+ "slug": "THECOMPANIESAPI_LIST_LISTS",+ "name": "List Lists",+ "description": "Return one page of company lists owned by the connected account."+ },+ {+ "slug": "THECOMPANIESAPI_RENAME_LIST",+ "name": "Rename List",+ "description": "Rename an existing company list without changing its query, synchronization, or notification settings."+ },+ {+ "slug": "THECOMPANIESAPI_SEARCH_COMPANIES",+ "name": "Search Companies",+ "description": "Search the company database with text or structured segmentation conditions and return one page of matching company profiles."+ },+ {+ "slug": "THECOMPANIESAPI_SEARCH_TAXONOMY",+ "name": "Search Taxonomy",+ "description": "Search provider taxonomy values for industries, technologies, or geographic levels and return normalized identifiers for company filters."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "thecompaniesapi_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Token",+ "type": "string",+ "description": "Create or copy a permanent API token from the API Tokens page in The Companies API settings. Paste only the token value; Composio adds the required \"Basic\" authorization prefix. Keep this token secret because it carries your API privileges.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "the_odds_api","name": "The Odds API",@@ -310785,7 +321456,7 @@],"toolCount": 8,"triggerCount": 0,- "version": "20260615_00",+ "version": "20260908_00","tools": [{"slug": "THE_ODDS_API_GET_EVENT_MARKETS",@@ -310795,7 +321466,7 @@{"slug": "THE_ODDS_API_GET_EVENT_ODDS","name": "Get Event Odds",- "description": "Tool to retrieve odds for a specific event. Use after confirming sport key via THE_ODDS_API_GET_SPORTS and event ID via THE_ODDS_API_GET_EVENTS; mismatched values return empty payloads rather than errors."+ "description": "Tool to retrieve odds for a specific event. Use after confirming the sport key via THE_ODDS_API_GET_SPORTS and event ID via THE_ODDS_API_GET_EVENTS. Before supplying markets, call THE_ODDS_API_GET_EVENT_MARKETS with the same event and bookmaker filters and use only returned keys because market availability changes over time."},{"slug": "THE_ODDS_API_GET_EVENTS",@@ -314439,19 +325110,24 @@"authSchemes": ["NO_AUTH"],- "toolCount": 2,+ "toolCount": 3,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{"slug": "TRIVAGO_MCP_TRIVAGO_ACCOMMODATION_RADIUS_SEARCH","name": "Trivago-accommodation-radius-search",- "description": "Search for accommodations and hotels using coordinates on trivago.\n\nUse this tool when you want to find accommodations near a specific location (landmark, neighborhood, or address).\n\nAdditional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-07-30\"}}"+ "description": "Search live hotel and accommodation listings near specific coordinates — a landmark, address, venue, or neighborhood — aggregated via trivago's metasearch of major booking sites. Returns the same, filterable results as trivago-accommodation-search. Use when the user anchors their search to a place rather than a named destination (e.g. \"near the stadium,\" \"within walking distance of X\").\n\nAdditional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-09-04\"}}"},{"slug": "TRIVAGO_MCP_TRIVAGO_ACCOMMODATION_SEARCH","name": "Trivago-accommodation-search",- "description": "Search for accommodations and hotels by destination or point of interest on trivago. Additional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-07-30\"}}"+ "description": "Search live hotel and accommodation listings by destination or point of interest, aggregated via trivago's metasearch of major booking sites. Returns results with price, rating, amenities, and a link per property. Supports date range, guest/room configuration, and filters for star rating, guest rating, and amenities. Use for destination- or place-name-based lodging search.\n\nAdditional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-09-04\"}}"+ },+ {+ "slug": "TRIVAGO_MCP_TRIVAGO_DESTINATION_PRICE_TRENDS",+ "name": "Trivago-destination-price-trends",+ "description": "Forecast monthly hotel price trends for a destination — average, minimum, and maximum nightly rate by star rating, across a date window. Use for planning questions like \"when is the cheapest month to visit X\" or \"how do prices change through the year\" — this is a forecasting tool, not a live-availability search.\n\nAdditional Information: {\"knownInformation\":{\"currentYear\":\"2026\",\"today\":\"2026-09-04\"}}"}],"triggers": [],@@ -316281,6 +326957,87 @@}]},+ {+ "slug": "twenty",+ "name": "Twenty",+ "logo": "https://logos.composio.dev/api/twenty",+ "description": "The #1 Open-Source CRM. Modern, powerful, affordable platform to manage your customer relationships.",+ "category": "crm",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 8,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "TWENTY_BATCH_CREATE_RECORDS",+ "name": "Batch Create CRM Records",+ "description": "Create 1-60 records of one type. Supported standard fields: companies (name, domainName, linkedinLink, annualRevenue, address, accountOwnerId); people (name, emails, linkedinLink, jobTitle, phones, avatarUrl, companyId); opportunities (name, amount, closeDate, stage, companyId, pointOfContactId, ownerId); tasks (title, bodyV2, dueAt, status, assigneeId). Custom fields, workspace-specific enum variants, and upsert are not supported."+ },+ {+ "slug": "TWENTY_CREATE_RECORD",+ "name": "Create CRM Record",+ "description": "Create one company, person, opportunity, or task using the supported standard fields in the parameter schema. Custom fields and workspace-specific enum variants are not supported."+ },+ {+ "slug": "TWENTY_DELETE_RECORD",+ "name": "Delete CRM Record",+ "description": "Permanently delete one company, person, opportunity, or task by UUID. Use only for a specifically identified record; this does not delete by filter or in bulk."+ },+ {+ "slug": "TWENTY_GET_RECORD",+ "name": "Get CRM Record",+ "description": "Get one company, person, opportunity, or task by its Twenty UUID, optionally including direct relations."+ },+ {+ "slug": "TWENTY_LIST_FIELDS",+ "name": "List CRM Fields",+ "description": "List field definitions from the connected Twenty workspace to discover exact field names, types, editability, nullability, uniqueness, and relation targets for schema inspection and filters. Record writes accept only fields exposed by the Create or Update CRM Record parameter schema."+ },+ {+ "slug": "TWENTY_LIST_OBJECTS",+ "name": "List CRM Objects",+ "description": "List standard and custom object definitions in the connected Twenty workspace for schema inspection. Record tools currently support only companies, people, opportunities, and tasks."+ },+ {+ "slug": "TWENTY_LIST_RECORDS",+ "name": "List CRM Records",+ "description": "List companies, people, opportunities, or tasks with Twenty filter syntax, ordering, relation depth, and forward cursor pagination."+ },+ {+ "slug": "TWENTY_UPDATE_RECORD",+ "name": "Update CRM Record",+ "description": "Partially update one company, person, opportunity, or task by UUID using the supported standard fields in the parameter schema; only supplied fields change. Custom fields and workspace-specific enum variants are not supported."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "twenty_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "API Key",+ "type": "string",+ "description": "In your Twenty Cloud workspace, go to Settings -> API & Webhooks -> + Create key. Copy the API key immediately because Twenty displays it only once.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "twittershots","name": "TwitterShots",@@ -318880,6 +329637,706 @@}]},+ {+ "slug": "vantage_mcp",+ "name": "Vantage MCP",+ "logo": "https://logos.composio.dev/api/vantage_mcp",+ "description": "Vantage MCP lets agents analyze authorized cloud costs, reports, resources, tags, budgets, anomalies, and optimization recommendations, and perform supported FinOps management actions.",+ "category": "model context protocol",+ "authSchemes": [+ "DCR_OAUTH"+ ],+ "toolCount": 127,+ "triggerCount": 0,+ "version": "20260902_00",+ "tools": [+ {+ "slug": "VANTAGE_MCP_CREATE_ANNOTATION",+ "name": "Create-annotation",+ "description": "Create an Annotation on one or more Cost Reports for a specific date. Use this tool when a user asks to add a note, explanation, or event marker to Cost Reports."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_BILLING_RULE",+ "name": "Create-billing-rule",+ "description": "Creates a new Billing Rule. Billing rules allow you to adjust, exclude, credit, charge, or apply custom modifications to your cost data.\nThe required fields depend on the rule type:\n- Exclusion rules require charge_type.\n- Adjustment rules require percentage. Optionally accepts service and category to scope the adjustment.\n- Charge and Credit rules require service, category, sub_category, amount, and start_date.\n- Custom rules require sql_query."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_BUDGET",+ "name": "Create-budget",+ "description": "Creates a budget based on the parameters specified. This is useful if you have been tasked with managing budgets\nor you are building a cost report with budgets in mind."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_BUDGET_ALERT",+ "name": "Create-budget-alert",+ "description": "Create a Budget Alert that notifies users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_CANVAS",+ "name": "Create-canvas",+ "description": "Creates a Canvas based on the parameters specified. A Canvas is an AI-generated cost analysis view created from a natural language prompt.\nThe prompt describes what cost data to analyze (e.g. \"Show me monthly costs by provider\"). Creating a canvas triggers an asynchronous refresh to generate the data."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_COST_ALERT",+ "name": "Create-cost-alert",+ "description": "Create a new Cost Alert in Vantage. Cost Alerts are threshold-based spending alerts for one or more Cost Reports.\n\nUse this tool when a user asks to create, add, or set up a cost alert, spending alert, budget alert, threshold alert, or spend-limit notification.\n\nDo not use this for Report Notifications, scheduled report summaries, or recurring Cost Report delivery."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_COST_REPORT",+ "name": "Create-cost-report",+ "description": "Create a new Cost Report in Vantage.\n\nCost Reports are saved queries that can be used to track and analyze spending over time. They can be filtered using VQL (Vantage Query Language) and configured with various display options.\n\nVQL Filtering Guide:\nAll costs originate from a Cost Provider (generally a cloud company like AWS, Azure, Datadog) and then filter on a service that they provide (like EC2, S3, etc).\nA cost provider is required on every VQL query.\nVQL is always in parenthesis. Always use single quotes around names that are being queried.\n\nBasic VQL Syntax:\n- Query on a cost provider: (costs.provider = '<provider name>')\n- Query on a service: (costs.provider = '<provider name>' AND costs.service = '<service name>')\n- Multiple providers: ((costs.provider = 'aws') OR (costs.provider = 'azure'))\n- Multiple services: (costs.provider = 'aws' AND costs.service IN ('AWSQueueService', 'AWSLambda'))\n- Filter by region: (costs.provider = 'aws' AND costs.region = 'us-east-1')\n- Filter by account: (costs.provider = 'aws' AND costs.account_id = '1000000717')\n\nTag Filtering:\n- Tag with specific value: (costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production')\n- Any value of a tag: (costs.provider = 'aws' AND tags.name = 'environment')\n- Resources without a tag: (costs.provider = 'aws' AND tags.name = NULL)\n- Multiple tag values: (costs.provider = 'aws' AND tags.name = 'environment' AND (tags.value = 'dev' OR tags.value = 'staging'))\n\nUse get-myself to find available workspaces and list-cost-providers/list-cost-services to find valid provider and service names for your VQL queries."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_DASHBOARD",+ "name": "Create-dashboard",+ "description": "Create a new Dashboard in Vantage.\n\nDashboards are collections of widgets that visualize cost data. You can optionally attach widgets (by\ntheir widgetable_token) and saved filters, and you can control the time range using either:\n- date_interval (recommended), or\n- start_date + end_date (custom range)\n\nNote: start_date/end_date are incompatible with date_interval.\n\nThe list of supported widgets is:\n- cost reports\n- usage reports\n- resource reports\n- kubernetes efficiency reports\n- financial commitment reports\n- recommendation saved views\n\nThe token returned in the response can be used to link to the Dashboard in the Vantage Web UI:\nhttps://console.vantage.sh/go/<token>"+ },+ {+ "slug": "VANTAGE_MCP_CREATE_FINANCIAL_COMMITMENT_REPORT",+ "name": "Create-financial-commitment-report",+ "description": "Create a new Financial Commitment Report in Vantage.\n\nFinancial Commitment Reports track committed spend and on-demand costs over time. They can be filtered\nusing VQL and grouped by dimensions such as commitment type, service, region, or tags.\n\nVQL Filtering Guide:\nFinancial Commitment Report VQL uses the financial_commitments namespace. A provider filter should be\nincluded in each query, and string values should be wrapped in single quotes.\n\nBasic VQL Syntax:\n- Query on a provider: (financial_commitments.provider = 'aws')\n- Query on a service: (financial_commitments.provider = 'aws' AND financial_commitments.service = 'AmazonEC2')\n- Multiple services: (financial_commitments.provider = 'aws' AND financial_commitments.service IN ('AmazonEC2','AmazonRDS'))\n- Filter by billing account: (financial_commitments.provider = 'aws' AND financial_commitments.provider_account_id = '123456789012')\n- Filter by region: (financial_commitments.provider = 'aws' AND financial_commitments.region = 'us-east-1')\n- Filter by tag: (financial_commitments.provider = 'aws' AND financial_commitments.resource_tags->>'environment' = 'production')\n\nUse get-myself to find available workspaces. Use the VQL for Financial Commitment Reports resource for\nthe full list of available financial_commitments fields and examples."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_FOLDER",+ "name": "Create-folder",+ "description": "Create a folder for organizing Cost Reports or Resource Reports. Set type to CostFolder for Cost Reports or ProviderResourceFolder for Resource Reports."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_NETWORK_FLOW_REPORT",+ "name": "Create-network-flow-report",+ "description": "Creates a saved Network Flow Report for analyzing cloud network traffic by cost or bytes."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_RECOMMENDATION_VIEW",+ "name": "Create-recommendation-view",+ "description": "Create a new Recommendation View in Vantage.\n\nRecommendation Views are saved filters for recommendations. They can be scoped by provider,\nbilling account, cloud account, region, recommendation type, tags, creation date, and minimum\npotential savings.\n\nUse get-myself to find available workspaces. Use list-recommendations to discover valid provider\nIDs, recommendation types, accounts, regions, tags, and savings ranges before creating a view.\n\nFilter examples:\n- AWS recommendations in production: provider_ids [\"aws\"], tag_key \"environment\", tag_value \"production\"\n- High-savings recommendations: min_savings 100\n- Recommendations created in a date range: start_date \"2024-01-01\", end_date \"2024-06-30\""+ },+ {+ "slug": "VANTAGE_MCP_CREATE_REPORT_FORECAST",+ "name": "Create-report-forecast",+ "description": "Create a scenario-model ReportForecast for a Cost Report.\nProvide at least one of scenario_model_tokens or business_metric_token. Use list-scenario-models and list-business-metrics to discover tokens.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the Cost Report."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_REPORT_NOTIFICATION",+ "name": "Create-report-notification",+ "description": "Create a new Report Notification in Vantage.\n\nReport Notifications send scheduled Cost Report summaries to configured users, Slack channels, or Microsoft Teams channels on a daily, weekly, or monthly cadence. Use this tool when a user asks to create, add, or set up scheduled report delivery for an existing Cost Report.\n\nDo not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications. Cost Alerts notify users when spend crosses a configured threshold; Report Notifications deliver scheduled report summaries."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_RESOURCE_REPORT",+ "name": "Create-resource-report",+ "description": "Create a saved Resource Report in Vantage. Resource Reports persist a VQL filter over cloud infrastructure resources so the view can be reopened, shared, added to dashboards, and queried later with list-provider-resources via resource_report_token. Returns the report token; link users to https://console.vantage.sh/go/<token>.\n\nResource Report VQL uses the resources and tags namespaces — not Cost Report costs VQL (create-cost-report). Use list-provider-resources for one-off resource queries without saving a report; use list-resource-reports to browse existing reports."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_SCENARIO_MODEL",+ "name": "Create-scenario-model",+ "description": "Create a ScenarioModel with optional periods and provider/service filters.\nAssign created ScenarioModels to Cost Report forecasts with create-report-forecast or update-report-forecast.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot create models."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_VIRTUAL_TAG_CONFIG",+ "name": "Create-virtual-tag-config",+ "description": "Creates a new Virtual Tag (Virtual Tag Config) in Vantage.\nDo not use this to edit an existing Virtual Tag Config; use update-virtual-tag-config for config settings or value order, and the Virtual Tag Config Value tools for individual values.\n\nVirtual Tag Configs define a derived (virtual) tag key and a set of values determined by VQL filters.\nThis is useful for normalizing cost attribution (e.g., mapping multiple provider tag formats into a\nsingle tag), collapsing noisy tag keys, and optionally overriding provider-supplied tags.\n\nYou can optionally:\n- backfill_until: backfill the virtual tag values to an earliest month\n- collapsed_tag_keys: collapse values for specific underlying tag keys (optionally scoped by provider)\n- values: define named values via VQL filters, optionally linked to Business Metrics and/or cost metrics"+ },+ {+ "slug": "VANTAGE_MCP_CREATE_VIRTUAL_TAG_CONFIG_VALUE",+ "name": "Create-virtual-tag-config-value",+ "description": "Adds a new mapping/value to an existing Virtual Tag Config without replacing its other values. Use this to append a mapping while editing a Virtual Tag; new values are added after existing values."+ },+ {+ "slug": "VANTAGE_MCP_CREATE_WORKSPACE",+ "name": "Create-workspace",+ "description": "Create a new Workspace in Vantage. Workspaces are isolated environments for organizing cost data and access control across teams."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_ANNOTATION",+ "name": "Delete-annotation",+ "description": "Delete an Annotation by its token. This action is irreversible. Use list-annotations to find the annotation_token."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_BILLING_RULE",+ "name": "Delete-billing-rule",+ "description": "Deletes a Billing Rule by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_BUDGET",+ "name": "Delete-budget",+ "description": "Deletes a Budget by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_BUDGET_ALERT",+ "name": "Delete-budget-alert",+ "description": "Delete a Budget Alert by token. This permanently removes the alert without deleting its monitored Budgets."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_CANVAS",+ "name": "Delete-canvas",+ "description": "Deletes a Canvas by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_COST_ALERT",+ "name": "Delete-cost-alert",+ "description": "Deletes a Cost Alert by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_COST_REPORT",+ "name": "Delete-cost-report",+ "description": "Deletes a cost report by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_DASHBOARD",+ "name": "Delete-dashboard",+ "description": "Deletes a Dashboard by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_FINANCIAL_COMMITMENT_REPORT",+ "name": "Delete-financial-commitment-report",+ "description": "Deletes a financial commitment report by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_FOLDER",+ "name": "Delete-folder",+ "description": "Deletes a Folder. Reports within the Folder will not be deleted."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_NETWORK_FLOW_REPORT",+ "name": "Delete-network-flow-report",+ "description": "Deletes a Network Flow Report by token."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_RECOMMENDATION_VIEW",+ "name": "Delete-recommendation-view",+ "description": "Deletes a recommendation view by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_REPORT_FORECAST",+ "name": "Delete-report-forecast",+ "description": "Delete a scenario-model ReportForecast by token. This action is irreversible.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the Cost Report."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_REPORT_NOTIFICATION",+ "name": "Delete-report-notification",+ "description": "Deletes a Report Notification by its token. This action is irreversible and stops the scheduled Cost Report summary from being delivered.\n\nUse this tool when a user asks to delete, remove, disable, or stop a scheduled report notification. Do not use this for deleting Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_RESOURCE_REPORT",+ "name": "Delete-resource-report",+ "description": "Deletes a resource report by its token. This action is irreversible."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_SCENARIO_MODEL",+ "name": "Delete-scenario-model",+ "description": "Delete a ScenarioModel by token. This action is irreversible and regenerates forecasts that referenced the model.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot delete the model."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_VIRTUAL_TAG_CONFIG",+ "name": "Delete-virtual-tag-config",+ "description": "Deletes an entire Virtual Tag Config and all of its mappings/values. To remove only one mapping, use delete-virtual-tag-config-value instead."+ },+ {+ "slug": "VANTAGE_MCP_DELETE_VIRTUAL_TAG_CONFIG_VALUE",+ "name": "Delete-virtual-tag-config-value",+ "description": "Deletes exactly one mapping/value from an existing Virtual Tag Config, not the containing tag. Remaining values are preserved without replacement or reordering."+ },+ {+ "slug": "VANTAGE_MCP_GET_ANOMALY",+ "name": "Get-anomaly",+ "description": "Gets a specific anomaly alert by its token."+ },+ {+ "slug": "VANTAGE_MCP_GET_BILLING_RULE",+ "name": "Get-billing-rule",+ "description": "Gets a specific Billing Rule by its token. Returns details about the rule including its type, configuration, and applicable dates."+ },+ {+ "slug": "VANTAGE_MCP_GET_BUDGET",+ "name": "Get-budget",+ "description": "Gets a specific Budget by its token. Optionally includes performance data showing actual spend vs. budget amounts by period.\nThe token of a budget can be used to link the user to the budget in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<BudgetToken>"+ },+ {+ "slug": "VANTAGE_MCP_GET_BUDGET_ALERT",+ "name": "Get-budget-alert",+ "description": "Get a specific Budget Alert by token. Budget Alerts monitor Budget objects."+ },+ {+ "slug": "VANTAGE_MCP_GET_BUSINESS_METRIC",+ "name": "Get-business-metric",+ "description": "Get a specific BusinessMetric by token.\nBusinessMetrics can be attached to Cost Reports for per-unit cost analysis, and their values can be retrieved with get-business-metric-values or get-business-metric-forecasted-values."+ },+ {+ "slug": "VANTAGE_MCP_GET_BUSINESS_METRIC_FORECASTED_VALUES",+ "name": "Get-business-metric-forecasted-values",+ "description": "Get forecasted values for a BusinessMetric.\nValues are returned in descending date order by the Vantage API and can include optional labels.\nUse start_date to limit results to values on or after a YYYY-MM-DD date.\nThis endpoint is paginated. If the user asks for all values, complete data, or values for a date range such as a month, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false before answering.\nThe API only supports a start_date lower bound. For bounded ranges, such as a specific month, fetch all pages from the requested start date and then filter the returned values to the requested end date locally."+ },+ {+ "slug": "VANTAGE_MCP_GET_BUSINESS_METRIC_VALUES",+ "name": "Get-business-metric-values",+ "description": "Get historical values for a BusinessMetric.\nValues default to monthly sums grouped by label. Use day for daily sums or raw to preserve original timestamps, including hourly values; binned sums may not suit gauges or percentages.\nValues are returned in descending date order by the Vantage API and can include optional labels.\nWhen a request depends on labels but exact values are not confirmed, call list-business-metric-labels first and pass the selected values through label_values. Skip label discovery when exact values are already supplied.\nUse start_date to limit results to values on or after a YYYY-MM-DD date.\nThis endpoint is paginated. If the user asks for all values, complete data, or values for a date range such as a month, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false before answering.\nThe API only supports a start_date lower bound. For bounded ranges, such as a specific month, fetch all pages from the requested start date and then filter the returned values to the requested end date locally."+ },+ {+ "slug": "VANTAGE_MCP_GET_CANVAS",+ "name": "Get-canvas",+ "description": "Gets a specific Canvas by its token. Returns the canvas details including its title, prompt, status, and structured table data.\nThe token of a canvas can be used to link the user to the canvas in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CanvasToken>"+ },+ {+ "slug": "VANTAGE_MCP_GET_COST_ALERT",+ "name": "Get-cost-alert",+ "description": "Gets a specific Cost Alert by its token.\n\nUse this tool when you already have a cost alert token, such as one returned by list-cost-alerts or referenced in Vantage. Cost Alerts are threshold-based spending alerts for Cost Reports.\n\nDo not use this for Report Notifications, scheduled report summaries, or recurring Cost Report delivery."+ },+ {+ "slug": "VANTAGE_MCP_GET_COST_ALERT_EVENT",+ "name": "Get-cost-alert-event",+ "description": "Gets a specific Cost Alert event by its token. Use after list-cost-alert-events when you need the full trigger record."+ },+ {+ "slug": "VANTAGE_MCP_GET_COST_PROVIDER_ACCOUNTS",+ "name": "Get-cost-provider-accounts",+ "description": "Get Cost Provider Accounts in a workspace with human-readable titles.\nUseful for mapping account IDs to names, or looking up an account_id for VQL."+ },+ {+ "slug": "VANTAGE_MCP_GET_COST_REPORT",+ "name": "Get-cost-report",+ "description": "Gets a specific cost report by its token. The token of a report can be used to generate a link to the report in the Vantage Web UI: https://console.vantage.sh/go/<token>\nThe same token can be used with the get-cost-report-forecast tool to retrieve forecasted future costs for the report."+ },+ {+ "slug": "VANTAGE_MCP_GET_COST_REPORT_FORECAST",+ "name": "Get-cost-report-forecast",+ "description": "Given a Cost Report Token, Vantage can forecast the costs for a given time range. Vantage will return costs that are *predicted*, but have not yet been actually incurred.\nIf the user does not set a date, best to pick the next month as the default.\nThe report token can be used to link the user to the report in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CostReportToken>"+ },+ {+ "slug": "VANTAGE_MCP_GET_DASHBOARD",+ "name": "Get-dashboard",+ "description": "Gets a specific dashboard by its token. The token of a dashboard can be used to generate a link to the dashboard in the Vantage Web UI: https://console.vantage.sh/go/<token>"+ },+ {+ "slug": "VANTAGE_MCP_GET_FINANCIAL_COMMITMENT_REPORT",+ "name": "Get-financial-commitment-report",+ "description": "Gets a specific financial commitment report by its token.\n\nUse this tool when you already have a financial commitment report token, such as one returned by\nVantage or referenced in the Vantage console. The response includes the report's title, workspace,\ndate range, grouping, cost scope, and filter configuration."+ },+ {+ "slug": "VANTAGE_MCP_GET_FOLDER",+ "name": "Get-folder",+ "description": "Gets a specific Folder by its token."+ },+ {+ "slug": "VANTAGE_MCP_GET_MYSELF",+ "name": "Get-myself",+ "description": "Get data that is available to the current auth token.\nThis includes the list of Workspaces they have access to.\n\ndefault_workspace_token: The token of the workspace that is set as the default for the user and can be used for queries unless told otherwise."+ },+ {+ "slug": "VANTAGE_MCP_GET_NETWORK_FLOW_REPORT",+ "name": "Get-network-flow-report",+ "description": "Gets a saved Network Flow Report by token. Open in the console at https://console.vantage.sh/go/<token>."+ },+ {+ "slug": "VANTAGE_MCP_GET_PROVIDER_RESOURCE",+ "name": "Get-provider-resource",+ "description": "Get detailed information about a specific provider resource using its token or UUID.\n\nThis returns comprehensive details about the resource including:\n- Resource metadata (instance type, size, configuration, etc.)\n- Account and billing account information\n- Provider and region details\n- Creation timestamp\n- Optional cost breakdown by category\n\nThe resource_token can be either a Vantage token (starting with prvdr_rsrc) or the resource's UUID/ARN from the cloud provider.\nSet include_cost to true to get cost information broken down by category."+ },+ {+ "slug": "VANTAGE_MCP_GET_RECOMMENDATION_DETAILS",+ "name": "Get-recommendation-details",+ "description": "Get comprehensive details about a specific cost optimization recommendation using its unique token.\n\nThis tool provides in-depth information about a single recommendation including:\n- Full description of the optimization opportunity\n- Exact potential cost savings amount and currency\n- Current status (open, resolved, dismissed)\n- Category and type of recommendation (e.g., ec2_rightsizing_recommender, unused_financial_commitments)\n- Cloud provider and provider account information\n- Service being optimized (e.g., EC2, RDS, S3)\n- Number of resources that would be affected\n- Creation and last updated timestamps\n- Additional metadata specific to the recommendation type\n\nUse this tool after getting a recommendation token from list-recommendations to understand exactly what optimization is being suggested and the potential impact.\n\nThe recommendation token can also be used with get-recommendation-resources to see the specific infrastructure resources involved."+ },+ {+ "slug": "VANTAGE_MCP_GET_RECOMMENDATION_RESOURCE_DETAILS",+ "name": "Get-recommendation-resource-details",+ "description": "Get comprehensive details about a specific infrastructure resource within a cost optimization recommendation, including the exact actions recommended for that resource.\n\nThis tool provides the deepest level of detail about a single resource that's part of a recommendation. The response includes:\n- Complete resource identification (resource ID, type, region, account)\n- Current configuration and specifications\n- Resource utilization metrics and patterns\n- Specific recommendation actions for this resource\n- Estimated cost savings for implementing the recommendations\n- CLI command for remediating the recommendation\n- Implementation complexity and effort estimates\n- Detailed metadata specific to the resource type and recommendation category\n\nUse this tool when you need to understand exactly what should be done with a specific resource. For example:\n- For rightsizing recommendations: shows current vs. recommended instance types, CPU/memory utilization data\n- For unused resources: shows usage patterns, last activity, and safe termination recommendations\n- For storage optimization: shows current vs. recommended volume types, IOPS usage, throughput patterns\n- For Reserved Instance recommendations: shows usage patterns, recommended commitment levels\n\nThis is the most granular level of recommendation data available and is essential for making informed decisions about implementing specific optimizations.\n\nYou must have both the recommendation token (from list-recommendations) and the resource token (from get-recommendation-resources) to use this tool."+ },+ {+ "slug": "VANTAGE_MCP_GET_RECOMMENDATION_RESOURCES",+ "name": "Get-recommendation-resources",+ "description": "Get a paginated list of all infrastructure resources affected by a specific cost optimization recommendation.\n\nThis tool returns the actual cloud resources (instances, volumes, load balancers, etc.) that are involved in a recommendation. Each resource entry includes:\n- Resource token (unique identifier for the specific resource)\n- Resource type (e.g., EC2 instance, EBS volume, RDS instance)\n- Resource identifier (instance ID, volume ID, etc.)\n- Current configuration details\n- Resource-specific metadata\n\nUse this tool after getting recommendation details to see exactly which resources need attention. For example:\n- For EC2 rightsizing recommendations: shows the specific instances that are over-provisioned\n- For unused resource recommendations: shows the idle instances, volumes, or load balancers\n- For Reserved Instance recommendations: shows the usage patterns and instance families\n- For storage optimization: shows the volumes that could be optimized\n\nEach resource has its own token that can be used with get-recommendation-resource-details to get comprehensive information about that specific resource and what actions are recommended.\n\nUse pagination (page parameter) to navigate through large numbers of affected resources."+ },+ {+ "slug": "VANTAGE_MCP_GET_RECOMMENDATION_VIEW",+ "name": "Get-recommendation-view",+ "description": "Gets a specific recommendation view by its token."+ },+ {+ "slug": "VANTAGE_MCP_GET_REPORT_FORECAST",+ "name": "Get-report-forecast",+ "description": "Get a specific scenario-model ReportForecast by token.\nUse list-report-forecasts to discover tokens for a Cost Report.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled."+ },+ {+ "slug": "VANTAGE_MCP_GET_REPORT_NOTIFICATION",+ "name": "Get-report-notification",+ "description": "Gets a specific Report Notification by its token.\n\nUse this tool when you already have a report notification token, such as one returned by list-report-notifications or referenced in Vantage. The response includes the notification title, Cost Report token, recipients, delivery channels, frequency, and tracked change type.\n\nDo not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications."+ },+ {+ "slug": "VANTAGE_MCP_GET_RESOURCE_REPORT",+ "name": "Get-resource-report",+ "description": "Gets a specific resource report by its token. The token of a report can be used to generate a link to the resource report in the Vantage Web UI: https://console.vantage.sh/go/<token>"+ },+ {+ "slug": "VANTAGE_MCP_GET_SCENARIO_MODEL",+ "name": "Get-scenario-model",+ "description": "Get a specific ScenarioModel by token.\nScenarioModels define future-cost adjustments that can be assigned to Cost Report forecasts.\nUse list-scenario-models to discover tokens. The token can also be used with update-scenario-model, delete-scenario-model, and report-forecast tools.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled."+ },+ {+ "slug": "VANTAGE_MCP_GET_TEAM",+ "name": "Get-team",+ "description": "Gets a specific team with its token."+ },+ {+ "slug": "VANTAGE_MCP_GET_TEAMS",+ "name": "Get-teams",+ "description": "Return all Teams that the user has access to."+ },+ {+ "slug": "VANTAGE_MCP_GET_USER",+ "name": "Get-user",+ "description": "Gets a specific User by their token. Use get-users to discover user tokens in the workspace."+ },+ {+ "slug": "VANTAGE_MCP_GET_USERS",+ "name": "Get-users",+ "description": "Return all Users that the user can see in the workspace.\n\nRequires account owner permissions; non-owners receive 403 from the API."+ },+ {+ "slug": "VANTAGE_MCP_GET_VIRTUAL_TAG_CONFIG",+ "name": "Get-virtual-tag-config",+ "description": "Returns one existing Virtual Tag (Virtual Tag Config) with its complete ordered mappings/values. Use this to show all values on a tag and discover value tokens before editing or reordering."+ },+ {+ "slug": "VANTAGE_MCP_GET_VIRTUAL_TAG_CONFIG_VALUE",+ "name": "Get-virtual-tag-config-value",+ "description": "Returns one mapping/value from an existing Virtual Tag Config, including its filter and allocation settings. Use this to inspect one mapping before editing it."+ },+ {+ "slug": "VANTAGE_MCP_GET_WORKSPACE",+ "name": "Get-workspace",+ "description": "Gets a specific Workspace by its token. Workspaces are isolated environments within Vantage for organizing cost data and access control across teams."+ },+ {+ "slug": "VANTAGE_MCP_LIST_ANNOTATIONS",+ "name": "List-annotations",+ "description": "List report annotations available to the authenticated Vantage access token, ordered from newest to oldest. Optionally filter annotations to a specific Cost Report."+ },+ {+ "slug": "VANTAGE_MCP_LIST_ANOMALIES",+ "name": "List-anomalies",+ "description": "Given a token of a Cost Report, look for anomalies in the report. You may optionally pass a Provider, like AWS to filter on. If you do pass a Provider, you can futher filter on a Service, like EC2 or S3.\nThe report token can be used to link the user to the report in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CostReportToken>"+ },+ {+ "slug": "VANTAGE_MCP_LIST_AUDIT_LOGS",+ "name": "List-audit-logs",+ "description": "List audit logs visible to the authenticated Vantage access token. Audit logs provide a chronological history of supported changes to user-facing resources in Vantage, such as cost reports, virtual tags, segments, recommendation commitments, and other workspace-related objects.\n\nResults are returned in reverse chronological order (newest first).\n\nEach audit log entry can include:\n- The audit log token\n- The affected object's token, type, and title\n- The event (`record_created`, `record_updated`, or `record_destroyed`)\n- The source of the action (`console`, `api`, or `finops_agent`)\n- The user display name, when available\n- The workspace title and workspace token, when available\n- The timestamp when the audit log was created\n- Field-level change data in `changed_values` and `unchanged_values`\n\nAudit logs commonly include actions such as:\n- Creating, updating, or deleting cost reports\n- Modifying report filters or related configuration\n- Creating, updating, or deleting virtual tags\n- Updating recommendation commitments\n- Creating, updating, or deleting segments\n\nUse pagination with the `page` parameter starting at 1. You can also pass `limit`; if omitted, the API defaults to 100 results per page.\n\nAudit logs can be filtered by:\n- `user`: numeric user ID associated with the action\n- `workspace_token`: workspace token\n- `action`: `create`, `update`, or `delete`\n- `object_type`: `cost_report`, `virtual_tag`, `recommendation_commitment`, or `segment`\n- `object_name`: exact object title\n- `object_token`: audited object token\n- `source`: `console`, `api`, or `finops_agent`\n- `start_date` and `end_date`: YYYY-MM-DD dates such as `2024-06-01`\n- `token`: audit log token\n\nUse cases for audit logs include:\n- Compliance and security review\n- Debugging change history\n- Change management for reports and configuration\n- Monitoring actions taken through the API or the Finops Agent"+ },+ {+ "slug": "VANTAGE_MCP_LIST_BILLING_RULES",+ "name": "List-billing-rules",+ "description": "List all billing rules available in the Vantage account. Billing rules allow you to adjust, exclude, or add charges to your cost data.\nUse the page value of 1 to start."+ },+ {+ "slug": "VANTAGE_MCP_LIST_BUDGET_ALERTS",+ "name": "List-budget-alerts",+ "description": "List Budget Alerts in Vantage. Budget Alerts notify users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window."+ },+ {+ "slug": "VANTAGE_MCP_LIST_BUDGETS",+ "name": "List-budgets",+ "description": "List all budgets available in the Vantage account. Budgets help track spending against predefined limits.\nUse the page value of 1 to start.\nA budget is built against a Cost Report. The Budget objects returned by this tool will have a \"cost_report_token\" field that contains the token of the Cost Report. The Cost Report has the \"filter\" field to know what is the range of providers & services that the budget is tracking.\nWhen a user is looking at a Cost Report for a specific date range, they can decide if the providers and services spend is higher than desired by looking at the budgets for that report and the date range of the budget.\nThe token of a budget can be used to link the user to the budget in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<BudgetToken>"+ },+ {+ "slug": "VANTAGE_MCP_LIST_BUSINESS_METRIC_LABELS",+ "name": "List-business-metric-labels",+ "description": "List distinct label values for a BusinessMetric. For multi-label metrics, values are flattened across label keys.\nUse this before get-business-metric-values when a label-dependent request does not provide confirmed exact label values.\nThis endpoint is paginated. If the user needs the complete set of labels, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false."+ },+ {+ "slug": "VANTAGE_MCP_LIST_BUSINESS_METRICS",+ "name": "List-business-metrics",+ "description": "List all BusinessMetrics available to the current Vantage API token.\nUse page 1 when calling this tool for the first time. If the user asks for all BusinessMetrics or needs to search across the full set, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false.\nBusinessMetrics represent business KPIs, such as requests, users, or revenue, that can be attached to Cost Reports for per-unit cost analysis.\nThe token of a BusinessMetric can be used with get-business-metric, list-business-metric-labels, get-business-metric-values, and get-business-metric-forecasted-values."+ },+ {+ "slug": "VANTAGE_MCP_LIST_CANVASES",+ "name": "List-canvases",+ "description": "List all saved Canvases available in the Vantage account. Canvases are AI-generated cost analysis views created from natural language prompts.\nUse the page value of 1 to start.\nThe token of a canvas can be used to link the user to the canvas in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CanvasToken>"+ },+ {+ "slug": "VANTAGE_MCP_LIST_COST_ALERT_EVENTS",+ "name": "List-cost-alert-events",+ "description": "List events for a Cost Alert. Events are individual alert trigger records and can be filtered by Cost Report token."+ },+ {+ "slug": "VANTAGE_MCP_LIST_COST_ALERTS",+ "name": "List-cost-alerts",+ "description": "List Cost Alerts available in the Vantage account. Cost Alerts are threshold-based spending alerts for Cost Reports.\n\nUse this tool when a user asks to list, show, view, or find cost alerts, spending alerts, budget alerts, threshold alerts, or spend-limit notifications.\n\nDo not use this for Report Notifications, scheduled report summaries, or recurring Cost Report delivery."+ },+ {+ "slug": "VANTAGE_MCP_LIST_COST_INTEGRATIONS",+ "name": "List-cost-integrations",+ "description": "List all cost provider integrations available to provide costs data from and their associated accounts.\nIntegrations are the cost providers that Vantage is configured to connect to and pull cost data from.\nIf a user wants to see their providers in the Vantage Web UI, they can visit https://console.vantage.sh/settings/integrations\n\nNote that when 'provider' is 'custom_provider', that has a special case. When doing a VQL query for custom provider, use the 'token' you get back. Here is an example, where the token of the custom provider is \"accss_crdntl_07171984\": \n (costs.provider = 'custom_provider:accss_crdntl_07171984')"+ },+ {+ "slug": "VANTAGE_MCP_LIST_COST_PROVIDERS",+ "name": "List-cost-providers",+ "description": "List of cost providers available to query for a given Workspace. Can be used to filter costs down to a specific provider in VQL queries."+ },+ {+ "slug": "VANTAGE_MCP_LIST_COST_REPORTS",+ "name": "List-cost-reports",+ "description": "List all cost reports available. Cost reports are already created reports authored by a user in Vantage. If the user isn't asking about a specific report, it's better to use the query-costs tool.\nWhen you first call this function, use the \"Page\" parameter of 1.\nThe 'Title' of a report is a good way to know what the report is about.\nThe 'filter' of a report also gives clues to the data it provides.\nThe 'token' of a report is a unique identifier for the report. It can be used to generate a link to the report in the Vantage Web UI. If a user wants to see a report, you can link them like this: https://console.vantage.sh/go/<token>\nVantage offers data related to a cost report: Forecasts. The same report token can be used on the get-cost-report-forecast tool and Vantage will forecast future costs."+ },+ {+ "slug": "VANTAGE_MCP_LIST_COSTS",+ "name": "List-costs",+ "description": "List the cost items inside a report. The Token of a Report must be provided. Use the page value of 1 to start.\nThe report token can be used to link the user to the report in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CostReportToken>\n\nThe DateBin parameter controls the time granularity of returned results.\nWhen DateBin=day you get a record for each service spend on that day. For DateBin=week you get one entry per week,\nwith the accrued_at field set to the first day of the week, but the spend item represents spend for a full week.\nSame with DateBin=month, each record returned covers a month of data. This lets you get answers with processing fewer\nrecords. If omitted, the API uses the cost report's configured date bin, or day if the report has no override.\n\nCost settings (credits, refunds, discounts, tax, amortization, etc.) default to the report's own settings.\nOnly provide these parameters if you need to override the report's defaults.\n\nUse settings_aggregate_by to choose the metric: cost (default), usage, or count.\nWhen aggregate_by is count, the response includes total_count and counts (date-binned distinct Group By permutation counts for the full requested period). Count is not supported for segment reports."+ },+ {+ "slug": "VANTAGE_MCP_LIST_COST_SERVICES",+ "name": "List-cost-services",+ "description": "List cost service display names for a workspace. These names may NOT match VQL costs.service identifiers used in query-costs filters.\nDo not copy names from this tool directly into VQL. Use vql_info or costs.service values from a broad query-costs probe instead."+ },+ {+ "slug": "VANTAGE_MCP_LIST_DASHBOARDS",+ "name": "List-dashboards",+ "description": "List all dashboards available in the Vantage account. Dashboards provide visualizations of cost data.\nUse the page value of 1 to start.\nThe token of a dashboard can be used to link the user to the dashboard in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<token>"+ },+ {+ "slug": "VANTAGE_MCP_LIST_FINANCIAL_COMMITMENT_REPORTS",+ "name": "List-financial-commitment-reports",+ "description": "List all financial commitment reports available in the Vantage account.\nUse the page value of 1 to start."+ },+ {+ "slug": "VANTAGE_MCP_LIST_FOLDERS",+ "name": "List-folders",+ "description": "List folders for Cost Reports or Resource Reports, optionally filtering by title, Workspace, or folder type. Use CostFolder for Cost Report folders and ProviderResourceFolder for Resource Report folders; folder tokens link to https://console.vantage.sh/go/<token>."+ },+ {+ "slug": "VANTAGE_MCP_LIST_NETWORK_FLOW_REPORTS",+ "name": "List-network-flow-reports",+ "description": "Lists saved Network Flow Reports. Use get-network-flow-report for a report's configuration."+ },+ {+ "slug": "VANTAGE_MCP_LIST_PROVIDER_RESOURCES",+ "name": "List-provider-resources",+ "description": "List infrastructure provider resources (instances, volumes, load balancers, etc.) from your cloud accounts.\nResources can be fetched either from a specific Resource Report or by using VQL filters.\n\nWhen using a resource_report_token, you get the pre-filtered resources from that report.\nWhen using VQL filters with workspace_token, you can dynamically query resources across your infrastructure.\nProvide either resource_report_token or filter (not both). When using filter, workspace_token is required.\n\nVQL for Resource Reports enables filtering using two primary namespaces:\n\n**Resources Namespace** - Access infrastructure attributes:\n- resources.provider (AWS, GCP, Azure, etc.)\n- resources.region (geographic location codes)\n- resources.account_id and resources.provider_account_id\n- resources.type (resource classification)\n- resources.label and resources.uuid (identifiers)\n- resources.metadata (detailed resource properties using ->> operator, e.g., resources.metadata->>'architecture')\n\n**Tags Namespace** - Tag-based filtering:\n- tags.name (tag key)\n- tags.value (tag content)\n\nVQL supports standard logical operators (AND, OR) and specialized functions:\n- Pattern Matching: LIKE and NOT LIKE for substring searches\n- Comparisons: IN/NOT IN for list evaluation; !=, <, >, <=, >= for values\n- Metadata Queries: >> operator for resource metadata (e.g., resources.metadata->>'architecture')\n\nVQL Representation of Resource Types:\n\n| Provider | VQL Representation | Friendly Name |\n|---|---|---|\n| AWS | aws_auto_scaling_group | Auto Scaling Group |\n| AWS | aws_cloudtrail | CloudTrail |\n| AWS | aws_cloudwatch_log_group | CloudWatch Log Group |\n| AWS | aws_db_instance | RDS Instance (NOT aws_rds_instance) |\n| AWS | aws_db_snapshot | RDS Snapshot (NOT aws_rds_snapshot) |\n| AWS | aws_docdb_cluster_instance | DocumentDB Cluster Instance |\n| AWS | aws_dynamodb_table | DynamoDB Table |\n| AWS | aws_ebs_volume | EBS Volume |\n| AWS | aws_instance | EC2 Instance (NOT aws_ec2_instance) |\n| AWS | aws_ec2_managed_prefix_list | EC2 Managed Prefix List |\n| AWS | aws_ec2_reserved_instance | EC2 Reserved Instance |\n| AWS | aws_ecs_service | ECS Service |\n| AWS | aws_ecs_task_definition | ECS Task Definition |\n| AWS | aws_egress_only_internet_gateway | Egress-Only Internet Gateway |\n| AWS | aws_eip | Elastic IP |\n| AWS | aws_elasticache_cluster | ElastiCache Cluster |\n| AWS | aws_elasticsearch_domain | Elasticsearch Domain |\n| AWS | aws_flow_log | Flow Log |\n| AWS | aws_glacier_vault | Glacier Vault |\n| AWS | aws_instance_snapshot | EC2 Instance Snapshot (NOT aws_ebs_snapshot) |\n| AWS | aws_internet_gateway | Internet Gateway |\n| AWS | aws_kms_key | KMS Key |\n| AWS | aws_lambda_function | Lambda Function |\n| AWS | aws_lb | Load Balancer |\n| AWS | aws_nat_gateway | NAT Gateway |\n| AWS | aws_rds_reserved_instance | RDS Reserved Instance |\n| AWS | aws_redshift_cluster | Redshift Cluster |\n| AWS | aws_s3_bucket | S3 Bucket |\n| AWS | aws_savings_plan | Savings Plan |\n| AWS | aws_secretsmanager_secret | Secrets Manager Secret |\n| AWS | aws_vpc | VPC |\n| AWS | aws_vpc_endpoint | VPC Endpoint |\n| AWS | aws_vpn_gateway | VPN Gateway |\n\nExample VQL queries:\n- Multi-provider: (resources.provider IN ('aws', 'gcp'))\n- Regional: (resources.provider = 'aws' AND resources.region = 'us-east-1')\n- Resource type: (resources.provider = 'aws' AND resources.type = 'aws_instance')\n- Metadata: (resources.provider = 'aws' AND resources.metadata->>'architecture' = 'x86_64')\n- Tags: (resources.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production')\n- Untagged resources: (resources.provider = 'aws' AND tags.name = NULL)\n\nSet include_cost to true to get cost breakdowns by category for each resource.\nUse the page parameter starting with 1 for pagination.\n\nResources include metadata specific to their type (EC2 instances show instance type, EBS volumes show size, etc.).\nEach resource has a unique token that can be used to get more details or link to the Vantage Web UI."+ },+ {+ "slug": "VANTAGE_MCP_LIST_RECOMMENDATIONS",+ "name": "List-recommendations",+ "description": "List all cost optimization recommendations available in the Vantage account. Recommendations are AI-powered suggestions that help identify opportunities to reduce costs and optimize cloud spending across your infrastructure.\n\nUse the page value of 1 to start pagination.\n\nRecommendations include various types such as:\n- EC2 rightsizing (resize overprovisioned instances)\n- Unused financial commitments (unused Reserved Instances or Savings Plans)\n- Idle resources (running but unused instances, volumes, load balancers)\n- Storage optimization (EBS volume type recommendations)\n- Reserved Instance and Savings Plan purchase recommendations\n\nEach recommendation includes:\n- Potential cost savings amount\n- Description of what can be optimized\n- Provider and service information\n- Number of resources affected\n- Current status (open, resolved, dismissed)\n\nRecommendations can be filtered by:\n- Status (open shows active recommendations, resolved shows implemented ones, dismissed shows ignored ones)\n- Cloud provider via provider (single) or provider_ids (multiple; requires workspace_token) — only use these when the user explicitly specifies cloud providers; do not infer or default to all providers\n- Specific workspace via workspace_token\n- Provider account ID via provider_account_id (single) or account_ids (multiple; requires workspace_token)\n- Billing account via billing_account_ids (requires workspace_token)\n- Region via regions (requires workspace_token)\n- Tag key/value pair via tag_key + tag_value (both required together; requires workspace_token) — use this when users ask about recommendations for a specific virtual tag, e.g. \"recommendations for department=engineering\"\n- Date range via start_date + end_date in YYYY-MM-DD format (both required together; requires workspace_token)\n- Minimum monthly potential savings via min_savings\n- Recommendation type via type (case-insensitive fuzzy matching; e.g. \"AWS recommendations\" -> type=aws; \"EC2 rightsizing\" -> type=aws:ec2:rightsizing)\n\nThe token of each recommendation can be used with other recommendation tools to get detailed information and see specific resources affected.\n\nFor users to view and manage recommendations in the Vantage Web UI, they can visit https://console.vantage.sh/recommendations"+ },+ {+ "slug": "VANTAGE_MCP_LIST_RECOMMENDATION_VIEWS",+ "name": "List-recommendation-views",+ "description": "List all recommendation views available in the Vantage account. Recommendation views are saved filters for cost optimization recommendations.\nUse the page value of 1 to start.\nThe title of a recommendation view is a good way to understand what optimization scope it represents.\nThe token of a recommendation view is its unique identifier and can be used to link the user to the view in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<token>\nThe workspace token, date range, providers, accounts, regions, and tag fields provide additional context about which recommendations are included in the view."+ },+ {+ "slug": "VANTAGE_MCP_LIST_REPORT_FORECASTS",+ "name": "List-report-forecasts",+ "description": "List scenario-model ReportForecasts for a Cost Report.\nReportForecasts assign ScenarioModels (and optionally a BusinessMetric) to a Cost Report for planning views.\nUse page 1 when calling this tool for the first time. Keep calling with pagination.nextPage until pagination.hasNextPage is false when listing all forecasts.\nThe token of a ReportForecast can be used with get-report-forecast, update-report-forecast, and delete-report-forecast.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled."+ },+ {+ "slug": "VANTAGE_MCP_LIST_REPORT_NOTIFICATIONS",+ "name": "List-report-notifications",+ "description": "List Report Notifications available in the Vantage account. Report Notifications are scheduled deliveries of Cost Report summaries to users, Slack channels, or Microsoft Teams channels.\n\nUse this tool when a user asks to list, show, view, or find scheduled report notifications or recurring Cost Report summaries. Use the page value of 1 to start.\n\nDo not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications. Cost Alerts are threshold-based spending alerts; Report Notifications are scheduled report deliveries."+ },+ {+ "slug": "VANTAGE_MCP_LIST_RESOURCE_REPORT_COLUMNS",+ "name": "List-resource-report-columns",+ "description": "List available columns for a resource type. The resource_type is a required parameter, and must be a valid VQL resource type name."+ },+ {+ "slug": "VANTAGE_MCP_LIST_RESOURCE_REPORTS",+ "name": "List-resource-reports",+ "description": "List all resource reports available. Resource reports are already created reports authored by a user in Vantage.\nWhen you first call this function, use the \"Page\" parameter of 1.\nThe 'Title' of a report is a good way to know what the report is about.\nThe 'filter' of a report also gives clues to the data it provides.\nThe 'token' of a report is a unique identifier for the report. It can be used to generate a link to the report in the Vantage Web UI.\nIf a user wants to see a report, you can link them like this: https://console.vantage.sh/go/<token>"+ },+ {+ "slug": "VANTAGE_MCP_LIST_SCENARIO_MODELS",+ "name": "List-scenario-models",+ "description": "List ScenarioModels available to the current Vantage API token.\nScenarioModels define future-cost adjustments (dollar or percent) that can be assigned to Cost Report forecasts via report-forecast tools.\nUse page 1 when calling this tool for the first time. If the user asks for all ScenarioModels, keep calling with pagination.nextPage until pagination.hasNextPage is false.\nThe token of a ScenarioModel can be used with get-scenario-model, update-scenario-model, delete-scenario-model, and create-report-forecast / update-report-forecast.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled."+ },+ {+ "slug": "VANTAGE_MCP_LIST_TAGS",+ "name": "List-tags",+ "description": "List tags that can be used to filter costs and cost reports.\nTags are associated with one or more Cost Providers.\nTags can be edited in the Vantage Web UI, or have further details displayed there. Link a user to the tag page like this: https://console.vantage.sh/settings/tags?search_query=<tag>\n\nRequires integration settings permission; callers without it receive 403 from the API.\nEach tag in the response uses the field `tag_key` (not `key`)."+ },+ {+ "slug": "VANTAGE_MCP_LIST_TAG_VALUES",+ "name": "List-tag-values",+ "description": "List values for a tag key. The argument is `key` (the tag key name); the API response fields use `tag_value`.\n\nRequires integration settings permission; callers without it receive 403 from the API."+ },+ {+ "slug": "VANTAGE_MCP_LIST_UNIT_COSTS",+ "name": "List-unit-costs",+ "description": "Retrieve the unit costs for a given CostReport, with optional paging, date filters, and ordering."+ },+ {+ "slug": "VANTAGE_MCP_LIST_VIRTUAL_TAG_CONFIGS",+ "name": "List-virtual-tag-configs",+ "description": "Lists or searches the Virtual Tags (Virtual Tag Configs) the current API token can access, including every mapping/value. Use this to discover config and value tokens or find a tag by key."+ },+ {+ "slug": "VANTAGE_MCP_LIST_WORKSPACES",+ "name": "List-workspaces",+ "description": "List all Workspaces available to the authenticated API token. Workspaces are isolated environments within Vantage for organizing cost data and access control across teams.\n\nUse get-myself to see the user's default workspace. Use get-workspace to retrieve details for a specific workspace."+ },+ {+ "slug": "VANTAGE_MCP_QUERY_COSTS",+ "name": "Query-costs",+ "description": "Query for costs in a Vantage Account. These are independent of a cost reports.\nUse Vantage VQL to structure a query.\nQueries must be scoped to a Workspace. Use the get-myself tool to know about available workspaces, and the get-cost-integrations tool to know about available cost providers. If the user didn't tell you a workspace it is best to ask them than to guess it.\nIt's best to set a date range of 30 days unless the user specifically wants to query for a longer time period.\n\nWhen a user asks for data from an account, use the \"get-cost-provider-accounts\" tool to match a name to an account. With that result, always use the account_id in the account_id parameter for this tool. \n\nHere is some more detailed info on using VQL:\nAll costs originate from a Cost Provider (generally a cloud company like AWS, Azure, Datadog) and then filter on a service that they provide (like EC2, S3, etc).\nA cost provider is required on every VQL query.\nVQL is always in parenthesis. Always use single quotes around names that are being queried.\nTo query on a cost provider, use this syntax: (costs.provider = '<provider name>'). The provider name must come from the list-cost-providers tool.\nTo query on a cost service, use this syntax: (costs.provider = '<provider name>' AND costs.service = '<service name>').\nFor AWS, costs.service must be a CUR identifier (e.g. 'AmazonEC2', 'AmazonVPC', 'AWSDirectConnect'). Use vql_info to resolve aliases — not display names from list-cost-services.\nIf a query returns no rows, run one broad probe query first (provider only, date_bin=month, wide date range) to learn available months and service identifiers before retrying with a narrower filter.\nFor month-over-month comparisons, span both months in start_date/end_date with date_bin=month and settings_show_previous_period=true instead of separate queries per month.\nPrefer one query-costs call with all needed groupings (e.g. service, account_id, tag:<key>) over multiple calls that only change groupings.\nYou can only filter against one cost provider at a time. If you want to query for costs from two providers, you need to use the OR operator. Example: ((costs.provider = 'aws') OR (costs.provider = 'azure'))\nYou can otherwise use the IN system to compare against a list of items, like this: (costs.provider = 'aws' AND costs.service IN ('AWSQueueService', 'AWSLambda'))\nTo filter within a cost provider, keep the cost provider part and add a AND section, example: (costs.provider = 'aws' AND costs.service = 'AmazonRDS')\nMany costs have tags on them. A tag is a \"name\" and one or more values.\nTo find an AWS cost that has a tag of \"environment\" the value \"production\", use this syntax: (costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production')\nYou can also query for any value of the \"environment\" tag, like this: (costs.provider = 'aws' AND tags.name = 'environment')\nItems without a tag can also be filtered, example: (costs.provider = 'aws' AND tags.name = NULL)\nParenthesis can be nested. Here we surround an OR clause to look for either of two values for a tag: (costs.provider = 'aws' AND tags.name = 'environment' AND (tags.value = 'dev' OR tags.value = 'staging'))\nA user can have more than one provider account. They can filter on provider accounts if they supply you with the account id. Example: (costs.provider = 'aws' AND costs.account_id = '1000000717')\nYou can also combine top-level queries to find for two providers: ((costs.provider = 'datadog') OR (costs.provider = 'azure'))\nSome cost providers operate in a specific region, you can filter using the costs.region field. Example: (costs.provider = 'aws' AND costs.region = 'us-east-1')\nNote that when users want to query a Custom Provider, that has a special case. When doing a VQL query for custom provider, use the 'token' you get back from the 'list-cost-integrations' tool. Here is an example, where the token of the custom provider is \"accss_crdntl_07171984\": \n (costs.provider = 'custom_provider:accss_crdntl_07171984')\n\nThe DateBin parameter controls the time granularity of returned results.\nWhen DateBin=day you get a record for each service spend on that day. For DateBin=week you get one entry per week,\nwith the accrued_at field set to the first day of the week, but the spend item represents spend for a full week.\nSame with DateBin=month, each record returned covers a month of data. This lets you get answers with processing fewer\nrecords. If omitted, DateBin defaults to day.\n\nCost settings (credits, refunds, discounts, tax, amortization, etc.) default to the workspace's default report settings.\nOnly provide these parameters if you need to override those defaults.\n\nUse settings_aggregate_by to choose the metric: cost (default), usage, or count.\nWhen aggregate_by is count, the response includes total_count and counts (date-binned distinct Group By permutation counts for the full requested period)."+ },+ {+ "slug": "VANTAGE_MCP_QUERY_NETWORK_FLOW_LOGS",+ "name": "Query-network-flow-logs",+ "description": "Queries aggregated network flow log data (costs and bytes). Pass a saved report token or an ad hoc filter. Unlike create/update, custom date ranges use start_date and end_date without date_interval=custom."+ },+ {+ "slug": "VANTAGE_MCP_SUBMIT_USER_FEEDBACK",+ "name": "Submit-user-feedback",+ "description": "Submit feedback on using the Vantage MCP Server. Ask the user if they'd like to provide feedback any time you sense they might be frustrated.\nStop suggesting if they say they're not interested in providing feedback."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_ANNOTATION",+ "name": "Update-annotation",+ "description": "Update the title, date, message, or associated Cost Reports of an existing Annotation. Providing report_tokens replaces all existing Report associations. Use list-annotations to find the annotation_token."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_ANOMALY",+ "name": "Update-anomaly",+ "description": "Updates an existing anomaly alert by its token. Use this to change the status of an anomaly alert (e.g. to archive or ignore it) and optionally provide feedback."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_BILLING_RULE",+ "name": "Update-billing-rule",+ "description": "Updates an existing Billing Rule. You can update the title, dates, and type-specific fields.\nType-specific fields:\n- Exclusion: charge_type\n- Adjustment: percentage, service, category\n- Charge/Credit: service, category, sub_category, amount, start_date\n- Custom: sql_query"+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_BUDGET",+ "name": "Update-budget",+ "description": "Updates an existing Budget. You can update the name, linked Cost Report, child Budget tokens for hierarchical budgets, period cadence, or budget periods."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_BUDGET_ALERT",+ "name": "Update-budget-alert",+ "description": "Update an existing Budget Alert's monitored Budgets, percentage threshold, monthly time window, or recipients. Budget Alerts monitor Budget objects."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_CANVAS",+ "name": "Update-canvas",+ "description": "Updates an existing Canvas. You can update the title, the prompt, or both. Updating the prompt triggers an asynchronous refresh to regenerate the canvas data."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_COST_ALERT",+ "name": "Update-cost-alert",+ "description": "Updates an existing Cost Alert. Use to change the title, threshold, interval, monitored Cost Reports, or notification destinations.\n\nUse list-cost-alerts or get-cost-alert to find the cost_alert_token. Do not use this for Report Notifications or recurring Cost Report delivery."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_COST_REPORT",+ "name": "Update-cost-report",+ "description": "Updates an existing Cost Report. Use to change the title, VQL filter, groupings, date range, chart type, folder, report settings, or attached business metrics.\n\nDo not use create-cost-report (creates a new report) or get-cost-report (reads without changing). Use list-cost-reports or get-cost-report to find the cost_report_token."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_DASHBOARD",+ "name": "Update-dashboard",+ "description": "Updates an existing Dashboard. You can update the title, widgets, saved filters, and date range settings."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_FINANCIAL_COMMITMENT_REPORT",+ "name": "Update-financial-commitment-report",+ "description": "Updates an existing Financial Commitment Report. Use this to change the report title, VQL filter, date range, date bucket, on-demand costs scope, or grouping dimensions.\n\nDate ranges can be set with either:\n- date_interval, or\n- start_date and end_date.\n\nUnless date_interval is \"custom\", date_interval is incompatible with start_date and end_date.\n\nVQL filters use financial commitment fields and should follow Vantage Query Language syntax. Additional VQL documentation is available at https://docs.vantage.sh/vql."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_FOLDER",+ "name": "Update-folder",+ "description": "Updates a Folder's title, parent, or SavedFilter tokens. Folder type cannot be changed after creation."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_NETWORK_FLOW_REPORT",+ "name": "Update-network-flow-report",+ "description": "Updates a saved Network Flow Report. Use list-network-flow-reports to discover tokens."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_RECOMMENDATION_VIEW",+ "name": "Update-recommendation-view",+ "description": "Updates an existing Recommendation View. Use this to change the view title or the filters applied to saved recommendation views.\n\nFilters can be scoped by provider, billing account, cloud account, region, tag key/value, and recommendation creation date range.\n\nDates must be YYYY-MM-DD formatted. Tag filters should use tag_key and tag_value together."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_REPORT_FORECAST",+ "name": "Update-report-forecast",+ "description": "Update a scenario-model ReportForecast. Providing scenario_model_tokens replaces the assigned models.\nSend business_metric_token as null to clear the BusinessMetric. Use set_as_default to make this the Cost Report default forecast.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the Cost Report."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_REPORT_NOTIFICATION",+ "name": "Update-report-notification",+ "description": "Updates an existing Report Notification in Vantage.\n\nUse this tool to change a scheduled Cost Report notification's title, Cost Report, recipients, Slack or Microsoft Teams channels, delivery frequency, or tracked change type. Report Notifications deliver recurring Cost Report summaries on a daily, weekly, or monthly cadence.\n\nDo not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications. Cost Alerts manage spend thresholds; Report Notifications manage scheduled report delivery."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_RESOURCE_REPORT",+ "name": "Update-resource-report",+ "description": "Updates an existing Resource Report. Use to change the title, VQL filter, table columns, or folder.\n\nDo not use create-resource-report (creates a new report) or get-resource-report (reads without changing). Use list-resource-reports or get-resource-report to find the resource_report_token."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_SCENARIO_MODEL",+ "name": "Update-scenario-model",+ "description": "Update an existing ScenarioModel. Providing periods replaces the full period set.\nUse null for priority, provider, service, or period end_at to clear those values.\nRequires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the model."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_VIRTUAL_TAG_CONFIG",+ "name": "Update-virtual-tag-config",+ "description": "Updates an existing Virtual Tag's config-level settings or complete ordered mappings/values. Supplying values replaces the entire list in that order, and an empty array clears it; use the value-level tools to append, partially edit, or delete one mapping."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_VIRTUAL_TAG_CONFIG_VALUE",+ "name": "Update-virtual-tag-config-value",+ "description": "Partially edits one mapping/value in an existing Virtual Tag Config. Omitted fields remain unchanged, display_name set to null clears it, and this tool cannot reorder values."+ },+ {+ "slug": "VANTAGE_MCP_UPDATE_WORKSPACE",+ "name": "Update-workspace",+ "description": "Update an existing Workspace. You can update the name, currency conversion settings, currency code, and exchange rate date method."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "DCR_OAUTH",+ "name": "vantage_mcp_DCR_OAuth",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": false,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": false,+ "default": null+ },+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": ""+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "vapi","name": "Vapi",@@ -320753,12 +332210,12 @@],"toolCount": 2,"triggerCount": 0,- "version": "20260730_01",+ "version": "20260904_00","tools": [{"slug": "VIATOR_MCP_GET_EXPERIENCE_DETAILS","name": "Get experience details",- "description": "Retrieves enriched information for a specific Viator experience, including detailed descriptions, highlights, imagery, pricing, duration, key features, and the click-out URL.The model should call this tool only when the user clearly refers to a specific experience—either by selecting it in the UI or by asking follow-up questions such as “Tell me more about…”;if multiple experiences were shown, the model must resolve ambiguity by asking which one the user means. This tool is intended for deepening experience understanding rather than search, and should only be invoked with a code previously returned by search_experiences."+ "description": "Retrieves enriched information for a specific Viator experience, including detailed descriptions, highlights, imagery, pricing, duration, key features, and the click-out URL.It also returns what is included and excluded in the price, high-level itinerary metadata, bookable experience options, traveler age bands and booking constraints, start/end locations and traveler pickup, additional information such as requirements and restrictions, available language guides, associated destinations, the operating time zone, and the operator.The model should call this tool only when the user clearly refers to a specific experience—either by selecting it in the UI or by asking follow-up questions such as “Tell me more about…”;if multiple experiences were shown, the model must resolve ambiguity by asking which one the user means. This tool is intended for deepening experience understanding rather than search, and should only be invoked with a code previously returned by search_experiences. get_experience_details only returns high-level itinerary metadata. Full itinerary content, including the sequence of stops and activities, detailed descriptions, and location information, is available through get_experience_itinerary. Clients should call that tool on demand when the traveler asks for more detail about what happens during the experience."},{"slug": "VIATOR_MCP_SEARCH_EXPERIENCES",@@ -321178,6 +332635,322 @@}]},+ {+ "slug": "vimeo",+ "name": "Vimeo",+ "logo": "https://logos.composio.dev/api/vimeo",+ "description": "Vimeo is a video platform for hosting, managing, sharing, and interacting with video content and account resources.",+ "category": "video & audio",+ "authSchemes": [+ "OAUTH2"+ ],+ "toolCount": 50,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "VIMEO_GET_CATEGORY",+ "name": "Get Category",+ "description": "Get one public Vimeo category by slug."+ },+ {+ "slug": "VIMEO_GET_CHANNEL",+ "name": "Get Channel",+ "description": "Get one public Vimeo channel by numeric ID."+ },+ {+ "slug": "VIMEO_GET_CURRENT_USER",+ "name": "Get Current User",+ "description": "Return the connected Vimeo user's numeric user ID, profile, account tier, capabilities, and resource counts. Use the ID with user-subject tools for self workflows."+ },+ {+ "slug": "VIMEO_GET_GROUP",+ "name": "Get Group",+ "description": "Get one public Vimeo group by numeric ID."+ },+ {+ "slug": "VIMEO_GET_ON_DEMAND_GENRE",+ "name": "Get On Demand Genre",+ "description": "Get one public Vimeo On Demand genre by ID. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_GET_ON_DEMAND_REGION",+ "name": "Get On Demand Region",+ "description": "Get one public Vimeo On Demand catalog region by country code. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_GET_ON_DEMAND_SEASON",+ "name": "Get On Demand Season",+ "description": "Get one season of a public Vimeo On Demand title. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_GET_ON_DEMAND_TITLE",+ "name": "Get On Demand Title",+ "description": "Get one public Vimeo On Demand title. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_GET_TAG",+ "name": "Get Tag",+ "description": "Get one public Vimeo tag by word."+ },+ {+ "slug": "VIMEO_GET_USER",+ "name": "Get User",+ "description": "Get one public Vimeo user profile."+ },+ {+ "slug": "VIMEO_GET_VIDEO",+ "name": "Get Video",+ "description": "Return metadata only for a public Vimeo video whose privacy.view is 'anybody'. Private, password-protected, team-only, unlisted, and otherwise restricted IDs are treated as inaccessible even when the connected token can view them; use LIST_MY_VIDEOS for the connected user's private videos."+ },+ {+ "slug": "VIMEO_LIST_CATEGORIES",+ "name": "List Categories",+ "description": "Return one sortable page of Vimeo's public video categories for discovering category slugs."+ },+ {+ "slug": "VIMEO_LIST_CATEGORY_CHANNELS",+ "name": "List Category Channels",+ "description": "Return one page of public channels assigned to a Vimeo category. Vimeo currently returns an internal error for search queries containing apostrophes; no escaping is applied. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_CATEGORY_GROUPS",+ "name": "List Category Groups",+ "description": "Return one page of public groups assigned to a Vimeo category. A search query must contain at least one letter or digit. Vimeo currently returns an internal error for queries containing apostrophes; no escaping is applied. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_CATEGORY_VIDEOS",+ "name": "List Category Videos",+ "description": "Return one sortable, filterable page of public videos in a Vimeo category. Vimeo's category-video endpoint currently fails non-empty search queries."+ },+ {+ "slug": "VIMEO_LIST_CHANNEL_CATEGORIES",+ "name": "List Channel Categories",+ "description": "List categories assigned to a public Vimeo channel. Vimeo returns the full relation; limit trims the returned data client-side and does not reduce provider data transfer."+ },+ {+ "slug": "VIMEO_LIST_CHANNEL_FOLLOWERS",+ "name": "List Channel Followers",+ "description": "Return one page of followers of a public Vimeo channel. This is distinct from channel moderators. Vimeo supports sorting and pagination for this follower list, but not search. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_CHANNEL_MODERATORS",+ "name": "List Channel Moderators",+ "description": "Return one page of moderators of a public Vimeo channel. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_CHANNELS",+ "name": "List Channels",+ "description": "Return one searchable, sortable page of Vimeo's public curated channels."+ },+ {+ "slug": "VIMEO_LIST_CHANNEL_TAGS",+ "name": "List Channel Tags",+ "description": "List tags assigned to a public Vimeo channel. Vimeo returns the full relation; limit trims the returned data client-side and does not reduce provider data transfer."+ },+ {+ "slug": "VIMEO_LIST_CHANNEL_VIDEOS",+ "name": "List Channel Videos",+ "description": "Return one searchable, sortable page of public videos in a Vimeo channel."+ },+ {+ "slug": "VIMEO_LIST_CUSTOM_LOGOS",+ "name": "List Custom Logos",+ "description": "Return one page of custom player logos owned by the connected Vimeo user. Custom logos depend on the Standard or Advanced Embed Presets feature; a Free account may return a successful empty list. Pass next_cursor as cursor to fetch the next page."+ },+ {+ "slug": "VIMEO_LIST_EMBED_PRESETS",+ "name": "List Embed Presets",+ "description": "Return one page of embed presets for the connected Vimeo user, or for the Vimeo user selected by optional user_id. Embed presets depend on the Standard or Advanced Embed Presets feature; a Free account may return a successful empty list. Pass next_cursor as cursor to fetch the next page."+ },+ {+ "slug": "VIMEO_LIST_FOLDERS",+ "name": "List Folders",+ "description": "Return one page of folders owned by the connected Vimeo user."+ },+ {+ "slug": "VIMEO_LIST_GROUP_MEMBERS",+ "name": "List Group Members",+ "description": "Return one page of members of a public Vimeo group. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_GROUPS",+ "name": "List Groups",+ "description": "Return one page of searchable, sortable public Vimeo groups. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_GROUP_VIDEOS",+ "name": "List Group Videos",+ "description": "Return one page of public videos in a Vimeo group. Pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_MY_VIDEOS",+ "name": "List My Videos",+ "description": "Return one searchable, sortable page of videos uploaded by the connected Vimeo user, including private videos visible to the grant. Use next_cursor to retrieve the next page. Vimeo's deprecated include_team_content input is intentionally omitted; use filter_uploader to narrow team-visible results to a team member or owner."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_GENRES",+ "name": "List On Demand Genres",+ "description": "List Vimeo On Demand catalog genres. Vimeo returns the full catalog; limit trims the returned data client-side and does not reduce provider data transfer. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_POSTERS",+ "name": "List On Demand Posters",+ "description": "List one page of poster artwork for a public Vimeo On Demand title and return next_cursor. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_REGIONS",+ "name": "List On Demand Regions",+ "description": "List countries and regions in the public Vimeo On Demand catalog. Vimeo returns the full catalog on every request; this action trims it client-side and returns a local cursor until every region is reachable. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_SEASONS",+ "name": "List On Demand Seasons",+ "description": "List one page of seasons for a public Vimeo On Demand title and return next_cursor. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_SEASON_VIDEOS",+ "name": "List On Demand Season Videos",+ "description": "List one page of On Demand season video metadata and return next_cursor; playback entitlement is not implied. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_TITLE_GENRES",+ "name": "List On Demand Title Genres",+ "description": "List genres assigned to a public Vimeo On Demand title. Vimeo returns the full relation; limit trims the returned data client-side and does not reduce provider data transfer. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_TITLES_BY_GENRE",+ "name": "List On Demand Titles By Genre",+ "description": "List one page of public Vimeo On Demand titles in a genre and return next_cursor. my_region is the only supported region filter; country is unsupported and rejected. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_ON_DEMAND_TITLE_VIDEOS",+ "name": "List On Demand Title Videos",+ "description": "List one page of On Demand title video metadata and return next_cursor; playback entitlement is not implied. Vimeo On Demand is being discontinued; these reads are expected to stop after Nov 20, 2026."+ },+ {+ "slug": "VIMEO_LIST_PORTFOLIOS",+ "name": "List Portfolios",+ "description": "Return one page of portfolios for the connected Vimeo user, or for the Vimeo user selected by optional user_id. Portfolios are available with Standard or Advanced; a Free account may return a successful empty list. Pass next_cursor as cursor to fetch the next page."+ },+ {+ "slug": "VIMEO_LIST_SHOWCASES",+ "name": "List Showcases",+ "description": "Return one searchable, sortable page of Showcases owned by the connected Vimeo user."+ },+ {+ "slug": "VIMEO_LIST_USER_FEED",+ "name": "List User Feed",+ "description": "Return one page of Activity records from a Vimeo user's feed. Use GET_CURRENT_USER to obtain the connected user's ID for self workflows. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_FOLDERS",+ "name": "List User Folders",+ "description": "Return one page of folders belonging to a Vimeo user or team owner. Vimeo's legacy API path calls folders projects; pass next_cursor as cursor to continue."+ },+ {+ "slug": "VIMEO_LIST_USER_FOLLOWED_CATEGORIES",+ "name": "List User Followed Categories",+ "description": "Return one page of categories followed by a Vimeo user. Use GET_CURRENT_USER to obtain the connected user's ID for self workflows. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_FOLLOWED_CHANNELS",+ "name": "List User Followed Channels",+ "description": "Return one page of channels followed by a Vimeo user. Use GET_CURRENT_USER to obtain the connected user's ID for self workflows. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_FOLLOWERS",+ "name": "List User Followers",+ "description": "Return one page of followers of a Vimeo user. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_FOLLOWING",+ "name": "List User Following",+ "description": "Return one page of users followed by a Vimeo user. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_LIKED_VIDEOS",+ "name": "List User Liked Videos",+ "description": "Return one page of videos liked by a Vimeo user. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_PICTURES",+ "name": "List User Pictures",+ "description": "Return one page of profile pictures for a Vimeo user. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_USER_WATCH_LATER",+ "name": "List User Watch Later",+ "description": "Return one page of videos in a Vimeo user's Watch Later queue. Use GET_CURRENT_USER to obtain the connected user's ID for self workflows. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_LIST_VIDEO_CATEGORIES",+ "name": "List Video Categories",+ "description": "List categories assigned to a public Vimeo video."+ },+ {+ "slug": "VIMEO_LIST_VIDEO_LIKERS",+ "name": "List Video Likers",+ "description": "Return one page of users who liked a public Vimeo video. Use next_cursor to retrieve the next page."+ },+ {+ "slug": "VIMEO_SEARCH_USERS",+ "name": "Search Users",+ "description": "Return one page of public Vimeo user profiles matching a search. Use next_cursor to retrieve the next page."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "OAUTH2",+ "name": "vimeo_oauth2",+ "fields": {+ "auth_config_creation": {+ "required": [+ {+ "name": "client_id",+ "displayName": "Client id",+ "type": "string",+ "description": "Client id of the app",+ "required": true,+ "default": null+ },+ {+ "name": "client_secret",+ "displayName": "Client secret",+ "type": "string",+ "description": "Client secret of the app",+ "required": true,+ "default": null+ }+ ],+ "optional": [+ {+ "name": "oauth_redirect_uri",+ "displayName": "Redirect URI",+ "type": "string",+ "description": "Add this Redirect URL to your app's OAuth allow list.",+ "required": false,+ "default": "https://backend.composio.dev/api/v1/auth-apps/add"+ },+ {+ "name": "scopes",+ "displayName": "Scopes",+ "type": "string",+ "description": "Scopes to request from the user, comma separated",+ "required": false,+ "default": "public,private"+ }+ ]+ },+ "connected_account_initiation": {+ "required": [],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "viral_loops","name": "Viral Loops",@@ -323077,6 +334850,92 @@}]},+ {+ "slug": "wise",+ "name": "Wise",+ "logo": "https://logos.composio.dev/api/wise",+ "description": "Access supported quotes, balances, transfers, recipients, and account data for PERSONAL or BUSINESS profiles using a personal API token created from a Wise Business account.",+ "category": "payment processing",+ "authSchemes": [+ "API_KEY"+ ],+ "toolCount": 9,+ "triggerCount": 0,+ "version": "00000000_00",+ "tools": [+ {+ "slug": "WISE_CREATE_QUOTE",+ "name": "Create Quote",+ "description": "Create a transient Wise bank-transfer quote for a personal or business profile. The quote expires; this tool does not create or fund a transfer and does not move money."+ },+ {+ "slug": "WISE_GET_EXCHANGE_RATE",+ "name": "Get Exchange Rate",+ "description": "Get Wise's latest exchange rate for one source and target currency pair; this is an indicative rate, not a transfer quote."+ },+ {+ "slug": "WISE_GET_QUOTE",+ "name": "Get Quote",+ "description": "Retrieve a Wise quote by profile and quote ID, including its current status, pricing, payment options, and expiration."+ },+ {+ "slug": "WISE_LIST_ACTIVITIES",+ "name": "List Activities",+ "description": "List a Wise profile's account activity with optional status, resource-type, and time filters, one page at a time."+ },+ {+ "slug": "WISE_LIST_BALANCES",+ "name": "List Balances",+ "description": "List standard balances and savings jars for a Wise profile without creating, deleting, or moving funds between balances."+ },+ {+ "slug": "WISE_LIST_CURRENCIES",+ "name": "List Supported Currencies",+ "description": "List currencies Wise currently supports for transfers, including their ISO codes and decimal support."+ },+ {+ "slug": "WISE_LIST_PROFILES",+ "name": "List Profiles",+ "description": "List the connected Wise account's personal or business profiles and return the profile IDs required by profile-scoped tools."+ },+ {+ "slug": "WISE_LIST_RECIPIENTS",+ "name": "List Recipients",+ "description": "List Wise recipients for a profile, optionally filtering by active status, ownership, currency, or account type. Returns summary identity fields but excludes bank-account details; this tool cannot modify recipients."+ },+ {+ "slug": "WISE_LIST_TRANSFERS",+ "name": "List Transfers",+ "description": "List and filter existing Wise transfers for a profile, one page at a time; this tool cannot create, fund, or cancel transfers."+ }+ ],+ "triggers": [],+ "authConfigDetails": [+ {+ "mode": "API_KEY",+ "name": "wise_api_key",+ "fields": {+ "auth_config_creation": {+ "required": [],+ "optional": []+ },+ "connected_account_initiation": {+ "required": [+ {+ "name": "generic_api_key",+ "displayName": "Personal API Token",+ "type": "string",+ "description": "Log into your Wise Business account, then go to Your Account > Connect and manage apps > API tokens > Add new token. Complete 2-step verification and copy the token when it is shown; Wise displays it only once. Use a production token for this connection.",+ "required": true,+ "default": null+ }+ ],+ "optional": []+ }+ }+ }+ ]+ },{"slug": "wisepops","name": "Wisepops",@@ -329355,7 +341214,7 @@],"toolCount": 24,"triggerCount": 0,- "version": "20260821_00",+ "version": "20260903_00","tools": [{"slug": "ZEPLIN_AUTH_O_AUTH_AUTHORIZE",diff --git a/docs/public/openapi-v3.json b/docs/public/openapi-v3.jsonindex 61dc090f2..4adb1df88 100644--- a/docs/public/openapi-v3.json+++ b/docs/public/openapi-v3.json@@ -113,6 +113,10 @@"name": "Tool Router","description": "(Labs) Tool router endpoints"},+ {+ "name": "Playground",+ "description": "Dashboard playground chat"+ },{"name": "Organization Management"},@@ -17184,7 +17188,20 @@},"fast_mode": {"type": "boolean",- "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results.",+ "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results. Also skips plan search entirely, so responses will not include cached-plan fields (recommended_plan_steps, known_pitfalls, reference_workbench_snippets) or plan-derived execution guidance.",+ "x-experimental": true+ },+ "submit_feedback": {+ "type": "object",+ "properties": {+ "enable": {+ "type": "boolean",+ "default": false,+ "description": "Set to true to expose the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session. Defaults to false."+ }+ },+ "additionalProperties": false,+ "description": "Exposes the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session so the agent can report tool executions with empty, incorrect, or failed results. Defaults to false.","x-experimental": true}},@@ -17948,6 +17965,16 @@}}},+ "404": {+ "description": "Not found. The referenced Session config or another requested resource does not exist in this project.",+ "content": {+ "application/json": {+ "schema": {+ "$ref": "#/components/schemas/Error"+ }+ }+ }+ },"408": {"description": "Request timeout. The session creation took too long to complete.","content": {@@ -18219,7 +18246,8 @@"COMPOSIO_WAIT_FOR_CONNECTIONS","COMPOSIO_REMOTE_WORKBENCH","COMPOSIO_REMOTE_BASH_TOOL",- "COMPOSIO_GET_TOOL_SCHEMAS"+ "COMPOSIO_GET_TOOL_SCHEMAS",+ "COMPOSIO_SUBMIT_FEEDBACK"],"description": "The unique slug identifier of the meta tool to execute","example": "COMPOSIO_MANAGE_CONNECTIONS"@@ -19389,11 +19417,27 @@},"fast_mode": {"type": "boolean",- "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results.",+ "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results. Also skips plan search entirely, so responses will not include cached-plan fields (recommended_plan_steps, known_pitfalls, reference_workbench_snippets) or plan-derived execution guidance.",+ "x-experimental": true+ },+ "submit_feedback": {+ "type": "object",+ "properties": {+ "enable": {+ "type": "boolean",+ "description": "Set to true to expose the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session, false to hide it."+ }+ },+ "required": [+ "enable"+ ],+ "additionalProperties": false,+ "description": "Exposes the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session so the agent can report tool executions with empty, incorrect, or failed results. Replaces the stored block when provided; `enable` is required when the block is sent.","x-experimental": true}},- "additionalProperties": false+ "additionalProperties": false,+ "x-experimental": true}},"additionalProperties": falsediff --git a/docs/public/openapi.json b/docs/public/openapi.jsonindex 25ed80e6d..185e40acf 100644--- a/docs/public/openapi.json+++ b/docs/public/openapi.json@@ -113,6 +113,10 @@"name": "Tool Router","description": "(Labs) Tool router endpoints"},+ {+ "name": "Playground",+ "description": "Dashboard playground chat"+ },{"name": "Invite Codes"},@@ -1770,7 +1774,7 @@},"/api/v3.1/api_key_revocation": {"post": {- "summary": "Publicly revoke leaked Composio API keys",+ "summary": "Revoke Composio API keys","description": "Public endpoint for reporting and revoking Composio API keys that have been leaked (e.g. via the GitHub Secret Scanning Partner Program, third-party scanners, or self-reported leaks). Accepts project (ak_*), user (uak_*), and org (oak_*) keys in a single batch. Matched keys are revoked and stop working immediately. The response shape is constant regardless of whether any submitted key matched, so callers cannot use this endpoint to probe key existence. The endpoint is rate limited; requests over the limit receive a 429.","tags": ["API Keys"@@ -4039,8 +4043,9 @@},"/api/v3.1/tools/scopes/required": {"post": {- "summary": "Get required scopes for tools",- "description": "Resolves required scopes for the specified tools at a given toolkit version. All requested tools must belong to the same toolkit. Returns the flat scope union plus per-tool structured scope requirements when available.",+ "summary": "Get required scopes for tools (DEPRECATED)",+ "description": "DEPRECATED: Use POST /api/v3.1/toolkits/{toolkit_slug}/scopes/recommended instead, discovering its `grant_context` options with GET /api/v3.1/toolkits/{toolkit_slug}/scopes/grant_context. Resolves required scopes for the specified tools at a given toolkit version. All requested tools must belong to the same toolkit. Returns the flat scope union plus per-tool structured scope requirements when available.",+ "deprecated": true,"tags": ["Tools"],@@ -4869,7 +4874,7 @@"additionalProperties": {"type": "string"},- "description": "Optional context about your OAuth app or the account being connected that can change which scopes are required, e.g. {\"account_type\": \"Google Workspace\"}. Get accepted keys and values from the List grant_context options endpoint."+ "description": "Context in which you want to grant scopes to your user. Pass a dimension and its selected value, for example {\"account_type\": \"Google Workspace\"}. Use the [List grant contexts](https://docs.composio.dev/reference/api-reference/toolkits/recommendToolkitScopesGrantContext) endpoint to discover available dimensions and values."},"include": {"type": "array",@@ -4884,6 +4889,13 @@"type": "string"},"description": "Scopes the recommendation must not include; the solver picks documented alternatives and fails when none exist."+ },+ "available_scopes": {+ "type": "array",+ "items": {+ "type": "string"+ },+ "description": "Scopes your OAuth app can request. The recommendation never names a scope outside this list and fails with scope_not_available when a tool cannot be covered inside it. Omit for an unbounded recommendation."}},"required": [@@ -4915,7 +4927,7 @@"additionalProperties": {"type": "string"},- "description": "The grant_context the recommendation was computed with; {} when none applies."+ "description": "The effective grant_context the recommendation was computed with - the toolkit default overlaid with your overrides; {} when none applies."},"scopes": {"type": "object",@@ -5019,7 +5031,7 @@}},"422": {- "description": "Exclusions conflict with the requested tools (exclude_conflict)",+ "description": "Exclusions or the available_scopes ceiling leave a requested tool with no grantable scope (exclude_conflict, scope_not_available)","content": {"application/json": {"schema": {@@ -5054,8 +5066,8 @@},"/api/v3.1/toolkits/{toolkit_slug}/scopes/grant_context": {"get": {- "summary": "List grant_context options",- "description": "Experimental: this endpoint is in beta and its contract may change.\n\nLists the grant_context keys and values this toolkit accepts. Pass them in the Get required scopes request to tailor the recommendation to your OAuth app or account.",+ "summary": "List grant contexts",+ "description": "Experimental: this endpoint is in beta and its contract may change.\n\nList of contexts in which you want to grant scopes to your user. Pass a dimension and its selected value in the `grant_context` field of the [Get required scopes](https://docs.composio.dev/reference/api-reference/toolkits/recommendToolkitScopes) request to tailor the scope recommendation.","tags": ["Toolkits"],@@ -5070,10 +5082,10 @@"schema": {"type": "string","minLength": 1,- "description": "Toolkit to list grant_context options for."+ "description": "Toolkit to list grant contexts for."},"required": true,- "description": "Toolkit to list grant_context options for.",+ "description": "Toolkit to list grant contexts for.","name": "toolkit_slug","in": "path"},@@ -5120,7 +5132,7 @@],"responses": {"200": {- "description": "Successfully discovered the toolkit's grant-context keys",+ "description": "Successfully discovered the toolkit's grant-context dimensions","content": {"application/json": {"schema": {@@ -5134,35 +5146,48 @@"type": "string","description": "Concrete toolkit version the answer was computed from; pass it back as toolkit_version to pin."},- "grant_context_keys": {+ "grant_context_dimensions": {"type": "array","items": {"type": "object","properties": {- "key": {+ "dimension": {+ "type": "string",+ "description": "Context in which you could grant scopes to your user."+ },+ "description": {"type": "string",- "description": "Key you can pass in grant_context when requesting scope recommendations, e.g. 'account_type'."+ "description": "What this dimension means and when to pass it."},- "allowed_values": {+ "values": {"type": "array","items": {"type": "string"},- "description": "Values this key accepts."+ "description": "Values that this dimension can take."}},"required": [- "key",- "allowed_values"+ "dimension",+ "description",+ "values"]},- "description": "Keys this toolkit accepts in grant_context under the auth scheme; [] when no scope depends on grant_context."+ "description": "Dimensions this toolkit accepts in grant_context under the auth scheme; [] when no scope depends on grant_context."+ },+ "default_grant_context": {+ "type": "object",+ "additionalProperties": {+ "type": "string"+ },+ "description": "The grant_context assumed when you pass none — pass a dimension and its selected value only to override or extend it."}},"required": ["auth_scheme","toolkit_version",- "grant_context_keys"+ "grant_context_dimensions",+ "default_grant_context"],"x-experimental": true}@@ -5824,11 +5849,29 @@},"fast_mode": {"type": "boolean",- "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results.",+ "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results. Also skips plan search entirely, so responses will not include cached-plan fields (recommended_plan_steps, known_pitfalls, reference_workbench_snippets) or plan-derived execution guidance.",+ "x-experimental": true+ },+ "submit_feedback": {+ "type": "object",+ "properties": {+ "enable": {+ "type": "boolean",+ "default": false,+ "description": "Set to true to expose the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session. Defaults to false."+ }+ },+ "additionalProperties": false,+ "description": "Exposes the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session so the agent can report tool executions with empty, incorrect, or failed results. Defaults to false.",+ "x-experimental": true+ },+ "session_config_id": {+ "type": "string",+ "format": "sessionConfigId",+ "description": "Experimental reusable Session config to resolve for this new Session. Mutually exclusive with inline toolkit and tool access fields; authentication and runtime fields remain per Session.","x-experimental": true}},- "description": "Experimental features - not stable, may be modified or removed in future versions.","x-experimental": true},"preload": {@@ -6562,9 +6605,23 @@]},"description": "Custom tools — standalone or extending Composio toolkits"+ },+ "source_session_config": {+ "type": "object",+ "properties": {+ "id": {+ "type": "string",+ "format": "sessionConfigId"+ }+ },+ "required": [+ "id"+ ],+ "description": "Experimental provenance for the reusable Session config resolved at creation.",+ "x-experimental": true}},- "description": "Experimental features including the generated system prompt. Only returned on session creation, not on GET.",+ "description": "Experimental v3.1 features - may change without notice","x-experimental": true},"warnings": {@@ -6642,6 +6699,16 @@}}},+ "404": {+ "description": "Not found. The referenced Session config or another requested resource does not exist in this project.",+ "content": {+ "application/json": {+ "schema": {+ "$ref": "#/components/schemas/Error"+ }+ }+ }+ },"408": {"description": "Request timeout. The session creation took too long to complete.","content": {@@ -7191,9 +7258,23 @@]},"description": "Custom tools — standalone or extending Composio toolkits"+ },+ "source_session_config": {+ "type": "object",+ "properties": {+ "id": {+ "type": "string",+ "format": "sessionConfigId"+ }+ },+ "required": [+ "id"+ ],+ "description": "Experimental provenance for the reusable Session config resolved at creation.",+ "x-experimental": true}},- "description": "Experimental features",+ "description": "Experimental v3.1 features","x-experimental": true},"warnings": {@@ -7750,11 +7831,27 @@},"fast_mode": {"type": "boolean",- "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results.",+ "description": "Experimental flag to skip the LLM reranker in tool search and serve embeddings/BM25-only results. Also skips plan search entirely, so responses will not include cached-plan fields (recommended_plan_steps, known_pitfalls, reference_workbench_snippets) or plan-derived execution guidance.",+ "x-experimental": true+ },+ "submit_feedback": {+ "type": "object",+ "properties": {+ "enable": {+ "type": "boolean",+ "description": "Set to true to expose the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session, false to hide it."+ }+ },+ "required": [+ "enable"+ ],+ "additionalProperties": false,+ "description": "Exposes the COMPOSIO_SUBMIT_FEEDBACK helper tool in this session so the agent can report tool executions with empty, incorrect, or failed results. Replaces the stored block when provided; `enable` is required when the block is sent.","x-experimental": true}},- "additionalProperties": false+ "additionalProperties": false,+ "x-experimental": true}},"additionalProperties": false@@ -8250,9 +8347,23 @@]},"description": "Custom tools — standalone or extending Composio toolkits"+ },+ "source_session_config": {+ "type": "object",+ "properties": {+ "id": {+ "type": "string",+ "format": "sessionConfigId"+ }+ },+ "required": [+ "id"+ ],+ "description": "Experimental provenance for the reusable Session config resolved at creation.",+ "x-experimental": true}},- "description": "Experimental features",+ "description": "Experimental v3.1 features","x-experimental": true},"warnings": {@@ -9167,9 +9278,23 @@]},"description": "Custom tools — standalone or extending Composio toolkits"+ },+ "source_session_config": {+ "type": "object",+ "properties": {+ "id": {+ "type": "string",+ "format": "sessionConfigId"+ }+ },+ "required": [+ "id"+ ],+ "description": "Experimental provenance for the reusable Session config resolved at creation.",+ "x-experimental": true}},- "description": "Experimental features",+ "description": "Experimental v3.1 features","x-experimental": true},"warnings": {@@ -10596,7 +10721,8 @@"COMPOSIO_WAIT_FOR_CONNECTIONS","COMPOSIO_REMOTE_WORKBENCH","COMPOSIO_REMOTE_BASH_TOOL",- "COMPOSIO_GET_TOOL_SCHEMAS"+ "COMPOSIO_GET_TOOL_SCHEMAS",+ "COMPOSIO_SUBMIT_FEEDBACK"],"description": "The unique slug identifier of the meta tool to execute","example": "COMPOSIO_MANAGE_CONNECTIONS"