Skip to main content
Glama

Build a versioned advertiser research graph from configured identity and approved context. (deprecated alias)

leanriq_build_world_research_profile
Idempotent

Build a versioned advertiser research graph from configured identity and approved context.. Deprecated alias for build_world_research_profile. Classification: read-only. 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.

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": "leanriq_build_world_research_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
seatIdNo
seatNameNo
advertiserIdNo
sourceLocaleNo
targetMarketNo
contentLocaleNo
marketContextNo
targetMarketsNo
contentLocalesNo
advertiserContextNo
defaultContentLocaleNo
marketLanguageProfileNo
resolvedContentLocaleNo
languageVariantGroupIdNo
requestedOutputLocalesNo
supportedContentLocalesNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
errorNo
statusYes
assistantSummaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / advertiserContext / properties / researchImages
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "assetId": {
      +        "maxLength": 160,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "label": {
      +        "maxLength": 220,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "url": {
      +        "format": "uri",
      +        "maxLength": 1800,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "assetId",
      +      "label",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 16,
      +  "type": "array"
      +}
  2. Added

TDQS

C2.8/5.0
Behavior2/5

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

The description does add real behavioral texture beyond the annotations: mutation modes (validate_only, preview_only, execute), the completed_items_not_rolled_back partial-failure policy, deterministic retry-key derivation when idempotencyKey is omitted, and the multi-seat write requirement. But it labels the tool 'Classification: read-only' while annotations declare readOnlyHint=false and the same description discusses mutations and 'execute' mode, so an agent could call a graph-creating mutation expecting no side effects.

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?

Purpose and deprecation are front-loaded, but the body mixes tool-specific facts (mutation modes, failure policy, seat rule) with generic response-formatting boilerplate about assistantSummary and not displaying raw JSON that applies to every LeanrIQ tool. There is also a doubled period in the opening sentence, a small sign of unpolished assembly.

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 described, but for a 16-parameter tool with a large nested advertiser payload the description never says which fields are mandatory in practice, how validate_only and preview_only differ in effect, or what happens to an existing profile when a new version is built. The closing idempotency and seat rules are helpful but do not cover the payload surface.

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 16 parameters, including a deeply nested advertiserContext with dozens of sub-properties (brands, competitors, approvedClaims, researchImages, campaignContext), so the description carries the full burden. It only addresses seatId/seatName and the omitted idempotencyKey; it explains nothing about advertiserId, targetMarket, contentLocale, or the identity-versus-approved-context split the payload expects.

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 first sentence gives a specific verb and resource ('Build a versioned advertiser research graph') and the second identifies it precisely as a deprecated alias of build_world_research_profile, so an agent can distinguish it from the canonical tool. It stops short of 5 because terms like 'configured identity' and 'approved context' are abstract and the description never explains what a world research profile actually contains or why one is built.

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 deprecation note implies the agent should prefer build_world_research_profile, which is useful routing guidance, and the closing sentences state that seatId/seatName must be supplied on a mutation when multiple seats are authorised. However, there is no explicit instruction such as 'use build_world_research_profile instead of this alias' and no statement of when to choose execute versus validate_only versus preview_only beyond listing the mode names.

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