`could_have_been_email_analyze`

Pack: could-have-been-email · Endpoint: https://gateway.pipeworx.io/could-have-been-email/mcp

Check if a meeting transcript could have been an email instead. Returns filler word count, decisions made, action items, and a suggested email that would’ve replaced the meeting.

Example call

Arguments

{
  "transcript": "Team standup: John reported completion of API integration. Sarah discussed Q4 roadmap priorities. Mike raised concern about database performance. Action: John to share API docs by Friday.",
  "duration": 15,
  "attendee_count": 5,
  "recurring": true
}

curl

curl -X POST https://gateway.pipeworx.io/could-have-been-email/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"could_have_been_email_analyze","arguments":{"transcript":"Team standup: John reported completion of API integration. Sarah discussed Q4 roadmap priorities. Mike raised concern about database performance. Action: John to share API docs by Friday.","duration":15,"attendee_count":5,"recurring":true}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('could_have_been_email_analyze', {
  "transcript": "Team standup: John reported completion of API integration. Sarah discussed Q4 roadmap priorities. Mike raised concern about database performance. Action: John to share API docs by Friday.",
  "duration": 15,
  "attendee_count": 5,
  "recurring": true
});

More examples

{
  "transcript": "All-hands meeting covering company performance, new benefits rollout, and office reopening policy. HR presented three policy options. Finance reviewed quarterly results. Q&A about remote work flexibility.",
  "duration": 45,
  "attendee_count": 32
}

Response shape

Field	Type	Description
`filler_word_count`	number	Count of filler words in the transcript
`decisions_made`	array	List of decisions made during the meeting
`action_items`	array	List of action items from the meeting
`suggested_email`	string	Email text that would have replaced the meeting
`could_have_been_email`	boolean	Whether the meeting could have been an email

Full JSON Schema

{
  "type": "object",
  "properties": {
    "filler_word_count": {
      "type": "number",
      "description": "Count of filler words in the transcript"
    },
    "decisions_made": {
      "type": "array",
      "description": "List of decisions made during the meeting",
      "items": {
        "type": "string"
      }
    },
    "action_items": {
      "type": "array",
      "description": "List of action items from the meeting",
      "items": {
        "type": "string"
      }
    },
    "suggested_email": {
      "type": "string",
      "description": "Email text that would have replaced the meeting"
    },
    "could_have_been_email": {
      "type": "boolean",
      "description": "Whether the meeting could have been an email"
    }
  }
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "could-have-been-email": {
      "url": "https://gateway.pipeworx.io/could-have-been-email/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

could_have_been_email_analyze