Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Get generated post

get_generated_post
Read-onlyIdempotent

Get the status of a post started with generate_post, by content id. While it is running, returns the status. When it has finished, returns the design id, a preview image, the draft post's id and time, and the caption. For a video it also returns the link to the MP4 file and its length in seconds when known; the preview image is a still frame. If it failed, returns the reason. Read-only.

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": {
      "workspace_key": "<workspace_key>",
      "content_id": "<content_id>"
    },
    "name": "get_generated_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_idYesThe content id returned by generate_post.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare this read-only and idempotent, so the bar is lower, yet the description goes well beyond them: it enumerates what is returned in each of three lifecycle states (running, finished, failed), including the failure-reason case. It also discloses the video-specific extras and that the preview is a still frame, which is non-obvious behavioral detail.

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?

Front-loaded with the core action and the dependency on generate_post, then layered by outcome state. Every sentence carries information, though the video/preview sentence plus the failure sentence make it denser than strictly necessary.

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?

There is no output schema, so the description must carry return-value semantics — and it does, covering all three statuses, the success payload (design id, preview, draft id/time, caption), video fields, and the failure reason. Nothing an agent needs to interpret a response 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% and both parameters carry their own descriptions (content_id from generate_post, workspace_key with a pointer to list_workspaces). The description only restates the content-id linkage, so it adds little beyond the schema; 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?

States a specific verb and resource (get the status of a generated post by content id) and ties itself directly to its producer, generate_post. That pairing distinguishes it from get_generated_image and get_design_preview without needing their schemas.

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?

The phrase 'post started with generate_post' tells the agent this is the follow-up/polling tool for a specific async job, and the running/finished/failed branches imply it is called repeatedly until terminal. It does not explicitly say to poll or how often, so it falls short of an explicit when/when-not rule.

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

All Blaze toolsInspect
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.

Resources