Skip to main content
Glama

Post Ai Createtask

hgr_post_ai_createtask
Destructive

Dedicated HGRApi tool for POST api/AI/CreateTask. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Creates AI optimization tasks for selected store products, including supplier-backed eBay product characteristics / item specifics. ownerAgent: optimization. Use when: Use to generate product improvements for review or optional automatic publication. Fields supports published eBay API and eBay No API products with exact supplier associations. Input: Header channel: current ChannelOAuthId. Action, AutoPublish, Listings (exact ListingVariation IDs), and Settings. For Fields, up to 100 distinct products; setting PROMT accepts fields:missing (default) or fields:replace. Output: Returns Success. Fields retrieves missing supplier details through scraping and consumes AI tokens when a valid proposal is saved. No historical supplier content or pending publication originals are required. Search terms: ai createtask. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

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": {
      "body": "<body>",
      "confirmed": "<confirmed>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_post_ai_createtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/AI/CreateTask request body.
confirmedYesMust be true after the user explicitly requested or confirmed the exact action.
channelOAuthIdYesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, idempotent=false, so the safety profile is known. The description adds meaningful behavior beyond that: Fields retrieves missing supplier details through scraping and consumes AI tokens when a proposal is saved, up to 100 distinct products, and confirmed=true is required before execution. That token-cost disclosure is genuinely useful context an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The useful content (purpose, use case, cost, prerequisites) is front-loaded, but the text is bloated with boilerplate such as the documentation prefix, 'This is an explicit tool with a fixed endpoint', and the trailing 'Search terms: ai createtask'. Several sentences could be trimmed without losing information.

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 destructive, non-idempotent mutation tool with an output schema, the description covers the essentials: what it creates, scope limits, token consumption, and the confirmed=true gate. Return values are handled by the output schema, so the only minor gap is the absence of guidance on related follow-up tools or failure handling.

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 100%, so the baseline is 3, but the description adds real meaning: the 100-product cap on Fields, the PROMT values fields:missing (default) or fields:replace, and the fact that ChannelOAuthId is resolved internally. This goes beyond the schema's own parameter descriptions for body and channelOAuthId.

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?

States a specific verb and resource: 'Creates AI optimization tasks for selected store products, including supplier-backed eBay product characteristics / item specifics.' It also explicitly disclaims being a generic endpoint caller, which helps distinguish it from other hgr_post_* wrappers. It does not name sibling alternatives like hgr_post_ai_gettaskresult or hgr_post_ai_publishnow, so sibling differentiation is only partial.

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?

'Use when: Use to generate product improvements for review or optional automatic publication' gives a clear positive usage context, and the note that no historical supplier content or pending publication originals are required rules out one scenario. However, it never states when NOT to use it or which sibling to pick instead (e.g., publishnow versus createtask), leaving alternative selection to inference.

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.

Resources