Convo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONVO_API_KEY | Yes | Your Convo API key, obtained from the Convo app dashboard under Settings. Required for accessing your meetings and related data. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_meetingsB | List your recent meetings. Search by title or filter by date. |
| get_transcriptC | Get the full transcript of a meeting with speaker names and timestamps. |
| get_summaryB | Get the summary of a meeting including key points, decisions, and action items. Generates automatically if not yet available. |
| get_feedbackA | Get AI coaching feedback for a meeting: communication score, strengths, growth areas, and talk-to-listen ratio. Generates automatically if not yet available. |
| ask_about_meetingC | Ask any question about a specific meeting. The AI will answer based on the transcript. |
| draft_followup_emailC | Draft a follow-up email based on a meeting. References actual discussion points. |
| share_meetingC | Generate a shareable link for a meeting. |
| get_upcoming_meetingsC | Get upcoming meetings from your connected Google Calendar. |
| get_account_infoB | Get your Convo account info including subscription tier and API usage stats. |
| prepare_for_meetingA | Prepare a briefing for an upcoming meeting. Searches past meetings with a person or company, pulls summaries and open action items, and returns a consolidated briefing so you show up prepared. |
| weekly_digestB | Get a consolidated digest of all your meetings over a time period. Includes total meeting time, all decisions made, all action items, and per-meeting summaries. |
| find_action_itemsA | Find all action items across your recent meetings. Shows who owns each item, priority, and which meeting it came from. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| meeting-prep | Prepare for an upcoming meeting by reviewing past interactions with a person or company. |
| weekly-review | Get a digest of all your meetings from the past week with decisions and action items. |
| follow-up-blitz | Find recent meetings and draft follow-up emails for each one. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent-meetings | List of your recent meetings (last 7 days) |
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no overlap; for example, 'get_summary' provides key points and decisions, while 'find_action_items' extracts tasks across meetings, and 'ask_about_meeting' allows specific queries. The descriptions clearly differentiate each tool's function, preventing misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'get_summary', 'list_meetings', and 'draft_followup_email'. This predictability makes it easy for agents to understand and use the toolset without confusion.
With 12 tools, the server is well-scoped for managing meetings, covering operations from preparation to follow-up. Each tool earns its place by addressing specific aspects like transcription, summarization, action tracking, and integration with calendars.
The toolset provides complete CRUD/lifecycle coverage for meeting management: listing and getting meetings, preparing, summarizing, extracting action items, drafting follow-ups, sharing, and generating digests. No obvious gaps exist, ensuring agents can handle end-to-end workflows without dead ends.