75 minutesThe Ultimate MCP Crash Course - Build From Scratch
Build a first MCP server and understand how tools, schemas, prompts, resources and transports fit together.
LangChain. A guided tour of an LLM trace, project, and dataset by LangChain's co-founder — token cost, latency, error rate, feedback aggregation, drilling into a single retrieval-step span. It's the closest visual analogue to what the article describes when it talks about "every call is a span" and why structured traces beat print logging.
It is a vendor walkthrough — watch it for the trace, project and dataset concepts rather than the product pitch; the 'every call is a span' idea transfers to any tracing stack.
You can navigate traces, projects and datasets in LangSmith and read off token cost, latency, error rate and per-span detail.
Basic familiarity with LLM API calls; you don't need to be a LangChain user to follow the trace concepts.
Last reviewed: May 18, 2026
Continue through the same learning path with the next curated companion videos.
75 minutesBuild a first MCP server and understand how tools, schemas, prompts, resources and transports fit together.
19 minutesImprove tool design so agents select the right action with the right parameters.
19 minutesIdentify the production RAG controls missing from naive document-chat demos.
Hand-picked external courses that go deeper on this topic.
Emory University Goizueta Business School faculty
The deeper, university-level counterpart to our beginner HubSpot marketing pick — Emory's business-school treatment goes past 'how to prompt' into training generative models for brand-specific output, the purchase-funnel economics of AI-generated content, and a full module of genuine skepticism about when generative AI is and isn't worth using in marketing.
IBM AI Academy
The genAI-era answer to the executive-strategy question. Three short courses aimed squarely at business leaders — no technical background required — on where generative AI creates value, how to govern it responsibly, and how to turn a vague "we should use AI" into a concrete, defensible use case. Rated 4.6 across ~700 reviews. Best taken before your next AI budget decision.