Skip to main content
Glama
getterdoneinc

getterdone-mcp-server

Official

create_task

Post a task to the GetterDone marketplace with automatic fund escrow. Set title, description, reward, category, location, and review criteria.

Instructions

Post a new task to the GetterDone marketplace. Funds are automatically escrowed from the agent's balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort title (e.g., 'Buy coffee at Starbucks on 5th Ave')
descriptionYesDetailed instructions for the worker
rewardYesUSD amount to pay the worker ($1–$100)
categoryNoTask categoryGeneral
latNoLocation latitude (optional when remote=true)
lngNoLocation longitude (optional when remote=true)
locationLabelNoHuman-readable address (optional when remote=true)
remoteNoSet true for any task that does not require the worker to be at a physical location — including image-only tasks, research tasks, writing, or any remotely-fulfilled work. If omitted or false, you MUST supply lat, lng, and locationLabel.
expiresInHoursNoHours until auto-expiry if unclaimed (0.5–720, i.e. 30 min minimum)
keywordsNoKeywords required in worker proof (max 20, each max 50 chars inclusive — a 50-character keyword is valid)
minImagesNoMinimum images required in worker proof (0–10). Pass 0 to explicitly record no image requirement. Omit entirely to leave reviewCriteria unset.
minVideosNoMinimum video clips required in worker proof (0–3). Workers may upload up to 3 clips (MP4/WebM/MOV, max 30 MB each). Omit if no video requirement.
minTrustScoreNoMinimum worker trust score to claim this task (0–100, default: open to all)
tagsNoOptional labels for searchability (max 10 tags, each max 50 chars, no HTML). Agents and workers can search by tag via the q= filter on list_tasks.
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses that funds are automatically escrowed, a key behavioral trait. However, it does not mention auth requirements, rate limits, or failure behavior. The escrow note adds value beyond the schema.

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?

Two sentences with no wasted words. The most critical information (purpose and automatic escrow) is front-loaded. Every sentence earns its place.

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

Completeness2/5

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

Despite 14 parameters and no output schema, the description is very brief. It only covers escrow. Important context like what happens after creation, how to verify success, or error handling is missing. The schema covers parameters but description lacks operational completeness.

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 baseline is 3. The description does not add any extra parameter meaning beyond what is already in the schema. It neither repeats nor contradicts the schema.

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 the action ('Post a new task') and the resource ('GetterDone marketplace'), distinguishing it from sibling tools like approve_task, cancel_task, etc. The verb and resource are specific and unambiguous.

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?

The description implies this tool is for creating new tasks, and the context of sibling tools makes it clear. However, no explicit guidance on when not to use it or alternatives is provided, but the purpose is sufficiently clear for an agent.

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/getterdoneinc/getterdone-mcp'

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