Postemi: Social Media Scheduler

fotoai_get_generation

Idempotent

The status of a FotoAI generation, and once it is completed its outputs saved into this Postemi workspace's media library.

Pass the generation_id from fotoai_generate (or any FotoAI generation id the user gives you). While status is "running" or "queued", wait and call again (or pass wait_seconds up to 50). When status is "completed", attach each media PATH (not the id) to create_post. A failed generation costs nothing.

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": {
      "generation_id": "<generation_id>"
    },
    "name": "fotoai_get_generation"
  }
}

Input Schema

Name	Required	Description
`import`	No	Save the outputs into the media library (default true).
`wait_seconds`	No	Wait up to this long for a running generation (0 to 50).
`generation_id`	Yes

Output Schema

Name	Required	Description	Default
`error`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations, it discloses the polling loop behavior, the 50-second wait cap, the media-library import side effect, and that a failed generation costs nothing (billing context). Annotations already cover idempotency and non-destructiveness, so this is solid added value; only a note on import=false consequences is absent.

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?

Three tight sentences ordered as purpose, then how to poll, then what to do with the result. The opening sentence is grammatically awkward ('The status of ... and once it is completed its outputs saved'), a minor blemish on otherwise front-loaded structure.

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-value detail is unnecessary, and the description fills the remaining gaps: status lifecycle values, polling cadence, wait cap, and downstream handoff to create_post via media PATH. 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 67% and the undocumented generation_id parameter is explained in prose (where to get it), while wait_seconds and import behavior are reinforced with practical intent. This meaningfully exceeds what the schema alone conveys.

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

Purpose4/5

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

States a specific verb and resource: retrieves the status of a FotoAI generation and notes outputs land in the workspace media library. It names fotoai_generate as the source of the id, which distinguishes it from the generation tool itself, though the opening sentence is a fragment that takes a moment to parse.

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?

Explicitly says to pass the generation_id from fotoai_generate or a user-supplied id, tells the agent to poll while status is running/queued (with wait_seconds up to 50), and instructs attaching the media PATH rather than the id to create_post. The alternative and follow-on routing are both spelled out.

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

All Postemi: Social Media Scheduler 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.