Skip to main content
Glama
Sign In
Launch Engine

Launch Engine

by ZionHopkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

content_repurpose

Read-only

Converts a single pillar page into 7+ platform-native assets for YouTube, short-form, Reddit, LinkedIn, newsletters, and social media.

Instructions

Single-Pass Content Repurposing — takes one pillar page and generates 7+ platform-native assets (YouTube, short-form, Reddit, LinkedIn, newsletters, social).

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": {
      "market_name": "<market_name>"
    },
    "name": "content_repurpose"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_nameYesThe market/pipeline slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false. Description adds context about generating assets but doesn't clarify if this is a read-only operation or creates persistent data, leaving potential ambiguity.

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?

One sentence, front-loads the core purpose, no fluff.

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?

Given simple schema and annotations, description adequately explains what the tool does and what it produces, though lacks details about output format or side effects.

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 covers the single parameter with description. Tool description adds no further meaning to the parameter beyond what schema provides.

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?

Clearly describes specific action: 'takes one pillar page and generates 7+ platform-native assets'. Distinguishes from siblings like content_engine by specifying the output types.

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?

Implies use for content repurposing but no explicit guidance on when to use vs alternatives or prerequisites.

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