Skip to main content
Glama

Post Ai Gettaskresult

hgr_post_ai_gettaskresult
Read-onlyIdempotent

Dedicated HGRApi tool for POST api/AI/GetTaskResult. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns the authorized AI proposal for review. ownerAgent: optimization. Use when: Use to inspect generated content before publication. Input: Header channel, TaskId, and ListingId (ListingVariation ID). Output: Title, description and images retain Result. Fields returns FieldsOptimization with previous/proposed values, per-field status, proposed changes and supplier URL evidence. Search terms: ai gettaskresult. Send the exact request payload in body. 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>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_post_ai_gettaskresult"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/AI/GetTaskResult request body.
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.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real context beyond them: what the payload contains (Title, description, images), the FieldsOptimization shape with previous/proposed values and supplier URL evidence, and the note that ChannelOAuthId is resolved internally. It doesn't mention error or empty-result behavior.

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?

Front-loaded with the endpoint and purpose, and the labeled Purpose/Use when/Input/Output structure is scannable. However, "Search terms: ai gettaskresult" and the fixed-endpoint boilerplate are filler, and the output details repeat what the output schema already provides.

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?

Covers purpose, trigger condition, body contents, auth resolution and result shape, which is enough for a two-parameter passthrough tool that also has an output schema. The only miss is the lack of any comparison to sibling AI-publisher tools.

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 baseline is 3, but the description goes further by naming the body contents (Header channel, TaskId, ListingId / ListingVariation ID) that the opaque "body" parameter does not document. That is meaningful added semantics for an untyped body.

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: "Returns the authorized AI proposal for review" for POST api/AI/GetTaskResult. It also explicitly disclaims generic-endpoint behavior ("it is not a generic endpoint caller"). It doesn't name a specific sibling to differentiate against, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a workable when-to-use cue: "Use to inspect generated content before publication." There is no when-not guidance and no pointer to the obvious alternatives (e.g. hgr_get_ai_gettasks for listing tasks), leaving the agent to infer routing.

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