Skip to main content
Glama

create_task

Submit a text description to create a task for a human expert in data scraping, software development, design, copywriting, or general tasks.

Instructions

Create a new Tendem task for a human expert.

Poll get_task until AWAITING_APPROVAL to see the price.

After creation, poll with get_task until status is AWAITING_APPROVAL to see the price (may take up to 10 minutes).

When creating a task consider available human expert specializations: 1. data_scraping

  • Task types: High-volume data extraction, scraping, cleansing and enrichment (web, social media, or document sets).

  • Threshold: MUST be used when manual effort would exceed ~4 hours OR when tools like Selenium/BS4/Apify are required. 2. software_development

  • Task types: Debugging/refactoring existing code. Writing automation scripts. Building full-stack apps (Python, Node, TS). Building/adding features to WordPress, Woocommerce, Shopify based websites and stores. 3. design

  • Task types: Logos, Branding, Presentations (decks), Print Materials (flyers/brochures/billboards), and Packaging. 4. copywriting

  • Definition: Writing where style, tone, and usage of language is important.

  • Task types: SEO Writing, Newsletters, Press Releases, Case Studies, Ad Copy, Landing Page texts, Social Media posts, UX Writing, Email campaigns, Proofreading, editing, refining and humanizing ai text. 5. general

  • Definition: Expert level knowledge not required, good at attention to detail, using software and ai tools.

  • Task types: Manual data collection, enrichment, cleaning and analysis (incl. lead generation, contact list building), market research, formatting documents, converting files.

Avoid tasks that: Required Regulated Expertise: Medical diagnosis, legal advice, PhD-level research, or real-money investment advice. Required access to private/internal systems without providing credentials e.g., "Check my email"

Args: text: The task description/prompt to execute.

Returns: The created task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
nameYes
statusYes
created_atYes
approval_request_infoNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains polling behavior and creation time, but does not cover all side effects. Still, it adds significant behavioral context.

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 well-structured with a clear first sentence, followed by polling instructions, specializations, and avoidance guidelines. It is appropriately sized for the tool's complexity, though slightly verbose.

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 complexity of task creation with asynchronous polling and multiple specialization options, the description covers creation, polling, specializations, and prohibitions. An output schema exists, so return values are not needed.

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

Parameters4/5

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

The only parameter 'text' is described as 'The task description/prompt to execute,' adding meaning beyond the bare schema (type string, no description). With 0% schema coverage, description compensates well.

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 'Create a new Tendem task for a human expert,' specifying the verb and resource, and distinguishes from sibling tools like approve_task and cancel_task.

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?

The description explicitly lists when to use this tool with specializations and thresholds, and provides avoidance guidelines for regulated expertise or private system access, offering clear when-to-use and when-not-to-use advice.

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/Toloka/tendem-mcp'

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