Skip to main content
Glama

Publish action-campaign tasks (make them live)

publish_action_tasks
DestructiveIdempotent

Draft tasks → open: members can now see, claim and do them. Charges credits PER TASK opened (see the dry run's pricing; confirm with the user first). A cash campaign must be funded first (the error returns fund_url). Tasks whose place is in the 14-day cooldown stay draft, are listed in blocked, and cost nothing. Omit task_ids to publish every draft.

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": "publish_action_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idsNoPublish only these
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations it discloses per-task credit charges, a funding prerequisite and the fund_url error path, and the 14-day cooldown behavior where tasks stay draft, appear in `blocked`, and cost nothing. This is exactly the mutation-side context the annotations cannot convey.

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?

Four tight, front-loaded statements with no filler, and the outcome is stated before the cost and constraint caveats. A few compressed phrases ("tasks whose place is in the 14-day cooldown") require slight parsing.

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?

With no output schema, the description still surfaces the meaningful return signals: the `blocked` list and the fund_url error. It does not describe what a successful response contains beyond the state change, which is a minor gap for a two-parameter mutation.

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?

Schema coverage is only 50% (campaign_id is undocumented), but the description compensates: it explains the omit-task_ids default-means-all behavior and ties campaign_id to the funding requirement for cash campaigns. Only the format/scope of campaign_id remains implicit.

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 names a precise state transition — draft tasks become open so members can see, claim, and do them — which is more specific than the title alone. It does not explicitly distinguish itself from the sibling update_action_tasks, leaving the boundary to be inferred.

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?

It gives concrete operating conditions: confirm credit charges with the user first, fund cash campaigns first (with fund_url in the error), and omit task_ids to publish everything. What is missing is a statement of when to use update_action_tasks or create_action_campaign instead.

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.