Skip to main content
Glama
deenesjakoruzh
CaBsCrypto

campaign-creator-provider

by CaBsCrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Campaign Creator Provider

独立したローカルファーストのTypeScriptプロバイダーで、URLと目的からバイリンガルのキャンペーン戦略、チャネルコピー、公開カレンダーを作成します。型付きライブラリAPI、MCP形式のJSON-RPC stdioコントラクト、およびVercelにデプロイされた小規模なHTTP APIを公開します。

プロバイダーは決定的なフィクスチャコンテンツを生成します。送信されたURLを取得したり、外部サービスを呼び出したり、コンテンツを公開したり、入力を永続化したり、Stellar Bazaarとやり取りしたりすることはありません。

Features

  • スペイン語（es、デフォルト）と英語（en）の出力

  • 戦略、チャネルコピー、および設定可能な1–30日のカレンダー

  • X、LinkedIn、Instagram、メールのチャネル

  • JSON Schemaツール定義と構造化された検証エラー

  • 単一のジェネレーター上でのHTTP、TypeScript、MCP形式のstdioエントリポイント

  • ネットワーク不要の決定的生成

  • Apache-2.0ライセンス

Related MCP server: moltline-mcp

HTTP API

ディスカバリ

curl https://campaign-creator-provider.vercel.app/

ヘルスチェック

curl https://campaign-creator-provider.vercel.app/health

キャンペーンを作成

curl -X POST https://campaign-creator-provider.vercel.app/api/campaign \
  -H "content-type: application/json" \
  -d '{"url":"https://example.com/product","objective":"Increase qualified sign-ups","locale":"en","days":7,"channels":["linkedin","email"]}'

必須フィールドはurl（絶対HTTP/HTTPS URL）とobjectiveです。オプションフィールドは次のとおりです。

フィールド

型

デフォルト

制約

locale

"es" | "en"

"es"

対応する出力言語

days

整数

7

1–30

channels

配列

すべてのチャネル

x、linkedin、instagram、emailのいずれか1つ以上

audience

文字列

ローカライズされたフィクスチャ

空でない

成功したリクエストは、HTTP 200でキャンペーンオブジェクトを直接返します。無効な入力はHTTP 400と、検証問題を含む安定したJSONエラーオブジェクトを返します。ルートはCORSをサポートし、レスポンスをキャッシュしません。

TypeScript API

import { createCampaign } from "@stellar-bazaar/campaign-creator-provider";

const campaign = createCampaign({
  url: "https://example.com/product",
  objective: "Increase qualified sign-ups",
  locale: "en",
  days: 7,
  channels: ["linkedin", "email"]
});

返されるCampaignPlanには、strategy、copy、calendar、ソースコンテキスト、およびフィクスチャメタデータが含まれます。

MCP形式のstdioコントラクト

ビルドされたサーバーは、stdinで1行につき1つのJSON-RPC 2.0オブジェクトを受け入れ、stdoutで1行につき1つのレスポンスを書き出します。initialize、tools/list、tools/call、notifications/initializedを実装しています。

echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"create_campaign","arguments":{"url":"https://example.com","objective":"Aumentar registros","locale":"es"}}}' | node dist/server.js

create_campaignの結果には、MCPテキストコンテンツと、structuredContent内の同じキャンペーンが含まれます。無効な引数は、構造化された検証問題とともにisError: trueを返します。ディスカバリメタデータについては、service-card.jsonを参照してください。

ローカル開発

Node.js 22.6以降が必要です。

npm ci
npm run test:all

test:allは、ライブラリとVercelハンドラーの両方を型チェックし、テストスイートを実行し、配布可能なパッケージをビルドします。

別のVercelプロジェクトをデプロイする

Vercel CLIで認証済みの場合：

vercel link --project campaign-creator-provider
vercel deploy --prod

追跡されているvercel.jsonは、3つのサーバーレスエントリポイントを明示的にビルドします。Vercelのローカル.vercel/リンクメタデータは無視され、決してコミットしてはなりません。

フィクスチャの境界

URLはキャンペーンコンテキストとしてのみ使用され、リクエストされることはありません。同一の正規化された入力は、campaignIdとgeneratedAtを含め、同一の出力を生成します。コピーは一般的なフィクスチャ素材であり、参照されたサイトが分析されたという主張ではありません。

このリポジトリとデプロイメントは独立しています。Stellar Bazaarに登録したり、変更したりすることはありません。

ライセンス

Apache License 2.0。LICENSEを参照してください。

Available Tools

1 tool
create_campaignB

Create a deterministic Spanish or English campaign plan, copy set, and calendar from a URL and objective.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
daysNo
localeNoes
audienceNo
channelsNo
objectiveYes

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions 'deterministic' but does not clarify whether the tool persists data, requires authentication, or has other side effects. It lacks disclosure of mutation, idempotency, or return behavior, which is a significant gap for a creation tool.

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, well-formed sentence with no filler. It front-loads the primary action and key attributes (deterministic, Spanish/English) efficiently, making it easy to parse and remember.

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?

Given the complexity of 6 parameters, no output schema, and no annotations, the description is inadequate. It does not explain the effect of optional parameters, expected outputs, or usage context, making it incomplete for reliable tool selection and invocation.

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?

Schema description coverage is 0%, and the description only implicitly explains the two required parameters (URL and objective). The optional parameters (days, locale, audience, channels) are not described at all, leaving agents without guidance on their meaning or selection. This is insufficient for a 6-parameter tool.

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 states a specific verb (Create) on a clear resource (campaign plan, copy set, and calendar) with defined inputs (URL and objective). It also mentions determinism and language options, making the tool's function unambiguous even without sibling tools to differentiate from.

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?

It implies usage when you have a URL and an objective, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention optional parameters or exclusions. With no sibling tools listed, a clearer context would be beneficial.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedcreate_campaign
Deploy Server
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

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool is exposed, so there is no possibility of selecting between overlapping operations. The purpose is immediately clear and unambiguous.

Naming Consistency5/5

The sole tool uses a clean snake_case verb_noun name, create_campaign, which follows common MCP naming conventions. With a single tool, consistency is trivially maintained.

Tool Count3/5

A single tool is on the thin side for a general-purpose server, but create_campaign is a substantial atomic operation that directly covers the provider's stated purpose. It is borderline rather than excessive or trivial.

Completeness4/5

The tool fully delivers the advertised campaign plan, copy set, and calendar generation in one deterministic action. Broader lifecycle operations like list, update, or delete are absent, but they appear outside the scope of a campaign creator.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • publiar-mcp

    TokDar2410621
    A
    license
    B
    quality
    C
    maintenance
    MCP server for Publiar that writes LinkedIn lead magnets without fabricating facts, renders matching visuals, publishes to LinkedIn, and tracks engagement, with 19 tools over stdio.
    19
    MIT

  • moltline-mcp

    GarphenGate
    A
    license
    A
    quality
    A
    maintenance
    Zero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.
    10
    MIT

  • research_with_sources

    CaBsCrypto
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables generating deterministic, cited research findings from caller-supplied source metadata and excerpts via a local-fixture MCP tool, supporting English and Spanish.
    Apache 2.0