AdvocateMCP

Subscribe to Updates

subscribe_to_updates

DestructiveIdempotent

Start a pending email subscription to updates from a business. Returns a confirmation URL that only the user must click within 7 days; no subscription is active until that confirmation. Idempotent: re-using the same idempotency_key returns the original subscription.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Business slug identifier
`topics`	Yes	Topic tags (e.g., ['deals', 'schedule_changes'])
`agent_id`	No	Optional agent identifier
`contact_email`	Yes	Email to subscribe — confirmed via returned token
`idempotency_key`	Yes	Idempotency key

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	'pending' until the user opens confirmation_url; a replay returns the stored state (e.g. 'confirmed' once they have)
`topics`	Yes	Normalised topic tags: trimmed, lower-cased, de-duplicated
`expires_at`	Yes	Unix seconds when confirmation_url stops working
`acknowledgment`	Yes	Customer-facing sentence to relay, including the confirmation link
`subscription_id`	Yes
`confirmation_url`	Yes	The link the user must open within 7 days to start receiving updates
`idempotent_replay`	No	Present and true when this idempotency_key already had a subscription; the stored token is returned, refreshed only if it had expired
`confirmation_token`	Yes	Capability token for this subscriber only — it is the proof of consent; never pass it to another tool or party

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "acknowledgment": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Customer-facing sentence to relay, including the confirmation link"
+    },
+    "confirmation_token": {
+      "description": "Capability token for this subscriber only — it is the proof of consent; never pass it to another tool or party",
+      "type": "string"
+    },
+    "confirmation_url": {
+      "description": "The link the user must open within 7 days to start receiving updates",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "Unix seconds when confirmation_url stops working",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "idempotent_replay": {
+      "description": "Present and true when this idempotency_key already had a subscription; the stored token is returned, refreshed only if it had expired",
+      "type": "boolean"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "'pending' until the user opens confirmation_url; a replay returns the stored state (e.g. 'confirmed' once they have)"
+    },
+    "subscription_id": {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "topics": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Normalised topic tags: trimmed, lower-cased, de-duplicated"
+    }
+  },
+  "required": [
+    "subscription_id",
+    "status",
+    "confirmation_token",
+    "confirmation_url",
+    "expires_at",
+    "topics",
+    "acknowledgment"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedJul 17, 2026
- addedInput schema / properties / contact_email / format
```
Added value: +"email"
```
- addedInput schema / properties / contact_email / pattern
```
Added value: +"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
```

Changed9 schema fields changedJul 16, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / agent_id / description

Previous value: -"Optional caller-asserted agent identifier; recorded for attribution"New value: +"Optional agent identifier"

changedInput schema / properties / contact_email / description

Previous value: -"Email to subscribe — must be confirmed via the returned token before any updates send"New value: +"Email to subscribe — confirmed via returned token"

removedInput schema / properties / contact_email / format
```
Removed value: -"email"
```
addedInput schema / properties / contact_email / minLength
```
Added value: +1
```

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Idempotency key",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / slug / description

Previous value: -"business slug"New value: +"Business slug identifier"

changedInput schema / properties / topics / description

Previous value: -"Topic tags the user wants updates on (e.g., ['deals', 'schedule_changes', 'new_services'])"New value: +"Topic tags (e.g., ['deals', 'schedule_changes'])"

changedInput schema / required

Previous value: -[
-  "slug",
-  "contact_email",
-  "topics"
-]New value: +[
+  "slug",
+  "contact_email",
+  "topics",
+  "idempotency_key"
+]

Changed9 schema fields changedJul 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Optional agent identifier"New value: +"Optional caller-asserted agent identifier; recorded for attribution"

changedInput schema / properties / contact_email / description

Previous value: -"Email to subscribe — confirmed via returned token"New value: +"Email to subscribe — must be confirmed via the returned token before any updates send"

addedInput schema / properties / contact_email / format
```
Added value: +"email"
```
removedInput schema / properties / contact_email / minLength
```
Removed value: -1
```

removedInput schema / properties / idempotency_key

Removed value: -{
-  "description": "Idempotency key",
-  "minLength": 1,
-  "type": "string"
-}

changedInput schema / properties / slug / description

Previous value: -"Business slug identifier"New value: +"business slug"

changedInput schema / properties / topics / description

Previous value: -"Topic tags (e.g., ['deals', 'schedule_changes'])"New value: +"Topic tags the user wants updates on (e.g., ['deals', 'schedule_changes', 'new_services'])"

changedInput schema / required

Previous value: -[
-  "slug",
-  "contact_email",
-  "topics",
-  "idempotency_key"
-]New value: +[
+  "slug",
+  "contact_email",
+  "topics"
+]

Changed9 schema fields changedJul 12, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / agent_id / description

Previous value: -"Optional caller-asserted agent identifier; recorded for attribution"New value: +"Optional agent identifier"

changedInput schema / properties / contact_email / description

Previous value: -"Email to subscribe — must be confirmed via the returned token before any updates send"New value: +"Email to subscribe — confirmed via returned token"

removedInput schema / properties / contact_email / format
```
Removed value: -"email"
```
addedInput schema / properties / contact_email / minLength
```
Added value: +1
```

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Idempotency key",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / slug / description

Previous value: -"business slug"New value: +"Business slug identifier"

changedInput schema / properties / topics / description

Previous value: -"Topic tags the user wants updates on (e.g., ['deals', 'schedule_changes', 'new_services'])"New value: +"Topic tags (e.g., ['deals', 'schedule_changes'])"

changedInput schema / required

Previous value: -[
-  "slug",
-  "contact_email",
-  "topics"
-]New value: +[
+  "slug",
+  "contact_email",
+  "topics",
+  "idempotency_key"
+]

First observedMay 5, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (idempotentHint, mutating hints), the description discloses the full workflow: the subscription is pending until the user clicks a confirmation URL, the URL is user-exclusive, and it expires within 7 days. It also specifies what idempotency means in practice — reusing the key returns the original subscription. This is exactly the behavioral nuance an agent needs and cannot derive from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with zero waste: purpose first, then the confirmation workflow, then idempotency semantics. Every sentence carries load-bearing information, and the most decision-relevant facts (pending state, 7-day window, user-only click) are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for this tool's complexity. The output schema covers return values, annotations cover the mutating/idempotent profile, the schema documents all five parameters, and the description covers the workflow quirks (pending, expiry, confirmation). No critical gap remains for an agent to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds genuine semantics on top: it ties contact_email to the confirmation flow and, more importantly, explains that re-using idempotency_key returns the original subscription — a behavioral consequence absent from the schema's bare 'Idempotency key' label.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Start a pending email subscription to updates from a business.' This is unambiguous and clearly distinct from the sibling tools (booking, quoting, availability, payment), so an agent can identify what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by the purpose statement — this tool is for email subscriptions to business updates, which is outside the booking/quote/payment domain of the siblings. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named, so the agent must infer applicability.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdvocateMCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Subscribe to Updates

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources