Skip to main content
Glama

Build a versioned advertiser research graph from configured identity and approved context.

build_world_research_profile
Idempotent

Build a versioned advertiser research graph from configured identity and approved context.. 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": "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.4/5.0
Behavior1/5

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

The description declares 'Classification: read-only' while the annotations set readOnlyHint=false, and it also describes mutation modes and per-mutation seat requirements — internally inconsistent and contradictory to the annotation. Beyond that, it says nothing about what a 'versioned' graph means, whether prior versions are kept, cost/latency, or what partial failure with completed_items_not_rolled_back implies for a rebuild.

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 purpose sentence is led first, which is good, but it is followed by generic boilerplate about JSON display, assistantSummary ordering, and tone that applies to every tool in this family rather than this one. There is also a doubled period after 'approved context..', a sign of templated assembly rather than authored copy.

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?

An output schema exists, so return-value explanation is fairly excused, and the mutation-mode/partial-failure policy does add real behavioral context for a state-building tool. However, for a 16-parameter, deeply nested, versioned-write tool, the description omits what makes a rebuild safe to re-run beyond idempotency and gives no sense of input precedence or scope.

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, many deeply nested (advertiserContext, marketContext, competitorIdentities), so the description should compensate and does not. It explains only the seatId/seatName write requirement and an idempotencyKey that does not even appear in the input schema; advertiserId, targetMarket, sourceLocale/contentLocale/defaultContentLocale, marketLanguageProfile, and languageVariantGroupId are left entirely undefined.

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 description gives a specific verb and resource: 'Build a versioned advertiser research graph from configured identity and approved context.' An agent can tell this creates/derives a research artifact, but 'configured identity and approved context' is abstract and does not map to the actual inputs (advertiserId, market, advertiserContext), nor does it distinguish this from the near-identical sibling leanriq_build_world_research_profile or from get_world_research_profile.

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?

There is no explicit statement of when to call this versus the many sibling tools (get_world_research_profile, refresh_brand_profile, resolve_or_provision_advertiser). The only actionable guidance is a constraint (seatId/seatName must be supplied on a write when multiple seats are authorised) and idempotencyKey behavior, which is prerequisite information rather than when-to-use routing.

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