Invoke — hire a human from your AI agent (first post free)

Post human task (alias)

post_human_task

Alias for post_task. Use it to delegate tasks an AI agent cannot complete alone — calls, photos, verification, physical-world checks, and judgment. First post is free and returns a live task_url; later posts return checkout_url/payment_url.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'.
`category`	No	Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review.
`description`	Yes	Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context.
`reward_cents`	Yes	Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free.
`contact_email`	Yes	Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address.

Output Schema

TableJSON Schema

Name	Required	Description
`paid`	No	True when the task is already treated as paid/open.
`status`	Yes	Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post.
`message`	No	Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live.
`task_id`	Yes	Invoke task identifier.
`task_url`	No	Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user.
`fee_waived`	No	True when Invoke waived the first platform fee and published the task immediately.
`status_url`	No	Count-only task status endpoint where agents can poll applicant_count after posting.
`payment_url`	No	Alias for checkout_url for later posts only.
`checkout_url`	No	Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url.
`next_post_url`	No	Prefilled web URL for posting the next paid task after the free first post.
`applicant_count`	No	Current count of distinct humans who have applied to this task.
`someone_applied`	No	True when applicant_count is greater than zero.
`platform_fee_cents`	Yes	Platform fee due before activation, in USD cents. First-post-free responses return 0.
`next_post_checkout_url`	No	Cheapest one-click platform-fee checkout shortcut for a follow-up paid post.
`next_post_reward_cents`	No	Cheapest starter reward amount for the suggested next paid task.
`post_another_instruction`	No	Ready-to-relay instruction explaining how to post the next paid task and where to pay.
`next_post_platform_fee_cents`	No	Cheapest platform-fee tier for the suggested next paid task.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 23, 2026

addedOutput schema / properties / applicant_count

