Skip to main content
Glama
Sign In
@fopost/mcp

@fopost/mcp

Official
by fopost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

repurpose_url

Fetch a blog or article URL and generate optimized social media posts for multiple platforms in one call. Write once, get up to 16 platform-specific versions.

Instructions

Fetch a blog/article URL and generate one optimized post per requested platform in a single call. The flagship "Developer Content Stack" feature — write once, get 16 versions. Costs 6 AI credits per call regardless of platform count.

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": {
      "url": "<url>",
      "platforms": "<platforms>"
    },
    "name": "repurpose_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
platformsYes
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It does disclose a meaningful behavioral trait: the call is batched, generates one post per platform, and costs 6 AI credits regardless of platform count. It omits response format, error behavior, and auth or rate-limit caveats, but the credit-cost disclosure is valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences carry the core action, scope, and cost without rambling. The flagship/"write once, get 16 versions" phrase is slightly promotional, but it is short and reinforces the batch behavior.

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?

The definition is enough to know what the tool does and roughly how to call it, but with no output schema it should describe the response shape, and it never explains workspace_id or when to prefer this over rewrite_for_platforms. These are clear gaps given the tool's moderate complexity.

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 0%, so the description must compensate. It explains url (the page to fetch) and platforms (the list for which optimized posts are generated), but says nothing about workspace_id. The enum on platforms also helps, but the required workspace context is unidentified.

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 names a specific action (fetch a blog/article URL) and a concrete outcome (generate one optimized post per requested platform in a single call). The URL-to-multiple-platforms behavior separates it from sibling tools like rewrite_for_platforms, even without naming them.

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 use case is implied: use this when you have a blog/article URL and want platform-specific posts in one call. However, it never explicitly contrasts the tool with rewrite_for_platforms or other siblings, nor gives when-not-to-use guidance.

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