Skip to main content
Glama
deenesjakoruzh
CaBsCrypto

campaign-creator-provider

by CaBsCrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Campaign Creator Provider

Unabhängiger, lokaler TypeScript-Provider, der aus einer URL und einem Ziel eine zweisprachige Kampagnenstrategie, Kanaltexte und einen Veröffentlichungskalender erstellt. Er stellt eine typisierte Bibliotheks-API, einen MCP-förmigen JSON-RPC-stdio-Vertrag und eine kleine, auf Vercel bereitgestellte HTTP-API bereit.

Der Provider generiert deterministische Fixture-Inhalte. Er ruft die übermittelte URL nicht ab, ruft keine externen Dienste auf, veröffentlicht keine Inhalte, speichert keine Eingaben und interagiert nicht mit Stellar Bazaar.

Funktionen

  • Spanische (es, Standard) und englische (en) Ausgabe

  • Strategie, Kanaltexte und ein konfigurierbarer Kalender über 1–30 Tage

  • X-, LinkedIn-, Instagram- und E-Mail-Kanäle

  • JSON-Schema-Tooldefinition und strukturierte Validierungsfehler

  • HTTP-, TypeScript- und MCP-förmige stdio-Einstiegspunkte über einen Generator

  • Netzwerkfreie deterministische Generierung

  • Apache-2.0-lizenziert

Related MCP server: moltline-mcp

HTTP-API

Discovery

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

Health

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

Kampagne erstellen

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"]}'

Pflichtfelder sind url (eine absolute HTTP/HTTPS-URL) und objective. Optionale Felder sind:

Feld

Typ

Standard

Einschränkungen

locale

"es" | "en"

"es"

Unterstützte Ausgabesprache

days

integer

7

1–30

channels

array

alle Kanäle

Einer oder mehrere von x, linkedin, instagram, email

audience

string

lokalisierter Fixture

Nicht leer

Erfolgreiche Anfragen geben das Kampagnenobjekt direkt mit HTTP 200 zurück. Ungültige Eingaben geben HTTP 400 und ein stabiles JSON-Fehlerobjekt mit Validierungsproblemen zurück. Routen unterstützen CORS und speichern Antworten nicht zwischen.

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"]
});

Der zurückgegebene CampaignPlan enthält strategy, copy, calendar, Quellkontext und Fixture-Metadaten.

MCP-förmiger stdio-Vertrag

Der erstellte Server akzeptiert ein JSON-RPC-2.0-Objekt pro Zeile auf stdin und schreibt eine Antwort pro Zeile auf stdout. Er implementiert initialize, tools/list, tools/call und 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

Das create_campaign-Ergebnis enthält MCP-Textinhalt und dieselbe Kampagne in structuredContent. Ungültige Argumente geben isError: true mit strukturierten Validierungsproblemen zurück. Siehe service-card.json für Discovery-Metadaten.

Lokale Entwicklung

Node.js 22.6 oder neuer ist erforderlich.

npm ci
npm run test:all

test:all typprüft sowohl die Bibliothek als auch die Vercel-Handler, führt die Testsuite aus und erstellt das verteilbare Paket.

Ein separates Vercel-Projekt bereitstellen

Mit authentifizierter Vercel-CLI:

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

Die nachverfolgte vercel.json erstellt explizit die drei serverlosen Einstiegspunkte. Die lokalen .vercel/-Verknüpfungsmetadaten von Vercel werden ignoriert und dürfen niemals eingecheckt werden.

Fixture-Grenze

Die URL wird nur als Kampagnenkontext verwendet und niemals angefordert. Identische normalisierte Eingaben erzeugen identische Ausgaben, einschließlich campaignId und generatedAt. Kopien sind generisches Fixture-Material, keine Behauptung, dass die referenzierte Website analysiert wurde.

Dieses Repository und die Bereitstellung sind unabhängig. Sie registrieren sich nicht bei Stellar Bazaar und ändern es nicht.

Lizenz

Apache License 2.0. Siehe 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