Skip to main content
Glama

Create link domain

create_link_domain
Destructive

Add a subdomain of the user's own (links.example.com) for short links. Returns two DNS records (CNAME and TXT) the user adds at their DNS host; then verify the domain. Optional: without one, tracked links use our domain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "create_link_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA subdomain you own, like links.example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / description
      Added value: +"A subdomain you own, like links.example.com"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the call returns two DNS records (CNAME and TXT) that the user must add at their DNS host, and the domain is not usable until verified. It does not address why annotations mark this create operation as destructiveHint=true (e.g., whether re-creating an existing domain overwrites settings) or any ownership/permission requirements, leaving that gap unexplained.

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?

Three short sentences ordered as purpose, then mechanics/next step, then the opt-out case — the most decision-relevant information comes first. No filler or restatement of the title.

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 single-parameter tool with no output schema, the description covers what is created, what comes back (CNAME/TXT records), the manual DNS step, the verification follow-up, and the default behavior when omitted. Only edge cases — duplicate domain, permission requirements, failure modes — are unaddressed.

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?

Only one parameter exists and schema coverage is 100%; the schema already documents 'domain' with the same links.example.com example. The description adds no format constraints (e.g., must be a subdomain of a verified root, no scheme/path), so it does not go 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?

States a specific verb and resource ('Add a subdomain of the user's own ... for short links') with the concrete example links.example.com, which immediately separates it from list/get/delete_link_domain. It also names the follow-on verification step, so the agent can distinguish creation from verification without opening either schema.

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 line 'Optional: without one, tracked links use our domain' gives an explicit condition for skipping this tool entirely, and 'then verify the domain' signals the required next step. It stops short of naming the sibling tools (verify_link_domain, list_link_domains) or stating prerequisites, so routing is clear but not fully explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.