Skip to main content
Glama

generate_social_media

Generate platform-optimized social media visuals with automatic aspect ratios, text-safe zones, and engagement-focused styling for Instagram, TikTok, YouTube, and other networks.

Instructions

Generate platform-optimized social media content with correct dimensions and engagement-focused styling.

Use this when:

  • Creating content for Instagram, TikTok, YouTube, Twitter, LinkedIn, Facebook, Pinterest

  • Need platform-specific aspect ratios automatically applied

  • Want scroll-stopping, engagement-optimized visuals

  • Need text-safe zones for overlay design

NOT for:

  • E-commerce product photography (use generate_product instead)

  • Logos or branding assets (use generate_logo instead)

  • General artistic images (use generate_image instead)

  • Editing existing social media images (use edit_image instead)

Chain with: If user requests specific pixel dimensions beyond platform defaults, chain with resize_image after generation.

Example: "generate_social_media content='summer sale announcement' platform='instagram-post'"

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": {
      "content": "<content>",
      "platform": "<platform>",
      "outputFormat": "<outputFormat>"
    },
    "name": "generate_social_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
contentYes
platformYes
contentTypeNo
outputFormatYespng
textPositionNo
outputFilenameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful behavior beyond the name — platform-specific aspect ratios are applied automatically and text-safe zones are produced for overlay design — but it says nothing about generation latency, cost/credits, failure modes, or what is returned (no output schema exists, and the description never says whether the result is a file path, URL, or inline asset).

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 one-line summary followed by clearly labeled when/not-for/chain sections, which is easy to scan. The trailing example largely restates the platform naming already implied, so one line is not fully earning its place.

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

Completeness3/5

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

Routing is complete and unambiguous, which is the hard part for a generation tool with 13 siblings. However, with 7 parameters at 0% schema coverage, no annotations and no output schema, the definition leaves both the platform value vocabulary and the return shape undocumented — gaps an agent will hit on first call.

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 description coverage is 0% across 7 parameters, and the description compensates for only two of them: 'content' and 'platform' appear in the example call. It adds no meaning for style, contentType, textPosition, outputFormat or outputFilename beyond the bare enums, and never explains accepted platform values (e.g. 'instagram-post') even though that string format is the single most error-prone input.

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?

States a specific verb and resource ('Generate platform-optimized social media content') and immediately scopes it with 'correct dimensions and engagement-focused styling'. The NOT-for block names four sibling tools, so an agent can route between generate_social_media, generate_product, generate_logo, generate_image and edit_image without opening any 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?

Gives an explicit 'Use this when' list (platforms, auto aspect ratios, text-safe zones) plus an explicit 'NOT for' list mapping each excluded case to the correct alternative. It also documents a chaining rule: use resize_image afterwards when custom pixel dimensions are needed.

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