Skip to main content
Glama

Subscribe or unsubscribe from Clera emails

setEmailSubscription
Idempotent

Turn one kind of Clera email on or off for the candidate, the same as the unsubscribe link in those emails. job_matches: the email with new roles that fit them. welcome_series: the welcome emails that help finish setting up the profile. Messages about a live introduction or interview are not covered here. To stop all contact, use setJobSearchStatus.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>",
      "subscribed": "<subscribed>"
    },
    "name": "setEmailSubscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
subscribedYestrue to receive these emails, false to stop them.

Output Schema

NameRequiredDescriptionDefault
channelYes
subscribedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, closed-world behavior, and the description adds value on top: it frames the effect as equivalent to an in-email unsubscribe link, scopes what it does not affect, and discloses that inputs/results are recorded for usage tracking and support. It does not say whether the change takes effect immediately or is reversible, which keeps it below a 5.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by compact enum glosses, then exclusions and the logging note. The closing privacy sentence is boilerplate but carries real disclosure value, so little is wasted.

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

Completeness4/5

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

With only two required parameters, an output schema present, and annotations covering safety and idempotency, the description supplies everything needed to call it correctly. The only gap is post-call behavior — whether the preference change is immediate and how it can be confirmed.

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 only 50% — the channel enum has no schema description — and the description compensates by defining each enum value ('job_matches: the email with new roles that fit them', 'welcome_series: the welcome emails...'). The boolean parameter is already documented in-schema, so no additional meaning is needed there.

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?

States a specific verb+resource ('Turn one kind of Clera email on or off') plus scope boundaries, and enumerates the two channels with a plain-language gloss of each. It explicitly separates itself from live introduction/interview messages and from setJobSearchStatus, so an agent can place it among siblings 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 Guidelines4/5

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

Gives an explicit exclusion ('Messages about a live introduction or interview are not covered here') and a named alternative with its condition ('To stop all contact, use setJobSearchStatus'). The positive trigger is only implied by the purpose sentence, so it stops just short of a full when/when-not/alternatives statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources