Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.create_jwt_template

Create a new JWT template in a connected Clerk application.

Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account.

Returns the new template summary.

Cost = 10 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique JWT template name.
claimsYesJWT claims template as a JSON object.
lifetimeNoToken lifetime in seconds (30–315360000).
signing_keyNoCustom signing private key (required when custom_signing_key is true).
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
signing_algorithmNoCustom signing algorithm (required when custom_signing_key is true).
allowed_clock_skewNoAllowed clock skew in seconds (0–300).
custom_signing_keyNoWhether to use a custom signing key and algorithm.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jwt_templateNoNewly created Clerk JWT template summary.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It states the return behavior ('Returns the new template summary') and the 10-token cost, but it does not discuss permissions, error conditions, or side effects beyond creating a template.

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 three brief paragraphs, each serving a clear purpose: purpose, prerequisite/connection guidance, and return/cost. No wasted words.

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?

With a rich input schema and an output schema, the description provides the essential prerequisite and connection targeting logic. It is complete for a create tool, though it could mention potential error cases or duplicate-name behavior.

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 coverage is 100%, so baseline is 3. The description adds meaningful semantics for clerk_instance_id ('Pass clerk_instance_id to target a specific connection, or omit it to use the default account'), which goes beyond the schema's description.

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 opens with a specific verb+resource: 'Create a new JWT template in a connected Clerk application.' This clearly states the tool's function and distinguishes it from sibling tools like update_jwt_template or delete_jwt_template.

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?

It explicitly instructs to call clerk.get_connected_accounts first and explains how to target a connection (via clerk_instance_id or default). This gives clear usage context, though it does not explicitly compare to alternatives like other token-creation tools.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources