Skip to main content
Glama
Sign In

Channel3 Shopping

by com.trychannel3
OverviewDiscussionsAdmin

Unwatch Product

unwatch_product
DestructiveIdempotent

Stop a watch made with watch_product in this conversation. Pass the session_key from watch_product's result, or the watch can't be matched to this conversation. The result includes a thread_id. You MUST include it unchanged as the thread_id parameter on every subsequent Channel3 tool call in this conversation — including searches for new, unrelated products. Never omit it once you have one.

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": {
      "watch_id": "<watch_id>"
    },
    "name": "unwatch_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
harnessNoThe program you're running in: codex, claude-code, cursor (local CLI or IDE), cursor-cloud (Cursor cloud agent), grok-bot, copilot-cli, opencode, antigravity, openclaw (even when it runs your turns in Codex), hermes, chatgpt, or your program's name if it isn't listed
watch_idYesThe watch_id from watch_product or from an alert.
thread_idNoConversation thread ID from the most recent Channel3 result, unchanged.
session_keyNoThis conversation's session_key, from an earlier result (a secret token, or a handle such as claude-code#2). Keep it to this conversation; don't share or log it.
conversation_idNoYour own ID for this conversation, if your program gives you one. Cursor and Grok Bot: the output of `printenv CURSOR_CONVERSATION_ID`. Codex and Antigravity send it automatically; others leave it empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds important behavior beyond those annotations: the session_key matching requirement and the requirement to propagate the returned thread_id to every subsequent Channel3 call in the conversation.

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?

The description is front-loaded with the purpose and then explains the required session_key and thread_id context. It is appropriately sized for a tool with cross-call state, though the repeated emphasis on never omitting thread_id is slightly verbose.

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?

Given the mutation annotations, complete parameter schema, and absence of an output schema, the description provides enough context to invoke the tool correctly. It covers the critical conversation-matching and thread_id requirements, though it does not describe the exact effect of stopping the watch on future alerts.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by linking session_key to watch_product's result and explaining the ongoing thread_id propagation requirement, making parameter usage clearer than the schema alone.

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 states a specific verb and resource: stop a watch made with watch_product in this conversation. It clearly distinguishes the operation from watch_product, its direct sibling, so an agent can identify the tool 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?

The description gives clear usage context: use it to stop an existing watch created by watch_product in this conversation. It adds the prerequisite that session_key must come from watch_product's result or the watch cannot be matched, but it does not explicitly list exclusions or alternative tools.

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

All Channel3 Shopping toolsInspect
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.

Resources