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 | {} |
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_testimonialB | 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
The CRUD tools for testimonials are clearly distinct, and the batch, export, links, and account tools have different scopes. There is minor potential confusion between list_testimonials and export_testimonials, but the descriptions clarify their distinct purposes.
All tools follow a consistent snake_case verb_noun pattern, including multi-word names like get_operation_schema and preview_testimonial_batch. No mixed conventions or vague verbs.
With 12 tools, the set is well-scoped for testimonial management, covering core CRUD, batch operations, export, and auxiliary functions without excessive clutter.
The surface covers testimonial CRUD (update is intentionally limited), batch preview/submit, export, links, invites, and account listing. Some gaps exist, such as no direct text/rating edits or invite sequence management, but core workflows are well supported.