Multi-Turn Function Calling Conversations
You'll learn: How to manage conversation state across multiple function calls and LLM responses within a single session.
The Challenge of Maintaining State
When your LLM needs to call multiple functions to answer a complex user query, each interaction creates a "turn" in the conversation. Unlike a simple one-shot function call, multi-turn conversations require you to maintain the full history of what's been said, what functions were called, and what results came back.
Think of it like a phone conversation with customer support: the agent doesn't forget what you said two minutes ago. Similarly, your LLM needs the entire context—original question, function calls made, and their results—to provide coherent, complete answers.
How Multi-Turn Works
Each turn in a multi-turn function calling conversation follows this pattern:
- User message → LLM decides to call a function
- Function execution → You run the function and get results
- Return results → Add function output as a new message
- LLM processes → Model may call another function OR provide final answer
The critical part: you must append each message to your conversation history array. This includes the assistant's function call requests and your function result messages.
Managing the Conversation Array
Your conversation state is a growing list of messages with different roles:
user: original queriesassistant: LLM responses (including function call requests)functionortool: results you return after executing functions
Each API call must include this entire history so the LLM understands what's already been done and what still needs attention.
Key Takeaway: Multi-turn function calling requires maintaining a complete message history that includes user queries, assistant function requests, and function results, enabling the LLM to make informed decisions across multiple interaction steps.