Smartling

Delete a comment from an issue. # Use cases - Remove an off-topic or incorrect comment # Examples - project_id="p1", issue_uid="i1", issue_comment_uid="c1" # Important This action cannot be easily undone.

smartling_delete_issue_comment

Edit the body text of an existing issue. # Use cases - Fix a typo in an issue's text - Clarify a previously-vague issue description # Examples - project_id="abc", issue_uid="i1", issue_text="Updated description"

smartling_edit_issue_text

Run an automated Linguistic Quality Assurance (LQA) evaluation on a single translated string and get back any detected quality errors. # What is an LQA evaluation? LQA evaluation checks a translation against its source string using Smartling's linguistic quality rules (e.g. blocklist compliance, omissions, mistranslations) and returns the list of errors found, each with a category and severity. It does not modify the string or record the errors anywhere; it only reports what an LQA scan would flag. # Use cases - Automatically screen a translation for quality issues right after it's produced (e.g. from MT or a translator) - Gate a workflow step transition on the string passing LQA with no critical/major errors - Spot-check a translation on demand without waiting for a scheduled LQA pass # Examples - Minimal: account_id, project_uid, hashcode, source_locale_id="en", target_locale_id="fr-FR", original_string, translation - With job/workflow context: also pass job_uid, workflow_uid, workflow_step_uid so the evaluation is attributed to that job step - With custom metadata: metadata={"integrationType": "TEST"}

smartling_execute_lqa_evaluation

Export glossary entries in various formats (CSV, XLSX, TBX). # What is glossary export? Glossary export allows you to export glossary entries with various filtering and formatting options. You can export entries in CSV, XLSX, or TBX formats with comprehensive filtering capabilities including locale filtering, entry state filtering, label filtering, and more. # Use cases - User requests to export entire glossary in a specific format - User wants to export glossary entries for specific locales - User needs to export filtered glossary entries (by state, labels, date ranges, etc.) - User wants to export glossary in TBX format for translation memory systems - User needs to export glossary entries with specific sorting or pagination # Examples - Export full glossary as CSV: {"glossary_uid": "abc123", "format": "CSV", "locale_ids": ["en-US", "fr-FR"]} - Export active entries only: {"glossary_uid": "abc123", "format": "XLSX", "entry_state": "ACTIVE"} - Export with custom filters: {"glossary_uid": "abc123", "format": "TBX", "tbx_version": "TBXcoreStructV02", "query": "marketing terms"}

smartling_export_glossary

Search issues across all projects in the current Smartling account, with pagination, sorting, filters, and optional project narrowing. The account is taken from the MCP token credentials. # Use cases - Find all HIGH-severity OPEN issues across the whole account - Cross-project triage of recent issues # Examples - All open: issue_state_codes=["OPENED"] - Narrow to two projects: project_ids=["p1","p2"]

smartling_find_account_issues

Search issues within a single Smartling project, with pagination, sorting, and rich filters. # Use cases - List all OPEN issues in a project, newest first - Find HIGH-severity TRANSLATION issues assigned to a specific user - Count + page through a project's issue backlog # Examples - All open issues: project_id="p1", issue_state_codes=["OPENED"] - By assignee: assignee_user_uid="user-1" - Sorted by creation date: sort_by={items:[{direction:"DESC", field_name:"createdDate"}]}, limit=30

smartling_find_project_issues

Get available accounts for the current user. # What are available accounts? Available accounts are Smartling accounts that the current authenticated user has access to. This tool is essential for determining which account UID to use with other Smartling MCP tools. # Use cases - User needs to determine which account UID to use before calling other Smartling tools - User wants to see all accounts they have access to - User needs to select the correct account context for their operations - Required before using other Smartling MCP tools that need accountUid parameter # Important Notes - This tool must be used before other Smartling MCP tools that require accountUid parameter - If the tool returns more than 1 account UID, the user will be asked to specify which one to use - The account UID from this response should be used in subsequent tool calls # Examples - Get available accounts: Use without any parameters - Account selection: If multiple accounts are returned, user must choose which account UID to use

