Skip to main content
Glama

Claim an action-campaign task for the user

claim_task

Hold an exclusive task for the user (default 24h) and get its draft, tracked link and proof rule. Pick tasks in places the user is ALREADY a member of — ask them. Membership tasks need attest_member:true (the USER confirms; never assume) and profile_url. Then: help the user rewrite draft_text in their own voice and post it THEMSELVES; then submit_campaign_work with task_id. If they can't, release_task. Open tasks need no claim. Free.

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>",
      "task_id": "<task_id>"
    },
    "name": "claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesFrom get_campaign_brief's tasks
campaign_idYes
profile_urlNoThe user's profile in that place, or a public profile
attest_memberNoThe USER confirmed they are already a member there

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the exclusive hold, the default 24h duration, that it is free, that the user (not the agent) must confirm membership, and that the user must post themselves. It does not address what happens on re-claim (annotations mark idempotentHint=false), what occurs when the hold expires, or any auth/scope requirements, leaving a gap for a non-idempotent mutation.

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-loaded with the core action and return values, then the workflow steps. Dense and telegraphic with several clauses packed into single sentences, but nearly every sentence carries actionable information; only the 'Free.' fragment is minor clutter.

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?

Despite no output schema, the description names what comes back and lays out the full claim-perform-submit-or-release loop, which is what an agent needs for a 4-param workflow tool. Missing only edge behavior such as expiry and duplicate-claim handling for a non-idempotent operation.

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?

With 75% schema coverage the baseline is already solid, and the description adds real meaning to attest_member ('the USER confirms; never assume') and to profile_url's intended value. campaign_id remains unexplained in both places, so it stops short of a 5.

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 a specific verb and resource ('Hold an exclusive task for the user') plus the concrete return payload: draft, tracked link, and proof rule. The default 24h hold and exclusivity distinguish it clearly from sibling release_task and submit_campaign_work.

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?

Gives explicit when-to-use conditions ('pick tasks in places the user is ALREADY a member of'), a when-not exception ('Open tasks need no claim'), and routes to alternatives: submit_campaign_work afterward, release_task if the user can't proceed. Preconditions for attest_member are spelled out.

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.