Hi team,
I noticed that a recent commit removed the "news" option from the topic parameter in the tavily_search tool schema, leaving only "general".
Reference Commit: 5e7fef3
The Issue: This is a breaking change that is causing schema validation errors. The main issue is that while "news" was removed from the topic enum, references to it still remain in other parameter descriptions, confusing the models. Error noticed - 1 validation error for call[tavily_search] topic Input should be 'general' [type=literal_error, input_value='news', input_type=str]
For instance, the time_range description explicitly states:
"This feature is available for both 'general' and 'news' search topics"
This inconsistency creates a trap for LLMs: the description leads them to believe "news" is a valid option, so they generate it, but the strict enum validation (["general"]) causes the tool call to fail.
Suggestion: Please either:
- Restore "news" to the enum (even if mapped internally to general) to maintain compatibility.
- Or completely remove all references to "news" from the tool descriptions to ensure the schema is self-consistent and doesn't mislead the models.
Hi team,
I noticed that a recent commit removed the "news" option from the topic parameter in the tavily_search tool schema, leaving only "general".
Reference Commit: 5e7fef3
The Issue: This is a breaking change that is causing schema validation errors. The main issue is that while "news" was removed from the topic enum, references to it still remain in other parameter descriptions, confusing the models. Error noticed -
1 validation error for call[tavily_search] topic Input should be 'general' [type=literal_error, input_value='news', input_type=str]For instance, the time_range description explicitly states:
"This feature is available for both 'general' and 'news' search topics"This inconsistency creates a trap for LLMs: the description leads them to believe "news" is a valid option, so they generate it, but the strict enum validation (["general"]) causes the tool call to fail.
Suggestion: Please either: