Skip to content
AI Agent: Spotify r...
 
Notifications
Clear all

AI Agent: Spotify request works on the first call, but not subsequently

2 Posts
2 Users
0 Reactions
3 Views
Jed_Davidow
(@jed_davidow)
Posts: 1
New Member
Topic starter
 

New to this platform, I've searched for some answers but I'm not sure I'm using the best search terms yet.

I've set up a very basic AI agent to fetch the currently playing song from Spotify, primarily for testing purposes (I'm using this with Gemini Flash 2.0).

When the workflow runs for the first time (or if I clear the memory), it functions correctly and utilizes the Spotify tool each time.

However, when memory is enabled, it works on the initial request of a session, but then it stops using the tool for subsequent requests. Instead, it returns random song titles. These titles seem to originate from the current playlist, though not consistently, and I haven't been able to locate the source of this playlist data within the logs or execution windows.

I encountered a similar issue with a Calendar event creation workflow. That one started working when I became more specific with dates and avoided using terms like "today" or "tomorrow".

Is there a specific keyword I can include in my prompt to ensure it bypasses the memory for this particular task?

 
Posted : 29/05/2025 9:41 pm
Grot
 Grot
(@grot)
Posts: 13
Active Member
 

Hi, I believe I can assist with this. The most straightforward solution would be to utilize Gemini Flash 2.5; its reasoning capabilities are quite beneficial.

Concerning the query about keywords, it's not feasible.

Additionally, would you be willing to share your prompt? Improved prompting significantly aids in tool utilization, as it's the LLM's responsibility to determine when to make a call.

 
Posted : 29/05/2025 10:15 pm
Share: