jev-marketing
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | No | API key for the default TypeSafe direct provider when making live Jev calls. | |
| OPENROUTER_API_KEY | No | API key for the OpenRouter provider when making live Jev calls. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ad_tagsC | Imported records only, not a complete ad library. Tags are judgments; days observed are not profitability. Default demo mode uses synthetic heuristic decisions, never Jev. |
| survivalA | Descriptive 60-day longevity in this supplied cohort only. Selection/survivor bias can dominate. Not calibrated survival odds or profitability. Default demo mode uses synthetic heuristic decisions, never Jev. |
| briefsC | Rubric scores are judgments, not predictions of ad survival, performance, or conversion lift. Default demo mode uses synthetic heuristic decisions, never Jev. |
| search_termsC | Negative keyword candidates require human review. No keyword match types inferred and no ad accounts changed. Default demo mode uses synthetic heuristic decisions, never Jev. |
| fatigueB | Heuristic alert on comparable supplied windows, not causal proof. Audience, placement, spend and seasonality can confound it. Default demo mode uses synthetic heuristic decisions, never Jev. |
| landing_matchC | Supplied text only. No page fetching or visual, legal, tracking, accessibility, or conversion audit. Default demo mode uses synthetic heuristic decisions, never Jev. |
| leadsB | Business facts versus the supplied ICP only. No enrichment, protected-trait scoring, or automatic rejection. Default demo mode uses synthetic heuristic decisions, never Jev. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a clearly distinct marketing analytics domain: ad tags, cohort survival, creative briefs, search terms, fatigue, landing page match, and lead qualification. No two tools overlap in purpose or output, and the descriptions reinforce their unique boundaries.
All tool names are lowercase nouns, with underscores used only for multi-word names (ad_tags, search_terms, landing_match). They are consistent in style, though they do not follow a verb_noun action pattern, making the naming slightly less predictable for an agent.
Seven tools is well within the ideal 3-15 range and directly matches the apparent scope of a marketing assessment suite. Each tool earns its place and covers a different facet without bloat.
The set covers the main aspects one would expect from a marketing audit/analysis server: ad tagging, longevity, creative quality, search term negatives, fatigue, landing page alignment, and lead fit. Minor gaps exist, such as no tool for budgeting, audience analysis, or reporting/export, but these do not severely hinder the core diagnostic purpose.