Skip to main content
Glama

Suggest picture ideas for a text post

flypost_suggest_post_image_ideas
Read-only

Have Flypost pitch three picture ideas for a TEXT post (each: a title, what is in the frame, and short on_image_text). Nothing is rendered or saved; you can also pitch 2-3 yourself. Show the user the ideas and let them pick, then render the chosen one with flypost_create_post_image. Rules for ideas: concrete and drawable, tied to this post, never a real product's UI or logo, no brand name, and the words on the image never claim more than the post does (a post that says 'reportedly' gets no image stating it as fact). Not for image, infographic or carousel posts (flypost_design_visual).

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": {
      "draft_id": "<draft_id>"
    },
    "name": "flypost_suggest_post_image_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
directionNoThe user's steer, e.g. 'simpler, no diagrams'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with a stronger operational claim: 'Nothing is rendered or saved.' It also discloses the content constraints the generated ideas must obey (drawable, no real product UI or logo, no brand name, no overclaiming). It stops short of describing ordering, cost, or failure modes, so it is strong but not exhaustive.

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 purpose and output shape, then workflow, then idea rules, then the exclusion — a sensible order. The rules clause is long and dense, but each rule materially constrains generation, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries return-value explanation well by enumerating the three fields per idea. For a two-parameter, side-effect-free tool it is nearly complete; the remaining gap is the unexplained draft_id mapping against a 50%-covered schema.

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

Parameters2/5

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

Schema coverage is only 50%: draft_id has no description in the schema, and the tool definition never explains that the post to tie ideas to is passed as draft_id. The 'direction' parameter (user steer) is only defined in the schema, and the description does not say how the 'you can also pitch 2-3 yourself' flow interacts with it. The post reference is implied by 'tied to this post' but never mapped to a parameter.

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 gives a specific verb and resource ('pitch three picture ideas'), names the exact output shape (title, frame content, on_image_text), and scopes it to TEXT posts. It also explicitly distinguishes itself from flypost_design_visual, so an agent can route without opening either 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?

It states when to use (text post needs imagery), when not to use ('Not for image, infographic or carousel posts' → flypost_design_visual), and the follow-on step (show ideas, then render the pick with flypost_create_post_image). It even permits an alternative path where the agent pitches ideas itself, which is explicit guidance rather than inference.

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.