Skip to main content
Glama

Choose which version an image post uses

flypost_select_image

Pin one of an image or infographic post's generated versions as the image it shows and publishes (the editor's version picker). flypost_view_visuals lists the versions. A new generation is pinned automatically; use this to go back to an earlier one. Place the logo afterwards.

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>",
      "image_url": "<image_url>"
    },
    "name": "flypost_select_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
image_urlYes

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?

The annotations establish that this is a safe, non-destructive, closed-world mutation, and the description adds useful context beyond them: that the selection is a pin that controls what 'shows and publishes', and that new generations are pinned by default, so this is a deliberate override. The closing 'Place the logo afterwards' adds workflow-ordering guidance that an agent could not infer from the schema. Reversibility and the fate of the previously pinned version are still unstated.

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?

Four short sentences, front-loaded with the action and destination, followed by the alternative, the default behavior, and the ordering note. No filler, and each sentence contributes a distinct fact.

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?

For a two-parameter selection tool with no output schema, this covers purpose, source of inputs, default behavior, and a downstream step, which is close to sufficient. The main gap is that it never states that the supplied image_url must come from the generated versions or what happens to the current pin when a different version is chosen.

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 description coverage is 0%, so the description must carry both parameters. It implicitly characterizes 'image_url' as one of the generated versions enumerated by flypost_view_visuals, which is genuinely useful, but it never explicitly states that constraint, and 'draft_id' (the post being acted on) is not addressed at all.

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 definition uses a specific verb ('Pin') on a specific resource ('one of an image or infographic post's generated versions as the image it shows and publishes'), with an explicit parenthetical mapping to the editor's version picker. It also distinguishes the tool's role from the listing tool by naming 'flypost_view_visuals' as the place where versions come from.

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?

It gives a concrete trigger for using it ('A new generation is pinned automatically; use this to go back to an earlier one') and points to the sibling that lists versions. What is missing is an explicit when-not or a named alternative for setting the published image from scratch (e.g., the attach/upload path), but the operative context is clear.

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.