smartling_get_available_accounts_for_current_user

Retrieve a list of translation jobs where a specific file is involved in a Smartling project. Returns a list of translation jobs that include the specified file. Each job object contains job metadata (UID, status, dates). **Special case - Unassigned strings**: If the file contains strings that are NOT assigned to any job, the response includes a special indicator object with all null values `{"jobUid":null,"dueDate":null,"createdDate":null,"status":null}`. This signals that some file content remains unassigned. # Use cases - Check which translation jobs contain a specific file - Identify files with unassigned strings that need job assignment - Diagnose why the connector doesn't deliver completed jobs (file content may span multiple incomplete jobs) # Parameters - project_uid: The unique identifier of the Smartling project - file_uri: The URI of the file to check job status for

smartling_list_file_jobs

Retrieve a specific glossary from the current Smartling account by its UID. # What is glossary? A Glossary is a list of terms and expressions that represent your brand, and influence your translations. Companies create Glossaries in order to provide a shared understanding of terms to be used across all business units and languages. With Smartling, you will be able to utilize the Glossary to synchronize translations across all responsible parties working on your translations. # Use cases - User requests to get detailed information about a specific glossary - Resolving glossary(s) by project: - If you have only project name then you can chain next tools to get glossaries uids: smartling_list_projects -> smartling_get_project -> smartling_get_linguistic_package (glossaries uids might be inside linguistic package) -> smartling_list_glossaries or smartling_get_glossary. - If you have project uid then you can chain next tools to get glossaries uids: smartling_get_project -> smartling_get_linguistic_package (glossaries uids might be inside linguistic package) -> smartling_list_glossaries or smartling_get_glossary.

smartling_get_glossary

Retrieve detailed information about a specific string issue. # What is a string issue? A string issue is a question, clarification request, or quality flag raised against a specific string (source or translation) inside a Smartling project. # Use cases - Inspect the full state of one issue by its UID - Read severity, type, comments count, and assignee on a single issue # Examples - Get an issue: project_id="abc123", issue_uid="issue-uid-1"

smartling_get_issue

Retrieve a single issue comment by UID. # Use cases - Read the full text of one specific comment # Examples - project_id="p1", issue_uid="i1", issue_comment_uid="c1"

smartling_get_issue_comment

Get detailed information about a specific Smartling job by its UID. # What is a job? A job is a translation task that contains files to be translated. Jobs help organize and manage translation work by grouping files together with specific target languages, due dates, and workflow requirements. # Use cases - User requests to get detailed information about a specific job - User needs to see comprehensive job details including source files, custom fields, and metadata - User wants to retrieve job priority, callback configuration, and user details - User needs to understand job creation and modification history # Examples - Get job by UID: Provide project_id and job_uid parameters - Retrieve job details: Returns complete job configuration with priority, source files, and custom fields - Check job progress: View job status, creation date, due date, and completion dates # Job Details Response The response includes extended job information beyond the basic job list: - Job priority level - Array of source files in the job - Callback method and URL configuration - Creation and modification user details - Custom field values - Complete job metadata and timestamps

smartling_get_job

Get the audit history of a specific Smartling job. # What is job history? Job history is the chronological audit trail of everything that has happened to a job: creation, status changes, content additions/removals, due date changes, priority changes, and rush request create/remove events. Each entry records the action, when it started/ended, who (if anyone) performed it, and event-specific details. # Use cases - User wants to know who changed a job's due date or priority, and when - User needs to see when content was added to or removed from a job - User wants an audit trail of status changes for a job - User is investigating unexpected job behavior and needs the sequence of events # Examples - Get recent history: Provide project_id and job_uid (returns up to 100 most recent entries) - Page through longer histories: Use offset with limit to retrieve subsequent pages, guided by totalCount in the response # Pagination - limit: Page size, 1-100 (default 100 if omitted) - offset: Zero-based offset into the history (default 0 if omitted) - totalCount in the response tells you how many entries exist in total

smartling_get_job_history

