aidelly

Create Repurpose Job

aidelly_create_repurpose_job

Run a synchronous repurpose job: extract source content, distill, and generate output for one (medium, shape) target.

Input Schema

Name	Required	Description
`body`	No	Optional body override for endpoints with sparse parameter schemas.
`query`	No	Optional query overrides for endpoints with sparse parameter schemas.
`shape`	Yes	Output shape ID — must be one of the valid shapes for the chosen `medium` (an invalid pair returns 400 listing the valid shapes): twitter: single_tweet \| thread_3 \| thread_5 \| thread_10 \| thread_script \| long_form_article instagram: single_post \| carousel_7 \| reel_script linkedin: short_post \| long_form_1500w \| article \| carousel_7 tiktok: caption \| video_script \| shorts_script youtube: description \| video_script \| shorts_script pinterest: pin_description threads: single_post \| thread_5 facebook: short_post substack_newsletter: essay_800w \| essay_2000w substack_note: note reddit_thread: post_title_and_body newsletter: issue_600w email: subject_and_body podcast: episode_outline \| show_notes lead_resource: lead_magnet_outline \| one_pager case_study: case_study_writeup bluesky: single_post \| thread_3 mastodon: single_post google_business: update_post
`medium`	Yes
`brand_id`	No
`sourceRef`	No	URL for `url`/`youtube`, storage ref for `pdf`, or row id for `aidelly_draft` / `aidelly_scheduled`. Required unless `sourceType` is `raw_text`.
`sourceText`	No	Required when `sourceType` is `raw_text`.
`sourceType`	Yes
`sourceTitle`	No
`workspace_id`	No	Workspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content.
`idempotency_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026
- addedInput schema / properties / idempotency_key / example
```
Added value: +"order-123:create-post:v1"
```
- addedInput schema / properties / idempotency_key / maxLength
```
Added value: +255
```
- addedInput schema / properties / idempotency_key / minLength
```
Added value: +1
```
- addedInput schema / properties / idempotency_key / pattern
```
Added value: +"^[\\x21-\\x7E]{1,255}$"
```

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / workspace_id / description

Previous value: -"Workspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content."New value: +"Workspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content."

Changed4 schema fields changedJul 22, 2026

changedInput schema / properties / medium / enum

Previous value: -[
-  "twitter",
-  "instagram",
-  "linkedin",
-  "tiktok",
-  "youtube",
-  "pinterest",
-  "threads",
-  "facebook",
-  "substack_newsletter",
-  "substack_note",
-  "reddit_thread",
-  "newsletter",
-  "email",
-  "podcast",
-  "lead_resource",
-  "case_study"
-]New value: +[
+  "twitter",
+  "instagram",
+  "linkedin",
+  "tiktok",
+  "youtube",
+  "pinterest",
+  "threads",
+  "facebook",
+  "substack_newsletter",
+  "substack_note",
+  "reddit_thread",
+  "newsletter",
+  "email",
+  "podcast",
+  "lead_resource",
+  "case_study",
+  "bluesky",
+  "mastodon",
+  "google_business"
+]

addedInput schema / properties / shape / description

Added value: +"Output shape ID — must be one of the valid shapes for the chosen\n`medium` (an invalid pair returns 400 listing the valid shapes):\ntwitter: single_tweet | thread_3 | thread_5 | thread_10 | thread_script | long_form_article\ninstagram: single_post | carousel_7 | reel_script\nlinkedin: short_post | long_form_1500w | article | carousel_7\ntiktok: caption | video_script | shorts_script\nyoutube: description | video_script | shorts_script\npinterest: pin_description\nthreads: single_post | thread_5\nfacebook: short_post\nsubstack_newsletter: essay_800w | essay_2000w\nsubstack_note: note\nreddit_thread: post_title_and_body\nnewsletter: issue_600w\nemail: subject_and_body\npodcast: episode_outline | show_notes\nlead_resource: lead_magnet_outline | one_pager\ncase_study: case_study_writeup\nbluesky: single_post | thread_3\nmastodon: single_post\ngoogle_business: update_post\n"

changedInput schema / properties / shape / example

Previous value: -"thread"New value: +"carousel_7"

addedInput schema / properties / workspace_id / description

Added value: +"Workspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content."

First observedJul 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description usefully adds the 'synchronous' execution trait, which is real behavioral context beyond the annotations, but omits credit cost, failure/partial-output behavior, and the relationship between the required idempotency_key and idempotentHint=false.

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?

A single front-loaded sentence with no filler; the core action and its pipeline are stated immediately. Nothing is redundant or padded.

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

Completeness2/5

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

For an 11-parameter tool with nested objects and no output schema, one sentence is not enough. It does not describe what a synchronous job returns, how long it blocks, credit implications, or error semantics for invalid (medium, shape) pairs, leaving the agent under-informed despite the reasonably detailed schema.

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 55%, with medium/shape/sourceRef/sourceText/workspace_id well documented in the schema itself. The description only restates the (medium, shape) pairing and adds the single-target constraint; it says nothing about sourceType variants, the generic body/query overrides, or sourceTitle, so it does not compensate for the uncovered parameters.

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 gives a specific verb and resource ('Run a synchronous repurpose job') and outlines the pipeline stages (extract, distill, generate), which is more informative than the bare title. It implicitly distinguishes itself from the read-only siblings aidelly_get_repurpose_job / aidelly_list_repurpose_jobs by describing job creation/execution, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative routing. The phrase 'for one (medium, shape) target' hints that multiple targets require multiple calls, but this is left to inference, and no prerequisites (e.g. workspace_id required for content creation) are stated.

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

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

Create Repurpose Job

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources