Skip to main content
Glama

unulu

by ai.unulu

Create a link-in-bio site

unulu_create_site

Create a link-in-bio site with a name, bio, and links. Returns a live URL on unu.lu that expires in 1 hour unless claimed. Do NOT call until you have at least a name and one link from the user — gather real content first, never create with placeholder or empty content. If the user provides a handle (e.g. '_guy.a' for Instagram), construct the full URL yourself — do not ask them to paste it. When feasible, offer to find all public links for the person. Before calling: tell the user they can choose a skin on the preview page for the overall aesthetic; ask permission before adding emoji leading_icons to decorate links (for not-well-known social URLs). The response includes an assistant_message with the site URL and claim details — present these to the user. Persist claim_token and claim_code_short for subsequent updates — never ask the user for them back in the same conversation. Never create a duplicate site; always update the existing one. After creation: tell the user they can pick a custom handle when they claim; share the preview URL in a copy-paste block; offer to refine bio, links, or ordering. Keep iteration fast — apply changes immediately, don't re-confirm minor edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioNoShort bio in first person, 1–3 sentences, capturing what's distinctive — no filler phrases like 'passionate about' or 'dedicated to'. If you lack context, write something short and honest rather than generic. Supports markdown.
nameYesDisplay name / heading for the site
linksNoLink-in-bio links. Order matters — place the most important link first. Well-known social links display branded icons automatically — omit leading_icon for these.
skin_idNoOptional theme skin. When omitted, the live site includes a visual theme chooser — prefer omitting so the user can pick their own.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesLive URL on unu.lu — always present as a clickable markdown link when showing to the user
site_idYesUnique site identifier
expires_atYesISO 8601 expiry timestamp (~1 hour from creation)
claim_tokenNoHMAC token for updating ephemeral (pre-claim) sites via updateSite. Present when the site is unclaimed.
claim_code_shortNoBackup code (XXXX-XXXX) for claiming the site via the short-code flow
assistant_messageYesPre-formatted message with the live site link, expiry notice, and short-code claim instructions. Share with the user as-is — do not paraphrase or restructure.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations, discloses expiration behavior (expires in 1 hour unless claimed), response contents (assistant_message with URL and claim details), token persistence requirements (persist claim_token and claim_code_short), and duplicate handling (always update existing). No contradiction with annotations; openWorldHint aligns with the live URL behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Long but packed with actionable guidance; front-loads the core action ('Create a link-in-bio site...') and then provides ordered pre- and post-steps. Slightly verbose, but every instruction serves a purpose and is structured logically.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive coverage of preconditions, creation flow, follow-up actions, and state persistence. With an output schema present and detailed annotations, this description fully equips the agent to execute correctly without requiring external knowledge.

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 already describes all parameters (100% coverage), but description adds important usage semantics: how to construct URLs from handles, when to omit leading_icon for well-known social links, and permission requirement for emoji icons. This goes beyond the schema's technical descriptions.

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 'Create a link-in-bio site with a name, bio, and links' and specifies the unique output (live URL on unu.lu expiring in 1 hour). Distinguishes from siblings by noting duplicate-avoidance via updating existing sites.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit preconditions ('Do NOT call until you have at least a name and one link'), alternatives (construct full URL yourself vs asking user), and workflow (offer to find links, ask permission for icons). Also states 'Never create a duplicate site; always update the existing one', implying when to use the update path instead.

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

All unulu 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.6/5.0
Disambiguation5/5

Each tool has a distinct purpose with no overlap: check_handle verifies availability, create_site builds a new site, get_state retrieves current site data, and update_site modifies an existing site. The descriptions clearly differentiate their functions, preventing agent misselection.

Naming Consistency5/5

All tools follow a consistent 'unulu_verb_noun' pattern (e.g., unulu_check_handle, unulu_create_site). This uniformity makes the tool set predictable and easy for agents to understand and navigate.

Tool Count5/5

With 4 tools, this server is well-scoped for handling link-in-bio sites on unu.lu. It covers the essential lifecycle: checking availability, creating, reading, and updating sites, which is appropriate for its focused domain without being overly sparse or bloated.

Completeness4/5

The tool set provides strong coverage for the core site lifecycle (check, create, read, update), but lacks a delete tool for removing sites. This minor gap can be worked around by agents, as the domain is otherwise well-covered with no dead ends in typical workflows.

Resources