Retrieve a specific linguistic package from the current Smartling account by its UID. # What is linguistic package? A linguistic package is a collection of translation resources, including glossaries and style guides that are used to ensure consistent and accurate translations. This bundle contains settings that determine which linguistic assets (glossaries, style guides) are provided to translators for your projects. # Use cases - User requests to get detailed information about a specific linguistic package. - Resolving linguistic package by project: - If you have only project name then you can chain next tools to get linguistic package: smartling_list_projects -> smartling_get_project -> smartling_get_linguistic_package. - If you have project uid then you can chain next tools to get linguistic package: smartling_get_project -> smartling_get_linguistic_package.

smartling_get_linguistic_package

Retrieve a specific project from the current Smartling account by its UID. # What is project? A project is a translation environment for the various types of content user wants to translate. # Use cases - User requests to get detailed information about a specific project.

smartling_get_project

Get specific style guide by its unique identifier. # What is styleguide? A Style Guide is a collection of rules about your preferences regarding content formatting, writing tone, and style. It is a tool for ensuring the language and tone of your brand is found accurate and consistent in your translations. # Use cases - User requests to get detailed information about a specific style guide.

smartling_get_styleguide

Get word count report from Smartling in CSV format for efficient analysis. # What is word count report? A word count report provides detailed information about word counts and weighted word counts for translation work. It includes data about projects, jobs, translation resources, agencies, locales, workflow steps, and fuzzy matching profiles. # API Constraints **CRITICAL**: The date range between start_date and end_date must be **less than 1 year (365 days)**. The API will return a validation error if the range exceeds this limit. # IMPORTANT: Apply Filters to Minimize Response Size **Always encourage users to apply as many filters as possible** to keep response size manageable: - **project_ids**: Filter by specific projects (most important filter) - **target_locale_ids**: Filter by specific target locales - **job_uids**: Filter by specific jobs - **user_uids**: Filter by specific translation resources - **workflow_step_types**: Filter by specific workflow steps (use smartling_get_workflow_step_types tool first) - **start_date/end_date**: Use narrow date ranges - **fields**: Request only the columns you need (see field list below) # Recommended Field Selection **Minimize the number of fields in the 'fields' parameter**. Only include what's needed for the specific query: - Minimal: "projectId,projectName,targetLocaleId,wordCount" - With job info: "projectId,projectName,targetLocaleId,jobUid,jobName,wordCount" - With translator: "projectId,targetLocaleId,translationResourceName,workflowStepType,wordCount" # Examples - Find projects with most words in French: {"start_date": "2024-01-01", "end_date": "2024-12-31", "target_locale_ids": ["fr-FR"], "fields": "projectId,projectName,wordCount"} - Find strings in AI Review step: {"start_date": "2024-01-01", "end_date": "2024-12-31", "workflow_step_types": ["AI Review"], "fields": "projectId,jobName,workflowStepType,wordCount"} - Translator productivity: {"start_date": "2024-01-01", "end_date": "2024-01-31", "user_uids": ["user-123"], "fields": "translationResourceName,targetLocaleId,wordCount"}

smartling_get_word_count_report

Get available workflow step types from Smartling for use in reporting and filtering. # What are workflow step types? Workflow step types define the different stages in a translation workflow, such as "Translation", "Review", "Edit", etc. This tool retrieves the complete list of available step types that can be used for filtering in other report tools. # Examples - Get all available workflow step types: {} (no parameters needed)

smartling_get_workflow_step_types

List content assignments for the current Smartling account. # What is a content assignment? A content assignment represents a unit of translation work assigned to a translator (user) or an agency within a specific workflow step of a translation job. Each assignment ties together a project, target locale, workflow step, translation job, and the assignee responsible for completing the work, along with the word count and due dates relevant to that step. # Use cases - Discover who (translator or agency) is assigned to active translation work across the account - Audit workflow ownership across projects, locales, and jobs - Identify unassigned content assignments (entries where userUid and agencyUid are null) - Review upcoming workflow-step or overall job due dates for resource planning - Inspect word counts per workflow step for capacity planning # Examples - List all content assignments for the current account: {} (no parameters)

smartling_list_content_assignments

List glossaries by set of filters. # Use cases - User requests to retrieve glossaries: - User asked to retrieve a list of all glossaries - User asked to search for glossaries by name or description - User asked to filter glossaries by state (active, archived, both) - User asked to look for glossary for a specific target locale - User asked to retrieve several glossaries by their UIDs

smartling_list_glossaries

List all comments on an issue. # Use cases - Read the discussion thread on an issue before responding - Audit comment activity for a specific issue # Examples - project_id="p1", issue_uid="i1"

smartling_list_issue_comments

List jobs from a specific Smartling project with optional filtering. # Use cases - User requests to retrieve all jobs from a project - User wants to filter jobs by name or status - User needs to see job progress and status information - User wants to understand what translation work is available or in progress # Examples - List all jobs in a project: Use only project_id parameter - Find jobs by name: Include job_name parameter for filtering - Filter by status: Use job_statuses parameter with specific statuses - Find active jobs: Use job_statuses=["IN_PROGRESS","AWAITING_AUTHORIZATION"] # Job Statuses Available job statuses include: - AWAITING_AUTHORIZATION: Job is waiting for approval to start - IN_PROGRESS: Job is currently being worked on - COMPLETED: Job has been finished - CANCELLED: Job was cancelled before completion - CLOSED: Job was closed after completion

smartling_list_jobs

List all linguistic packages from the current Smartling account. # Use cases - User requests to get a list of available linguistic packages. # Examples - List all linguistic packages: {"account_id": "your-account-uid"}

smartling_list_linguistic_packages

List projects from the current Smartling account by name. # Use cases - User requests to retrieve projects: - User asked to retrieve a list of all projects - User asked to search for projects by name - User asked to filter archived projects - User asked to look for projects with a specific project type codes - Resolving project by project name: - If you have only project name then you can chain next tools to get project details: smartling_list_projects -> smartling_get_project (project list tool returns a simplified objects list with no additional information, so it needs to be followed by a get project call). # Examples - List all projects: {} (no parameters) - Find projects by name: { "project_name_filter": "Mobile App" } - List active projects of specific type: { "include_archived": false, "project_type_codes": ["web", "mobile"] }

smartling_list_projects

List style guides from the current Smartling account by name. # Use cases - User requests to retrieve style guides: - User requests to retrieve all style guides. - User requests to retrieve style guides based on their names. # Examples - List all style guides: {} (no parameters) - Find style guides by name: { "name": "Marketing" }

smartling_list_styleguides

List users from a Smartling account with optional filtering. # What are users in Smartling? Users are individuals who have access to the Smartling platform with specific roles and permissions. They can be translators, project managers, reviewers, or other team members involved in the localization process. # Use cases - User requests to retrieve all users from the account - User wants to search for specific users by name - User needs to filter users by role or project assignment - User wants to find users with specific status (active, pending) - User wants to find users assigned to specific projects - User needs to retrieve user contact information # Examples - List all users: Use without any parameters - Search by name: Use keyword parameter to search in first and last names - Filter by role: Use user_roles parameter with specific role names - Find project users: Use project_ids parameter to find users assigned to specific projects - Get active users: Use user_status="ACTIVE" to filter only active users # User Statuses Available user statuses include: - ALL: All users regardless of status (default) - ACTIVE: Users who are currently active - PENDING: Users who have pending invitations # Common Roles Common user roles in Smartling include: - ROLE_TRANSLATION_RESOURCE: Translation Resource - ROLE_PROJECT_MANAGER: Project Manager - ROLE_ACCOUNT_OWNER: Account Owner

smartling_list_users

