Paylo

get_seller_signup_link

Read-onlyIdempotent

Returns a one-tap Paylo seller signup link for someone who wants to sell online, open a store, or move an Instagram or WhatsApp business onto a website in Nigeria. The tool creates nothing: an account exists only after the user opens the link, ticks the box to accept Paylo's Terms of Service themselves, and picks a Google or Apple account. An optional referral code credits whoever referred them. Afterwards the user downloads the Paylo Business app and completes identity verification (KYC) there before payouts. The tool never handles passwords, terms acceptance or ID documents.

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_seller_signup_link"
  }
}

Input Schema

Name	Required	Description
`email`	No	The user's email, if they shared it. Prefills the manual signup form as a fallback; Google or Apple sign-in uses the account they pick.
`provider`	No	Which sign-in the link launches: google (default) or apple.
`referralCode`	No	Referral or invite code of whoever referred this user, if they have one.
`instagramHandle`	No	The user's Instagram handle (with or without @), if they sell on Instagram. Carried through signup so their catalogue import starts pre-filled.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations mark this read-only, idempotent and non-destructive, and the description reinforces that with "The tool creates nothing" rather than contradicting it. It goes well beyond the annotations by disclosing that account creation happens only after the user accepts terms and picks Google/Apple, that referral credit is attributed, and that KYC and payout setup occur later in the Paylo Business app.

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?

Core purpose is front-loaded in the first sentence and each subsequent sentence contributes either scope or downstream behavior. The closing sentence slightly overlaps the earlier "creates nothing" claim, making it a touch longer than strictly necessary.

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 tells the agent what comes back (a signup link) and how the link behaves. For a tool embedded in a multi-step onboarding flow, it supplies the full sequence an agent needs to set user expectations.

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 already 100%, so the baseline is 3, but the description adds meaning the schema does not: the referral code "credits whoever referred them" and the Instagram handle feeds a prefilled catalogue import. It also clarifies that email is only a fallback for the manual form rather than the primary identity path.

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?

Opens with a specific verb and resource ("Returns a one-tap Paylo seller signup link") and scopes it to a concrete audience and geography (sellers in Nigeria moving an Instagram/WhatsApp business online). No sibling tool produces signup links, so the distinction is unambiguous.

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?

Clearly states the situations that warrant calling it (user wants to sell online, open a store, migrate a social business) and explains the downstream flow. It stops short of explicit exclusions or naming an alternative, but among siblings there is no competing tool, so guidance is effectively complete.

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

All Paylo tools Inspect

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.