Google Translation | Tooluse.net Help

Translate explicit plain-text inputs through Google Cloud Translation Basic v2 using an enabled customer Cloud project API key or an existing platform-provided connection when available. Source language can be detected. No Advanced v3 projects, documents, glossaries, batches or managed Google OAuth.

What you can do (1)

What you can do

Available commands: 1 (1 read, 0 write). Enable only the commands your application needs.

Command	Effect
Translate text — `google.translate`	Read

Connect and use

Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.

Get your provider credentials

Follow these steps for Google Translation, then enter the issued values in the connection form below.

Create/select a Google Cloud project, enable Cloud Translation API and billing, then use APIs & Services → Credentials to create a separate API key restricted to Cloud Translation API. Paste it into API Key here, select Translate text and save. Server/IP restrictions must admit Tooluse.net; browser-referrer keys are not server credentials. Call the Basic v2 example with texts and targetLanguage, optionally sourceLanguage. Google meters translated characters. This key does not grant Advanced v3, documents/glossaries or Google account OAuth. If your workspace offers a platform-provided connection, select it and call the example without obtaining another provider key.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field	Requirement
API Key	Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "texts": [
      "Hello"
    ],
    "targetLanguage": "fr"
  }
}'

Commands

Translate text — google.translate

Translate the supplied plain-text strings into targetLanguage with the existing Basic v2 NMT request. Optionally specify sourceLanguage; otherwise Google detects it. Requests are metered by Google. This is a POST read, not a resource write or an OAuth account connection.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter	Type	Required in parent	Description	Constraints
`texts`	array	Required	Explicit strings to translate in this invocation; Google character billing applies.	`minItems: 1; maxItems: 10`
`texts[]`	string	Optional		`maxLength: 1000`
`targetLanguage`	string	Required	Supported Google target language code, e.g. fr.	`maxLength: 1000`
`sourceLanguage`	string	Optional	Optional supported source language code; omit to detect the source.	`maxLength: 1000`

Full JSON Schema

Full JSON Schema

Example input

{
  "texts": [
    "Hello"
  ],
  "targetLanguage": "fr"
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation