Skip to main content
Glama

Create personalized links

create_personalized_links

Makes personalized links for a demo, one per prospect: each link's values fill the demo's variables for whoever opens it ({{company}}, {{first_name}}… in step copy; built-ins first_name, last_name, full_name, company, title, email, domain, plus the custom ones in content.variables). Each link can name its rep ({{rep.first_name}}, {{rep.calendar}}…) and an intro video. Up to 500 at once, e.g. from a CRM list. The URL carries only an opaque code (?p=…); the values are stored with the link as workspace data, like leads. Values for variables the demo doesn't have are dropped. Pro and Team plans. Returns each link's hosted URL and embed URL.

Requires: demos:read, demos:write.

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": {
      "demoId": "<demoId>",
      "links": "<links>"
    },
    "name": "create_personalized_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYes
demoIdYesDemo id (from list_demos), e.g. "d_Ab12Cd34Ef56Gh78".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / links / items / properties / introVideo
      Added value: +{
      +  "description": "An intro video before the demo: a YouTube, Loom, Vimeo or Wistia link, or a shared AtriumKit video; \"none\" for none (default: the demo’s own, if any).",
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedInput schema / properties / links / items / properties / repEmail
      Added value: +{
      +  "description": "The rep for {{rep.name}}, {{rep.calendar}}…: a member of the workspace, by email (default: you).",
      +  "maxLength": 254,
      +  "type": "string"
      +}
    • changedInput schema / properties / links / items / properties / values / description
      Previous value: -"Variable key → value, e.g. { \"first_name\": \"Sam\", \"company\": \"Acme\" }."New value: +"Variable key → value, e.g. { \"first_name\": \"Sam\", \"company\": \"Acme\", \"domain\": \"acme.com\" } (domain: their logo on logo spots and cards)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond readOnlyHint=false and destructiveHint=false, it discloses the storage model (values stored as workspace data like leads, URL only carries an opaque ?p= code), silent data loss for unknown variables, the 500-item batch ceiling, authorization scopes, and the return shape (hosted URL and embed URL). The one gap is idempotency-style behavior on retries, which is only implied by the idempotentHint=false annotation rather than stated outright.

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?

Information is front-loaded on the first line and every sentence adds something distinct; the parenthetical variable examples do real work. It is dense and long for a two-parameter tool, with the trailing 'Requires:' line slightly detached from the rest of the flow.

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?

With no output schema, the description still states the return values (hosted URL and embed URL), and it covers limits, permission prerequisites, plan restrictions, and the consequence of unknown variables. Nothing essential for a correct call is missing.

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 sits at 50%, and the description compensates well for the largest parameter: it enumerates the built-in variable keys (first_name, last_name, full_name, company, title, email, domain) plus custom content.variables, and explains rep interpolation via {{rep.first_name}}/{{rep.calendar}} and the intro video option. It does not explain the `label` field's defaulting behavior, which the schema itself documents.

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?

"Makes personalized links for a demo, one per prospect" gives a specific verb and resource and immediately encodes the one-per-prospect scale, which separates it from list_personalized_links. The follow-on sentences about variable interpolation and rep/video options further pin down what the tool produces, so an agent knows exactly what it is calling without reading 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?

The description supplies real usage context: bulk generation (up to 500), sourced e.g. from a CRM list, scoped to a demo's variables, and gated on Pro/Team plans plus demos:read and demos:write. It does not name an alternative or state when NOT to use this rather than the sibling listing tool, so it stops short of full routing 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.