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

Delete a manual LQA finding that was recorded by mistake. # Use cases - Remove a finding recorded against the wrong string or in error # Examples - project_id, target_locale_id, hashcode, recorded_error_uid # Important This action cannot be easily undone.

smartling_delete_lqa_error

Download translated content for a file from Smartling - as a single file for one locale, a zip of all locales for one file, or a zip of multiple files across specified locales. # Modes - SINGLE_LOCALE: one file, one locale - returns the translated file itself - ALL_LOCALES_ZIP: one file, every locale that has translations - returns a zip archive - MULTIPLE_FILES_ZIP: multiple files, each with its own locale list - returns a zip archive (up to 500 file/locale combinations total) # Use cases - User wants to download the French translation of a single file - User wants every locale's translation of one file bundled into one zip - User wants a zip covering several files across several locales in one download # Examples - Single file, one locale: mode=SINGLE_LOCALE, file_uri="strings.json", locale_id="fr-FR" - One file, all locales: mode=ALL_LOCALES_ZIP, file_uri="strings.json" - Several files: mode=MULTIPLE_FILES_ZIP, files=[{"file_uri":"a.json","locale_ids":["fr-FR","de-DE"]},{"file_uri":"b.xml","locale_ids":["es-ES"]}] # Important Notes - For MADCAP, DITA_ZIP, CSV, XLSX_TEMPLATE, and XCSTRINGS files only, locale_id in SINGLE_LOCALE mode also accepts a comma-separated locale list or "all" to get one combined (non-zip) file with all of those locales. - MULTIPLE_FILES_ZIP returns a "no files found" text response instead of a file when file_filter=PUBLISHED_FILES_ONLY excludes every requested file. - Returns a presigned download URL, not the file content itself. The URL is valid for 15 minutes, so fetch it promptly - re-run this tool to get a fresh URL if it expires.

smartling_download_translated_file

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_id, 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 LQA findings across the whole Smartling account as a CSV file, using the same filters as smartling_find_account_lqa_errors. # Use cases - Produce a CSV report of findings for offline analysis or sharing # Examples - All critical findings this quarter: severity_name_uids=["sev-critical"], created_date_after="2026-07-01T00:00:00Z" Returns a presigned download URL, not the CSV content itself. The URL is valid for 15 minutes, so fetch it promptly - re-run this tool to get a fresh URL if it expires.

smartling_export_account_lqa_errors

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"} # Return value Returns a presigned download URL for the exported file, not the file content itself. The URL is valid for 15 minutes, so fetch it promptly - re-run this tool to get a fresh URL if it expires.

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 LQA findings across the whole Smartling account, with rich filters. The account is taken from the MCP token credentials. # Use cases - Find all critical-severity findings account-wide - Find findings for a specific job, schema, workflow step, locale, or reviewer - Page through the full set of recorded findings with sort/offset/limit # Examples - Critical findings: severity_name_uids=["sev-critical"] - Findings in a job: job_filter={translation_job_uids: ["job-1"], presence: "HAS_ANY"} - Sorted, paginated: sort_by=[{field_name: "errorCreatedDate", direction: "DESC"}], limit=50

smartling_find_account_lqa_errors

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

Get a file's translation status for every locale, and its last-modified date per locale. Returns two independent results - `status` (per-locale progress and word counts) and `lastModified` (per-locale last-modified dates) - from two separate Smartling API calls. They are not merged together. # Use cases - User wants completed/authorized string and word counts per locale for a file - User wants to know which locales were updated most recently for a file # Examples - Check a file's status: Provide project_id and file_uri

smartling_get_file_status

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

Get the per-asset, per-locale results of one instant (machine) translation request. # Use cases - Check progress or final results of a request made via smartling_integration_request_instant_translation - Diagnose a failed instant-translation request (per-locale errorMessage) # Examples - Full results for a request: action_uid="action-123" - Only failed items: action_uid="action-123", state="FAILED"

smartling_integration_get_instant_translation_request

