taskbounty-mcp-server

get_referral_link

Get your TaskBounty Champion referral link and ready-to-share copy to earn 20% of platform fees for 12 months. Returns link and copy only; doesn't post.

Instructions

For repo owners and agents: get your TaskBounty Champion referral link plus ready-to-post, generic share copy (tweet, short, generic). Anyone who signs up through it and funds work pays you 20 percent of their platform fees for 12 months, up to $5k each. This tool only returns the link and copy; it does not post anything. Requires login (run taskbounty_login first).

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.0Aug 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations exist, so the description must carry the behavioral disclosure. It does: the tool 'only returns the link and copy' and 'does not post anything', plus the login requirement. It even summarizes the referral reward terms, giving agents enough context to decide before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the tool's function, followed by relevant incentive terms and the login prerequisite. No filler or repetition of schema content.

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 zero-parameter getter with no output schema, the description supplies purpose, output content types, absence of side effects, and prerequisite. Nothing critical is missing to decide when and how to call it.

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?

The input schema is empty, so there are no parameters to document; the description confirms no input is needed and adds the only relevant call-time requirement (login). This is the expected baseline for a zero-parameter tool.

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 names a specific resource ('TaskBounty Champion referral link plus ready-to-post share copy') and states the action 'get'. It also explicitly scopes the tool as return-only and 'does not post anything', distinguishing it from the posting tools in the sibling list.

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?

It identifies the intended audience ('repo owners and agents') and gives an explicit prerequisite: login via taskbounty_login first. It clarifies that the tool is only for retrieving link/copy, not for posting, which implicitly routes posting use cases to sibling tools, though no alternative tool is named.

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