Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.create_session

Create a new session for a Clerk user 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 created session object with id, user_id, status, last_active_at, expire_at, client_id, created_at, and updated_at.

Cost = 10 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesClerk user id (user_...) to create a session for.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoClerk session id (sess_...).
statusNoCurrent status of the session.
user_idNoClerk user id (user_...) that owns this session.
client_idNoClerk client id associated with this session.
expire_atNoUnix timestamp in milliseconds when this session expires.
created_atNoUnix timestamp in milliseconds when the session was created.
updated_atNoUnix timestamp in milliseconds when the session was last updated.
last_active_atNoUnix timestamp in milliseconds of the last activity on this session.

Schema Changelog

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

  1. Added

TDQS

A4/5.0
Behavior3/5

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

No annotations are present, so the description must carry the transparency burden. It does disclose the cost (10 tokens) and the return fields, but it does not mention permissions, side effects, or failure modes. This is a partial disclosure that leaves important behavioral aspects undocumented.

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 four sentences with no filler. The purpose is front-loaded, followed by a prerequisite, parameter guidance, return fields, and cost. Each sentence earns its place and the structure is clean and scannable.

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 low-complexity create tool with full schema and an output schema, the description provides the essential usage context (prerequisite, parameter behavior, return payload). It lacks error-handling notes or side-effect warnings, but it is reasonably complete given the tool's simplicity and the existence of an output schema.

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 input schema already covers both parameters with meaningful descriptions (user_id format, clerk_instance_id default behavior). The description adds a note to call get_connected_accounts first, but this is more of a usage guideline than additional parameter semantics. With 100% schema coverage, the baseline is 3, and the description does not significantly exceed that.

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 'Create a new session for a Clerk user in a connected Clerk application,' which clearly states the verb, resource, and scope. It distinguishes itself from sibling tools like clerk.create_session_token by focusing on the session object rather than a token.

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 provides an explicit prerequisite ('Call clerk.get_connected_accounts first') and explains when to pass clerk_instance_id versus omit it for the default account. It does not explicitly state when not to use this tool, but the context is clear enough for selection among similar create 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