Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Refine Caption

refine_caption

Rewrite an existing caption to follow an instruction like shorter, more playful or add a question. Returns the revised text only, nothing saved or posted.

Instructions

Rewrite an existing caption following an instruction, such as "shorter", "more playful" or "add a question at the end". Returns { caption }, the rewritten text; nothing is saved or posted. Send partialText to continue from a partly written caption. Pass platform to target 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. Costs the same as generate_caption.

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>",
      "originalText": "<originalText>"
    },
    "name": "refine_caption"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesHow the caption should change
platformNoPlatform the caption is for; generation targets that platform's character limit; check the returned text before posting
partialTextNoA partly written caption to continue from
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
originalTextYesThe caption to rewrite

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with caption: the rewritten text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that nothing is persisted, the required ai.generate permission and which roles hold it, the exact 403 error code, credit cost (2 credits, same as generate_caption), the refund-on-failure rule, the own-provider-key exception, and explicit no-retry guidance when credits run out. This is unusually rich behavioral context that the structured annotations do not supply.

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 description is front-loaded with the core action and return shape, then layers on continuation, platform targeting, permissions, and credit economics. Every sentence carries distinct information; there is no filler or repetition.

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 an output schema ({caption}) and full schema coverage, the description needn't restate parameter formats, and instead covers what the schema cannot: permissions, cost, failure modes, and the no-retry rule. Nothing an agent needs to call this safely is missing.

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 schema already documents all five parameters, which sets the baseline at 3. The description adds value with example instruction values for prompt ('shorter', 'more playful') and explains the continuation semantics of partialText and the character-limit targeting of platform in operational terms.

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 resource: 'Rewrite an existing caption following an instruction.' It also rules out write side effects ('nothing is saved or posted') and names the related tool generate_caption when discussing cost. It stops short of explicitly stating how this differs in purpose from generate_caption, so sibling differentiation is implied rather than spelled out.

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?

The description gives concrete usage conditions: use partialText to continue a partly written caption, pass platform to target a character limit, and check the returned text before posting. It also gives explicit failure handling (403 permission_denied, out-of-credits: explain and do not retry). It never explicitly says when to choose generate_caption over this tool, leaving that inference to the agent.

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