Add a new subscriber to a status page, specifying delivery channel, destination, scoped components, and optional opt-in confirmation for email.
Add a subscriber to a status page (admin).
Optional: email (legacy EMAIL), channel, destination, componentIds, requireConfirmation.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| page_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.7.0Input schema / properties / body / properties / channelAdded value: +{
+ "anyOf": [
+ {
+ "enum": [
+ "EMAIL",
+ "SMS",
+ "WEBHOOK"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Delivery channel (default: EMAIL)"
+}Input schema / properties / body / properties / componentIdsAdded value: +{
+ "anyOf": [
+ {
+ "items": {
+ "format": "uuid",
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Component IDs to scope; omit to leave existing scope; empty list widens to the whole page"
+}Input schema / properties / body / properties / destinationAdded value: +{
+ "anyOf": [
+ {
+ "maxLength": 2048,
+ "minLength": 0,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Channel destination (email, phone, or webhook URL)"
+}Input schema / properties / body / properties / email / anyOfAdded value: +[
+ {
+ "format": "email",
+ "maxLength": 320,
+ "minLength": 0,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / body / properties / email / defaultAdded value: +nullInput schema / properties / body / properties / email / descriptionPrevious value: -"Email address to add as a confirmed subscriber"New value: +"Email for EMAIL channel; legacy clients may send only this"Input schema / properties / body / properties / email / formatRemoved value: -"email"Input schema / properties / body / properties / email / minLengthRemoved value: -1Input schema / properties / body / properties / email / typeRemoved value: -"string"Input schema / properties / body / properties / requireConfirmationAdded value: +{
+ "anyOf": [
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "When true (EMAIL only), create unconfirmed and send opt-in; null/false confirms immediately"
+}Input schema / properties / body / requiredRemoved value: -[
- "email"
-]v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full behavioral burden. It only notes that the action is admin-scoped and lists optional fields; it does not disclose side effects such as sending opt-in confirmation emails, duplicate subscription behavior, or immediate confirmation semantics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two compact lines with the purpose front-loaded and no filler. The optional-field list is directly useful without repeating schema details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema and rich nested input schema cover field details, so the description does not need to explain return values or every parameter. However, with no annotations and minimal behavioral disclosure, an agent still lacks important context about side effects and confirmation behavior, leaving a clear gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds the useful 'legacy EMAIL' marker and flags the fields as optional, but the input schema already provides detailed descriptions for each nested property. It does not substantially compensate for the 0% top-level schema coverage, but it remains at a baseline level because the schema carries most parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Add') and resource ('subscriber to a status page'), and adds the '(admin)' scope. This clearly distinguishes it from sibling operations like list_status_page_subscribers and remove_status_page_subscriber.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives, and no exclusions or prerequisites. The name and verb imply creation, but there is no explicit when/when-not context to help an agent choose it reliably.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/devhelmhq/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server