List workflows from a specific Smartling project with optional filtering. # What is a workflow? A workflow in Smartling defines the translation process steps that content goes through from source to target languages. Each workflow contains steps like translation, editing, review, and publishing, with specific configurations for each step. # Use cases - User requests to retrieve all workflows for a project - User wants to search workflows by keyword - User needs to filter workflows by specific locales - User wants to find workflows with specific UIDs or step UIDs - User needs to understand the translation process configuration # Important Notes - Results are limited to the first 100 workflows to avoid response size limits - Response includes essential workflow and step information with verbose fields removed for performance # Examples - List all workflows in a project: { "project_id": "project-123" } - Search workflows by keyword: { "project_id": "project-123", "keyword": "marketing" } - Filter workflows by locales: { "project_id": "project-123", "locale_ids": ["es-ES", "fr-FR"] } - Find specific workflows: { "project_id": "project-123", "workflow_uids": ["workflow-uid-1", "workflow-uid-2"] }

smartling_list_workflows

Translates file content using machine translation. # Use cases - User requests to translate files (text or binary). Two ways to supply the file - provide exactly one of `upload_id` or `file_content`: 1. `upload_id` (preferred, default choice): call smartling_request_upload_url first, PUT the file to the returned URL, then pass the returned upload_id here. Use this whenever you can run shell commands (e.g. Claude Code, Codex CLI, opencode, Cursor, Cline, Windsurf), regardless of file size or type - do not fall back to file_content just because the file is small. 2. `file_content` (inline base64): only use this when you cannot run shell commands (e.g. claude.ai) or the user explicitly asks for inline/base64 content. Auto-detects source language if `source_locale` not provided. Must ask user for `target_locale` if not specified.

smartling_machine_translate_file

Translates text content using machine translation. # Use cases - User requests to translate text or simple text files (txt format). For file translation, read the file contents first. Split long text into sentence-based chunks to preserve meaning and context - avoid breaking mid-sentence or splitting related content. Each chunk becomes an object `{ "key": "<unique_key>", "source_text": "<text_to_translate>" }` with `key` (unique identifier) and `source_text` (content to translate) in the `text_items_to_translate` array. Total request size must not exceed 10MB. Auto-detects source language if `source_locale` not provided. Must ask user for `target_locale` if not specified.

smartling_machine_translate_text

Match terms within a specific glossary. # Use cases - User requests to find specific terms in a source and translated strings. - User requests to find specific terms in a source only strings. # Examples - Match glossary terms in source and translated strings: { "glossary_uids": ["glossary-uid-1"], "source_locale_id": "en-US", "translation_locale_id": "fr-FR", "source_text_to_match": [ { "key": "text-1", "text": "Hello" }, { "key": "text-2", "text": "World" } ], "translation_text_to_match": [ { "key": "text-1", "text": "Bonjour" }, { "key": "text-2", "text": "Monde" } ] } - Match glossary terms in source only strings (pass only source strings but leave translation strings empty and preserve keys): { "glossary_uids": ["glossary-uid-1"], "source_locale_id": "en-US", "translation_locale_id": "fr-FR", "source_text_to_match": [ { "key": "text-1", "text": "Hello" }, { "key": "text-2", "text": "World" } ], "translation_text_to_match": [ { "key": "text-1", "text": "" }, { "key": "text-2", "text": "" } ] }

smartling_match_glossary_terms

Open or close (resolve) an issue. # Use cases - Resolve an issue once the underlying string question is answered - Re-open a resolved issue that needs more discussion # Examples - Resolve: project_id="p1", issue_uid="i1", issue_state="RESOLVED" - Re-open: issue_state="OPENED"

smartling_open_or_close_issue

Remove all tags from strings in a Smartling project. # Use cases - Clean slate for string reorganization - remove all tags before applying new categorization - Prepare strings for migration to a different tagging system - Batch clean up of strings during project restructuring # Examples - Clean up strings before project migration - Remove all tags from deprecated feature strings - Reset tagging for strings that will be recategorized - Clean up test strings that accumulated development tags # Parameters - project_id: The unique identifier of the Smartling project - string_hashcodes: Array of string hashcodes to remove all tags from (max 1000 hashcodes) # Important Note This operation removes ALL tags from the specified strings. Use with caution as this action cannot be easily undone.

smartling_remove_all_tags_from_strings

