Skip to main content
Glama

create_access_link

Generate a workspace access link with customizable role, expiration, and space restrictions. Supports anonymous reusable links and personalized access.

Instructions

Create a Huly workspace access link. When role is omitted, role=GUEST. Supports anonymous reusable guest links by setting personalized=false with notBefore and expiration, and can restrict access to specific Huly space IDs via spaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoWorkspace role granted by the link. Defaults to GUEST.
firstNameNoa string that will be trimmed
lastNameNoa string that will be trimmed
navigateUrlNoOptional URL/path Huly should open after the link is used.
spacesNoOptional Huly space IDs this link should grant access to. Use list_teamspaces, list_card_spaces, or other list tools to discover space IDs.
notBeforeNoUnix timestamp in seconds before which the link is invalid.
expirationNoUnix timestamp in seconds after which the link expires.
personalizedNoWhether the link is bound to one person. Omit to use Huly's personalized-link behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

The description adds meaningful behavioral details beyond annotations, such as default role, anonymous link support, and space restrictions. It does not contradict annotations. While annotations already indicate non-destructive mutation, the description enriches understanding of idempotent and open-world aspects.

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 highly concise with two sentences, front-loading the core purpose. Every sentence adds essential information, and there is no redundancy with schema or annotations.

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 tool's complexity (8 optional parameters, output schema exists), the description covers key behaviors and constraints. It could mention authentication requirements or limits, but overall suffices for typical usage scenarios.

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 high (100%), but the description adds value by explaining composite behavior like anonymous links (using personalized, notBefore, expiration) and default role. This extends beyond per-parameter schema descriptions, providing extra context for decision-making.

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 verb 'Create' and resource 'Huly workspace access link', making the tool's purpose clear. It distinguishes from siblings by focusing specifically on access links, which is unique among many create tools like create_workspace or create_invite.

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 clear context for when to use the tool, including default behavior for omitted role and special features like anonymous reusable links. However, it lacks explicit comparisons to alternative tools (e.g., create_workspace) or when-not-to-use guidance.

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/dearlordylord/huly-mcp'

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