Skip to main content
Glama

Earning Paths Atlas

Get platform details

get_platform

Use when you already picked a platform and need all sourced facts: rules, human steps, KYC, fees, payout minimum and methods, VAT/merchant of record, known ban reasons, sources, check date. Free. No legal or tax advice.

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": {
      "id": "<id>"
    },
    "name": "get_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlatform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner, hackerone, immunefi, algora, kaggle, numerai, rapidapi, aws-marketplace, cloudflare-pay-per-crawl, skyfire, nevermined, l402, amazon-kdp, freelancer-com, amazon-mechanical-turk, paddle, github-marketplace, shopify-app-store, itch-io, steam, tablejourney, mercor, cantina, opire

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Platform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner, hackerone, immunefi, algora, kaggle, numerai, rapidapi, aws-marketplace, cloudflare-pay-per-crawl, skyfire, nevermined, l402, amazon-kdp, freelancer-com, amazon-mechanical-turk, paddle, github-marketplace, shopify-app-store, itch-io, steam, tablejourney"New value: +"Platform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner, hackerone, immunefi, algora, kaggle, numerai, rapidapi, aws-marketplace, cloudflare-pay-per-crawl, skyfire, nevermined, l402, amazon-kdp, freelancer-com, amazon-mechanical-turk, paddle, github-marketplace, shopify-app-store, itch-io, steam, tablejourney, mercor, cantina, opire"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Platform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner, hackerone, immunefi, algora, kaggle, numerai, rapidapi, aws-marketplace, cloudflare-pay-per-crawl, skyfire, nevermined, l402, amazon-kdp, freelancer-com, amazon-mechanical-turk, paddle, github-marketplace, shopify-app-store, itch-io, steam"New value: +"Platform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner, hackerone, immunefi, algora, kaggle, numerai, rapidapi, aws-marketplace, cloudflare-pay-per-crawl, skyfire, nevermined, l402, amazon-kdp, freelancer-com, amazon-mechanical-turk, paddle, github-marketplace, shopify-app-store, itch-io, steam, tablejourney"
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Platform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner"New value: +"Platform id, one of: adobe-stock, etsy, spreadshirt, redbubble, gumroad, polar, lemon-squeezy, apify, fiverr, upwork, amazon-partnernet-de, youtube, superteam-earn, shutterstock, pond5, ko-fi, patreon, stripe-mpp, x402, hugging-face, github-sponsors, product-hunt, smithery, glama, medium-partner, hackerone, immunefi, algora, kaggle, numerai, rapidapi, aws-marketplace, cloudflare-pay-per-crawl, skyfire, nevermined, l402, amazon-kdp, freelancer-com, amazon-mechanical-turk, paddle, github-marketplace, shopify-app-store, itch-io, steam"
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it marks the tool as free, implies a read-only lookup, discloses that results carry sources and a check date (freshness/provenance), and adds an explicit 'no legal or tax advice' disclaimer. It does not state behavior for an unknown id or any rate/limit constraints, so it stops short of full disclosure.

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?

A single front-loaded 'Use when...' clause followed by a compact enumeration of returned facts; nothing is redundant. The dense field list reads as a run-on, but each item conveys real scope information.

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, so the enumeration of returned facts, provenance fields, and the legal-advice disclaimer is exactly the right compensation. Only the failure behavior for an invalid or unsupported id is left unstated, a minor gap given the schema's explicit enum.

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 coverage is 100% and the id field already documents the exact allowed slug set, so the description need not restate formats. It adds only the implicit constraint that the id is for a platform the caller already selected, which is baseline rather than additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear 'get a platform's full sourced fact record' framing and enumerates the contents (rules, KYC, fees, payout minimum, VAT/MoR, ban reasons, sources, check date). 'Use when you already picked a platform' implicitly separates it from discovery-oriented siblings like list_platforms and recommend, though no sibling is named.

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 opening clause gives a genuine selection condition: call this after a platform has already been chosen and the full fact set is needed. That effectively rules out discovery use, but no alternative is named and no when-not guidance (e.g., what to use for comparisons or earning plans) is stated.

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