Skip to main content
Glama

Referral link for a destination or plan

get_referral_link
Read-onlyIdempotent

Build your tracked link (requires an active affiliate key): pass plan_id for a plan page with the plan preselected, destination (country, city, region or ISO-2) for a destination page, or nothing for your partner landing page. Share only where advertising is allowed and mark it as an ad; the price returned is current and may change.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_referral_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for names and texts (default en).
plan_idNoExact plan ID from search_plans.
destinationNoCountry, city, region, ISO-2 code or destination slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: an authorization requirement (active affiliate key), and the fact that the returned price is a live value that may change — a dynamic-output trait not expressible in the annotations. It does not mention link expiry or regeneration, which keeps it at 4.

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?

Effectively one long sentence with the purpose front-loaded, followed by the mode routing and then the compliance caveat. Every clause carries information, though the compliance and price-volatility remarks feel appended rather than integrated, slightly taxing scanability.

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?

There is no output schema, and the description partially compensates by noting the price returned is current and may change, but it does not describe the link format or any expiry. For a three-parameter, all-optional read tool with full schema coverage, this is close to sufficient.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: plan_id yields a page with that plan preselected, destination accepts country/city/region/ISO-2, and omitting both yields the partner landing page. The enum on lang is left to the schema, which is fine.

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+resource ("Build your tracked link") and then enumerates the three distinct output modes keyed to each parameter: plan page, destination page, or partner landing page. An agent can predict the result of the call from the description alone, without opening the 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?

Gives clear conditional routing (pass plan_id for a plan page, destination for a destination page, nothing for the landing page) plus a hard prerequisite (active affiliate key) and a compliance condition (share only where advertising is allowed, mark as an ad). It does not name a sibling alternative, e.g. get_affiliate for checking key status, so it stops short of full when/when-not guidance.

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.

Resources