Skip to content

Conversation

@guy-hartstein
Copy link

@guy-hartstein guy-hartstein commented Dec 16, 2025

This pull request focuses on a comprehensive renaming and documentation update for the Tavily extractor tool across English, Korean, and Portuguese documentation and the Python codebase. The main goal is to standardize the tool's name from TavilyExtractorTool to TavilyExtractTool, clarify configuration options, and improve documentation accuracy and usability for multiple languages.

Key changes include:

Tool Renaming and Code Updates

  • Renamed all references of TavilyExtractorTool to TavilyExtractTool in Python imports and exports within crewai_tools modules, ensuring consistent usage throughout the codebase. [1] [2] [3]

English Documentation Enhancements

  • Updated all English documentation pages to use TavilyExtractTool instead of TavilyExtractorTool, including code examples and navigation cards. [1] [2] [3] [4] [5]
  • Expanded and clarified configuration options, separating agent-settable (runtime) and user-settable (initialization) parameters, and added new options such as query, format, chunks_per_source, and extra_kwargs.
  • Improved feature list to include query-based reranking and updated Tavily API documentation links. [1] [2]

Korean Documentation Updates

  • Renamed the tool and updated all references in Korean documentation to match the new English naming and configuration, including code examples, parameter explanations, and feature lists. [1] [2] [3] [4] [5]
  • Clarified runtime and initialization parameters, added new options, and improved translation consistency. [1] [2]
  • Updated Tavily API documentation links to the latest endpoints.

Portuguese Documentation Updates

  • Renamed the tool and updated all references in Portuguese documentation, including navigation, code examples, and configuration details. The file was also renamed for consistency. [1] [2] [3] [4] [5] [6]
  • Updated configuration and feature lists, and corrected Tavily API documentation links.

These changes ensure that the tool's naming, usage instructions, and configuration are clear, accurate, and consistent across all supported languages and in the codebase.


Note

Renames TavilyExtractorTool to TavilyExtractTool, adds new extraction parameters, and updates docs (EN/KO/PT) and tool specs/exports accordingly.

  • Library (crewai_tools):
    • Tool rename: TavilyExtractorTool -> TavilyExtractTool in imports/exports (crewai_tools/__init__.py, tools/__init__.py).
    • Implementation (tools/tavily_extractor_tool/tavily_extractor_tool.py):
      • Rename classes/schemas to TavilyExtractTool/TavilyExtractToolSchema.
      • Add runtime args: extract_depth (override), query.
      • Add init options: format, include_favicon, include_usage, chunks_per_source, extra_kwargs.
      • Wire new params into sync/async extract() calls; update install prompts.
    • Specs (tool.specs.json): update humanized/name/schema titles from TavilyExtractorTool to TavilyExtractTool.
    • Docs: Update README under tavily_extractor_tool/ to new name and argument notes (incl. extra_kwargs).
  • Documentation site:
    • EN/KO: Rename card to "Tavily Extract Tool" and update tool pages to TavilyExtractTool, add clarified config sections (agent-settable vs init), new options (e.g., query, format, chunks_per_source, extra_kwargs), and updated Tavily API links.
    • PT-BR: Add "Tavily Extract Tool" card and new page tavilyextracttool.mdx with updated examples/config; update API links.

Written by Cursor Bugbot for commit 259ca3d. This will update automatically on new commits. Configure here.

…ameters

- Rename class from TavilyExtractorTool to TavilyExtractTool for consistency
- Add new parameters: format, include_favicon, include_usage, chunks_per_source, query
- Add extra_kwargs for forward compatibility with tavily-python updates
- Update documentation across en, ko, pt-BR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant