Skip to main content
Glama

lokalise_list_glossary_terms

Retrieve paginated glossary terms for a project to discover defined terminology, including brand names and forbidden words, ensuring translation consistency and preventing errors.

Instructions

Retrieves paginated glossary terms that define translation rules for consistency. Required: projectId. Optional: limit (100), cursor for pagination. Use to discover defined terminology including brand names, technical terms, and forbidden words. Returns: Terms with properties (case-sensitive, translatable, forbidden) and translations. Essential before translating to prevent terminology errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID to list glossary terms for
limitNoNumber of glossary terms to return (1-5000, default: 100)
cursorNoCursor for pagination. Use nextCursor from previous response

Implementation Reference

  • The MCP tool handler function for 'lokalise_list_glossary_terms'. Calls glossaryController.listGlossaryTerms() and formats the response.
    async function handleListGlossaryTerms(args: ListGlossaryToolArgsType) {
    	const methodLogger = Logger.forContext(
    		"glossary.tool.ts",
    		"handleListGlossaryTerms",
    	);
    	methodLogger.debug(
    		`Getting Lokalise glossary terms list (limit: ${args.limit || "default"}, cursor: ${args.cursor || "none"})...`,
    		args,
    	);
    
    	try {
    		const result = await glossaryController.listGlossaryTerms(args);
    		methodLogger.debug("Got the response from the controller", result);
    
    		return {
    			content: [
    				{
    					type: "text" as const,
    					text: result.content,
    				},
    			],
    		};
    	} catch (error) {
    		methodLogger.error("Tool failed", {
    			error: (error as Error).message,
    			args,
    		});
    		return formatErrorForMcpTool(error);
    	}
    }
  • Zod schema defining input args for list glossary terms tool: projectId (string), limit (optional number 1-5000), cursor (optional string for pagination).
    export const ListGlossaryToolArgs = z
    	.object({
    		projectId: z.string().describe("Project ID to list glossary terms for"),
    		limit: z
    			.number()
    			.int()
    			.min(1)
    			.max(5000)
    			.optional()
    			.describe("Number of glossary terms to return (1-5000, default: 100)"),
    		cursor: z
    			.string()
    			.optional()
    			.describe("Cursor for pagination. Use nextCursor from previous response"),
    	})
    	.strict();
    
    export type ListGlossaryToolArgsType = z.infer<typeof ListGlossaryToolArgs>;
  • Registration of the tool named 'lokalise_list_glossary_terms' on the MCP server with description, schema (ListGlossaryToolArgs.shape), and handler (handleListGlossaryTerms).
    server.tool(
    	"lokalise_list_glossary_terms",
    	"Retrieves paginated glossary terms that define translation rules for consistency. Required: projectId. Optional: limit (100), cursor for pagination. Use to discover defined terminology including brand names, technical terms, and forbidden words. Returns: Terms with properties (case-sensitive, translatable, forbidden) and translations. Essential before translating to prevent terminology errors.",
    	ListGlossaryToolArgs.shape,
    	handleListGlossaryTerms,
    );
Behavior3/5

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

With no annotations, the description must disclose all behavioral traits. It mentions paginated retrieval and parameters, but does not state read-only nature, permission requirements, or rate limits. It is adequate but lacks depth.

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?

Three sentences, each purposeful: purpose and parameters, use case, return content and importance. No wasted words, well front-loaded.

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

Completeness4/5

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

For a simple list tool with no output schema, the description covers purpose, parameters, return content (properties and translations), and usage recommendation. It could detail the response structure more, but it is fairly complete.

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

Parameters4/5

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

Schema description coverage is 100%, and the description adds value by noting the default for limit and explaining cursor comes from nextCursor in the previous response, enhancing understanding beyond the schema alone.

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 tool retrieves paginated glossary terms for translation consistency, distinguishing it from sibling tools like create, delete, update glossary terms, and other list endpoints.

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

Usage Guidelines4/5

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

The description explicitly recommends using before translating to prevent errors and implies a discovery use case, but does not provide explicit when-not-to-use scenarios or alternative tools.

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/AbdallahAHO/lokalise-mcp'

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