Hi, Sending some feedback on the MCP integration from a developer use case perspective. We've ran into some major gaps/roadblocks when using the MCP:
1. Expose created_at filtering in search_conversations. The underlying API supports date filtering but the MCP tool doesn't expose it. Agents scoped to a time window have to paginate all historical results and apply the cutoff manually.
2. Expose source.body text search in search_conversations. Again, supported by the API but not exposed in the MCP. Forces agents doing content-based retrieval to call get_conversation on every result individually.
3. Add source.subject filtering to search_conversations. Not sure if this exists in the underlying API — if it does, same ask as above. If not, it's a genuine gap: for email-based workflows, subject line is the most reliable signal for identifying conversation origin.
4. fetch drops source.subject from its output. get_conversation returns it correctly; fetch doesn't include it in its summary. Forces a redundant call for a consistently useful field.
5. Add tag filtering to search_conversations. Tags are the primary categorization mechanism but aren't queryable at search time.
6. Add custom attribute filtering to search_conversations. search_contacts supports this — parity in search_conversations would make agent-based segmentation significantly more practical.