Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Publish post now

publish_post_now

Publish a draft or scheduled post immediately to the connected social accounts it targets, instead of waiting for its scheduled time. This posts publicly and cannot be undone from Blaze. Confirm the post and its channels with the user before calling.

Only draft or scheduled posts with at least one connected, active account can be published. Posts that are already published, publishing, or retrying are rejected so nothing is posted twice. Publishing runs in the background: call get_scheduled_post afterwards to see the result and the live post links.

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>",
      "id": "<id>"
    },
    "name": "publish_post_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric ID of the scheduled post to publish.
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.7/5.0
Behavior5/5

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

Annotations only give generic hints (readOnly=false, destructive=false, idempotent=false, openWorld=true); the description adds the important context: the action is public and irreversible from Blaze, ineligible statuses (published/publishing/retrying) are rejected to prevent double-posting, and execution is asynchronous so results must be polled. This is exactly the kind of behavioural detail annotations cannot carry, and it does not contradict them.

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?

Three tight sentences: effect first, then the confirmation requirement, then eligibility rules and the asynchronous follow-up. Every sentence carries actionable content; nothing is repeated from the schema or annotations.

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 a two-parameter irreversible asynchronous mutation with no output schema, the description covers all decision-relevant facts: what it does, what it requires of the user, which post states are accepted, that it is public and irreversible, and how to learn the outcome. Nothing needed to call it correctly 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 are documented there (id = numeric scheduled post ID; workspace_key with a pointer to list_workspaces). The description adds only the implicit notion that the post 'targets' accounts, which is not parameter-level meaning. Baseline 3 applies when the schema does the work.

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?

Specific verb+resource: 'Publish a draft or scheduled post immediately to the connected social accounts it targets.' It clearly distinguishes itself from schedule_posts (which sets a time) and edit_scheduled_post (which modifies rather than sends). An agent can select it without inspecting the schema.

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

Usage Guidelines5/5

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

Explicit guidance on when to use ('instead of waiting for its scheduled time'), a required human-confirmation step ('Confirm the post and its channels with the user before calling'), preconditions ('Only draft or scheduled posts with at least one connected, active account'), and a stated follow-up alternative ('call get_scheduled_post afterwards').

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