Skip to main content
Glama

Add, edit or close action-campaign tasks

update_action_tasks

Free (tasks are charged when published). add: new tasks (they start as drafts — publish them). edit: [{task_id, …fields}] — the place, reward, cap and mode are locked while someone holds the task or after an approval. close: task ids; a held task can't be closed until the hold ends. A funded cash pool never changes, so cash tasks can be added or re-priced only before funding; the new deposit is returned.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "update_action_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNo
editNo
closeNo
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost behavior (free until published), the draft lifecycle, partial-lock semantics on held/approved tasks, close restrictions, and cash-pool immutability with the new deposit being returned. These are the non-obvious mutation traits an agent needs before calling a non-idempotent write tool.

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?

Front-loads the pricing fact, then organizes by operation in short, dense fragments with almost no filler. The compression occasionally hurts clarity — 'the new deposit is returned' and 'the place, reward, cap and mode are locked' require the reader to re-parse, but nothing is redundant.

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 a multi-mode mutation tool with no output schema, the description covers cost, lifecycle, locking, and funding constraints thoroughly. It does not say what is returned (created task ids, errors on locked edits), which would matter for the add path, but otherwise nothing essential is missing.

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 top-level parameters (add, edit, close, campaign_id) carry no schema descriptions, and the description compensates: it explains add as draft creation, edit as a list of {task_id, …fields} patches, close as a list of ids, and which fields are not patchable. It adds no guidance for campaign_id and leaves the draft-text/instructions fields entirely to the nested 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?

States the resource (action-campaign tasks) and enumerates all three operations with their mechanics: 'add: new tasks (they start as drafts)', 'edit: [{task_id, …fields}]', 'close: task ids'. The draft-vs-published note implicitly routes publishing to the sibling publish_action_tasks, so an agent can distinguish the tools without opening the schema.

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 concrete conditions: edits are blocked on place/reward/cap/mode while a task is held or after approval, a held task can't be closed until the hold ends, and cash tasks can only be added or re-priced before funding. It stops short of explicitly naming sibling tools (publish_action_tasks, create_action_campaign) as alternatives, so the routing is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.