AutomateSocials

Generate an image

generate_image

Destructive

Makes a picture from a description and stores it, ready to attach to a post. Call it as soon as you know what the picture should be: the user is asked to confirm the spend before it runs, with the price, so you do not need to ask them first. Describe the subject and the setting in the prompt; the model cannot see the brand kit, so put anything from it that matters into the words. If the project has set an image prompt, it is wrapped around what you write and sets the look, so you do not need to repeat the house style.

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": {
      "prompt": "<prompt>"
    },
    "name": "generate_image"
  }
}

Input Schema

Name	Required	Description
`count`	No	How many to make, up to 4. Defaults to 1.
`model`	No	A model from list_image_models. Defaults to the workspace one.
`prompt`	Yes	What the picture should show, in detail.
`imageUrl`	No	An existing picture to edit or work from, rather than starting blank.
`resolution`	No	1K, 2K or 4K. Larger costs more at some models.
`aspectRatio`	No	e.g. 1:1, 4:5 for Instagram, 16:9 for a link preview.
`forPlatform`	No	Where this picture is going: facebook, instagram, x, linkedin or tiktok. Give it and the shape is chosen to suit that feed, which saves the user a cropped post.
`ignoreProjectStyle`	No	Generate exactly this prompt, without the project's image template. Only when the user asks for something outside their usual look.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description explains that the user confirms spend with price before execution, that the generated image is stored for later attachment, and that the model cannot see the brand kit. It also explains how project-level image prompts wrap the supplied prompt, which is meaningful behavioral context.

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?

The purpose is front-loaded in the first sentence, and the remaining sentences each add operational value: spend confirmation, prompt guidance, and project-style interaction. There is no obvious filler.

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?

Given eight parameters, full schema descriptions, no output schema, and annotations covering safety hints, the description supplies the important missing context: cost confirmation, storage behavior, brand-kit limitations, and project-style wrapping. An agent has enough information to call it correctly.

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 100%, so the parameter definitions already carry the baseline burden. The description still adds useful meaning for the prompt: describe subject and setting, include brand-kit details manually, and rely on the project image prompt for house style rather than repeating it.

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 uses a specific verb and resource: it makes a picture from a description, stores it, and makes it ready to attach to a post. That clearly separates it from sibling tools like generate_video and gives an agent enough to understand the tool's core action.

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 clearly states when to call it: as soon as the picture is known, without asking the user first because spend confirmation and price are handled. It does not explicitly name alternatives such as estimate_image_cost or list_image_models, so it falls short of full when/when-not/alternative routing.

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

All AutomateSocials 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.

Resources

Need Help?