Skip to main content
Glama

Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor. Defaults match Studio: 90-day DISPLAY evidence and no mixed social/video banner inference. Without forceRefresh, an existing canonical result is reused when available.

run_competitor_intelligence
Idempotent

Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor. Defaults match Studio: 90-day DISPLAY evidence and no mixed social/video banner inference. Without forceRefresh, an existing canonical result is reused when available.. Classification: creates billable AI usage. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_competitor_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
domainNo
marketNo
regionNo
seatIdNo
marketsNo
websiteNo
seatNameNo
brandNameNo
advertiserIdNo
competitorIdNo
evidenceModeNoDISPLAY
forceRefreshNo
lookbackDaysNo
sourceLocaleNo
strategyModeNoBOTH
targetMarketNo
contentLocaleNo
evidenceLimitNo
marketContextNo
strategyModesNo
targetMarketsNo
competitorNameNo
contentLocalesNo
competitorDomainNo
competitorWebsiteNo
crossChannelLimitNo
recommendationModeNoFULL
defaultContentLocaleNo
competitorKeyMessagesNo
competitorPositioningNo
marketLanguageProfileNo
resolvedContentLocaleNo
languageVariantGroupIdNo
requestedOutputLocalesNo
supportedContentLocalesNo
advertiserGuidanceSnapshotNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
errorNo
statusYes
assistantSummaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / crossChannelLimit
      Added value: +{
      +  "maximum": 120,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Changed15 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"
      +}
    • removedInput schema / properties / targetMarkets / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -]
    • addedInput schema / properties / targetMarkets / items
      Added value: +{
      +  "maxLength": 160,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / targetMarkets / maxItems
      Added value: +50
    • addedInput schema / properties / targetMarkets / type
      Added value: +"array"
  3. Changed1 schema field changed
    • addedInput schema / properties / recommendationMode
      Added value: +{
      +  "default": "FULL",
      +  "enum": [
      +    "FULL",
      +    "EVIDENCE_ONLY"
      +  ],
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / competitorKeyMessages
      Added value: +{
      +  "items": {
      +    "maxLength": 300,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 8,
      +  "type": "array"
      +}
    • addedInput schema / properties / competitorPositioning
      Added value: +{
      +  "maxLength": 1200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / evidenceLimit / maximum
      Previous value: -24New value: +48
    • changedInput schema / properties / limit / maximum
      Previous value: -24New value: +48
  6. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations cover the safety profile (non-readonly, open-world, idempotent, non-destructive), and the description goes meaningfully beyond them: billable AI consumption, durable execution, partial-failure semantics ('completed_items_not_rolled_back'), and deterministic idempotency-key derivation. The gap is that it advertises 'Mutation modes: validate_only, preview_only, execute' and an 'idempotencyKey' input that do not appear in the schema, which could mislead an agent looking for those controls.

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 front-loaded purpose and execution-policy block are well ordered, but the definition pads itself with generic response-presentation instructions (never display raw JSON, mention IDs only when useful) that do not describe the tool's behavior, contains a doubled period, and repeats the reuse rule from the title.

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

Completeness3/5

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

The existence of an output schema means return values needn't be described, and execution/idempotency/billing are well covered. However, for a tool with 38 optional parameters and zero schema descriptions, the definition leaves the agent without guidance on which identifier fields to supply and how they interact, which is the main completeness failure.

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?

Schema description coverage is 0% across 38 parameters, so the description carries the full burden and largely fails to. Only forceRefresh (reuse behavior) and the evidenceMode default of DISPLAY are given meaning; the many competing identity fields (competitorId, competitorName, competitorDomain, website, brandName) and strategy/locale/market parameters are left completely unexplained.

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?

The opening sentence gives a concrete verb and resource ('Run canonical LeanrIQ Competitor Intelligence V2 for one advertiser-scoped competitor') and pins the scope to a single competitor. It implies but does not explicitly name how it differs from siblings such as get_competitor_intelligence or list_competitor_evidence, so the agent must infer the run-vs-read split from naming alone.

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?

The description explains the caching rule ('Without forceRefresh, an existing canonical result is reused') and that defaults mirror Studio, which is real when-to-use signal. It never states when to prefer this over the read-only sibling tools or when a fresh run is warranted, so guidance remains implied rather than explicit.

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