---
title: ToolRouter — Agent Use Case Guide
description: Step-by-step guide for completing a task with a specific AI agent using ToolRouter.
url: https://toolrouter.com/tools/translate/use-cases/translate-marketing-content/copilot
---
# How to Translate Marketing Content with Copilot

Copilot brings translation directly into your i18n workflow, treating localization as a code task rather than an external handoff. Translate locale files, UI strings, and documentation without leaving your editor, then review the changes in your diff view alongside the rest of your code. This is ideal for developers who maintain localization as part of the build process, ensuring that new features ship with translations rather than accumulating a backlog of untranslated strings that need a separate localization pass.

## Setup

{"mcpServers":{"toolrouter":{"command":"npx","args":["-y","toolrouter-mcp"]}}}

## Steps

1. Add ToolRouter to your Copilot MCP configuration
2. In Copilot Chat: "Translate all marketing strings in this file to Spanish using the translate tool"
3. Copilot translates each string and updates your localization files directly
4. Review the changes in your diff view
5. Ask Copilot to generate locale files for additional languages

## Example Prompt

```
Translate all the marketing copy in our en.json locale file to French and German using the translate tool. Output as fr.json and de.json.
```

## Tips

- Copilot can update i18n files directly in your project structure
- Use with JSON, YAML, or .properties locale file formats
- Ask Copilot to validate that all translation keys match across locale files
