Skip to main content
Glama

Create review

create_review

Review one asset against a brand's active Brand Skill for the requested checks. Linked files are downloaded and uploads are copied when the review is created. Each account can have 20 reviews pending or processing at once. Returns the review_id and status immediately. Then call get_review with the returned review_id and wait: true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_session_id": "<brand_session_id>",
      "assets": "<assets>",
      "checks": "<checks>"
    },
    "name": "create_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYesImage to review. Supported formats: PNG, JPEG, WebP, GIF, and SVG.
checksYesAspects of the asset to evaluate against the Brand Skill. Select the checks relevant to the requested review.
contextNoOptional. What the asset is for, or what was asked for.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
referencesNoSupporting images to compare against, such as a logo or product photo.
idempotency_keyNoOptional key for safely retrying this request. Reuse it only with the same input.
brand_session_idYesBrand session ID from list_brands for the brand to review against.

Output Schema

NameRequiredDescriptionDefault
statusYesCurrent review status.
review_idYesReview ID. Pass it as review_id to get_review.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses real operational traits: linked files are downloaded and uploads copied at creation time, a per-account cap of 20 pending/processing reviews, immediate return of review_id and status, and the asynchronous completion path. These are exactly the behaviors an agent needs and none are in the annotations.

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

Conciseness5/5

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

Four short sentences, front-loaded with purpose, then the mechanics, then the quota, then the required next step. Nothing is repeated and each sentence carries distinct information.

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

Completeness5/5

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

For an async creation tool with an output schema, the description covers what is needed: what is created, what happens to linked/uploaded assets, the concurrency limit, what comes back immediately, and the exact polling call to make next. Return-value detail is correctly left to the output schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter including llm_model, idempotency_key, references and brand_session_id. The description only restates asset/check semantics at a high level and adds no format or constraint detail beyond the structured fields, so the baseline 3 applies.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Review one asset against a brand's active Brand Skill for the requested checks'), scoping it to a single asset and a selected check set. That is enough to separate it from siblings like create_brand_edit or get_review without opening any schema.

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

Usage Guidelines4/5

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

It gives concrete when-to-use guidance for the checks argument ('Select the checks relevant to the requested review') and an explicit follow-up route: call get_review with the returned review_id and wait: true. It does not state exclusions or prerequisites for brand_session_id beyond naming the source, so it falls just short of a 5.

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