Skip to main content
Glama
FlywheelStudio

ULink MCP Server

Create Link

create_link

Create a smart link in a ULink project for unified platform routing or dynamic deep links. Supports idempotent creation with externalId to avoid duplicates.

Instructions

Create a new smart link in a ULink project. Supports unified links (single URL that routes by platform) and dynamic links (parameterised deep links). You must specify the project, domain, and link type. Optionally set platform-specific URLs, fallback URLs, custom slug, metadata, and parameters. Pass externalId (any stable string from your system) to make creation idempotent on (project, externalId).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoHuman-readable name for the link
slugNoCustom slug for the short URL (auto-generated if omitted)
typeYesLink type: 'unified' for smart routing or 'dynamic' for parameterised deep links
iosUrlNoURL to open on iOS devices
domainIdYesThe domain to host the link on
metadataNoArbitrary metadata attached to the link
projectIdYesThe project to create the link in
androidUrlNoURL to open on Android devices
externalIdNoOptional stable identifier from your system (e.g. 'share:user-123:post-456'). Repeated calls with the same (project, externalId) return the existing link instead of creating a duplicate. Idempotent.
parametersNoKey-value parameters passed through the deep link
fallbackUrlNoFallback URL for unsupported platforms
iosFallbackUrlNoiOS-specific fallback URL (e.g. App Store link)
androidFallbackUrlNoAndroid-specific fallback URL (e.g. Play Store link)
allowQueryPassthroughNoWhen true, query params appended to this link URL at click time (e.g. ?orderId=123) are merged into the resolved link's parameters and OVERRIDE stored parameters with the same key. Parameter values arrive as strings. Applies on both immediate app open and after deferred install. No SDK change required. Default: false.
Behavior4/5

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

With no annotations, the description discloses key behaviors: idempotency via externalId, support for two link types, and required fields. It doesn't mention return values, error handling, or permissions, but the idempotency note is a valuable behavioral detail beyond the schema.

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?

The description is moderately concise with five sentences, each serving a purpose: purpose, types, requirements, optionals, idempotency. It is front-loaded with 'Create...' and avoids unnecessary fluff.

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

Completeness3/5

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

Given 14 parameters, nested objects, and no output schema, the description covers the creation requirements and idempotency but does not explain what the response contains, error scenarios, or authentication. This leaves gaps for an agent invoking the tool successfully.

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?

Schema description coverage is 100%, so the description adds minimal parameter meaning. It summarizes optional groups (platform URLs, fallback URLs, slug, metadata, parameters) but does not elaborate on individual parameters beyond what the schema already provides.

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 clearly states 'Create a new smart link in a ULink project' with a specific verb and resource, and further distinguishes the two link types. It differentiates from sibling tools like update_link, delete_link, and list_links by focusing on creation.

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 required fields (project, domain, link type) and notes optional settings, giving clear context for when to invoke. However, it doesn't explicitly mention when not to use this tool, such as when updating an existing link, so it lacks explicit exclusions/alternatives.

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/FlywheelStudio/ulink-mcp-server'

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