Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Generate Caption

generate_caption

Generate platform-aware social media captions from a prompt and return text only for review; nothing is saved or posted, so pass the result to a post-creation tool.

Instructions

Write a new social media caption from a prompt with AdaptlyPost AI. Returns { caption }, text only; nothing is saved or posted, so pass the caption to create_post, update_post or bulk_schedule_posts yourself. Pass platform and generation targets that platform's character limit; check the returned text before posting. Needs the ai.generate permission, which Admin, Editor and Contributor hold and Viewer does not (403 permission_denied). Each call spends 2 of the member's AI credits (the member who signed in or created the key), refunded if generation fails, unless the member has their own AI provider key connected in AdaptlyPost. With no credits left the call fails: explain that generation is unavailable with the current credit balance and do not retry automatically. To rework a caption you already have, use refine_caption instead.

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

Input Schema

NameRequiredDescriptionDefault
promptYesWhat the caption should say or be about, including tone, audience, hashtags or a call to action
platformNoPlatform the caption is for; generation targets that platform's character limit; check the returned text before posting. Omit for a general caption
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with caption: the generated text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the required permission (ai.generate) with the exact role matrix and 403 permission_denied error, the 2-credit cost per call, the refund-on-failure rule, the BYO-key exception, and the failure mode at zero credits. The "nothing is saved or posted" note is consistent with readOnlyHint=false and idempotentHint=false, since the mutation is credit spend rather than content creation.

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 and the text-only return contract are front-loaded, and every sentence carries operational weight (credits, permissions, failure handling, alternative tool). Minor redundancy exists where the platform character-limit guidance duplicates the input schema description, but nothing is 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?

Despite a simple three-parameter schema, the description covers what an agent actually needs to call this safely: cost, permission, failure handling, non-persistence, and the follow-up call. An output schema exists, so the description only needs the lightweight "{ caption }" confirmation, which it provides.

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 the schema already documents prompt, platform, and workspaceId thoroughly, including the platform enum and character-limit behavior. The description repeats the platform character-limit guidance rather than adding new semantics, so it lands at the baseline for a fully documented schema.

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?

Opens with a specific verb and resource ("Write a new social media caption from a prompt with AdaptlyPost AI") and explicitly returns "{ caption }, text only; nothing is saved or posted." It also names the sibling that handles the adjacent job (refine_caption for reworking existing text), so an agent can discriminate it from both generation and posting tools.

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 when-to-use (new caption from a prompt) and when-not-to-use ("To rework a caption you already have, use refine_caption instead"), plus the downstream actions to take with the result (create_post, update_post, bulk_schedule_posts). It even prescribes behavior on credit exhaustion: explain unavailability and do not retry automatically.

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

Deploy Server

Other Tools