Skip to main content
Glama

Retrieve a template version

lob_template_versions_get
Read-onlyIdempotent

Retrieve a specific version of a template using its template ID and version ID.

Instructions

Retrieve a specific version of a template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_idYesTemplate ID (`tmpl_…`).
version_idYesTemplate version ID (`vrsn_…`).

Implementation Reference

  • Registration of the lob_template_versions_get tool. It reads the template_id and version_id from input, and makes a GET request to the Lob API endpoint /templates/{template_id}/versions/{version_id}.
    registerTool(server, {
      name: "lob_template_versions_get",
      annotations: { title: "Retrieve a template version", ...ToolAnnotationPresets.read },
      description: "Retrieve a specific version of a template.",
      inputSchema: { template_id: TEMPLATE_ID, version_id: VERSION_ID },
      handler: async ({ template_id, version_id }) =>
        lob.request({ method: "GET", path: `/templates/${template_id}/versions/${version_id}` }),
    });
  • Input schema for lob_template_versions_get requiring template_id and version_id (defined as constants elsewhere).
    inputSchema: { template_id: TEMPLATE_ID, version_id: VERSION_ID },
  • Handler that destructures template_id and version_id from args and makes a GET request to the Lob API to retrieve a specific template version.
    handler: async ({ template_id, version_id }) =>
      lob.request({ method: "GET", path: `/templates/${template_id}/versions/${version_id}` }),
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint; the description adds no additional behavioral context beyond restating the operation.

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?

One concise sentence with no redundant information.

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 read operation with full schema and annotations, the description is adequate. Could mention relation to sibling tools.

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?

Schema coverage is 100%, with patterns explained. The description adds no extra meaning to parameters.

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 explicitly states the action (Retrieve), resource (a specific version of a template), and clearly distinguishes from siblings like list versions.

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., list vs get) is provided.

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/optimize-overseas/lob-mcp'

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