Discover everything needed to search a connector's content: connection status, valid filter values, and locale mappings. # Why call this first smartling_integration_search_assets needs asset types, Smartling submission statuses, connector-specific filter values, and Smartling-locale codes to filter by - all of which vary per connector and per account. This tool fetches all of it in one call so the caller can construct a valid search_assets call afterward. # Use cases - Before searching a connector's content, to learn valid asset_type/submission_status/ custom_filters values - To check whether a connector is actually connected/usable for a project before proceeding # Examples - Discover Intercom's filters in project "proj-123": project_id="proj-123", integration_id="intercom" # Response - connected=false means the integration isn't ready for this project - every other field is omitted, and smartling_integration_search_assets should not be called yet. - connectorFilters lists every connector-specific custom_filters key/value pair available, including which asset_type (if any) it applies to.

smartling_integration_get_search_context

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 detailed status of a Smartling job batch, including per-file and per-locale progress. # What is a job batch? A job batch is a session for uploading multiple files and attaching them to a translation job in one coordinated flow, instead of the caller polling each upload/parse/attach step individually. See smartling_create_job_batch for how batches are created. # Use cases - User wants to check whether all files in a batch have finished uploading and attaching - User needs to see per-file, per-locale string counts after a batch executes - User is debugging why a batch's files are stuck or failed # Examples - Check batch progress: Provide project_id and batch_uid - Debug a stuck batch: Inspect files[].status and files[].errors for the failing file

smartling_get_job_batch_status

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

Get per-locale, per-workflow-step progress for a translation job, or for a single file within it. # Use cases - Check how far along a job is, overall or for one target locale - Check how far along a single file within a job is - Find the workflow UIDs currently active on a job (e.g. before checking LQA/MQM statistics availability) # Examples - Full job progress: project_id, job_uid - One locale only: also target_locale_id="fr-FR" - One file only: also file_uri="strings.json" (cannot be combined with target_locale_id)

smartling_get_job_progress

Get the full category/severity/error-type breakdown for one LQA schema - the tool that resolves human-readable names to the UIDs smartling_record_lqa_error and smartling_update_lqa_error need. # Use cases - Resolve an error type name (e.g. "Mistranslation") to its errorTypeUid before recording a finding - Resolve a severity name (e.g. "Major") to its severityNameUid before recording a finding - Check whether a schema uses named severities or a numeric point range # Which severity field to use Check severityTypeCode first: - NAMED: match severityNames[].name to your desired severity, then pass its severityNameUid to smartling_record_lqa_error/smartling_update_lqa_error - POINT_RANGE: pass a numeric severity_score within severityRange.min-max instead - severityNames will be empty # Examples - Resolve UIDs for a schema: schema_uid from smartling_list_lqa_schemas

smartling_get_lqa_schema_topology

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

Get MQM (Multidimensional Quality Metrics) quality scores for one or more translation jobs, gated by whether statistics are actually available yet. # What is MQM? MQM statistics are computed from LQA findings recorded against a job's translations (see smartling_record_lqa_error), rolled up into per-job, per-schema, and per-locale quality scores. They're only meaningful once enough LQA review has happened - this tool checks availability per job before returning scores, so a job with no LQA review yet reports mqmStatisticsAvailable=false and a null statistics object instead of a misleading zero/perfect score. # Use cases - "Show quality information for Job NAME" -> read the job-level fields (qualityScore, criticalErrorCount, etc.) inside statistics - "Show quality scores for [language] for Job NAME" -> read statistics.schemas[].targetLocales[] for that locale - "Show strings with critical errors" -> use this tool to find jobs with statistics.criticalErrorCount > 0, then smartling_find_account_lqa_errors filtered by severity to enumerate the actual strings # Examples - Single job: jobs=[{project_id: "proj-1", job_uid: "job-1"}] - Multiple jobs, possibly across projects: jobs=[{project_id: "proj-1", job_uid: "job-1"}, {project_id: "proj-2", job_uid: "job-2"}] # Important Always check each result's mqmStatisticsAvailable before showing a quality score/answer - a false value means don't show a score for that job at all, not that quality is zero.

