Skip to main content
Glama

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

aidelly_create_repurpose_job

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional body override for endpoints with sparse parameter schemas.
queryNoOptional query overrides for endpoints with sparse parameter schemas.
shapeYesOutput 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
mediumYes
brand_idNo
sourceRefNoURL for `url`/`youtube`, storage ref for `pdf`, or row id for `aidelly_draft` / `aidelly_scheduled`. Required unless `sourceType` is `raw_text`.
sourceTextNoRequired when `sourceType` is `raw_text`.
sourceTypeYes
sourceTitleNo
workspace_idNoWorkspace 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.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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."
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

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

Annotations provide basic traits (not read-only, not idempotent, not destructive), but the description adds little beyond stating 'synchronous'. It does not disclose that the operation requires an idempotency key for deduplication, nor does it mention side effects like resource creation or potential errors. There is no contradiction with annotations.

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 a single sentence that efficiently conveys the core action and target. It uses active voice and is front-loaded with the key verb 'run'. No redundant or vague phrases.

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?

Given the absence of an output schema, the description should explain what the tool returns, but it does not. It also omits mention of prerequisites (e.g., workspace_id requirement for creating content) and potential errors. However, it adequately describes the main workflow for a moderate-complexity tool.

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?

With schema description coverage at 55%, the description adds no additional meaning to any parameter. It does not explain the purpose of idempotency_key, workspace_id, or sourceRef beyond what the schema already provides. The schema's shape enum list is detailed, but the description fails to compensate for the lower coverage.

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?

The description clearly states the tool's purpose: running a synchronous repurpose job that extracts, distills, and generates output for one (medium, shape) target. It specifies the action, resource, and scope, distinguishing it from sibling tools like get_repurpose_job and list_repurpose_jobs.

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

Usage Guidelines3/5

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

The description implies the tool is for creating a single repurpose job, but it does not explicitly state when to use it versus alternatives, such as when to retrieve results or list jobs. There is no guidance on prerequisites like required workspace permissions.

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

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