tolgee-mcp

by ytarfa

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_language

Removes a language and all its translations from a Tolgee project. Provide the project and language IDs to execute.

Instructions

Delete a language from a Tolgee project. This removes all translations for this language.

Args:
    project_id: The numeric ID of the project.
    language_id: The numeric ID of the language to delete.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "language_id": "<language_id>"
    },
    "name": "delete_language"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`language_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description notes that deletion removes all translations, which is a key behavioral trait. However, with no annotations, it should disclose more (e.g., reversibility, permissions, side effects).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences plus an inline args list. The args list is somewhat redundant given the schema, but the overall structure is clean and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and a destructive operation, the description lacks essential context like whether the deletion is permanent, cascading effects, or required permissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description bears the burden. It only restates the parameter names and types ('numeric ID'), which adds minimal value beyond the schema's integer type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Delete a language' and the resource 'from a Tolgee project', with the consequence 'removes all translations'. It distinguishes from siblings like create_language and update_language.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., disabling a language). No prerequisites or conditions mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.