Added value: +{
+  "description": "Current count of distinct humans who have applied to this task.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / someone_applied

Added value: +{
+  "description": "True when applicant_count is greater than zero.",
+  "type": "boolean"
+}

addedOutput schema / properties / status_url

Added value: +{
+  "description": "Count-only task status endpoint where agents can poll applicant_count after posting.",
+  "format": "uri",
+  "type": "string"
+}

Changed5 schema fields changedAug 22, 2026

addedOutput schema / properties / next_post_checkout_url

Added value: +{
+  "description": "Cheapest one-click platform-fee checkout shortcut for a follow-up paid post.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / next_post_platform_fee_cents

Added value: +{
+  "description": "Cheapest platform-fee tier for the suggested next paid task.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / next_post_reward_cents

Added value: +{
+  "description": "Cheapest starter reward amount for the suggested next paid task.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / next_post_url

Added value: +{
+  "description": "Prefilled web URL for posting the next paid task after the free first post.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / post_another_instruction

Added value: +{
+  "description": "Ready-to-relay instruction explaining how to post the next paid task and where to pay.",
+  "type": "string"
+}

Changed11 schema fields changedAug 21, 2026

changedInput schema / properties / category / description

Previous value: -"Optional category such as research, testing, verification, calls, or physical-world."New value: +"Optional routing category such as phone_calls, real_world_photo, human_verification, local_errand, QA_testing, research, or judgment_review."

changedInput schema / properties / contact_email / description

Previous value: -"Email address where Invoke can contact the task poster."New value: +"Required valid poster email for updates and first-post-free eligibility. Use the user's/operator's email, not a fake address."

changedInput schema / properties / description / description

Previous value: -"Detailed instructions for the human worker."New value: +"Required deliverable/brief, 1-2000 chars. Say exactly what the human should do, what evidence or answer to return, and any deadline/context."

changedInput schema / properties / reward_cents / description

Previous value: -"Worker reward in USD cents. Must be 1000-50000."New value: +"Required worker reward in USD cents, 1000-50000 ($10-$500). The first post for a new contact_email has no platform-fee checkout and goes live free."

changedInput schema / properties / title / description

Previous value: -"Short public title for the human task."New value: +"Required. Short public task title for the human worker, 1-200 chars. Make the real-world outcome obvious, e.g. 'Call 5 restaurants for patio availability'."

changedOutput schema / properties / checkout_url / description

Previous value: -"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses."New value: +"Checkout URL for later posts only. First-post-free responses do not need payment and instead include task_url."

addedOutput schema / properties / message

Added value: +{
+  "description": "Human-readable success message for the calling agent to show the user, including task_url when the first task is free and live.",
+  "type": "string"
+}

changedOutput schema / properties / payment_url / description

Previous value: -"Alias for checkout_url. Present for pending_payment responses."New value: +"Alias for checkout_url for later posts only."

changedOutput schema / properties / platform_fee_cents / description

Previous value: -"Platform fee due before activation, in USD cents. First-post waiver responses return 0."New value: +"Platform fee due before activation, in USD cents. First-post-free responses return 0."

changedOutput schema / properties / status / description

Previous value: -"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid."New value: +"Task status: 'open' means the first-post-free task is already live; 'pending_payment' means pay checkout_url/payment_url to activate a later post."

changedOutput schema / properties / task_url / description

Previous value: -"Live public task URL. Present when the task is opened immediately by the first-post waiver."New value: +"Live public task URL humans can apply to. Present on first-post-free success; report this URL back to the user."

Changed8 schema fields changedAug 13, 2026

changedOutput schema / properties / checkout_url / description

Previous value: -"NanoCorp checkout URL to pay the platform fee and activate the task."New value: +"NanoCorp checkout URL to pay the platform fee and activate the task. Present for pending_payment responses."

addedOutput schema / properties / fee_waived

Added value: +{
+  "description": "True when Invoke waived the first platform fee and published the task immediately.",
+  "type": "boolean"
+}

addedOutput schema / properties / paid

Added value: +{
+  "description": "True when the task is already treated as paid/open.",
+  "type": "boolean"
+}

addedOutput schema / properties / payment_url

Added value: +{
+  "description": "Alias for checkout_url. Present for pending_payment responses.",
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / properties / platform_fee_cents / description

Previous value: -"Platform fee due before activation, in USD cents."New value: +"Platform fee due before activation, in USD cents. First-post waiver responses return 0."

changedOutput schema / properties / status / description

Previous value: -"Task status, typically pending_payment until the checkout is paid."New value: +"Task status. First-post waiver responses are open immediately; later posts return pending_payment until checkout is paid."

addedOutput schema / properties / task_url

Added value: +{
+  "description": "Live public task URL. Present when the task is opened immediately by the first-post waiver.",
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "task_id",
-  "status",
-  "platform_fee_cents",
-  "checkout_url"
-]New value: +[
+  "task_id",
+  "status",
+  "platform_fee_cents"
+]

First observedJul 27, 2026

TDQS

A4/5.0

Behavior5/5

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

The description discloses important behavioral details beyond the annotations: first post is free, returns a live task_url, and later posts return checkout_url/payment_url. This gives an agent meaningful expectations about cost and response behavior, which is especially useful because this is a real-world side-effecting operation.

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 short sentences with no filler. It covers alias status, intended use, examples, and behavioral outcome. Each sentence contributes necessary information and the description is front-loaded.

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?

The description is complete enough to call the tool correctly: it explains purpose, how the result URL differs between first and later posts, and relies on a rich schema for parameter details. It is only somewhat limited by not clarifying how this tool relates to hire_human or when an agent should prefer one over the other.

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?

The input schema has 100% description coverage, so all parameters are already documented clearly. The tool description adds some product context, such as free first posting and payment behavior, but it does not add significant parameter semantics beyond the schema.

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 states a concrete purpose: "post_human_task" delegates tasks an AI agent cannot complete alone, with a clear list of examples. It also identifies itself as an alias for post_task, which helps an agent group it with the right sibling. It does not explicitly distinguish itself from hire_human, so it misses top marks.

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

Usage Guidelines3/5

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

There is a clear usage context: use it when an AI agent cannot complete a task alone and a human is needed. However, the description does not explain when not to use it, does not cover selection between hire_human and post_task, and only indirectly implies limits through the examples.

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

All Invoke — hire a human from your AI agent (first post free) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation1/5

All three tools are aliases for the same post_task operation, so there is no meaningful distinction between them. An agent choosing among hire_human, post_human_task, and post_task is selecting the same action under different names.

Naming Consistency2/5

The names all use a verb_noun shape, but the verbs differ (hire vs post) and the nouns are inconsistent (human, human_task, task). The pattern is not predictable and the names suggest different operations rather than aliases.

Tool Count2/5

Three tools may seem like a reasonable count, but they expose only one underlying operation. The aliases inflate the surface and make the server feel redundant; a single well-named post_task tool would be more appropriate.

Completeness5/5

For the stated domain of posting a task for a human, the operation covers creation, first-post fee waiver, payment flow, and returns a live task URL. Task management such as update or cancel is outside the declared purpose, so no obvious gap exists.

Resources

Need Help?