LeanrIQ

Poll a durable LeanrIQ task returned by build_ad, revise_creative, trafficking, or another queued capability and continue with the completed output.

get_task

Read-onlyIdempotent

Poll a durable LeanrIQ task returned by build_ad, revise_creative, trafficking, or another queued capability and continue with the completed output.. Classification: read-only. Execution: synchronous. Task support: forbidden. The returned JSON is internal application state for LeanrIQ and ChatGPT orchestration. Use assistantSummary first when responding to the user. Never display raw JSON, data, or meta unless the user explicitly asks for raw JSON. Mention IDs only when useful for follow-up or debugging. Prefer concise, human language, highlight the most useful insight, and suggest the next best LeanrIQ action.

Input Schema

Name	Required	Description	Default
`seatId`	No
`taskId`	Yes
`seatName`	No
`sourceLocale`	No
`targetMarket`	No
`contentLocale`	No
`marketContext`	No
`targetMarkets`	No
`contentLocales`	No
`defaultContentLocale`	No
`marketLanguageProfile`	No
`resolvedContentLocale`	No
`languageVariantGroupId`	No
`requestedOutputLocales`	No
`supportedContentLocales`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`error`	No
`status`	Yes
`assistantSummary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 13, 2026

addedInput schema / properties / contentLocale
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / contentLocales

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / defaultContentLocale
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / languageVariantGroupId

Added value: +{
+  "maxLength": 160,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / marketContext

Added value: +{
+  "properties": {
+    "currency": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "targetMarket": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "targetMarkets": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "timeZone": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / marketLanguageProfile

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / requestedOutputLocales

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / resolvedContentLocale
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / sourceLocale
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / supportedContentLocales

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / targetMarket

Added value: +{
+  "maxLength": 160,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / targetMarkets

Added value: +{
+  "items": {
+    "maxLength": 160,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}

First observedAug 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the 'Classification: read-only' line mostly restates them. The description does add useful non-schema context—synchronous execution, task-support forbidden, and response-rendering rules (assistantSummary first, hide raw JSON)—but omits polling/retry semantics such as how long a task stays valid or what a pending vs failed task looks like.

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 purpose is front-loaded, but the opening sentence is duplicated verbatim from the title (with a doubled period), and the metadata/formatting block is chatty relative to the core task. Several sentences are styling instructions rather than tool guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a 15-parameter tool with nested context objects and 0% param coverage the description is too thin on inputs. A polling tool should also indicate failure/timeout states, which it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes 15 parameters at 0% schema description coverage, and the description never names or explains a single one—not even the required taskId or the seat/market context fields. Nothing compensates for the schema gap, leaving the agent to guess what each input means.

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+resource ('Poll a durable LeanrIQ task') and identifies exactly which capabilities produce such tasks (build_ad, revise_creative, trafficking). An agent can distinguish this from list_tasks, cancel_task, and retry_task without opening any 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?

Clear context: poll the task object returned by an async capability and continue with the completed output. It does not, however, state when to prefer this over list_tasks or when to abandon polling in favor of cancel_task/retry_task, so no explicit exclusions are offered.

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

All LeanrIQ tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?