LeanrIQ

update flight

update_flight

Idempotent

update flight. Classification: writes to Studio. Execution: durable. Task support: optional. Mutation modes: validate_only, preview_only, execute. Partial failure policy: completed_items_not_rolled_back. 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. If idempotencyKey is omitted on a mutation, the MCP layer derives a deterministic retry key from the tool and business arguments so an accidental identical replay cannot create duplicate work. For a mutation when more than one seat is authorised, seatId or seatName must be supplied on that exact tool call; a remembered or previously selected seat is not sufficient for a write.

Input Schema

Name	Required	Description	Default
`name`	No
`dryRun`	No
`seatId`	No
`flightId`	Yes
`platform`	No
`seatName`	No
`accountId`	No
`approvalId`	No
`campaignId`	No
`advertiserId`	No
`sourceLocale`	No
`targetMarket`	No
`contentLocale`	No
`marketContext`	No
`targetMarkets`	No
`contentLocales`	No
`idempotencyKey`	No
`thirdPartyTags`	No
`creativeConfigs`	No
`expectedVersion`	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"
+}

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / creativeConfigs / items / properties / thirdPartyTags

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "creativeId": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "name": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "tag": {
+        "maxLength": 12000,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "tag"
+    ],
+    "type": "object"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

addedInput schema / properties / thirdPartyTags

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "creativeId": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "name": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "tag": {
+        "maxLength": 12000,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "tag"
+    ],
+    "type": "object"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

First observedAug 12, 2026

TDQS

C2.5/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description usefully adds traits beyond them: the partial-failure policy (completed_items_not_rolled_back), the deterministic idempotency-key derivation for accidental replays, and the requirement that seatId/seatName be passed on the exact mutation call rather than remembered. These are genuinely valuable operational details for a write tool.

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?

It is labeled and organized, but a large fraction is generic response-formatting boilerplate ("Never display raw JSON", "suggest the next best LeanrIQ action") that applies to any tool and is front-loaded with a tautological opening line. The tool-specific content is buried among orchestration instructions.

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?

For a 26-parameter mutation with nested objects, the description omits what is actually being updated, how expectedVersion interacts with updates, and the semantics of the vast majority of fields. The output schema exists so return values needn't be described, but the write-behavior coverage is too thin for a tool of this complexity.

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

Parameters2/5

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

With 26 parameters at 0% schema description coverage, the description carries the full burden, yet it only explains idempotencyKey and seatId/seatName. The other ~23 parameters (dryRun, expectedVersion, creativeConfigs, marketContext, locales, etc.) get no semantic explanation, leaving the agent to guess their meaning and interaction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"update flight" merely restates the tool name/title; it doesn't say what fields are updatable or the scope of the update. "Classification: writes to Studio" is the only descriptive content, and it duplicates what readOnlyHint=false already tells the agent. It does nothing to distinguish this from update_campaign, update_advertiser, validate_flight, or delete_flight.

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

Usage Guidelines2/5

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

The mutation modes (validate_only, preview_only, execute) hint at how to invoke it but give no guidance on when to choose update_flight over siblings like validate_flight, retraffick_flight, or create_flight. The seat rule is a prerequisite, not when-to-use guidance, and there are no exclusions.

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?