Skip to main content
Glama
Sign In

Creadal

by com.creadal
OverviewDiscussionsAdmin

Design a social post or ad

create_social_design

Make a social media post or ad in the member's Creadal account from a professionally designed ready template: headline, supporting line, offer, call-to-action button, brand and website filled in, the member's own picture (a product photo or an app or website screenshot, given as a public https link) placed in the template's picture frame, and their logo (a public https link, PNG with transparency is best) in place of the brand name. Returns a preview picture and a link to open and edit it in the Creadal editor. Use this, not generate_presentation, for posts, stories and ads. Optionally makes the picture with AI instead (uses one AI image from the member's plan).

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": {
      "headline": "<headline>"
    },
    "name": "create_social_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNoThe button text, e.g. 'Start free'.
offerNoAn offer, price or detail line, e.g. 'Free for 14 days'.
formatNosquare 1080x1080 (default), portrait 1080x1350, story 1080x1920, landscape 1200x628 (link ads), wide 1280x720.
kickerNoA small line above the headline, e.g. 'New' or the product category.
websiteNoWebsite or social handle.
headlineYesThe main line, short (2 to 6 words reads best).
languageNoLanguage of the template texts left as they are: en (default) or tr.
logo_urlNoOptional: a public https link to the logo (PNG with transparency is best).
image_fitNocover fills the frame (photos, default); contain shows the whole picture (screenshots).
image_urlNoOptional: a public https link to the picture to show (product photo or screenshot).
brand_nameNoThe brand, shown where the template has its brand name (and under the logo when there is no logo).
descriptionNoWhat is advertised and for whom, in a sentence: helps pick the best template.
subheadlineNoA supporting line under the headline.
template_idNoOptional: a template id to use instead of the best match.
image_promptNoOptional: describe a picture to make with AI when there is no image_url (uses one AI image from the plan).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare the write/open-world profile, and the description adds context annotations cannot: the return value ('a preview picture and a link to open and edit it in the Creadal editor') and a resource cost ('uses one AI image from the member's plan'). It does not mention any failure modes (e.g., unreachable or non-public image URLs), which is the only notable gap.

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-loads the core action and the full list of fields, then tacks on returns, routing and the AI option. The single long enumerative sentence is dense but each clause carries real information; a tighter split into 2-3 sentences would read better without losing content.

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 correctly covers the return value, and with 15 parameters it still explains the overall composition and the AI-image fallback. Nothing an agent needs to call it is missing, though error conditions and whether the design is saved versus preview-only could be clearer.

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 100%, so every parameter including the two enums (format, image_fit) is already documented with examples and pixel dimensions. The description's parameter-level content (public https image link, PNG with transparency logo) largely restates the schema, so it adds little beyond the baseline.

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 ('Make a social media post or ad ... from a professionally designed ready template') and enumerates exactly what the template is filled with. It also names the sibling it is not ('not generate_presentation'), 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?

Gives explicit routing guidance: 'Use this, not generate_presentation, for posts, stories and ads.' It also explains the alternative path for imagery (image_prompt when there is no image_url) and its cost, so the agent knows both when to pick this tool and which mode to use.

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

All Creadal toolsInspect
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