Skip to main content
Glama

LeanrIQ Creative Runtime: Default preview mode works without Studio and stores research, briefs, builds, QA, and previews in a LeanrIQ workspace. collaborate keeps proposals non-destructive; operate deliberately creates Studio work. Publish is never inferred: traffic_ready and publish remain explicit governed Studio actions.

launch_creative_campaign
Idempotent

LeanrIQ Creative Runtime: Default preview mode works without Studio and stores research, briefs, builds, QA, and previews in a LeanrIQ workspace. collaborate keeps proposals non-destructive; operate deliberately creates Studio work. Publish is never inferred: traffic_ready and publish remain explicit governed Studio actions.. Classification: writes to Studio, creates billable AI usage, publishes externally. Execution: synchronous. Task support: forbidden. 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

NameRequiredDescriptionDefault
KPINo
ctaNo
toneNo
brandNo
forceNo
offerNo
budgetNo
seatIdNo
channelNo
endDateNo
productNo
audienceNo
elementsNo
flightIdNo
headlineNo
platformNo
seatNameNo
verticalNo
accountIdNo
mustAvoidNo
objectiveYes
skippableNo
startDateNo
approvalIdNo
campaignIdNo
flightNameNo
constraintsNo
creativeIdsNo
destinationNo
funnelStageNo
mustIncludeNo
persistenceNo
targetSizesNo
workspaceIdNo
advertiserIdNo
campaignNameNo
deliverablesNo
saveToStudioNo
sourceLocaleNo
targetMarketNo
contentLocaleNo
executionModeNopreview
marketContextNo
targetMarketsNo
contentLocalesNo
idempotencyKeyNo
landingPageUrlNo
sourceAssetIdsNo
supportingCopyNo
thirdPartyTagsNo
durationSecondsNo
revisionRequestNo
workspaceSourceNo
performanceEvidenceNo
defaultContentLocaleNo
sourceFrameImageUrlsNo
workspaceAccessTokenNo
marketLanguageProfileNo
resolvedContentLocaleNo
languageVariantGroupIdNo
requestedOutputLocalesNo
createCampaignIfMissingNo
supportedContentLocalesNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
errorNo
statusYes
assistantSummaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • 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"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / sourceFrameImageUrls
      Added value: +{
      +  "items": {
      +    "maxLength": 4000,
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
  3. Changed6 schema fields changed
    • addedInput schema / properties / cta
      Added value: +{
      +  "maxLength": 500,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / durationSeconds
      Added value: +{
      +  "maximum": 120,
      +  "minimum": 5,
      +  "type": "integer"
      +}
    • addedInput schema / properties / headline
      Added value: +{
      +  "maxLength": 500,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / skippable
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / sourceAssetIds
      Added value: +{
      +  "items": {
      +    "maxLength": 240,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
    • addedInput schema / properties / supportingCopy
      Added value: +{
      +  "maxLength": 500,
      +  "minLength": 1,
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / creativeIds
      Added value: +{
      +  "items": {
      +    "maxLength": 240,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 24,
      +  "minItems": 1,
      +  "type": "array"
      +}
  5. Changed1 schema field changed
    • 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"
      +}
  6. First observed

TDQS

B3.1/5.0
Behavior5/5

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

Substantial disclosure beyond annotations: classification as a Studio write that incurs billable AI usage and can publish externally, synchronous execution, task support forbidden, mutation modes (validate_only/preview_only/execute), partial-failure policy (completed_items_not_rolled_back), deterministic idempotency-key derivation, and the rule that seatId/seatName must be passed explicitly on a multi-seat write. These materially raise the agent's confidence about side effects and safety.

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

Conciseness2/5

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

The text opens by restating the title nearly verbatim, is a dense run-on with a stray double period, and mixes governance, behavior, and user-facing response style rules. The most decision-relevant facts (mutation modes, seat requirement) are buried in the middle rather than front-loaded.

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-value explanation is not required, but for a 63-parameter mutation tool with rich nested objects and enum modes the definition is still incomplete — the vast majority of parameters are unexplained and the relationship between executionMode, persistence, and saveToStudio is never clarified.

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 63 parameters and 0% schema description coverage, the schema does none of the work, so the description must compensate — yet it only addresses idempotencyKey and seatId/seatName. The other ~60 parameters (objective, executionMode, persistence, brand, locales, etc.) carry no semantic explanation in either place.

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

Purpose3/5

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

The description frames the tool around execution modes and governance rather than stating plainly what launch_creative_campaign does (launch/assemble a creative campaign). It implies creation ('operate deliberately creates Studio work') but never gives a clean verb+resource anchor, and it repeats the title verbatim.

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?

It conveys useful mode-selection guidance — default preview works without Studio, collaborate keeps proposals non-destructive, operate creates Studio work, and publish/traffic_ready are never inferred. However, it never names a sibling tool as an alternative nor states explicit preconditions (e.g. when to use this instead of build_campaign_creative_set or run_creative_chain).

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