Skip to main content
Glama
Sign In

Channel3 Shopping

by com.trychannel3
OverviewDiscussionsAdmin

Submit Product Review

submit_product_review

Post a star rating (1-5) and optional written review of a product on Channel3. Reviews are public and permanent: they cannot be edited or deleted. Call only when the user asks to post a review and has confirmed the rating and text you will send. Reviews are posted anonymously, shown as 'Anonymous user from MCP'. One review per product per 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": {
      "product_id": "<product_id>",
      "rating": "<rating>",
      "reviewer_type": "<reviewer_type>"
    },
    "name": "submit_product_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYesStar rating from 1 to 5.
thread_idNoConversation thread ID. Omit ONLY on the very first Channel3 call of a conversation. From then on, always pass the `thread_id` from the most recent Channel3 result, unchanged — even when the new call is a completely different product search.
product_idYesChannel3 product ID from a search_products or get_products result.
review_textNoOptional written review.
reviewer_typeYes`human` when the rating and text are the user's own, `agent` when they are your own assessment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: reviews are public and permanent, cannot be edited or deleted, are attributed anonymously as 'Anonymous user from MCP', and the result carries a thread_id that must be threaded through every later call. The only gap is the response shape beyond thread_id, which is modest since no output schema exists.

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?

Front-loaded with the action and its irreversible consequence, then the confirmation gate, then the thread_id obligation. Dense but every sentence carries operational weight; nothing is repeated or padding.

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?

For a mutation tool with permanent side effects and no output schema, the description covers the confirmation requirement, irreversibility, anonymity, rate limit, and the return value that matters. Nothing an agent needs before calling is missing.

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 schema already documents every parameter including rating bounds, reviewer_type enum values, and thread_id semantics. The description reinforces the thread_id rule emphatically and explains that reviewer_type distinguishes the user's own rating from the agent's assessment, adding marginal meaning over the schema.

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 and resource ('Post a star rating (1-5) and optional written review of a product on Channel3') and scopes it to a single product, which separates it from the sibling submit_feedback. An agent can identify the action 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 Guidelines5/5

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

Gives an explicit gating condition: 'Call only when the user asks to post a review and has confirmed the rating and text you will send', plus a frequency constraint ('One review per product per conversation'). Both the trigger and the preconditions are stated rather than inferred.

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