taskbounty-mcp-server

create_bounty_draft

Create an unfunded draft bounty to specify task details, title, amount, and deadline, then fund it separately via Stripe checkout.

Instructions

Create a new bounty as an unfunded DRAFT. Returns task_id and slug. Bounty is created as DRAFT/UNFUNDED. Call fund_bounty next to get a Stripe Checkout URL the user can open to fund. Requires TASKBOUNTY_API_KEY.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Bounty title (5-200 chars).
`short_summary`	Yes	One-line summary (10-500 chars).
`description`	Yes	Full bounty description (20-10000 chars).
`category`	Yes	Category, e.g. 'code', 'research', 'design'.
`bounty_amount`	Yes	Bounty amount in USD.
`submission_deadline`	Yes	ISO 8601 deadline. Must be at least 7 days from now.
`evaluation_criteria`	No	Optional evaluation criteria.
`expected_output_format`	No	Optional expected output format.
`github_repo_url`	No	Optional GitHub repo URL for code tasks.
`tags`	No	Optional comma-separated tags.
`platform`	No	Optional platform: 'general' or 'code'.
`language`	No	Optional language filter (e.g. 'typescript').

Tool Definition Quality

A3.9/5.0

Behavior3/5

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

No annotations, so description carries burden. It discloses draft/unfunded status and return values, but no error handling or side effects. Adequate but not rich.

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: purpose, next step, auth. Front-loaded and efficient with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Describes return values but no output schema. Missing error responses and behavior for edge cases. Moderately complete for a creation tool.

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 covers 100% of parameters with descriptions. Description adds no additional parameter info, so baseline 3 applies.

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?

Clearly states the tool creates an unfunded draft bounty and returns task_id and slug. Distinguishes from sibling tools like fund_bounty.

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?

Explicitly instructs to call fund_bounty next and notes API key requirement. Lacks explicit when-not-to-use scenarios but provides clear next steps.

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

Install Server

Other Tools

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eliottreich/taskbounty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server