Split and rename multiple toolkits

Author: EricGustin

examples/code/guides/agentauth/auth_with_google.js

@@ -5,7 +5,7 @@ import { google } from "googleapis";
  * In this example, we will use Arcade to authenticate with Google and
  * retrieve Gmail messages.
  *
- * Consider using the Arcade Google toolkit, which simplifies the process for
+ * Consider using the Arcade Gmail toolkit, which simplifies the process for
  * retrieving email messages even further!
  *
  * Below we are just showing how to use Arcade as an auth provider, if you need to directly get a token to use with Google.

examples/code/guides/agentauth/auth_with_google.py

@@ -8,7 +8,7 @@
 In this example, we will use Arcade to authenticate with Google and
 retrieve Gmail messages.
 
-Consider using the Arcade Google toolkit, which simplifies the process for
+Consider using the Arcade Gmail toolkit, which simplifies the process for
 retrieving email messages even further!
 
 Below we are just showing how to use Arcade as an auth provider, if you need to directly get a token to use with Google.

examples/code/home/crewai/custom_auth_flow.py

@@ -50,7 +50,7 @@ def tool_manager_callback(tool_manager: ArcadeToolManager, tool_name: str, **too
 
 manager = ArcadeToolManager(executor=tool_manager_callback)
 
-tools = manager.get_tools(tools=["Google.ListEmails"], toolkits=["Slack"])
+tools = manager.get_tools(tools=["Gmail.ListEmails"], toolkits=["Slack"])
 
 crew_agent = Agent(
     role="Main Agent",

examples/code/home/crewai/use_arcade_tools.py

@@ -4,7 +4,7 @@
 
 manager = ArcadeToolManager(default_user_id="user@example.com")
 
-tools = manager.get_tools(tools=["Google.ListEmails"])
+tools = manager.get_tools(tools=["Gmail.ListEmails"])
 
 
 crew_agent = Agent(

examples/code/home/mcp/streamable-http/typescript-client.ts.fake

@@ -66,7 +66,7 @@ try {
   const callToolRequest: CallToolRequest = {
     method: "tools/call",
     params: {
-      name: "Google_ListEmails",
+      name: "Gmail_ListEmails",
       arguments: {
         n_emails: 5,
       },

pages/home/auth-providers/google.mdx

@@ -6,7 +6,7 @@ The Google auth provider enables tools and agents to call Google/Google Workspac
 
 <Tip>
   Want to quickly get started with Google services in your agent or AI app? The
-  pre-built [Arcade Google toolkit](/toolkits/productivity/google/gmail) is what
+  pre-built [Arcade Gmail toolkit](/toolkits/productivity/gmail) is what
   you want!
 </Tip>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Google auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Google toolkit](/toolkits/productivity/google/gmail), which provides pre-built tools for interacting with Google services
+- The [Arcade Gmail toolkit](/toolkits/productivity/gmail), which provides pre-built tools for interacting with Google services
 - Your [app code](#using-google-auth-in-app-code) that needs to call Google APIs
 - Or, your [custom tools](#using-google-auth-in-custom-tools) that need to call Google APIs
 
@@ -149,9 +149,9 @@ Use `client.auth.start()` to get a user token for Google APIs:
 
 ## Using Google auth in custom tools
 
-You can use the pre-built [Arcade Google toolkit](/toolkits/productivity/google/gmail) to quickly build agents and AI apps that interact with Google services like Gmail, Calendar, Drive, and more.
+You can use the pre-built Arcade Google toolkits, like [Arcade Gmail toolkit](/toolkits/productivity/gmail), to quickly build agents and AI apps that interact with Google services like Gmail, Calendar, Drive, and more.
 
-If the pre-built tools in the Google toolkit don't meet your needs, you can author your own [custom tools](/home/build-tools/create-a-toolkit) that interact with Google APIs.
+If the pre-built tools in the Google toolkits don't meet your needs, you can author your own [custom tools](/home/build-tools/create-a-toolkit) that interact with Google APIs.
 
 Use the `Google()` auth class to specify that a tool requires authorization with Google. The `context.authorization.token` field will be automatically populated with the user's Google token:
 

pages/home/auth-providers/index.mdx

@@ -157,7 +157,7 @@ You can create multiple auth providers of the same type, for example, you can ha
 
 However, Arcade's tools are configured to select an auth provider by the type. This means that if you have multiple auth providers of the same type, Arcade will not know which one to use and authorizing the tool will fail.
 
-To work around this, you can fork Arcade's tools and modify them to specify your own auth provider by the unique ID that you give each of them. For example, if you have two Google auth providers, `acme-google-calendar` and `acme-google-email`, you can modify Arcade's Google.ListEmails tool like this:
+To work around this, you can fork Arcade's tools and modify them to specify your own auth provider by the unique ID that you give each of them. For example, if you have two Google auth providers, `acme-google-calendar` and `acme-google-email`, you can modify Arcade's Gmail.ListEmails tool like this:
 
 ```python
 @tool(

pages/home/auth/auth-tool-calling.mdx

@@ -43,7 +43,7 @@ const client = new Arcade(); // Automatically finds the `ARCADE_API_KEY` env var
 
 ### Authorize a tool directly
 
-Many tools require authorization. For example, the `Google.ListEmails` tool requires authorization with Google.
+Many tools require authorization. For example, the `Gmail.ListEmails` tool requires authorization with Google.
 
 This authorization must be approved by the user. By approving, the user allows your agent or app to access only the data they've approved.
 
@@ -57,7 +57,7 @@ USER_ID = "you@example.com"
 
 # Request access to the user's Gmail account
 auth_response = client.tools.authorize(
-  tool_name="Google.ListEmails",
+  tool_name="Gmail.ListEmails",
   user_id=USER_ID,
 )
 
@@ -74,7 +74,7 @@ const userId = "you@example.com";
 
 // Request access to the user's Gmail account
 const authResponse = await client.tools.authorize({
-  tool_name: "Google.ListEmails",
+  tool_name: "Gmail.ListEmails",
   user_id: userId,
 });
 
@@ -117,7 +117,7 @@ Once the user has approved the action, you can run the tool. You only need to pa
 
 ```python
 emails_response = client.tools.execute(
-    tool_name="Google.ListEmails",
+    tool_name="Gmail.ListEmails",
     user_id=USER_ID,
 )
 print(emails_response)
@@ -128,7 +128,7 @@ print(emails_response)
 
 ```js
 const emailsResponse = await client.tools.execute({
-  tool_name: "Google.ListEmails",
+  tool_name: "Gmail.ListEmails",
   user_id: userId,
 });
 

pages/home/auth/call-third-party-apis-directly.mdx

@@ -168,7 +168,7 @@ For each item in the list/array, you could use the [`users.messages.get`](https:
 </Steps>
 
 <Note>
-  Consider using the [Arcade Google toolkit](/toolkits/productivity/google/gmail), which simplifies the process for retrieving email messages even further! The pattern described here is useful if you need to directly get a token to use with Google in other parts of your codebase.
+  Consider using the [Arcade Gmail toolkit](/toolkits/productivity/gmail), which simplifies the process for retrieving email messages even further! The pattern described here is useful if you need to directly get a token to use with Google in other parts of your codebase.
 </Note>
 
 ### How it works

pages/home/auth/how-arcade-helps.mdx

@@ -28,7 +28,7 @@ With Arcade, developers can now create agents that can _act as the end users of
 
 ### Auth permissions and scopes
 
-Each tool in Arcade's toolkits has a set of required permissions - or, more commonly referred to in OAuth2, **scopes**. For example, the [`Google.SendEmail`](/toolkits/productivity/google/gmail#sendemail) tool requires the [`https://www.googleapis.com/auth/gmail.send`](https://developers.google.com/identity/protocols/oauth2/scopes#gmail) scope.
+Each tool in Arcade's toolkits has a set of required permissions - or, more commonly referred to in OAuth2, **scopes**. For example, the [`Gmail.SendEmail`](/toolkits/productivity/gmail#gmailsendemail) tool requires the [`https://www.googleapis.com/auth/gmail.send`](https://developers.google.com/identity/protocols/oauth2/scopes#gmail) scope.
 
 A scope is what the user has authorized someone else (in this case, the AI agent) to do on their behalf. In any OAuth2-compatible service, each kind of action requires a different set of permissions. This gives the user fine-grained control over what data third-party services can access and what actions can be executed in their accounts.
 
@@ -41,7 +41,7 @@ To learn how Arcade allows for actions (tools) to be authorized through OAuth2 a
 
 ### Tools that don't require authorization
 
-Some tools, like [`Search.SearchGoogle`](/toolkits/search/google_search#searchgoogle), allow AI agents to retrieve information or perform actions without needing user-specific authorization.
+Some tools, like [`GoogleSearch.Search`](/toolkits/search/google_search#googlesearchsearch), allow AI agents to retrieve information or perform actions without needing user-specific authorization.
 
 <Tabs items={["Python", "JavaScript"]} storageKey="preferredLanguage">
 <Tabs.Tab>
@@ -50,9 +50,9 @@ from arcadepy import Arcade
 
 client = Arcade(api_key="arcade_api_key")  # or set the ARCADE_API_KEY env var
 
-# Use the Search.SearchGoogle tool to perform a web search
+# Use the GoogleSearch.Searchtool to perform a web search
 response = await client.tools.execute(
-    tool_name="Search.SearchGoogle",
+    tool_name="GoogleSearch.Search",
     input={"query": "Latest AI advancements"},
 )
 print(response.output.value)
@@ -64,9 +64,9 @@ import { Arcade } from "@arcadeai/arcadejs";
 
 const client = new Arcade(api_key="arcade_api_key");  // or set the ARCADE_API_KEY env var
 
-// Use the Search.SearchGoogle tool to perform a web search
+// Use the GoogleSearch.Search tool to perform a web search
 const response = await client.tools.execute({
-  tool_name: "Search.SearchGoogle",
+  tool_name: "GoogleSearch.Search",
   input: { query: "Latest AI advancements" },
 });
 console.log(response.output.value);