Sitecore Send
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smtp_emailC | Send an email using SMTP |
| get_listsB | Get all available mailing lists |
| get_single_listB | Get a single mailing list details: total count, status, etc |
| get_subscribersB | Get subscribers of a mailing list |
| get_subscriber_by_emailC | Get subscriber by email |
| add_subscriberB | Add subscriber to a mailing list |
| unsubscribe_subscriberB | Unsubscribe subscriber from a mailing list |
| send_transactional_emailB | Send an email using transactional email service |
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 8 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools like add_subscriber, get_subscribers, and unsubscribe_subscriber handle different subscriber operations, while send_smtp_email and send_transactional_email target different email sending methods. The descriptions clearly differentiate each tool's function.
All tool names follow a consistent verb_noun pattern using snake_case throughout. Examples include add_subscriber, get_lists, send_smtp_email, and unsubscribe_subscriber. There are no deviations in naming conventions, making the set predictable and readable.
With 8 tools, the count is well-scoped for a Sitecore Send server focused on mailing list and email operations. Each tool earns its place by covering distinct aspects like subscriber management, list retrieval, and email sending, without being too sparse or overwhelming.
The tool surface provides strong coverage for the mailing list and email domain, including CRUD-like operations for subscribers (add, get, unsubscribe) and lists (get), plus email sending. A minor gap is the lack of tools for updating subscriber details or managing list properties, but core workflows are well-covered.