Perkadoo

Create a giveaway

create_giveaway

Draft a hosted giveaway: prize, dates, draw, entry page, bonus entries and official rules. It starts as a draft with a preview link. A signed-in person approves it at dashboardUrl before it goes live; send them that link.

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": {
      "brandId": "<brandId>",
      "name": "<name>",
      "opensAt": "<opensAt>",
      "closesAt": "<closesAt>"
    },
    "name": "create_giveaway"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The giveaway's name, shown as its title.
`rules`	No	The official rules. sponsorCountry and countries default to the brand's own country. A person approves them before the giveaway goes live.
`prizes`	No	One prize per place for placed draws; otherwise the first prize goes to every winner.
`brandId`	Yes	Brand ID, the project that runs the giveaway.
`opensAt`	Yes	When entries open, as an ISO 8601 time.
`closesAt`	Yes	When entries close, as an ISO 8601 time. Must be after opensAt.
`language`	No	The language entrants see: en or es. Left out, the language of the brand's country, else en.
`timezone`	No	The time zone the official rules and dashboard use, e.g. Europe/London. Left out, the brand's own: from its site's country domain, then its saved zone.
`entryPage`	No	The hosted entry page's headline, description, image, brand color and bonuses.
`drawMethod`	No	single: one winner. multiple: equal winners. placed: 1st, 2nd, 3rd…	single
`winnerCount`	No	How many winners to draw.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / entryPage / description

Previous value: -"The hosted entry page's headline, description, image, brand colour and bonuses."New value: +"The hosted entry page's headline, description, image, brand color and bonuses."

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "The language entrants see: en or es. Left out, the language of the brand's country, else en.",
+  "enum": [
+    "en",
+    "es"
+  ],
+  "type": "string"
+}

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare the generic safety profile (not read-only, not destructive, not idempotent, closed-world). The description adds real behavioral context: the object is created in draft state, a preview link and dashboardUrl are produced, and a signed-in human must approve before publication. It does not cover whether drafts expire, how they are later published, or what happens on name collisions.

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, no filler, and the draft-then-approve lifecycle is front-loaded right after the scope statement. Every sentence carries information the agent must act on.

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?

For an 11-parameter nested creation tool with no output schema, the description supplies the two return artifacts the agent needs (preview link, dashboardUrl) and the approval gate. It leaves the post-creation path — how the draft goes live, or whether it can be edited — unstated, which is a modest gap for a create 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 coverage is 100%, so the schema already documents all 11 parameters including nested objects and enums. The description's list ('prize, dates, draw, entry page, bonus entries and official rules') merely gestures at those parameter groups without adding format or defaulting detail beyond what the schema states.

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?

States a specific verb ('Draft') and resource ('hosted giveaway') and enumerates the surface it covers: prize, dates, draw, entry page, bonus entries and official rules. The 'draft, not live' framing implicitly separates it from update_giveaway, but it never names a sibling explicitly.

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?

Gives clear context for use: it creates a draft that requires human approval at dashboardUrl before going live, and instructs the agent to send that link. It stops short of stating when-not-to-use (e.g. editing an existing giveaway via update_giveaway) or any plan gating for bonus entries.

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

All Perkadoo 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.

Resources

Need Help?