Remove strings from an existing Smartling job by their hashcodes. # Use cases - User wants to remove specific strings from a translation job - User needs to exclude certain content from an existing job - User wants to remove strings for specific target locales only - User needs to clean up job content before authorization # Examples - Remove strings from job: Provide project_id, job_uid, and array of hashcodes - Remove for specific locales: Include target_locale_ids to remove strings for specific languages only - Clean up job: Remove unnecessary strings before job authorization # Parameters - hashcodes: Array of string hashcodes to remove from the job - target_locale_ids: (Optional) Specific target locales to remove strings for

smartling_remove_strings_from_job

Remove tags from strings in a Smartling project. # Use cases - Remove outdated tags from strings # Examples - Clean up categorization tags: tags=["old-feature", "deprecated"] - Remove release tags after deployment: tags=["v2.0", "pending-release"] # Parameters - project_id: The unique identifier of the Smartling project - tags: Array of tag strings to remove (max 100 tags, each max 128 characters) - string_hashcodes: Array of string hashcodes to remove tags from (max 1000 hashcodes)

smartling_remove_tags_from_strings

Requests a short-lived URL for uploading a local file, for use with other tools that accept an "upload_id" parameter (e.g. smartling_machine_translate_file). # Use cases - Preferred, default first step before translating or otherwise processing any local file, whenever you can run shell commands (e.g. Claude Code, Codex CLI, opencode, Cursor, Cline, Windsurf) - use this instead of inline base64 content regardless of file size or type. Only usable by clients that can run shell commands (e.g. Claude Code, Codex CLI, opencode, Cursor, Cline, Windsurf) to PUT the file to the returned URL - not usable from claude.ai or other clients without local file/shell access, which should keep using inline base64 content instead. The returned URL expires in 15 minutes. Upload immediately after requesting it, then pass the returned upload_id to the tool that needs the file.

smartling_request_upload_url

Search for strings in a Smartling project using various filters. # What is string searching? String searching allows you to find translation strings within a Smartling project based on various criteria like status, content, target locales, and more. This helps manage and locate specific strings for translation workflows. # Use cases - User requests to find strings by status (e.g., "untranslated", "translated", "approved") - User wants to search strings by source content keywords - User needs to find strings for specific target locales - User wants to discover strings in a project for review or analysis - User needs to find strings matching specific criteria for translation management # Examples - Search all untranslated strings in a project: Use project_uid and status parameters - Find strings containing specific text: Use project_uid and source_keyword parameters - Search strings for specific locales: Use project_uid and locale_ids parameters - General string discovery: Use project_uid parameter only for all strings (up to 100 results)

smartling_search_strings

Search translation memory for similar translations in a Smartling project. # What is translation memory? A Translation Memory is a cloud-based database of all translations that have occurred within your Smartling account, as well as any translations that you may have imported to Smartling. Translation Memories are used to leverage (or read from) previously used translations with new source content - allowing for cost savings, time savings, and translation consistency. As translations are saved, they write to a designated Translation Memory. # Use cases - Useful for finding existing translations that match or are similar to source text. # Examples - Search for translations of "Hello world" in French: { "project_id": "project-uid-123", "locale_id": "fr-FR", "search": "Hello world", "minimum_score": 0.7 } - Find exact matches for UI text: { "project_id": "project-uid-123", "locale_id": "es-ES", "search": "Click here to continue", "minimum_score": 0.95 }

smartling_search_translation_memory

Mark an issue as answered or un-answered. # Use cases - Mark an issue answered after a reply is posted - Clear the answered flag if the reply is later found inadequate # Examples - project_id="p1", issue_uid="i1", answered=true

smartling_update_issue_answered

Assign an issue to a specific user. # Use cases - Route an issue to the responsible PM or translator for action # Examples - project_id="p1", issue_uid="i1", assignee_user_uid="user-xyz"

smartling_update_issue_assignee

Edit the text of an existing comment. # Use cases - Fix a typo in a comment - Update outdated guidance in a comment # Examples - project_id="p1", issue_uid="i1", issue_comment_uid="c1", comment_text="Edited"

smartling_update_issue_comment