Skip to main content
Glama
Sign In

Convika

by com.convika
OverviewDiscussionsAdmin

Create claim link

create_claim_code

Create a claim link for a landing page you built, so someone else can take ownership of it — no card required.

This powers the "I built you a page" outreach: you build and publish a landing page on your own account, then mint a claim link bound to that page. You share the link; when the recipient signs up through it, that exact page — same URL, same content they already saw — moves into their account immediately. Claiming is free: the recipient gets the Free plan with no card (the page shows a small Convika bar at the bottom; analytics and starter AI-edit credits included). The response's recipientGets field states the exact terms; quote it when you tell the recipient what they get.

  • The page must already exist on your account. Build it with create_landing_page_preview, then publish_site to production so the recipient can see it live before they sign up.

  • The link is single-use and expires in 14 days by default — tell the recipient the deadline. An unclaimed showcase page is automatically unpublished about 30 days after the code was minted.

  • Ownership transfers without changing the URL, so the page you showed them in your message becomes theirs at the same URL.

  • Returns the signup URL to send, plus the code and its limits.

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe ID of the landing page to bind to the claim link. Must be a page on your account.
maxClaimsNoHow many times the link can be claimed. Defaults to 1 (single-use).
expiresInDaysNoDays until the link expires. Defaults to 14 (the claim window communicated to the recipient).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / siteId / description
      Previous value: -"The ID of the landing page to bind to the claim link. Must be a site on your account."New value: +"The ID of the landing page to bind to the claim link. Must be a page on your account."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavior: single-use by default, 14-day default expiry, auto-unpublish of unclaimed pages around 30 days, URL-preserving ownership transfer, free recipient plan, and a recipientGets field to quote. These are exactly the operational details an agent needs before invoking the tool.

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 front-loaded with the core action and uses bullets for operational constraints, making it skimmable. It is somewhat long and repeats the “no card” benefit, but most sentences carry relevant workflow or behavioral information.

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?

For a mutation tool with no output schema, the description is highly complete: it covers prerequisites, ownership-transfer behavior, expiry, single-use limits, recipient terms, and what the response contains. An agent has enough information to call it correctly and explain the outcome to a user.

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 siteId, maxClaims, and expiresInDays are already well documented structurally. The description adds useful context about defaults and single-use behavior, but it does not add parameter-level syntax or constraints 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 states a specific verb and resource: create a claim link bound to a landing page so ownership can transfer. It clearly distinguishes this from building or publishing the page by naming the outreach workflow and the exact outcome, so an agent can identify the tool 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?

The description gives clear usage context: it is for the “I built you a page” outreach and requires the page to already exist and be published. It names prerequisite siblings (create_landing_page_preview, publish_site) but does not explicitly state when not to use this tool versus alternatives such as referral links.

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

All Convika toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources