podcast-guest-crm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Anthropic API key required for AI-powered features such as draft_outreach_email. | |
| PODCAST_GUEST_CRM_SUPABASE_URL | Yes | Your Supabase project URL, used for authentication. | |
| PODCAST_GUEST_CRM_SUPABASE_ANON_KEY | Yes | Your Supabase anon key, used for authentication. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_guestsA | List guests in the pipeline, paginated and filterable by stage, priority, and free-text search. Wraps GET /api/v1/guests. |
| add_guestA | Create a new guest in the discover stage. Wraps POST /api/v1/guests. Fit scoring runs asynchronously after creation; call list_guests or the guest detail endpoint shortly after to see fitScore populate. |
| update_guest_stageA | Transition a guest to a new lifecycle stage. Wraps PATCH /api/v1/guests/:id/stage. Valid paths: discover -> outreach -> scheduled -> recorded -> published -> follow_up, with back-transitions outreach -> discover (declined), scheduled -> outreach (reschedule), recorded -> scheduled (re-record), follow_up -> outreach (invite back) or follow_up -> published. Invalid transitions are rejected by the API, not this tool. |
| draft_outreach_emailA | Generate an AI outreach email draft for a guest. Wraps POST /api/v1/outreach/draft. Uses claude-sonnet-4-6 server-side (packages/ai). Returns subject, body, a confidence score, and the reasoning behind the draft. |
| get_analytics_summaryA | Dashboard overview: total guests, stage breakdown, average fit score, reply and booking conversion rates, top topics, recent activity. Wraps GET /api/v1/analytics/overview. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: managing guests (list, add, update stage), viewing analytics, and drafting emails. There is no overlap or ambiguity between tools, making selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern in snake_case: list_guests, add_guest, update_guest_stage, get_analytics_summary, draft_outreach_email. The verb-first structure is uniform and predictable.
With exactly 5 tools, the server is well-scoped for its purpose. Each tool covers a core function of the CRM (guest management, pipeline updates, analytics, outreach), and none are redundant or excessive.
The tool set covers the main guest lifecycle (create, list, update stage) and adds analytics and email drafting. However, there is no tool to fetch a single guest's details or edit guest fields beyond stage, which is a minor gap.