Skip to main content
Glama
deenesjakoruzh
CaBsCrypto

campaign-creator-provider

by CaBsCrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Campaign Creator Provider

독립적이고 로컬 우선(local-first) TypeScript 프로바이더로, URL과 목표(objective)로부터 이중 언어 캠페인 전략, 채널 카피, 게시 캘린더를 만듭니다. 타입이 지정된 라이브러리 API, MCP 형태의 JSON-RPC stdio 계약, 그리고 Vercel에 배포된 소형 HTTP API를 제공합니다.

이 프로바이더는 결정적(deterministic) 픽스처 콘텐츠를 생성합니다. 제출된 URL을 가져오지 않으며, 외부 서비스를 호출하지 않고, 콘텐츠를 게시하거나 입력값을 저장하지 않으며, Stellar Bazaar와 상호작용하지 않습니다.

기능

  • 스페인어(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

integer

7

1–30

channels

array

모든 채널

x, linkedin, instagram, email 중 하나 이상

audience

string

지역화된 픽스처

비어 있지 않음

성공적인 요청은 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에 한 줄에 하나의 JSON-RPC 2.0 객체를 입력받고 stdout에 한 줄에 하나의 응답을 씁니다. 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은 세 개의 서버리스 엔트리포인트를 명시적으로 빌드합니다. 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