smartling_get_mqm_statistics

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

Get an existing translation job by name template, or create one if none matches - a simplified alternative to smartling_create_job for batch/file-upload workflows. # When to use this instead of smartling_create_job Use this tool when you just need a translationJobUid quickly to start uploading files (e.g. via smartling_create_job_batch), especially in automation/scripting scenarios. Use smartling_create_job instead when you need full control over job creation (custom fields, reference numbers, precise due dates, etc). # Dynamic job naming name_template supports date pattern placeholders using Java DateTimeFormatter syntax (e.g. "{yyyy}", "{QQQ}", "{yyyy-MM-dd}"), evaluated at request time using time_zone_name (or server time if omitted). # Job creation behavior (mode) - REUSE_EXISTING (default): Returns an existing job if one matches the evaluated name. If that job is closed, creates a new job with a unique name using the salt strategy. - CREATE_NEW: Creates a new job with the evaluated name; if one already exists, appends a unique identifier using the salt strategy. # Examples - Quarterly job: name_template="Q{QQQ} {yyyy} Localization", mode="REUSE_EXISTING" - Always-unique job: name_template="Feature Release {yyyy}", mode="CREATE_NEW", salt="TIMESTAMP"

smartling_get_or_create_translation_job

List the connectors (integrations, e.g. Intercom, Zendesk) available on a Smartling account. # What is a connector? A connector pulls content from a 3rd-party system into Smartling so it can be searched and translated without leaving Smartling. Call this tool first, before any other smartling_integration_* tool, to discover which connectors exist on the account and their normalized integration_id. # Use cases - User asks what integrations/connectors are set up for an account - Determining a valid integration_id before calling smartling_integration_get_search_context # Examples - List connectors for an account: provide account_id

smartling_integration_list_available

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 # Filtering by job Calling this tool without `job_uids` returns every content assignment across the entire account, which can be very large for accounts with many jobs and may fail to return. Whenever you already know (or can find) the translation job(s) you care about, look up their UIDs first with `smartling_list_jobs` or `smartling_search_strings`, then pass them via `job_uids` to scope the response down. # Examples - List content assignments for two specific jobs: { "job_uids": ["abc123def456", "ghi789jkl012"] } - List all content assignments for the current account (only when no job scope is known): {} (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 job batches for a Smartling project, optionally filtered by translation job or status. # Use cases - User wants to see all batches created for a specific translation job - User wants to find batches stuck in a particular status (e.g. still ADDING_FILES) - User needs the batch_uid for a recently created batch to check its status or act on it # Examples - List all batches for a project: Provide only project_id - Find batches for one job: Add translation_job_uid - Find in-progress batches: Add status=EXECUTING - Page through results: Use offset with limit, guided by totalCount in the response

smartling_list_job_batches

List the source files attached to a Smartling job. # Use cases - User wants to see which files are already part of a job before adding or removing more - User needs a file's fileUid or per-job locale coverage # Pagination - limit: Page size (default 1000 if omitted) - offset: Zero-based offset into the file list (default 0 if omitted) - totalCount in the response tells you how many files exist in total # Examples - List all files in a job: project_id, job_uid - Page through a job with many files: add offset/limit, guided by totalCount

smartling_list_job_files

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

Read back the LQA findings already recorded on one specific string. # Use cases - Check what's already recorded before editing or deleting a finding - Answer "what quality issues were found on this string?" # Examples - project_id, target_locale_id, hashcode

smartling_list_lqa_errors_per_string

List LQA schemas configured for a Smartling account. # What is an LQA schema? An LQA schema defines the categories, error types, and severity levels used when recording manual LQA findings on a string, and whether MQM (Multidimensional Quality Metrics) statistics are computed for translations scored against it. # Use cases - Find the schema_uid needed before recording a finding (see smartling_get_lqa_schema_topology and smartling_record_lqa_error) - Check which schemas are MQM-compatible # Examples - List all schemas: account_id only - Sorted by most recently modified: sort_by="MODIFIED_DATE", direction="DESC"

smartling_list_lqa_schemas

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