Senja MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_testimonialsC | Read one native page with exact current search, tag, approval, language and date/rating filters. |
| get_testimonialB | Read one exact testimonial, including native video metadata and public/dashboard links. |
| create_testimonialC | Create one text/video testimonial from an authorized existing customer statement. Explicit approval is required. |
| update_testimonialA | Change only native approval status and tag additions/removals. Text, rating and customer edits remain dashboard-only. |
| delete_testimonialA | Permanently delete exactly the requested testimonial. Irreversible; confirmation required. |
| list_linksB | Read native form, widget, Wall of Love, quick-link, case-study and sizzle-reel groups with their IDs and URLs. |
| send_invitesB | Send email invites using a selected form and its existing follow-up sequence. Local cap100 recipients, not a documented provider quota. |
| list_accountsB | Local profile labels/default/auth method only. No keys, token paths, provider identity or network request. |
| get_operation_schemaA | Local reviewed method/path/query/body schema and provenance for one native tool. No credentials or provider request. |
| preview_testimonial_batchB | Local validation and SHA-256 of exact ordered testimonial/import/invite work, selected profile label and reviewed schema. No provider reads, key load, identity check, price or rollback guarantee. |
| submit_testimonial_batchA | Confirmed one-to-twenty ordered testimonial/import/invite tasks. Prevalidate all and verify exact hash before first request. Stop on first failure with known results/failed index/unattempted indices; no retries, rollback or implicit continuation. |
| export_testimonialsA | Confirmed paginated GET export to an exclusive new0600 JSON file. Stop on short native page or local caps. Never downloads media, follows URLs, overwrites files, retries or implies an atomic complete backup. |
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 12 tools
Most tools target clearly distinct resources or actions: single testimonial CRUD, listing, export, batch preview/submit, links, accounts, and schema introspection. Some overlap exists because submit_testimonial_batch can include testimonial/import/invite work that overlaps with create_testimonial and send_invites, but descriptions distinguish single versus batch workflows.
All tools use snake_case and follow a predictable verb_noun pattern, including compound batch tools like submit_testimonial_batch and preview_testimonial_batch. Naming is consistent and readable throughout.
The 12 tools are well scoped for a testimonial management surface covering CRUD, invites, export, batching, links, accounts, and schema inspection. No tool appears redundant, and the count fits comfortably within a reasonable MCP server size.
Core testimonial lifecycle operations are present: create, list, get, limited update, delete, export, invites, and batch processing. Notable gaps remain: update_testimonial only changes approval status and tags, and there is no create/update/delete for forms, widgets, or links, though the core testimonial workflows are covered.