Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.create_admin_portal_link_token

Create an admin portal link token in a connected Clerk instance.

Sensitive — the returned token is a single-use deep-link secret; do not log or expose it.

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

Cost = 15 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopesNoOptional scopes for the link (for example "admin_portal:read").
it_contact_idNoOptional opaque IT contact reference for the link.
organization_idNoOptional organization id (org_...) to scope the admin portal link.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
seconds_until_expirationNoLink token lifetime in seconds (default 3600, max 86400).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
admin_portal_link_tokenNoCreated admin portal link token from the Backend API.

Schema Changelog

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

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations, but description carries burden well: highlights that the token is a sensitive single-use secret and warns against logging. Also discloses cost and prerequisite, adding useful context for safe invocation.

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?

Four concise sentences, each with distinct value: purpose, security warning, usage prerequisite, cost. Front-loaded, no fluff.

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?

Given the high schema description coverage and presence of output schema, the description covers the key aspects: purpose, security, prerequisite, instance targeting, and cost. No major gaps for a token creation tool.

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 covers all 5 params at 100%, so baseline is 3. The description adds meaningful guidance for clerk_instance_id (how to obtain via get_connected_accounts, default account behavior) beyond the schema.

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?

Clearly states the tool creates an admin portal link token in a connected Clerk instance. Distinguishes from sibling token tools (actor, session, sign-in, m2m) by naming the specific resource.

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?

Provides explicit prerequisite: call clerk.get_connected_accounts first. Explains when to pass clerk_instance_id vs omit. No explicit alternatives, but the context is clear enough for this specialized token tool.

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