Skip to main content
Glama

Repurpose Content for Another Platform

repurpose_content
Read-only

Adapt content from one social platform to another by automatically adjusting character limits, hashtag styles, and formatting requirements.

Instructions

Take content from one platform and adapt it for another. Handles character limits (X: 280, LinkedIn: 3000, Instagram: 2200), hashtag styles, and format differences automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
original_textYesThe original post content
source_platformYesOriginal platform
target_platformYesTarget platform

Implementation Reference

  • The core logic for repurposing content is implemented in the repurposeContent function.
    function repurposeContent(text: string, sourcePlatform: PlatformType, targetPlatform: PlatformType): string {
      const targetLimits = PLATFORM_LIMITS[targetPlatform];
      const hashtags = selectHashtags(targetPlatform, targetPlatform === "instagram" ? 5 : 3);
    
      // Strip existing hashtags
      let cleaned = text.replace(/#\w+/g, "").trim();
      // Remove trailing dots (Instagram spacer)
      cleaned = cleaned.replace(/\n\.\n\.\n\.\n?/g, "\n").trim();
    
      let result: string;
    
      if (targetPlatform === "x") {
        // X/Twitter: ultra-concis, prendre le hook + CTA
        const lines = cleaned.split("\n").filter((l) => l.trim().length > 0);
        const hook = lines[0] || "";
        // Find a line that looks like a CTA
        const ctaLine = lines.find((l) =>
          l.includes("?") || l.toLowerCase().includes("stresszeroentrepreneur") || l.toLowerCase().includes("rdv"),
        );
    
        result = hook;
  • src/index.ts:798-813 (registration)
    The 'repurpose_content' tool is registered with the MCP server using server.registerTool, defining the input schema and the handler that calls repurposeContent.
    server.registerTool(
      "repurpose_content",
      {
        title: "Repurpose Content for Another Platform",
        description:
          "Take content from one platform and adapt it for another. " +
          "Handles character limits (X: 280, LinkedIn: 3000, Instagram: 2200), " +
          "hashtag styles, and format differences automatically.",
        inputSchema: {
          original_text: z.string().describe("The original post content"),
          source_platform: z.enum(["linkedin", "instagram", "x", "tiktok"]).describe("Original platform"),
          target_platform: z.enum(["linkedin", "instagram", "x", "tiktok"]).describe("Target platform"),
        },
        annotations: { readOnlyHint: true, openWorldHint: false, destructiveHint: false },
      },
      async ({ original_text, source_platform, target_platform }) => {
Behavior4/5

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

Beyond annotations (readOnlyHint), the description adds valuable behavioral specifics: exact character limits for platforms (X: 280, etc.), automatic hashtag style conversion, and format handling. However, it omits what happens when content exceeds limits (truncation vs. error) and the return format.

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?

Two well-structured sentences with zero waste: first sentence establishes the core purpose, second details specific capabilities. Information is front-loaded and every clause earns its place.

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 lack of an output schema, the description should indicate what the tool returns (the adapted text). While it comprehensively covers input transformation logic, the omission of return value description leaves a gap for a tool with no output schema documentation.

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?

With 100% schema coverage, the baseline is 3. The description elevates this by providing the semantic context for the platform enums—specifically the character constraints and formatting rules that apply to each—adding meaning beyond the schema's basic 'Original platform' labels.

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 core action ('Take content... and adapt it') and resource, distinguishing it from sibling creation tools like 'draft_post' or 'generate_thread'. The specific mention of platform constraints (X, LinkedIn, Instagram) further clarifies the scope.

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?

While the description implies usage by defining the transformation workflow, it lacks explicit guidance on when to choose this over 'draft_post' (create new) versus adapting existing content. No alternatives or exclusion criteria are named.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gomessoaresemmanuel-cpu/content-distribution-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server