Skip to main content
Glama

Get review

get_review
Read-only

Get a review's status and, once completed, a verdict, note, and evidence pictures for each requested check. Set wait to true to wait until it completes or fails, up to the timeout. If the result is still pending or processing, repeat the same call with wait: true. After the JSON, each evidence picture has a resource link to the same URL, followed by the picture when it fits the size limit. Only the review's creator can read it.

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": {
      "review_id": "<review_id>"
    },
    "name": "get_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait while the review is pending or processing, until it completes or fails or the timeout expires. Defaults to false.
timeoutNoHow long this read may wait, in seconds, including setup and polling. Applies when wait is true. Defaults to and is capped at 45 seconds.
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.
review_idYesReview ID returned by create_review.
inline_mediaNoSet to false to get only the JSON and resource links, without images or audio, for example when re-reading a result you have already seen. Defaults to true, which adds images and audio after their links while the result stays within its size limit.

Output Schema

NameRequiredDescriptionDefault
errorNoFailure details. Present once the review failed.
assetsYesWhat was reviewed.
checksNoOne result for each requested check.
statusYesCurrent review status.
contextYesContext sent with the request.
skill_idYesBrand Skill version the review judged against; null once that version is deleted.
warningsNoNonfatal evidence-image problems on a completed Review. Verdicts and notes remain available; unavailable image links are omitted.
failed_atNoTime the review failed. Present once failed.
review_idYesReview ID.
created_atYesTime the review was created.
referencesYesReferences sent with the request.
completed_atNoTime the review completed. Present once completed.
brand_session_idYesBrand the review judged against.
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.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the polling/timeout semantics, the authorization constraint (creator-only access), and the response shaping behavior (JSON first, then a resource link per evidence picture, followed by the embedded picture only when it fits the size limit). The instruction to repeat the call is consistent with idempotentHint=false, since status can change between reads.

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

Conciseness4/5

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

Purpose is front-loaded and each subsequent sentence covers a distinct concern (waiting, re-polling, media embedding, access). It is slightly dense at five sentences, with some detail that borders on return-value documentation, but no sentence is filler.

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?

With an output schema present, return shape needn't be documented, yet the description still covers the async lifecycle, timeout bound, media embedding caveat, and permission requirement. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: wait is framed as blocking until terminal state or timeout, and the media-payload behavior clarifies what inline_media toggles. llm_model is left entirely to the schema, which is appropriate given its analytics-only role.

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 ("Get a review's status") and enumerates what the result contains (verdict, note, evidence pictures per requested check). It is clearly distinguishable from the sibling create_review, which writes rather than reads.

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 polling: set wait to true to block until completion or failure, and repeat the same call with wait: true if the result is still pending or processing. It also states the access constraint (only the creator can read). It stops short of naming an alternative tool or stating when not to use this one, but no comparable sibling exists in the provided list.

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