Skip to main content
Glama

Set contact topic

set_contact_topic
DestructiveIdempotent

Subscribe a contact to a topic, or unsubscribe them (e.g. "promotions" vs "order updates").

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": {
      "id": "<id>",
      "topic": "<topic>",
      "subscribed": "<subscribed>"
    },
    "name": "set_contact_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact id
topicYesTopic id (see list_topics)
sourceNoWhere the change came from, e.g. "preference_page". Default "api".
subscribedYestrue subscribes the contact to the topic, false unsubscribes them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subscribed / description
      Added value: +"true subscribes the contact to the topic, false unsubscribes them"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds the dual direction of the operation and topic examples, but does not explain consequences of unsubscribing (e.g. suppression of messages) or the default source behavior, leaving meaningful behavioral context unstated.

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?

A single, front-loaded sentence with an inline example. Every element earns its place and there is no unnecessary preamble.

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

Completeness3/5

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

For a toggle-style mutation tool with no output schema and strong annotations, the description is adequate but incomplete. It omits important context such as whether unsubscribing affects message deliverability or consent records, and does not mention the default source value or how to discover topic IDs (aside from the schema's reference to list_topics).

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented in the schema, including the meaning of subscribed=true/false. The description adds only an example of topic names, which is minimal beyond what the schema provides, so baseline 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: subscribe or unsubscribe a contact to a topic, with a concrete example of topics. It is clear what the tool does, though it doesn't explicitly distinguish itself from siblings like get_contact_topics or set_consent.

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?

The description implies usage by describing the subscribe/unsubscribe action, but it gives no explicit guidance on when to use this versus alternatives such as set_consent, add_to_list, or get_contact_topics for checking current state. An agent must infer the routing.

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.