Skip to main content
Glama

list_languages

Retrieve all languages configured in a POEditor translation project to manage multilingual content effectively.

Instructions

List languages in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNo

Implementation Reference

  • Handler function that calls the poeditor API to list languages for the specified project.
    async (args) => {
      const id = requireProjectId(args.project_id ?? null);
      const res = await poeditor("languages/list", { id: String(id) });
      return { content: [{ type: "text", text: JSON.stringify(res.result ?? {}, null, 2) }] };
    }
  • Zod schema defining the optional project_id input for the list_languages tool.
    const ListLanguagesInput = z.object({
      project_id: z.number().int().positive().optional()
    });
  • src/server.ts:286-295 (registration)
    Registration of the list_languages tool using McpServer.tool method, including name, description, input schema, and inline handler.
    server.tool(
      "list_languages",
      "List languages in the project.",
      ListLanguagesInput.shape,
      async (args) => {
        const id = requireProjectId(args.project_id ?? null);
        const res = await poeditor("languages/list", { id: String(id) });
        return { content: [{ type: "text", text: JSON.stringify(res.result ?? {}, null, 2) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('List') but doesn't describe the return format (e.g., list structure, pagination), potential errors (e.g., invalid project_id), or any side effects. This leaves significant gaps for an agent to understand how to use it effectively.

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

Conciseness5/5

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

The description is a single, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't cover return values, error conditions, or behavioral nuances. For a tool with one parameter and no structured support, more detail is needed to guide an agent adequately.

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

Parameters3/5

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

The schema description coverage is 0%, so the description must compensate. It mentions 'project' which relates to the 'project_id' parameter, adding some context. However, it doesn't explain the parameter's role (e.g., required vs. optional, what happens if omitted) or provide examples, resulting in only marginal value beyond the bare schema.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('languages in the project'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'list_available_languages', which appears to serve a similar purpose, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_available_languages' or 'list_terms'. It lacks context about prerequisites, such as whether a project must exist or be accessible, and offers no exclusions or recommended scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ryan-shaw/poeditor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server