Brandize

Get logo result

get_logo_result

Read-only

Poll a logo job by its jobToken. Once payment has settled, returns a URL to download the full-resolution, watermark-free asset; otherwise a pending status. Read-only and safe to poll — after the user pays, keep polling every ~5 seconds for up to a few minutes (payment confirmation is not instant) until the status is paid.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jobToken`	Yes	The jobToken returned by generate_logo.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	Human-readable guidance for the current state.
`tier`	No	Purchased delivery tier; present once paid or processing.
`format`	No	Deliverable format (e.g. "zip"); present once paid.
`status`	Yes	Job state. Only `paid` carries a downloadable asset.
`assetUrl`	No	Download URL for the deliverable; present once paid.
`includes`	No	What the deliverable bundle includes; present once paid.
`brandName`	No	Brand name on the deliverable; present once paid.
`emailNote`	No	Note about the emailed download link; present once paid.
`retryAfterSeconds`	No	Seconds to wait before polling again, when not yet ready.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "assetUrl": {
+      "description": "Download URL for the deliverable; present once paid.",
+      "type": "string"
+    },
+    "brandName": {
+      "description": "Brand name on the deliverable; present once paid.",
+      "type": "string"
+    },
+    "emailNote": {
+      "description": "Note about the emailed download link; present once paid.",
+      "type": "string"
+    },
+    "format": {
+      "description": "Deliverable format (e.g. \"zip\"); present once paid.",
+      "type": "string"
+    },
+    "includes": {
+      "description": "What the deliverable bundle includes; present once paid.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Human-readable guidance for the current state.",
+      "type": "string"
+    },
+    "retryAfterSeconds": {
+      "description": "Seconds to wait before polling again, when not yet ready.",
+      "type": "number"
+    },
+    "status": {
+      "description": "Job state. Only `paid` carries a downloadable asset.",
+      "enum": [
+        "not_found",
+        "pending_payment",
+        "processing",
+        "paid"
+      ],
+      "type": "string"
+    },
+    "tier": {
+      "description": "Purchased delivery tier; present once paid or processing.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already set readOnlyHint=true, and the description reinforces it with 'Read-only and safe to poll'. It adds valuable behavioral context: pending status before payment, polling interval, and non-instant confirmation. No contradiction with 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?

Two sentences, front-loaded with purpose and then timing details. Every word earns its place with no redundancy. Very efficient.

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?

An output schema exists, so return values don't need explanation. The description covers the polling workflow, status behavior, and timing constraints completely for a single-parameter tool. Nothing essential is missing.

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 coverage is 100% for the single parameter jobToken, including a clear description referencing generate_logo. The tool description repeats the parameter name but adds no new semantic detail beyond the schema, so 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 states a specific action (poll a logo job) and resource (by jobToken), and clarifies the outcome (download URL or pending status). It clearly distinguishes itself from sibling tools like generate_logo or buy_logo_variation by focusing on result retrieval.

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?

Provides explicit guidance on when to use (after payment settles) and how to poll (every ~5 seconds, up to a few minutes). It implies not to use before payment, though it doesn't name an alternative tool explicitly. The 'safe to poll' note adds usage clarity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Brandize tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.