Skip to main content
Glama

Remove an image from a post

flypost_remove_post_image
DestructiveIdempotent

Take one image off a post draft (image_url from flypost_list_post_images). An attached photo just comes off; removing the visual a post publishes with turns a standalone post back into a plain text post, or puts a concept-backed post back on the concept's own generated visual. The post keeps no copy, so to put it back you would attach it again. Only remove an image the user asked you to take off.

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_remove_post_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
image_urlYesThe attached image url to take off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description explains exactly what the mutation destroys and what the post becomes afterward: the published visual reverts to plain text for standalone posts, or falls back to the concept's generated visual for concept-backed posts. It also discloses that no copy is retained, so restoration requires re-attaching — context an agent could not infer from the schema.

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?

Purpose is front-loaded in the first clause, and each following sentence adds a distinct fact (fallback behavior, irreversibility, user-consent boundary) with no filler. The phrasing around the concept-backed fallback is slightly dense but still parses cleanly.

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 destructive mutation with annotations covering safety and idempotency, the description supplies consequences, sourcing of the identifier, and the consent condition. Only the treatment of draft_id state (must be a draft) is left implicit, which is a minor omission rather than a blocker.

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?

With 50% schema coverage, the description partly compensates by stating that image_url comes from flypost_list_post_images and that it is 'the attached image url to take off'. draft_id is only implied via 'post draft' and gets no explicit treatment, so half the parameters remain thin, matching the baseline.

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?

The description opens with a specific verb and scope: 'Take one image off a post draft', which tells the agent this is a single-image removal on a post (not a slide) and names flypost_list_post_images as the source of the identifier. It is clear and effectively distinguishes the post variant from the slide variant, though it never states that contrast explicitly.

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?

'Only remove an image the user asked you to take off' is an explicit when-not guardrail, and the parenthetical pointing at flypost_list_post_images gives the prerequisite for obtaining a valid image_url. It stops short of naming a concrete alternative for the slide case, but the usage boundary is unambiguous.

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.