Skip to main content
Glama
kuyen-labs

Fuul MCP Server

by kuyen-labs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

create_incentive

Create a draft incentive for affiliate conversions by providing name, trigger IDs, and payout terms. Use a dry run for validation before confirming.

Instructions

Creates a draft incentive (conversion): POST /api/v1/projects/:projectId/incentives. Body: name, trigger_ids[] (draft or published trigger UUIDs — resolved to current draft), payout_terms[] (PayoutTermDto, min 1 each). REQUIRED: list_payout_schemas first — pick reward_types[].id (fixed-reward | variable-reward | proportional-pool | leaderboard) and use create_payload_example. Schemes on wire: pay-per-attribution (fixed/variable), pool, rank. type: point | onchain-currency. payee_type: affiliate | end-user | both. Fixed: calculation_strategy fixed, referrer_amount/referral_amount. Variable: calculation_strategy variable, trigger_amount_source, base_currency, *_amount_percentage. Pool: scheme pool, amount_source, pool_amount, pool_duration, pool_calculation_day_cron. Leaderboard: scheme rank, rank_scheme_config.ranks, pool window fields. MCP normalizes variable terms (referral_amount → referral_amount_percentage). dry_run then confirmed. Before executing (including dry_run), this tool refreshes project metadata (same as get_project) and resolves trigger_id / conversion_id / trigger_ids[] to the current draft UUIDs. If you pass a published_trigger_id from before a dashboard publish, it is remapped to the current draft_trigger_id for the same ref. Responses include _draft_id_resolution when an ID was remapped. Unknown stale UUIDs fail with an explicit error. On successful execution (not dry_run), the response includes _publish_metadata_reminder: publish project metadata from the dashboard (Project → Incentives or Triggers → Publish now). The MCP cannot publish for you.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoIf true, validate and return a preview only; no server mutation.
confirmedNoMust be true to perform the mutation after reviewing dry_run output.
project_idYes
nameYes
trigger_idsYesDraft trigger UUIDs that activate this incentive.
payout_termsYesPayoutTermDto[] (min 1). Use list_payout_schemas reward_types[].create_payload_example. Schemes: pay-per-attribution (fixed/variable), pool, rank. See create_incentive_payload_guide.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explains that the tool performs a mutation (creates draft), refreshes project metadata, resolves trigger IDs to current draft UUIDs, returns error for stale IDs, and includes _publish_metadata_reminder on success. It also notes that the MCP cannot publish for the user, making side effects transparent.

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 long but well-structured: core purpose first, then step-by-step guidance. Every section adds value, though some details about payout schemes could be condensed for even better conciseness.

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?

Given the tool's complexity (6 params, nested payout_terms, no output schema), the description covers all key aspects: prerequisites, ID resolution, dry_run workflow, error handling, and post-execution reminders. It is fully complete for confident agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the input schema, especially for payout_terms where it details scheme types, field mappings, and normalization rules. It also clarifies ID resolution for trigger_ids and the purpose of dry_run/confirmed. Schema coverage is 67%, but the description compensates fully.

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 clearly states it creates a draft incentive via a specific API endpoint, and distinguishes it from sibling tools like create_trigger by detailing prerequisite steps (list_payout_schemas first) and the required workflow (dry_run then confirmed).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit prerequisites: 'REQUIRED: list_payout_schemas first—pick reward_types[].id and use create_payload_example.' Also explains when to use dry_run before confirmed, and that the tool refreshes project metadata and resolves IDs. This gives clear when-to-use guidance.

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

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/kuyen-labs/mcp_server'

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